Boardroom Answers · Technology & Platform · Operational Excellence
This platform was substantially built by one founder directing AI agents. If you get hit by a bus — or just burn out — what exactly have we bought?
The question a VP Engineering / Head of Platform asks.
The short answer
Bus factor is one today — I will say it before you do. What you would inherit: strictly typed code, 3,577 executable behaviour specs, rebuildable-from-zero schema, written invariants, managed infrastructure, and escrow on paper.
The full executive answer
It is the single most important diligence question about a company my size, so let me answer what you would actually inherit rather than defend my indispensability. First, the codebase is engineered for successor engineers, not for my memory: strict typing throughout — meaning the code documents its own contracts and a new engineer's mistakes are caught at compile time; 3,577 tests that encode the intended behaviour executably; 192 numbered, re-runnable database migrations that reconstruct the entire schema from zero; and a written working agreement in the repository that captures the invariants — the tenant-isolation rules, the AI-safety rules, the deployment gates — precisely so they are enforced by pipeline and document rather than carried in my head. The AI-assisted development model cuts both ways here, and the second edge favours you: the practices that let AI agents work on this codebase safely — explicit conventions, machine-enforced rules, exhaustive tests — are exactly the practices that onboard human engineers fast.
Second, structural continuity: your data is in standard Postgres, continuously exportable through the API and file exports we discussed, and the operational stack is managed services — hosting, database, identity all keep running without daily founder heroics. There is no hand-operated machinery that stops when I sleep.
Third, the honest residue: yes, today the bus factor is one, and I will not dress that up. The mitigations with dates rather than adjectives: key-person insurance and source-code escrow with a release-conditions agreement are standard enterprise-contract terms I will sign; and the first engineering hires are an explicit use of the funding round this launch supports. Ask any acquirer's technical diligence team what they fear in a small vendor — undocumented tribal knowledge and untested code. This company's entire engineering culture is the inversion of that.
Grounded in: ISO/IEC 25010 maintainability characteristics; source-code escrow as vendor-continuity control
The natural next questions
Related governed answers
- Your product is built on hundreds of open-source packages. What is your software supply-chain security story?
- You are a one-person company. If you get hit by a bus, sign with a competitor, or simply burn out, my organisation has built board processes on a dead product. Why would I ever accept that risk?
- Walk me through your CI/CD pipeline, step by step, as it actually exists — not the aspiration.?
Want this answered live, on your data?