What you receive — the Handover Manifest
The Handover Manifest is the literal deliverables list at Substrate Handover. Nine artefacts, delivered at close:
- Repo — the substrate codebase (MIT-licensed, hosted in your GitHub from minute one)
- Ontology — the entity-and-edge schema that mirrors how your business actually works
- Runbooks — operational procedures, written down, executable
- Decision history — the why behind every architectural and operational call, captured
- Integration map — every connector, every data path, every downstream dependency, documented
- Audit log — every command, every action, every change, timestamped
- Retrieval graph — the queryable knowledge layer your AI plugs into
- DR procedure — disaster recovery runbook, tested
- Training docs — onboarding for the next engineer who touches the substrate
These are not deliverables in a folder. They are live artefacts — maintained, versioned, and queryable after handover. For the first time, your CEO and CFO can see the operating business as a queryable system. Every connector, every workflow, every decision on record — available in plain English, on your own infrastructure.
Three mechanisms that move valuation
The asset moves valuation through three mechanisms that PE and M&A practitioners apply as standard diligence adjustments. Each is independently recognised. Together they compound.
1. Key-person risk discount removal
SME valuations routinely carry a haircut when operating knowledge is locked in the founder or senior staff. The substrate externalises that knowledge — into code, runbooks, a queryable retrieval graph, and a structured decision history. A buyer's adviser observes the externalisation directly and reduces the discount accordingly. This is not a soft claim. It is a documented reduction in enterprise value risk.
2. Documented operational IP premium
Buyers pay higher multiples for businesses they can step into and operate without the seller present. The Handover Manifest is the strongest available evidence of operability: auditable runbooks, live integrations, a working agentic layer, and a full audit trail. It is not a promise that the business runs without the founder; it is proof. That distinction drives the premium.
3. Capitalisable software asset
The substrate is owned software — codebase, structured data, documentation — self-hosted on your infrastructure. A buyer's auditor can recognise it on the balance sheet as an intangible asset under capitalised software development. We deliver the artefact in a form their accounting framework can receive.
The math, conservatively framed
◉ Illustrative example — Practice tierA Practice-tier engagement at a mid-sized professional firm. All-in cost: R 800,000 to R 1.2 million across Foundation, Practice, and Stewardship. A mature firm of this size carries an enterprise value in the R 50 million to R 80 million range. SME valuations at this scale routinely absorb a key-person discount of 10 to 30 per cent. Removing even 2 per cent of that discount — a conservative figure — recovers R 1 million to R 1.6 million of enterprise value. That recovery is from the asset alone, before any operational leverage.
We name the lever. Your auditor and your prospective buyer quantify.
For the full math, the Federation case, and the trend line: read the essay →
Independent verification
During Stewardship, an independent technical due-diligence firm audits the substrate in production. That report is the third-party verification a buyer's auditor requires to capitalise the substrate as an intangible asset on the balance sheet. Audits of in-production substrates are honest. Audits of scaffolding are theatre.
Independent verification is included by default in every Practice and Federation engagement.
Where this lands
The asset class exists. The artefacts are defined. The math is there for your advisers to run.
You end this engagement owning a capital asset — MIT-licensed, capitalisable, transferable in M&A. The operational leverage that follows is on top.