What I’ve Built and Rescued
My track record is best read as a set of recurring problems I’m brought in on, not a list of logos. I build lean systems that businesses end up owning rather than renting, I rescue builds that have stalled or gone over budget, I get critical old systems off life support without breaking the business, and I tell investors what they’re actually buying before the money moves. Across all of it the constant is the same: senior judgement, applied hands-on, by someone who also runs an agency and has had to make this work as a business and not just as code.
I’m not going to manufacture credibility with invented numbers or client names I can’t stand behind. What follows is the honest shape of the work — the kinds of systems and the recurring situations — stated plainly. If you’ve done this long enough, the shape tells you more than a logo wall ever could.
The lean builds — things people now own instead of rent
A large part of what I’ve done is build the smallest version that actually solves the problem, and build it so the business owns its core. The pattern repeats: someone arrives convinced they need an expensive off-the-shelf platform or a six-figure bespoke system, and the real answer is a lean MVP they can stand up fast, earn from, and grow from a position of strength. Internal tools, dashboards that pull scattered data into one trustworthy view, workflow systems that replace a stack of rented SaaS — the kind of thing where, a year on, the business has its own asset compounding in value instead of a monthly bill it can never escape.
That’s not me being cheap on a client’s behalf. It’s that owning the core is what makes everything afterward possible — connecting systems, automating across them, extending on your terms. I’ve watched the difference between a business that owns its data and one that rents access to its own operation play out over years, and it’s not close.
The rescues — builds that stalled, over-ran, or quietly caught fire
I get called when something that was supposed to work doesn’t. The build that’s months late and nobody can say why. The agency relationship that’s gone sour and the codebase is a mystery. The system that “mostly works” until it doesn’t, at the worst possible moment. These are some of the most useful engagements I do, because by the time I’m in the room the cost of carrying on blind is already high and a clear read changes everything.
The lesson that repeats here is that the risk is almost never the code itself — it’s the assumptions nobody wrote down. The first real progress on a stalled build usually comes from surfacing the decisions that were made implicitly and never examined, not from writing more software faster. Getting a stuck project back on the rails is mostly an act of diagnosis followed by ruthless scope discipline, and only then a build.
The legacy work — keeping the critical old thing alive, or getting off it safely
Plenty of businesses run on something old and load-bearing that everyone is slightly afraid of. I do the work of keeping those systems alive when they have to stay, and moving off them without breaking the business when they have to go. Migrations are where confidence and caution have to coexist — you commit hard to the move and you respect what the old system quietly handles that nobody documented. Done badly, a migration takes the business down with it; done well, nobody outside the room ever notices it happened. I’ve done enough of them to know which assumptions to distrust.
The judgement calls — due diligence and the decisions that land months later
Before money moves — an acquisition, an investment, a big commitment to a platform or a rebuild — someone needs to know what’s really there, and that read has to be honest rather than reassuring. I do the work of looking under the hood and telling the buyer plainly what they’re getting: what’s solid, what’s a liability, what’s going to cost them after the deal closes. The value is in being the person who’ll say the uncomfortable thing while it still matters, because the technical decisions whose cost lands months later are exactly the ones worth getting an experienced eye on now.
Proven at scale, available in person
The thing that holds all of this together is the rare double at the centre of this whole site: I’ve had to make software work as a business, through building and running my agency Digital Royalty, and I’m still the individual you get direct access to. The agency means the standards and the delivery are proven at a scale a freelancer can’t claim. The consultancy means when you want senior judgement on a hard problem, you get the actual senior person — not a relay through account managers. The range above exists because I’ve done the work at both ends.
Who this is for
This record is worth paying for when the cost of the wrong decision is bigger than the cost of my time — a rebuild you might not need, a platform you’d be locked into, an acquisition you can’t fully see. If you want the cheapest pair of hands to execute a plan you’ve already fixed, the experience here is wasted on you, and a contractor will serve you better.
See a real engagement
The shape of the work is the honest version; the detail lives elsewhere. My case studies carry specific engagements with the problem, the approach, and the outcome laid out properly. For the way I’d actually run any of this, see how I work, and for what shaped that approach, my story. (Back to about.)