Skip to content

Consultant vs In-House: Borrow the Judgement or Build the Capability

Borrow it from a consultant when you need senior expertise occasionally or once; build it in-house when you need it constantly and forever. That’s the whole decision, and it turns on a single question: is this capability something your business runs on every day, or something you need at specific moments and then not again? You don’t put a rarely-used skill on permanent payroll, and you don’t rent the thing your company is fundamentally built on. Match the arrangement to how often you actually need the capability.

The instinct that gets this right is the same one I apply to software: own the thing that’s core to you, borrow the rest. Here’s how that plays out with people.

What you’re really weighing

Strip away the org-chart thinking and this is a make-or-buy decision applied to expertise. Every capability your business touches sits somewhere on a line from “central to everything we do” to “needed now and then.” Where it sits tells you whether to own it or borrow it.

Borrowing from a consultant gives you senior judgement on demand — someone who’s done this many times, brought in for the specific need, paid only while you need them, gone when you don’t. No salary between engagements, no managing a permanent hire, no pretending there’s enough of this work to fill a full-time role. The cost is that the expertise leaves with the person; you rented the answer, you didn’t keep the capability.

Building in-house gives you capability you own — the knowledge lives in your team, available all the time, deepening with every project, accountable to you day to day. The cost is real and permanent: salary, management, the slow build of someone learning your business, and the awkward truth that if the need turns out to be intermittent you’re paying full-time for part-time value.

So the question is honest and simple: how often do you actually need this, and is it core enough to be worth owning?

When a consultant is the right call

Borrow it when the need is occasional, finite, or specialised:

  • You need it once or rarely — a one-off architecture decision, a due diligence before an acquisition, a project rescue. There’s no permanent role here, just a moment.
  • The expertise is too senior or too specialised to keep busy full-time. A world-class head on your particular problem for a fortnight, not a salaried generalist for a year.
  • You need an outside view precisely because it’s outside — someone with no internal politics, no sunk cost in the current approach, free to tell you the uncomfortable thing your own people can’t or won’t.
  • You need it now and can’t wait three months to hire, onboard, and hope the hire was right.

For any of those, building in-house is the wrong shape. You’d be hiring a permanent role to meet an occasional need, paying year-round for something you use twice. Borrow the judgement, apply it, move on — and ideally have the consultant transfer enough of it that your own people are better for it afterwards. The best version of borrowing leaves capability behind.

When in-house is the right call

Build it in-house when the need is constant, core, and worth owning:

  • You need this capability every day — it’s not an occasional call, it’s the daily running of your business.
  • It’s central to what you do. Your competitive edge, the system everything depends on, the thing you cannot afford to not deeply understand. You don’t outsource your core.
  • You need the knowledge to stay — to accumulate, to live in your team, to be there next year and the year after, not walk out the door when an engagement ends.
  • There’s genuinely enough of this work to justify and fill a permanent role.

When that’s the shape, leaning on a consultant indefinitely is the false economy — and I’d say so. Renting your core capability forever means never owning the thing your business most depends on, paying in perpetuity for access to expertise that should live inside your walls, and staying permanently dependent on someone who can leave. That’s renting your own foundation. If a capability is central and constant, own it.

How the two actually work together

The framing as a versus is a little false, and the best outcomes use both. The sharpest play is usually: borrow the senior judgement to make the big call and set the direction, then build the in-house capability to run it day to day. I make the architecture decision and hand your team a foundation they own and understand, rather than them either flailing without senior input or staying dependent on me forever.

That’s the worldview again — own what’s core, borrow what’s occasional, and use the borrowed expertise to make what you own better rather than to replace owning it. A consultant who makes you more dependent on consultants has done it wrong. A good one leaves your in-house capability stronger than they found it. What you’re left holding after the engagement ends is the whole point.

Who this isn’t for

If you’re trying to decide between a part-time senior leader and a full-time one rather than between borrowing and building, that’s a different cut — see fractional CTO vs full-time. And if the need is delivery capacity at scale rather than a judgement call or a permanent skill, neither borrowing one consultant nor making one hire is the answer — that’s a team.

How I’d decide it

Ask how often you need it and how core it is. Occasional or one-off, however senior? Borrow it — bring in a consultant, get the call made right, keep the capability transfer. Constant and central to your business? Build it in-house and own it, because renting your foundation forever is the slow expensive mistake.

If you’re not sure whether a need is a one-off or a permanent gap, tell me about it — and if the answer is “borrow now, build later,” I’ll usually tell you exactly what to hand your own team so you’re not dependent on me a year from now. The comparisons index frames how this borrow-or-build call relates to the other shapes of help.