Skip to content

Technical Advisory

Technical advisory is me giving you a straight answer on a specific technical decision — build or buy, this stack or that, rebuild or repair, hire or outsource — before you commit money to it. No team to bring in, no platform to adopt. Just the judgement of someone who’s made these calls and seen how they land, applied to yours while it’s still cheap to change course.

What this is

This is advice you can act on, scoped to a decision rather than a project. You bring me the question — the quote that feels too big, the architecture your developers are proposing, the SaaS contract you’re about to sign for three years, the rebuild someone’s pushing for — and I tell you what I’d do and why, in plain English, with the reasoning laid out so you can weigh it yourself.

It’s deliberately not delivery. I don’t write the code or run the build here; I tell you whether the build is the right one and where it’ll bite you. Sometimes that’s a single conversation that saves you a six-figure mistake. Sometimes it’s a short engagement to work a thornier decision properly — map the options, kill the bad ones, and leave you with a call you can defend to your board.

The point of difference is that I have no product to sell you. A vendor’s “advice” points at their platform. A contractor’s advice points at more billable hours. Mine points at the cheapest thing that solves your actual problem — which is usually less than you walked in expecting to spend.

When you need this

You need this when a decision is about to get expensive and you don’t have anyone whose technical judgement you fully trust to make it. A few recognisable versions of that:

  • You’ve been quoted a large sum for a build and you can’t tell if it’s fair, padded, or solving the wrong problem.
  • Your team wants to adopt a platform, a framework, or an architecture, and you need someone independent to pressure-test it before you’re locked in.
  • You’re choosing between building something and renting it, and the SaaS bill stretches out for years.
  • An external agency or contractor is telling you something and you’ve no way to know if it’s true.

The thread is that the cost of the decision lands later, when it’s hard to undo. Advice is cheapest exactly then — before the money’s spent, not after.

How working with me goes

I start by finding the real question, because the one you ask is often a layer above the one that matters. “Should we build a CRM?” is usually “why don’t we trust our own numbers?” — and that changes the answer. So the first thing I do is make sure we’re solving the right problem.

Then it’s direct and fast. You give me the context — the quotes, the plans, the constraints, the thing that doesn’t smell right — and I come back with a clear recommendation and the reasoning behind it, not a deck and not a maybe. I’ll tell you when a proposed build is twice the size it needs to be, when something you’re about to rent is something you should own, and when the honest move is to do nothing yet. My bias is toward simplicity and toward you owning your data and systems, because that’s what keeps every later decision cheap. You walk out able to act, not with a document you have to interpret.

What you walk away with

  • A clear recommendation on the decision in front of you, with the reasoning — not a hedge.
  • The expensive option killed before you committed to it: the oversized build, the lock-in contract, the rebuild you didn’t need.
  • A view of what to own versus what to rent, so your costs compound in your favour rather than as monthly rent.
  • Enough understanding of why to defend the call to a co-founder, a board, or an investor.

Who this isn’t for

If you’ve already decided and you want someone to validate it, this isn’t that — I’ll tell you what I actually think, which sometimes isn’t what you hoped. Advice is only worth paying for if you’re open to acting on it.

When you need a team instead

If the honest answer to your decision is “yes, build it, and you’ll need a team to build and run it for years,” advisory has done its job and the next thing you need is delivery. That’s my agency, Digital Royalty — the same standards with the team and process to build at scale. A clean split works well: I make the call and define the brief, the agency executes it. Because I run both, I can tell you honestly which side of that line your decision sits on.

Talk to me

If there’s a technical decision in front of you and you’re not sure it’s the right one, that’s exactly what this is for. Tell me about it — a short conversation is often enough for me to tell you what I’d do. If the decision is really about whether something will hold up, an architecture review digs deeper; if you suspect what you’ve already built is the problem, a software audit gives you the truth; and if the decision is broader than one call, the other ways I help cover the rest. If you’re weighing advice against hiring delivery, build vs buy is the framework I’d hand you.