Independent Consultant vs Dev Shop: Judgement or Capacity
An independent consultant sells senior judgement; a dev shop sells production capacity. If your problem is deciding what to build, whether it’ll hold, or why it broke, you want one senior independent head, and a dev shop is the wrong tool — you’d be buying a production line to answer a question. If your problem is building a defined thing that needs more hands than you have, you want a shop’s capacity, and a lone consultant can’t supply it. The deciding question is whether you’re short on the right decision or short on the right output. They solve opposite shortages.
I’m the independent-consultant side of this, so let me be careful to argue the shop’s side honestly too — because for a real class of problems the shop is exactly what you should buy.
What each one actually sells
An independent consultant is concentrated seniority, sold direct. You get one experienced person — often the most experienced person you’ll work with on the problem — with no layers, no account manager, no juniors billing against your project. The product is judgement: the right call, made by someone who’s made it before. The strength is depth and directness. The limit is throughput: one person can think hard about your hardest problem, but one person cannot be a production line.
A dev shop is a managed delivery machine. The product is capacity and coordination — a team, project management, the ability to build a substantial defined thing over time with the work spread across people. The strength is output and the process around it. The catch, and it’s a real one, is what sits between you and the senior talent: a sales pitch led by their best people, work often done by their most junior, an account manager translating in both directions, and your project competing for attention with everyone else’s. Not every shop is like that, but enough are that you should go in knowing it.
So this isn’t “individual vs company” as a matter of scale. It’s judgement sold direct against capacity sold through a layer. Which you want depends entirely on which you’re short of.
When an independent consultant is right
Go independent when you need the call, not the output:
- The problem is fundamentally a decision: what to build, which architecture, build or buy, why this stalled, what this codebase is really worth.
- You want direct access to genuine seniority with nothing in between — the person you’re talking to is the person doing the thinking.
- The work is depth, not volume. One hard problem thought through properly beats a team producing the wrong thing at speed.
- You value candour. An independent has no bench to keep billable and no incentive to scope the engagement bigger than it needs to be — which makes it far easier to tell you the honest, smaller answer.
For any of those, a dev shop is overkill pointed at the wrong target. You’d be buying production capacity to resolve a question that capacity doesn’t resolve. Worse, a shop has a structural reason to find you a build — that’s what it sells — when the honest answer might be “you don’t need to build much at all.” That’s most of what I do: the senior call, direct, sized to the real problem.
When a dev shop is right
Go to a dev shop when you need output at a scale one person can’t supply:
- You know what you want built, it’s substantial, and it genuinely needs more hands than you have — the bottleneck is capacity, not the decision.
- You need managed delivery: a team, a process, project management, the work coordinated across people so it keeps moving.
- The job is sustained production over time, not a single sharp judgement call.
- You don’t have the in-house capacity to build it and don’t want to hire a permanent team for what might be a defined piece of work.
When that’s the shape, a lone consultant is the wrong answer and I’d say so. One person is a throughput ceiling and a single point of failure for real build volume — fine for the decision, hopeless as the factory. If you need a defined thing built at scale, you need a team built to build it.
But notice the trap, because it’s where money dies: buying the factory before you’ve made the decision. People go straight to a dev shop, get sold a six-month build, and never had the senior, independent judgement check whether that was the right thing to build at all — because the shop selling the build is the last party with an incentive to tell them it isn’t. So they build capably in the wrong direction and pay for the privilege twice.
Where I’d send you instead — and why I can
When the honest answer is “you need real delivery capacity with a team and a process,” my own recommendation is Digital Royalty — my agency, built precisely for managed delivery at scale, to the standards I’d hold myself. I can make that hand-off cleanly because I’m independent: I make the decision direct, with no bench to feed, and when the answer is genuinely “this needs a team to build,” I route you to one rather than stretching a solo engagement past what one person should carry. The independent consultant and the delivery team aren’t rivals here — they’re two rungs, and the clean path is the judgement first, the capacity second, so the building is pointed the right way before anyone’s hands touch a keyboard. If you want that split spelled out fully, it’s consultant vs agency.
Who this isn’t for
If you just need a single contained piece built and can specify and manage it yourself, you don’t need a whole shop or a consultant — a freelancer is your best value. And if your need is ongoing technical leadership rather than either a decision or a build, that’s a fractional CTO.
How I’d decide it
Name your actual shortage. Short of the right decision — what to build, whether it holds, what it’s worth? Buy judgement: one senior independent head, direct, no layers. Short of output — a defined, substantial thing that needs a team to build? Buy capacity, and buy it from a team built to deliver and stand behind it. Just don’t buy the factory before the decision’s been made independently, because that’s the most expensive order to get backwards.
Not sure whether you’re short on the decision or the delivery? Tell me about it — I’ll make the call with you direct, and if it turns out you need the team, I’ll point you straight at the agency. For how this choice sits among the other hiring-shape decisions, the comparisons index lays out the full set.