When to Build It Yourself: A Founder's Lesson on Outsourcing the Wrong Thing

Every small business owner eventually faces the same fork in the road: you have a vision for something — a product, a system, a capability — that's bigger than what your team can build today. So you outsource it. You hire the agency, the offshore dev shop, the specialist contractor, and you hand over the thing you care about most, trusting that expertise plus a statement of work equals a finished result.

Sometimes it does. Often, it teaches you an expensive lesson about what should never have left your own four walls in the first place.

After 25 years building and running businesses in a technical field, I've learned that the outsourcing decision is one of the most consequential — and most misunderstood — calls a founder makes. Here's what I'd tell a younger version of myself.

Outsource capacity, not judgment

The cleanest way I've found to think about it: you can safely outsource capacity, but you should be very careful about outsourcing judgment.

Capacity is execution against a clear, well-understood specification — work where you already know exactly what "good" looks like and just need more hands to produce it. Judgment is the work where the requirements are still being discovered, where the thing being built is core to your competitive advantage, and where a hundred small decisions made along the way will determine whether the result is any good.

The mistake I made — and I see other founders make constantly — was handing an outside team something that was really judgment work and treating it like capacity work. I assumed a detailed brief would carry the intent. It didn't. The people doing the building didn't have the context, the domain instinct, or the stake in the outcome that the work required. What came back was technically "done" and substantively wrong, and the gap between those two only became visible once I was deep into it.

The warning signs I missed

In hindsight, the signals were there early. A few I'd tell any small business leader to watch for:

You can't clearly articulate what "done" means. If you can't write a specification precise enough that a stranger could execute it without you, the work isn't ready to outsource — it's still judgment work, and it needs to stay close to you until it isn't.

The vendor never pushes back. A team doing real thinking will ask hard questions and challenge your assumptions. A team that simply agrees to everything is often just building exactly what you said, which is not the same as building what you need.

You stop being able to evaluate progress. The moment you find yourself accepting status updates because you can't independently judge whether they're true, you've lost the thread. Outsourcing should extend your reach, not blind you.

What it cost — and what it was worth

Course-correcting wasn't cheap. Bringing critical work back in-house meant absorbing cost I'd hoped to avoid and rebuilding things I thought were finished. No founder enjoys that.

But the lesson reshaped how I run the business, and that's been worth more than the setback cost. I now draw a hard line between the work that defines us — which stays in-house, under people who own the outcome — and the work that supports us, which I'm happy to delegate to partners who are genuinely better at it than we are. That distinction has made every subsequent build faster, cleaner, and more defensible.

The takeaway for small business leaders

Outsourcing isn't good or bad. It's a tool, and like any tool it's powerful when matched to the right job and destructive when matched to the wrong one. The founders who get burned aren't the ones who outsource too much or too little — they're the ones who outsource the wrong category of work.

Before you hand something to an outside team, ask yourself one question: Is this capacity, or is this judgment? If it's capacity — execution against something you already understand cold — outsource it without guilt and free yourself to focus elsewhere. If it's judgment — the stuff that's core, ambiguous, and definitional to your business — keep it close, even when keeping it close is harder and slower and more expensive in the moment.

The expensive version of this lesson is learning it after the invoice. The cheap version is reading it in an article. Take the cheap one.