How we close
the valuation gap.
No new budget. The engagement is funded from delivery spend you already carry — legacy payroll, outsourced support, loss-making services — and replaced with a clean operating model.
Four steps, in this order.
Each step depends on the one before: decision rights first, then the right people, then the team, then the rebuild.
01 Mandate
A defined scope, agreed by board resolution before we start. Every decision that crosses the product–services boundary gets one owner and a deadline.
02 Talent alignment
The leaders who built the company hold the moat. Each senior role is re-cast for the current stage.
03 Team
Senior capability employed onto your books, built around the people who hold the product knowledge. No bench, no recurring vendor fees.
04 Rebuild & routing
Done last. Without the first three, a rebuild produces a newer version of the same asset.
Where each step binds, tier by tier →
The functional transformation
Your managers design the processes they will run, so they survive after we leave.
Every client request gets
a destination and a price.
Requests are never refused; they are routed. Only what many customers can buy enters the core.
- Core · one product
Code, data model, versioned API, MCP interface. Built once, sold many times. Owned and supported by the company.
- Enablers
Reusable templates built on the public API. The customer copies, adapts and owns them.
- Edge
Customer-specific integrations connected through the versioned API. Owned by the customer, or built by professional services under a priced statement of work. It never touches the core.
How the boundary is enforced daily
Senior engineers direct the AI.
A person signs off every output.
Each senior operator directs a fleet of production-hardened AI agents. Agents don’t make decisions: architecture is set first, and every system ships with its runbook.
We claim cadence, not a per-engineer multiple, because cadence is what a buyer can verify. On fixed architecture it rose from quarterly to two production releases a month.
operator
The guard-rails
Each failure mode has a named guard-rail in front of it.
What stays when we leave.
Everything permanent lands on your payroll. Four handover logs stay with the company — what makes the improvement attributable when diligence takes the numbers apart.
The decision log
Who owns each decision, its deadline, and the reason when it is used.
The baseline book
What was measured at the start, signed, and how each figure was counted.
The benefits tracker
Every claimed gain with its owner. Identified and realised improvements reported side by side.
The boundary log
Every customer commitment with its destination: core, enabler or edge. Nothing promised without a record.
How each change appears in your P&L.
Every installation lands on a line a CFO or a buyer already watches.
Together: gross margin above 80%, services under 15% of mix, NRR above 110%, R&D at 20–30% of revenue — the shape priced at around 3–3.8x revenue rather than 1–2.6x (private M&A, 2024–Q1 2026, Aventis).
We only make money when your spend goes down.
- An integrator earns more when your delivery spend goes up. We cannot bill a single hour of delivery.
- Our fee is fixed at signature and doesn’t grow with scope, headcount or duration.
Three questions for any integrator pitching alongside us:
How many of your people end up on my payroll at the end?
What happens to your revenue if my engineering spend halves?
What is your fee if my EBITDA does not move?
Common questions.
“We tried a transformation before and it died in month six.”
Process-first programmes die in month six because nobody owns what the process asks. We go org design, then people, then process.
“Couldn’t we do this ourselves for less?”
The plan is yours either way. What you buy is the decisions made and the sequence held, under decision rights.
“Everyone claims AI savings.”
We claim cadence, measured on your own dashboard against the manual version.
“It all reverts the day you leave.”
Everything permanent is on your payroll, with named successors and the four handover logs.
Start with the Two-Week Read.
Two weeks, no fee — access instead. A verbal answer on whether there’s a multiple-shifting number here, and roughly where it sits. If there isn’t enough, we say so.