Founder dependency
Founder centrality is expected early and dangerous if it persists.
It is acceptable for the founder to own architecture and product truth while the system is being discovered. By month twelve, it becomes problematic if only the founder can map a customer, explain the evidence model, run deployments, manage counterparties or explain failure states. Documentation, fixtures, acceptance tests and a technical-commercial deployment operator are part of de-risking the company.