Skip to content

What I Take On — and Where I Send You Instead

I take on the technical problems that need one senior person who’s done it before — not a team, and not a tool. Advisory when you need a direction you can trust, audits when you need the truth about what you’ve built, due diligence before you spend real money, and hands-on rescue or a lean MVP when something has to get done properly. If what you actually need is an ongoing team to build and run software at scale, I’ll tell you, and point you at my agency.

That last sentence is the whole reason this page reads differently from an agency’s. I’m one person. That’s the offer and the limit, and being straight about both is what makes the rest of it worth trusting.

The work is judgement, not headcount

Most problems people bring me aren’t a shortage of hands. They’re a shortage of the right call. A team of five building the wrong thing quickly is worse off than one person who tells you what to build before you spend the money. The expensive mistakes I get called in on are almost never “we didn’t have enough developers” — they’re a rebuild that wasn’t needed, a platform you’re now locked into, an MVP that cost six figures because nobody scoped it down.

So most of what I sell is decisions you can act on. That’s deliberate. The leverage in software isn’t typing faster; it’s not building the wrong thing in the first place.

I’d rather you build less and own more

The default advice in this industry is to spend: buy the platform, hire the team, rent the SaaS, add the headcount. My default is the opposite. What’s the smallest thing you could own that solves the real problem, and how fast can you have it?

Own your data and your systems and every later move gets cheaper — you can connect them, automate across them, and extend them on your terms instead of paying rent for limited access to your own operation. A fair number of engagements with me end with you spending less than you walked in expecting to, because the honest answer was “build a lean version and keep the cash,” not “here’s a bigger project.” If you want the full version of that argument, it’s in build or buy.

The real problem is rarely the stated one

“We need a CRM” is usually “our data is scattered and nobody trusts the numbers.” “The app is slow” is usually three decisions made badly eighteen months ago. The first thing I do on any engagement is find the actual problem, because solving the stated one is the most common way I see people waste money. A clear diagnosis is worth more than a fast build, and it’s most of what the advisory and audit work below is really for.

Where I stop and the agency starts

Direct access to one senior person is the point — no layers, no account manager, no juniors learning on your budget. But it also means that when the honest answer is “you need a standing team building and running this for years,” I’m the wrong shape, and selling you otherwise would be selling you the wrong thing.

That’s what Digital Royalty is for — my agency, same standards, with the team and the process behind it. The fact that I run it is exactly why I can tell you honestly which side of the line your problem sits on. If you’re weighing those two routes, consultant vs agency is the honest version of that decision.

What’s in here

  • Fractional CTO — senior technical leadership a day or two a week, for founders who need the calls made right without a full-time hire.
  • Technical advisory — a direction you can trust on a specific decision, without bringing anyone in-house.
  • Architecture review — an honest read on whether what you’ve built will hold, and what to do about it if it won’t.
  • Software audit — the truth about the state of your codebase, in plain English a non-technical owner can act on.
  • Security audit — where you’re exposed and what actually matters to fix first.
  • Technology due diligence — for investors and acquirers who need to know what they’re really buying before the money moves.
  • Project rescue — for the build that’s stalled, over budget, or quietly on fire, when you need someone to get it back on the rails.
  • Legacy software modernisation — keeping critical old systems alive, or moving off them without breaking the business.
  • MVP development — the lean first version, built fast and built to own, when the answer is “build it.”
  • AI consultancy — a straight read on where AI actually helps your business and where it’s a distraction.
  • CTO coaching — for the technical leader who wants someone senior to think out loud with.
  • Interim CTO — holding the technical reins through a gap, a transition, or a crisis.

Who this isn’t for

If you want the cheapest possible quote, or someone to take orders and write code without questioning the plan, I’m not your person — and you’ll get more from a contractor who will. I’m worth hiring when the cost of the wrong decision is bigger than the cost of my time.

Start here

If you roughly know which engagement fits, the expertise pages show the kinds of problems I actually solve and the tools I solve them with. If you don’t, that’s fine — tell me about your problem and I’ll tell you which of these it is, or whether it’s one for the agency instead. Either way you’ll get a straight answer. (Back to the homepage.)