Ask an agency owner about a subcontractor who burned them, and you’ll almost never hear “the code was bad.” You’ll hear “he went dark two days before launch.” Or “he missed the deadline and I found out from the client.” Or, worst of all, “he emailed my client directly.”
The technical risk in outsourcing is real, but it’s manageable — you can review code, you can test. The relationship risk is the one that quietly ends agencies, and most people underprice it.
Why it’s the expensive one
Your client never sees the subcontractor. They see you. So a missed deadline isn’t the developer’s missed deadline — it’s yours. A dev who contacts your client directly doesn’t just overstep; he makes you look like you can’t control your own supply chain. And trust with a client works the way it always does: it builds slowly, over months of things going right, and it breaks in a single afternoon.
That asymmetry is the whole problem. The upside of a good subcontractor is spread over a year. The downside of a bad one arrives all at once, aimed at the relationship you spent the most to build.
“Just find someone trustworthy” isn’t a plan
Trust is a feeling, and feelings don’t survive a bad month. The developer you trusted in March is the same one who goes quiet in June when he’s overcommitted to someone else. Character helps, but it’s not a control. What actually protects you is structure — the arrangement set up so that the bad outcomes are difficult, not just unlikely.
The structure that makes it hard, not just unlikely
- Everything through you. The developer has no channel to your client. No shared Slack, no CC on the email, no “quick call to clarify.” If there’s no path, there’s no going around you.
- NDA and IP assignment in writing, before the brief. If it ever ends badly, the confidentiality and the code are already yours. You’re not negotiating from a bad position after the fact.
- A capacity answer up front. The best defence against a missed deadline is a developer who says “not this month” instead of overcommitting. Someone who treats being full as a fact to tell you, not a weakness to hide, is someone who won’t blow up your launch to protect their pipeline.
- One person who owns it. The more hands and handoffs, the more places the work can go quiet without anyone noticing until it’s late.
You can’t outsource the relationship — so protect it
The client relationship is the thing you can never hand off; it’s the actual product. What you can do is make sure the person doing the work has no way to touch it. That’s not distrust. It’s just doing white-label properly — the arrangement built so that the developer’s job is the code, and yours stays yours.
That’s how I work, on every brief: all communication through you, my name nowhere in the deliverables or the metadata, and the NDA and work-for-hire signed before the work starts. The specifics — and the contracts themselves — are on my How I work page. If you’ve been burned before and want to see the four commitments that answer it directly, they’re on the home page. And when you’re ready, just send me a brief.