How I Help You Decide Who to Hire
These pages resolve one decision: what shape of technical help your problem actually needs. A consultant, an agency, a full-time hire, a freelancer, a fractional CTO, a contractor — they are not interchangeable, and most people pick by what’s familiar or what a vendor talked them into rather than by what the problem requires. My job here is to give you a sharper version of that decision than you walked in with, including the cases where the honest answer is someone other than me.
That last part is the whole point of this section. A consultant who tells every reader “hire me” is a salesperson with a blog. I run an agency and sell my own time directly, so I have no incentive to force every problem into one box — I can tell you plainly when you need a team I’m not part of, a hire on your own payroll, or a cheaper pair of hands, because I’m not protecting a single product. That independence is what makes the steer worth reading.
Most people are comparing the wrong things
The mistake I see again and again is buyers comparing options on price and headcount when the real variable is something else entirely. They line up day rates and team sizes and pick the cheapest or the biggest, and they never ask the question that actually decides it: is this one hard call, or a standing need? A problem of judgement, or a problem of capacity? Something you want to own afterwards, or something you’re happy to rent?
Get those right and the choice usually makes itself. A single architecture decision that will shape the next three years is not a job for a junior contractor, however cheap — it’s worth one senior head for a fortnight. A sustained build that has to run for years is not a job for one consultant, however good — it’s a team’s work, and pretending otherwise sets you up to fail. The comparisons in this section are built around the variables that actually move the decision, not the ones that are easiest to put in a table.
The shape of the need decides the shape of the help
Here’s the frame I’d use. Strip the decision down to two questions and most of the noise falls away.
First: is this a decision or a delivery? A decision is one or a handful of hard calls — what to build, whether what you have will hold, what you’re really buying, how to get a stalled project moving. That’s judgement work, and judgement is what one senior person is for. Delivery is the sustained business of building and running software month after month — that’s capacity work, and capacity is what teams are for. Buying capacity to solve a judgement problem gets you five people building the wrong thing fast. Buying judgement to solve a capacity problem gets you one excellent person who can’t be in three places at once.
Second: how much do you want to own when it’s over? Some help leaves you with a system, a team, and the knowledge to run both. Some leaves you renting access to your own operation from whoever you hired. I weigh that on every one of these pages, because the cheapest engagement on day one is often the one that owns you by year two. The build-don’t-rent instinct that runs through everything I do applies to people and arrangements, not just software — borrowing senior judgement to make your own team better is leverage; renting a dependency you can never bring in-house is a slow tax.
Where I fit, and where I honestly don’t
I’m one senior consultant with direct access — no account manager, no juniors on your budget, no layers. For a hard problem that needs experienced judgement made right, that’s the sharpest tool there is. But it’s also a ceiling, and I’d rather name it than sell past it. I can own the architecture, the rescue, the due diligence, the standing advisory. I cannot be a delivery team with redundancy, on-call cover, and a process behind it. When that’s what you need, the right answer is my agency, Digital Royalty, and several of these pages exist partly to get you there. Sending you to the agency when the agency is right isn’t a loss — it’s the same honesty that makes the steer toward me worth trusting.
What’s in this section
- Consultant vs agency — the big one: when one senior person is enough, and when you genuinely need a team and a process behind the work. The honest hand-off to my agency lives here.
- Fractional CTO vs consultant — a standing part-time leadership role versus a sharp one-off engagement. Mostly a question of whether the need is ongoing or finite.
- Fractional CTO vs full-time CTO — for the founder weighing a part-time senior leader against a six-figure full-time hire, and usually buying more seniority than the role can keep busy.
- Freelancer vs agency — cheap flexible hands versus accountable managed delivery, and how to tell which your project actually needs.
- Consultant vs in-house — borrowing senior judgement versus building the capability on your own payroll, and what you’re left holding either way.
- Technical advisor vs contractor — the difference between someone who decides what should be built and someone who builds it, and why you usually need to be clear which one you’re hiring.
- Independent consultant vs dev shop — senior judgement on tap versus production capacity, and the trap of buying a factory when you needed an architect.
- When to hire a consultant — the actual trigger conditions, so you bring me in when it pays and don’t when it doesn’t.
- How to evaluate a developer — how to tell a genuinely good engineer from a confident one when you can’t read the code yourself.
Once you know the shape
A comparison tells you which kind of help you need; the services pages describe what working with me on each one actually looks like. If you’ve narrowed it to a senior individual, start there. And if you want to see the kinds of problems I actually solve rather than the shape of the engagement, the expertise pages cover the specialisms I’m hired for. If you’re still not sure which side of a decision you’re on, that’s exactly the conversation worth having.
Tell me about your problem and I’ll tell you straight which one you need — including when it’s the agency and not me. (Back to the homepage.)