Consultant vs Agency: When One Person Is Enough, and When You Need a Team
If your problem is a handful of hard calls — what to build, whether what you’ve got will hold, why a project has stalled, what you’re really buying — one senior consultant is enough, and a whole agency is overkill you’ll pay for. If your problem is building and running software for months or years, one consultant is not enough no matter how good they are, and you need an agency with a team and a process behind it. The deciding question isn’t quality or budget. It’s whether you’re buying a decision or buying delivery.
I can say that without hedging because I’m on both sides of it. I sell my own time as a consultant, and I run an agency, Digital Royalty. So I have no reason to talk a delivery problem into a solo engagement that will fail, or a single decision into a retainer you don’t need. Here’s how I’d actually split it.
What you’re really choosing between
People frame this as “individual or company,” as if it’s about size or price. That’s the wrong axis. The real difference is what each one is.
A consultant — me — is concentrated senior judgement with direct access. No account manager, no juniors learning on your budget, no layers between you and the person doing the thinking. You get one experienced head, fast, on the specific call that matters. The strength is depth and directness. The limit is that it’s one head: I can’t be in three places at once, I don’t carry redundancy, and I am not a team.
An agency is a system for delivering work at scale over time. The value isn’t any single person — it’s the team, the process, the redundancy, the project management, the fact that when one person is off the work doesn’t stop. The strength is sustained, accountable delivery. The cost is that it’s heavier and pricier than one person, and rightly so, because it’s doing a fundamentally bigger job.
So the question is never “who’s better.” A scalpel isn’t better than a kitchen; they do different jobs. The question is which job you actually have.
When a consultant is enough
Bring in one senior person when the problem is finite and turns on judgement:
- You need to know whether your architecture will survive the next two years of growth — and what to do if it won’t.
- A build has stalled, blown its budget, or quietly caught fire, and you need someone to diagnose it and get it back on the rails.
- You’re about to spend real money acquiring or investing in a company and you need to know what you’re really buying, technically.
- You need a direction you can trust on a specific decision — build or buy, this stack or that, rebuild or modernise — without bringing anyone in-house.
- You want senior leadership a day or two a week to make the big calls right, without a full-time hire.
What these share: the value is in getting the call right, and one experienced person can get it right. Throwing a team at any of them wouldn’t make the answer better — it would just cost more and add coordination overhead to a problem that didn’t need coordinating. This is most of what I take on, and it’s where one person genuinely beats a company.
When you need an agency
Now the honest other side, and on this page it’s the more important one. You need a team and a process — not me alone — when the problem is sustained delivery:
- You need a real piece of software built, properly, over months — not advised on, built.
- You need it then run: maintained, supported, kept secure and online, evolved as the business changes.
- The work is bigger than any one person can hold, or it has to keep moving whether or not a single individual is available that week.
- You need accountability that survives a person being ill, on holiday, or moving on — redundancy, cover, a process that doesn’t live in one head.
- It has to scale: more features, more users, more integrations, more team, over a real timeframe.
If that’s you, hiring a lone consultant is a mistake, and a good one will tell you so. One person building and running a serious system is a single point of failure with no cover and no slack — fine for a fortnight, dangerous for a year. The moment the work outgrows what one head can carry, you don’t need a more brilliant individual. You need a team built to carry it.
Where I send you, and why it’s not a loss
When the honest answer is “you need a team,” I send you to Digital Royalty. That’s my agency — same standards I’d apply myself, with the team, the process, and the accountability that one person structurally cannot provide. Built to take a real system from nothing to live and keep it running.
I want to be precise about why this isn’t me losing the work or fobbing you off. I’m not badmouthing agencies to win solo engagements and then quietly running one. The distinction is shape of need, not quality. One hard problem that turns on judgement → me, directly, no layers. Sustained build-and-run at scale → the agency, because that’s the job a team does and a soloist can’t. Selling you the wrong shape — talking a delivery problem into a solo retainer because I’d rather keep your money than route it next door — would be exactly the dishonesty this whole site exists to avoid.
And the fact that I run the agency is the credibility, not a conflict. Most solo consultants can’t hand you a team when you outgrow them; they either oversell their own capacity or vanish. Most agencies can’t put one named senior person in front of you who’ll tell you when you don’t need the agency. I can do both, which means I can tell you the truth about which side of this line your problem sits on. If you want the relationship between the two spelled out, the agency page covers it.
The mistake that costs the most
The expensive error here is buying scale before you need it. A pre-product founder with one hard architecture decision signs a six-month agency retainer because “we’ll need the team eventually” — and burns months of runway on capacity they won’t use for a year, when a fortnight of senior judgement was the actual job. The mirror image is just as costly: a company with a year of real delivery ahead hires one freelancer to save money, and twelve months later they’ve got a fragile system only that one person understands, no cover, and a rebuild on the horizon.
Match the shape to the need now, not to where you imagine you’ll be. You can always escalate from a consultant to an agency when the work grows into it — in fact that’s the clean path, because the judgement work I’d do first is exactly what makes the later build cheaper and less risky. Buying the team before there’s team-sized work is how you set money on fire early.
Who this comparison isn’t for
If you already know you need ongoing delivery at scale, you don’t need to weigh “consultant vs agency” at all — skip me and go straight to the agency. And if you want the cheapest possible pair of hands to execute a spec you’ve fully worked out yourself, neither a consultant nor an agency is your best value — that’s a freelancer or contractor question.
How I’d decide it
Ask one thing: when this engagement ends, what did you need from it — a decision made right, or a system built and running? If it’s the decision, hire one senior person and keep it lean; that’s me, and it’s when hiring a consultant pays. If it’s the system, hire the team that’s built to deliver and stand behind it.
Not sure which one you’ve got? That’s the most common place to be, and it’s a short conversation. Tell me about your problem and I’ll tell you straight which side of this line you’re on — if it’s a team you need, I’ll point you at Digital Royalty and you’ll have lost nothing but the uncertainty. If you’re weighing a few of these shapes at once, the comparisons index lays out how the whole set of choices fits together.