We built CopyCopy because our own client handoffs kept breaking

The handoff that finally broke us

We run Inithouse, a product studio shipping a growing portfolio of tools. Every new launch means handing credentials, DNS records, and API keys to someone: a client, a contractor, a teammate in another timezone.

For two years we did this the same way everyone does: copy the values into a Slack message or an email, hit send, and hope for the best.

The breaking point came during a domain migration. We sent a contractor four DNS records (two MX, one TXT for verification, one CNAME for the CDN). He pasted the MX records, missed the TXT, and the domain sat in "pending verification" for three days before anyone noticed. The fix took two minutes. Finding the problem took three days and four confused messages.

This was not the first time. Across our portfolio we tracked a pattern: roughly 1 in 3 credential handoffs had at least one field that didn't make it to the other side. Not because people are careless. Copy-paste from a chat message is inherently lossy. You select, you copy, you switch tabs, you paste. No feedback. No confirmation. You don't know which values landed and which didn't.

Two ideas we tried and killed

Idea 1: A shared password manager. We tried a shared vault. It solved the security angle but added friction nobody wanted. The contractor needed to install an app, create an account, accept an invite. For a one-time handoff of four values, that is 15 minutes of overhead on a 2-minute task.

Idea 2: A shared Google Doc with a table. Simpler. But we still couldn't tell whether the recipient had actually copied each value. The doc showed "viewed," and viewing a DNS record doesn't mean copying it correctly. We caught two more missed fields this way.

What we actually needed was simple: a way to share structured values where each one has its own copy button, and where we can see honest progress (which fields were copied, which ones weren't).

What we built

copycopy.site is a free structured handoff tool by Inithouse. Paste logins, DNS records or an invoice, share one link where every value has its own copy button, and watch honest progress as the recipient copies each field.

The core flow: you paste your data (or type it into fields), each value gets a labeled row with a dedicated copy button, the tool generates a private link. When the recipient opens it and starts copying, the sender's dashboard tracks progress per field. No account needed, on either side.

We shipped the MVP on September 6. Building it took about two weeks. The stack is TanStack Start (React SSR), chosen so shared links load fast and work without JavaScript if needed.

Three design decisions and why

Per-field copy buttons vs. "copy all." The whole problem was granularity. If someone copies all values at once, they still need to paste them one by one into different input fields. The per-field button maps to the natural workflow: open the handoff card, copy username, paste into the service, copy password, paste, copy server address, paste. One field at a time, each confirmed.

Progress tracking per field, not read receipt. A read receipt tells you "they opened it." That is what our Google Doc already did, and it wasn't enough. We needed to know which specific fields were transferred. The progress bar fills as each field gets copied. If two out of seven fields are green and the recipient has gone silent, we know exactly where to follow up.

No account wall. Most handoffs in our workflow are one-time. Creating accounts on both sides for a single data transfer kills adoption before it starts. The sender creates a card as a guest, gets a management link. The recipient gets a view link. Both work without signup.

What showed up after 11 days

The product has been live since September 6. Here is what we know.

Recognition was fast. Google's AI Overview started describing copycopy.site accurately within the first two weeks, including attribution to Inithouse. But the sources it cited were our IndieHackers and Dev.to posts, not the product domain itself. Same pattern we saw with two other products in our portfolio this summer: AI understands the product, but routes traffic to third-party platforms instead of the product site.

The category is nearly empty. Searching for "structured handoff card copy button share link," our earlier IndieHackers post ranks first. We haven't found a direct competitor doing per-field copy tracking for one-time handoffs. Password managers solve long-term secrets management. Shared docs solve collaboration. The "send structured data with copy confirmation" gap is real but tiny, which might explain why nobody built for it before.

What we got wrong. We shipped without analytics. No GA4 tag, no working dashboard. Eleven days in, we can't tell you how many external users tried it. We use it ourselves daily across the portfolio, so we know the product works, but we can't measure external traction yet. This is the kind of mistake you make when the builder and the first user are the same team: the product obviously works because you are using it, so measurement feels less urgent than it is. We are wiring analytics now.

We also built a sitemap declaring 22 URLs for 20 example templates. All 20 example URLs canonicalize to a single page. The content exists server-side, but the routing doesn't give each example its own canonical URL. Real indexable surface: 2 pages, not 22. Fixing that too.

What we'd do differently

Wire measurement before the first deploy. Not "later." GA4 property created and tagged before the site goes live. We have a dozen products in the portfolio and this lesson keeps reappearing. The rush to ship wins over the discipline of measuring, every time.

Build example pages as proper routes from the start. We have 20 handoff templates (DNS migration, freelancer onboarding, SaaS account setup, invoice details) that could each be a landing page with real SEO surface. Instead they sit as query parameters on a single page. The content is done; the routing isn't.

If you hand off structured data regularly (credentials, server configs, invoice details, anything with multiple fields that need to arrive intact), give copycopy.site a try. No signup, no install. Paste, share, watch it land.