Why a US founder chose a Chinese dev team (and why he stayed for 2 years)

In the spring of 2024, a solo founder in Austin sent us a Calendly link with a one-line note: “My local agency just doubled their quote and pushed the timeline to October. Can we talk?”

He wasn’t looking forward to the call. He’d told us, on that first call, that hiring a Chinese dev team felt like it should be the obvious move on price — but every story he’d heard from other founders made it sound like a coin flip. Communication that fell apart at the first hard conversation. Code that “looked done” but didn’t work. Agencies that vanished after the deposit cleared. NDAs that turned out to be unenforceable.

He worked with us anyway. He’s still working with us, two years later. This post is the story of how we got past those fears — and what we changed about how we work to make sure no other client has to go through that calculus blind.

The three fears, named out loud

On our second call, before we’d written a single line of code, we did something most agencies don’t do: we asked him to list his fears, in order, and we promised to design our entire engagement around them.

His list was short and specific:

1. Communication will break down at the moment it matters most. The 12-hour time zone difference means when something is on fire at 3pm in Austin, our team is asleep. He’d heard horror stories of urgent messages sitting unread for 14 hours.

2. My IP will leak. He had no real way to verify that our engineers wouldn’t reuse his code, his designs, or his investor pitch in someone else’s product six months later. The legal infrastructure to enforce a US-Chinese contract felt theoretical at best.

3. You’ll take the deposit and ghost me. He’d seen this happen to a friend. The agency took 40% upfront, delivered increasingly thin updates for two months, and then stopped responding. The friend had no leverage and no recourse.

These weren’t unreasonable fears. We’d seen them play out for clients of other agencies many times. So we designed our engagement to make each one structurally hard to happen.

Fear 1: Communication will break

What he expected

Slack messages sitting unread overnight. Vague “we’re looking into it” responses. Daily standups at impossible hours. Engineers who kind-of spoke English but couldn’t carry a nuanced product conversation.

What we did

Loom-first, not Slack-first. Almost every meaningful update we send is a 3-to-7-minute Loom video. Loom forces the person sending it to be specific — you can’t ramble for seven minutes about nothing. And it’s async: he can watch it at 9am Austin time, regardless of when we recorded it. We send these every Friday and on every meaningful milestone.

Notion as a single source of truth. Every decision, every spec, every changelog lives in a Notion workspace he co-owns. There’s no “I asked you about this two weeks ago in Slack and now I can’t find it” because the answer is always in Notion under a clear page name.

A 4-hour response SLA on US business days. Any Slack message or email he sends gets a real response — not “got it, looking into it” but an actual answer or “I need until tomorrow morning to look into X, here’s why” — within 4 business hours US time. We staff our team to make this possible. It’s a structural choice, not a promise.

A real overlap window. Our team is online from 7am to 11am US Pacific. That’s the four-hour window where realtime conversation can happen if it needs to. Outside that window, he gets the async machinery above. He told us, around month three, that he felt more in the loop than he had with any of his three previous local engineers.

Fear 2: IP will leak

What he expected

Vague NDAs that “didn’t really mean anything across borders.” Engineers committing code to personal GitHub accounts. Code samples appearing on a recruiter’s portfolio later. Designs being lifted for a competing product.

What we did

Mutual NDA, signed before any code or specs change hands. We sent ours within 6 hours of his first email. Standard mutual format — protects both sides. He signed within a day.

His code, his repos, his cloud. Every line of code we wrote went into a GitHub organization he owned. We had collaborator access only. No mirrors, no internal copies. When a team member rotated off the project, their access was revoked the same day.

No code samples, ever. Our standard contract has a clause: we will never use any code, design, or product spec from his engagement in any portfolio, sales material, or other client work. We’ve turned down two prospective clients in the last year who specifically asked us to show them our work for him.

A 24-hour exit clause. This is the thing he tells other founders about most. The contract states explicitly: if he wants to terminate the engagement, we hand over everything in 24 hours — codebase access (he already has it), documentation, current sprint status, any credentials we hold. No “transition period,” no “we need to wrap up the current sprint.” 24 hours, full stop.

He’s never used the exit clause. But he told us, two years in, that the clause being there is what made him willing to start. We’d rather have a happy long-term client than a coerced one.

Fear 3: You’ll take the deposit and ghost me

What he expected

The classic story: 30% deposit, two weeks of enthusiastic communication, then progressively thinner updates as the calendar runs out, then silence.

What we did

Smaller payments, more milestones. Instead of one big upfront payment, we split into 30/30/40: 30% at kickoff, 30% at the midpoint demo, 40% on delivery. The midpoint demo is a real working product that does something useful — not slides, not mockups. If we couldn’t deliver that, he wouldn’t have to pay for it.

Public-by-default delivery. Every Friday demo went into a Notion page that listed exactly what we’d shipped, what was in flight, and what was blocked. He could see the trajectory week-over-week, and so could we. There was no opportunity for things to drift quietly.

A US-banked invoicing entity. This was a small thing that mattered more than we expected. He paid invoices to a US bank account from a US-incorporated entity — no international wire complications, no “did the money arrive” anxiety, clean accounting on his side. The actual engineering work happened in Beijing; the contractual and financial relationship was domestic for him. Less weird, less risky-feeling.

Live receipts of activity. He had read access to our project Linear board, our GitHub commit history, and our Notion workspace. He could see, every day, that work was happening. There was no “trust us, we’re working on it” — there was just the actual work, visible.

What surprised him

A few things he told us, around month six, that he hadn’t expected:

The async-first model made him a better operator

He’d expected to lose efficiency to async. The opposite happened. The discipline of writing things down, recording demos, and using Loom for updates spilled into how he ran the rest of his company. He told us he’d cut his internal meeting load by 60% within a year, partly because of patterns he’d picked up from working with us.

The cost difference was real but not the main thing

He’d budgeted us as roughly 50% of what a US shop would have charged. That math held up. But he told us, candidly, that the cost wasn’t why he stayed past the first project. He stayed because the actual collaboration was better than what he’d had with US engineers — more predictable, more transparent, less politicking. The cost difference was the bonus.

The cultural friction was lower than he expected

Almost all of his interactions were with engineers who’d worked with US clients for years and had internalized a direct-but-respectful communication style. He never had to decode hedging. He never had to read between cultural lines. When something was a bad idea, we said so. When something was a great idea, we said that too.

Two years later

He’s now three projects in with us. The first one shipped in 6 weeks and helped him close his seed round. The second was a major product expansion that took 4 months. The third is currently a long-term retainer where we run his entire backend team while he focuses on growth.

He’s referred us to four other founders, three of whom now work with us.

The fears were real. The structural answers worked.

---

If you’re a US founder weighing offshore vs. local, reach us on WhatsApp. We’ll show you the contract, the workflow, and the references — and we’ll be honest with you if we don’t think we’re the right fit.