Your team isn't the bottleneck. Your missing frameworks are.
Last updated 4 June 2026
The Founder Dependency Index measures what percentage of decisions in your business only you can make. Divide last week's founder-only decisions by total decisions made across the company. Most founders land above 70%, meaning they've become the decision-making infrastructure, not a symptom of a people problem, but a structure problem.
The Founder Dependency Index: How Replaceable Are You Right Now?
What is the Founder Dependency Index?
Take the number of decisions last week that only you could make. Divide by the total decisions made across the business. Multiply by 100.
That percentage is roughly how replaceable you are right now.
Most founders who run this calculation land above 70%. A vague feeling of being overwhelmed never gave you a number like that. 74% does.
Why "I have a people problem" is usually the wrong diagnosis
The team keeps escalating things they should handle. They wait for you before anything moves. The natural conclusion: hire better people, or have the same accountability conversation again.
Neither tends to work, because the diagnosis is wrong.
The team probably isn't the problem. At some point you became the decision-making infrastructure, the place where judgment lived, where calls got made, where ambiguity got resolved. And you never replaced yourself with anything external to your own head.
They didn't fail to step up. They were never given a structure that let them.
What this looks like in practice
A founder came back from a week off to 40 unresolved threads in his inbox. Not crises. Things that sat there because nobody had a clear, written sense of what "good enough to move forward" looked like without him in the room. He'd told them what to do plenty of times. But they'd only ever watched him decide. No written threshold. No documented rule. So when he wasn't there, they waited.
Another founder hired a COO. The first thing the COO asked for was the playbook. The founder went quiet, because the playbook was his own head. Nothing to hand over.
The one that stays with me: a $200 vendor approval got escalated because there was no documented threshold for what the team could approve on their own. Two hundred dollars, and the founder had to weigh in.
None of these are people problems. All of them are structure problems.
How to calculate your dependency ratio
| What you're measuring | How to calculate it | |---|---| | Decisions only you could make last week | Count manually, calendar, Slack, email | | Total decisions made across the business | Estimate across your team leads | | Your dependency ratio | First ÷ second × 100 |
If you're above 70%, you're not running a business with a people problem. You're running a business where the decision-making lives in one place, and that place is you.
Where founders actually start fixing this
Not with a new framework. Not with a hiring plan.
With the count.
Count the decisions only you made this week. That number is your baseline. Once you have it, you can begin to ask which of those decisions could have been made by someone else if a written threshold or rule had existed. That's where the structure gets built, one documented boundary at a time.
You can't improve what you haven't measured.