M08DiagnoseDiagnosis· Module 3
Founder Dependency
Approvals, pricing, key customers and problem-solving all route through one person. The business waits.
- Stabilise
- Institutionalise
- Scale
- Leadership
- Governance
- People
- ~5 min · Diagnostic
The business problem
In many founder-led businesses, capable staff still escalate routine decisions, key customers call only the founder, and critical knowledge — pricing, supplier terms, technical judgement — lives in one head. The founder is busy; the business slows whenever the founder is away.
Why it matters
Founder dependency caps growth at the founder's capacity, makes the business fragile, and reduces its value to lenders, buyers and investors. It is also the main reason founders cannot take a holiday.
What you will learn
- Measure how much of the business depends on you
- Distinguish decisions that need the founder from those that only reach the founder
- Identify dependency in relationships, knowledge, decisions and information
- Prioritise the first handovers
Core questions
- Which decisions stop when I am unavailable?
- Which customers or suppliers deal only with me?
- What knowledge exists only in my head?
- Who could take over each area, with the right rules?
Work through the module
CaseWhat is happening?
Engineering services, 30 people · Illustrative teaching case
A founder of an engineering services firm approves every quote, signs every purchase and handles every major client. On a two-week trip, tenders are missed and site work stalls waiting for material approvals. The managers are experienced, but nothing tells them what they are allowed to decide.
Full teaching case: The Founder Bottleneck · The Business That Cannot Run Without Its Founder
DecisionWhat does the leader need to decide?
Continue to hold control personally, or define what others may decide and accept they will sometimes decide differently?
FrameworkHow should they think about the problem?
The four dependencies
Founder dependency sits in four places: relationships (who the customers and suppliers trust), knowledge (how things are priced, made and fixed), decisions (who may approve what) and information (who can see how the business is doing). Each needs a different handover.
ToolWhat can they use?
Founder dependency checklistDiagnostic
- Score each function 1–5 for dependency on the founder
- Log every decision that reaches you for two weeks
- Mark which needed you, and which only came to you by habit
- List knowledge that exists only in your head
ApplicationHow does it apply to their business?
Apply it to your own business:
- Keep a two-week decision log
- Score the four dependencies for your business
- Choose three handovers to start this quarter
ImplementationWhat changes?
What should change in the business:
- Write approval limits for the decisions you logged
- Document the knowledge behind the first handover
- Introduce customers and suppliers to their new point of contact
ReviewDid it work?
How to tell whether the change worked:
- Has the number of decisions reaching you fallen?
- Did the business keep moving during your last absence?
- Are handed-over decisions being made within the agreed limits?
After this module you should be able to decide
Continue to hold control personally, or define what others may decide and accept they will sometimes decide differently?
And leave with: A founder-dependency score with the first three handovers identified.
Sequence · Diagnosis
Related modules
Part of these learning paths