Project Rescue
Project rescue is me walking into a build that’s stalled, over budget, or quietly on fire, working out why, and getting it back on the rails. You’ve spent real money and the thing still isn’t shipping — or it ships and breaks. I find the actual cause, stop the bleeding, and give you a path forward that’s based on where you genuinely are, not where the plan said you’d be.
What this is
This is triage and recovery for a software project that’s gone wrong. I come in, get an honest picture fast, and tell you the truth: what state it’s really in, why it got here, what’s salvageable, what isn’t, and the shortest sound route to something that works. Then I help you take that route — directing the existing team, replacing what needs replacing, or rolling up my sleeves on the critical path myself if that’s what gets it unstuck.
The first job is almost always separating the real problem from the noise. A stalled project is usually not a shortage of effort — people are working hard, that’s why everyone’s confused about why it isn’t done. It’s a scope that quietly tripled, an architecture decision that’s now fighting every new feature, a team pointed at the wrong target, or a plan that was never buildable in the first place. The hard part is naming that without flinching, which is exactly what an outside senior person is for.
It is not me promising to take the whole thing over and run it indefinitely. Rescue is intensive and finite: stabilise it, get it moving, and hand you back a project that’s healthy enough to continue — with whoever’s right to continue it.
When you need this
You need this when the gap between “where we are” and “where we said we’d be” has stopped closing and nobody can clearly explain why. The familiar signs:
- The deadline has slipped more than once and you no longer believe the new one.
- The budget’s gone and there’s still no working product, or a working product nobody trusts.
- Your team is busy and demoralised, and every status update is vaguer than the last.
- An agency or contractor relationship has broken down and you’re holding a half-finished build you don’t understand.
Underneath all of those is the same thing: you’ve lost the ability to tell whether this can be saved or whether you’re throwing good money after bad. That’s the call I’m there to make, honestly and early, before more money goes in.
How working with me goes
I move fast, because a project in trouble is bleeding money every week and the first thing you need is the truth, not a slow audit. I start by getting an unvarnished read — the code, the architecture, the plan, and crucially the people, because the team usually knows exactly what’s wrong and hasn’t been able to say it safely.
Within a short window I’ll tell you the diagnosis straight: salvageable and here’s how, or not salvageable and here’s the cheaper restart. If it’s worth saving, we agree the shortest sound path — what to cut, what to fix, what to finish — and I help drive it, working alongside your people rather than over them. My bias is ruthless toward the smallest thing that gets you to working software you own, because that’s how stalled projects actually un-stall: by shipping something real, not by perfecting the plan. The last time I walked into a stalled build, half the fix was permission to stop building three features nobody had asked for.
What you walk away with
- An honest diagnosis: what’s really wrong, why, and whether it’s worth continuing.
- The bleeding stopped — the spend that wasn’t getting you anywhere, halted.
- A short, sound path to working software, scoped down to what actually matters.
- A team re-pointed at the right target and able to say what’s true again.
- A working product you own, healthy enough to carry forward — or a clear-eyed decision to restart, which is sometimes the cheapest answer.
Who this isn’t for
If you want someone to confirm the project is fine and the only problem is needing more time and money, I’m not it — I’ll tell you if it’s unsalvageable, and that’s sometimes the most valuable thing I can say. This is for owners who’d rather face the real state of it than keep funding hope.
When you need a team instead
Rescue gets the project healthy and moving; it’s intensive and finite by design. If, once it’s stable, what you need is a standing team to build out the rest and run it for the long term, that’s ongoing delivery — a team’s job, not a rescuer’s. That’s what my agency, Digital Royalty, is for: picking up a stabilised project and carrying it at scale, with the team and process to do it properly. Because I run both, the hand-off is clean — I can stabilise it and pass it across without you starting over.
Tell me what’s going wrong
If a build has stalled and you can’t tell whether to push on or pull the plug, that’s exactly when to bring me in — early, before more money disappears into it. Tell me what’s going wrong and I’ll tell you straight whether it’s worth saving. If the project isn’t broken so much as ageing — a critical old system you can’t safely change — that’s legacy software modernisation instead; and if you need a senior hand on the technical direction beyond this one fire, a fractional CTO is the ongoing version, alongside the other ways I help. The framework I use to triage these is in how to rescue a stalled build.