My Story
From Enterprise Chaos to Exit Strategy Mastery
I didn’t set out to become an exit strategy consultant.
For 13+ years, I was the person companies called when their most critical projects were falling apart.
Heathrow Terminal 4. Stage 4 delivery under impossible pressure. Multi-stakeholder chaos. Regulatory nightmares. Budget scrutiny from every direction.
Olympia London redevelopment. Coordination across facade contractors, consultants, engineers. Technical reviews with zero margin for error. Compliance reporting that could halt the entire project.
US Embassy 30GS. BIM modeling and Stage 4 technical drawings for a high-security government facility. Consultant coordination with WSP & AMEY. Every detail under microscope.
Chelsea Riverview. Façade design and BIM coordination for residential and commercial spaces where aesthetic precision met structural requirements.
These weren’t just construction projects. They were high-stakes operational systems where:
➤ One communication breakdown could cost millions
➤ One misaligned stakeholder could derail timelines
➤ One undocumented process could create liability nightmares
Here’s what I learned managing £1B+ in enterprise projects:
The businesses that survive pressure aren’t the ones with the best ideas or the hardest workers.
They’re the ones with systems that work when the founder isn’t in the room.
I saw the same patterns repeat across countries, industries, and team sizes:
➜ Clear delivery frameworks = Projects that scale without chaos
➜ Documented communication systems = Teams that function without the founder
➜ Stakeholder management protocols = Clients who trust the process, not just the person
➜ Risk forecasting infrastructure = Businesses that prevent crises instead of reacting to them
That’s when I realized something:
Most service business founders are trying to scale using the same chaotic systems that barely worked at £500K revenue.
They think they need:
↳ More staff
↳ Better tools
↳ Harder work
What they actually need:
The same enterprise-grade operational frameworks I used to deliver Heathrow Terminal 4.
But adapted for service businesses planning their exit.
Because here’s the truth nobody tells founders:
Your business isn’t worth what you think it’s worth.
It’s worth what a buyer will pay for a system that works without you.
Buyers don’t want your hustle. They don’t want your personal relationships. They don’t want a business that collapses when you take a vacation.
They want:
↳ Documented delivery systems that any competent team can follow
↳ Client relationships built on trust in the process, not dependency on you
↳ Financial clarity that proves margins are sustainable
↳ Team structures that function without constant founder intervention
That’s exactly what I build.
I take the same crisis-prevention frameworks I used on £1B+ international projects and adapt them for service businesses planning exits within 2-5 years.
Not theory. Not frameworks that sit in a drawer.
Implemented systems that increase business value while reducing your dependency.
Because the best exits aren’t desperate sales.
They’re strategic choices made from positions of strength.
Let me show you how to build that position.
