Questions People Ask Before Hiring Me
These are the real questions I get before someone decides to work with me — answered plainly, the way I’d answer them on a call. If yours isn’t here, tell me about your problem and I’ll answer it directly.
What do you actually do?
I’m a senior technical software consultant. People bring me the hard technical problems that turn on judgement rather than headcount: a build that’s stalled or over budget, a platform decision that’s expensive to undo, a system they’ve outgrown, a codebase they can’t tell is good or bad, or an investment they need checked before the money moves. I find the real problem — rarely the one in the brief — and tell them plainly what to do about it. Sometimes that’s advice, sometimes an audit, sometimes a lean build. It’s always direct access to one experienced person, not a team. The full range is on the services page.
How are you different from a software agency?
An agency gives you a team and a process to build and run software at scale. I give you one senior person’s judgement, directly. The difference matters most before anything gets built: an agency is the right shape when you know what you need and need it delivered and operated for years; I’m the right shape when the expensive question is what to build, or whether you should build at all.
Here’s the part most consultants can’t say honestly: I run an agency myself, Digital Royalty. So when your problem genuinely needs a team, I’ll tell you, and point you there — same standards, with the process behind it. Running both is exactly why I can be straight about which one you actually need. The longer version of that decision is consultant vs agency.
When should I hire you instead of just hiring a developer?
Hire a developer when you know what to build and you need it built. Hire me when the costly question is the decision, not the code. A developer builds what you ask for; I’m paid to tell you whether you should be asking for it. If you’re a non-technical founder spending real money and you can’t tell whether it’s spent well, or you’re about to commit to a build or a platform where the wrong call lands months later when it’s hard to undo, that’s exactly when one experienced person paid for their judgement is the cheapest insurance you’ll buy. If you want someone to take orders and write code without questioning the plan, I’m genuinely not your person — a contractor will serve you better.
How do engagements work?
It starts with a short conversation to find the real problem. From there it depends on what that problem turns out to be. Advisory and fractional work usually settles into a regular rhythm — a day or two a week, plus being reachable when a real decision lands between sessions. Audits and due diligence are scoped pieces of work with a clear deliverable: the truth about what you’ve built, in plain English you can act on. A rescue or a lean build is hands-on until it’s back on the rails or shipped.
What stays constant is that you deal with me directly, you get the reasoning and not just the answer, and I’ll tell you when the honest move is to do less than you walked in expecting to.
What does it cost?
It depends on the shape and length of the work, so I price it per engagement rather than publishing a rate card that would be wrong for most situations. What I can tell you is the principle: I’m worth hiring when the cost of the wrong decision is bigger than the cost of my time, and I’m not the right call if you’re chasing the cheapest possible quote. A fair number of engagements end with you spending less than you expected — not because I’m cheap, but because the honest answer was often “build a lean version and keep the cash” rather than “here’s a bigger project.” If budget is the deciding factor, tell me the budget and I’ll tell you straight whether there’s a version of the work that fits it.
Do you work in Portsmouth and London in person?
Yes. Portsmouth and London are my two hubs — that’s genuinely where I am, not a map pin. I work in person with south-coast and Hampshire founders and businesses, and with London startups and scaleups who want senior judgement without London agency overhead. Most of the work happens wherever the problem is, remote or on site, but proximity still counts when the stakes are high and you’d rather look someone in the eye. The Portsmouth and London pages cover the local picture.
Will you just build the thing I ask for?
Not without telling you whether you should build it the way you’re imagining — that’s the value. My bias is toward the smallest thing that solves the real problem and toward you owning your data and systems rather than renting them, because that’s what keeps you cheap and flexible later. If I think a proposed build is twice the size it needs to be, or that a tool you’re about to rent is something you should own, I’ll say so before a line of code gets written. If you’ve already decided to build and want it done lean and done to own, that’s exactly the MVP development work, and build or buy explains the thinking behind it.
How do I start?
Tell me about your problem. A short conversation is usually enough for me to tell you what you’re actually dealing with, and which shape of help fits — advisory, an audit, a lean build, or a team from the agency if that’s the honest answer. There’s no pitch at the end of it; you’ll get a straight read either way. If you’d rather get a sense of how I think before reaching out, the comparisons and playbooks are the honest version of how I’d approach your situation.