The Founder Dependency Index: how to measure whether your business runs on you

Most founders can feel the problem long before they can name it. The business is growing, the team is capable, and yet everything still seems to come back to one desk. Approvals wait for you. Decisions stall when you are away. The knowledge that keeps the place running lives mostly in your head. This is founder dependency, and it is structural rather than a matter of effort.

The Founder Dependency Index, or FDI, exists to make that pattern visible. It turns a vague sense of being the bottleneck into a single number you can watch move.

What the index measures

The FDI is a score from 0 to 100. A higher number means the business relies on you personally to function; a lower number means it can answer more of its own questions. The aim is a descending number over time, not a perfect score on day one.

It is built from a few factors that together describe the dependency:

• Control. How many decisions can only be made by you, and how often work waits on your sign-off.
• Delegation. Whether whole workflows have a clear owner, or whether you still hold the doing as well as the deciding.
• Capacity. How much of your week is spent on work only you can do, versus work that has drifted onto your desk.
• Clarity. Whether the business runs on a shared, written understanding, or on context that exists only in conversation with you.

Alongside these, the index looks at signals from how the business actually behaves: whether recurring bottlenecks get resolved or keep returning, whether delegated work reliably lands, and how much of your calendar goes to low-leverage meetings. Each factor is weighted, then combined into the single score.

Why a single number helps

Founder dependency is hard to manage because it hides in a hundred small moments. A number gives it one place to live. It lets you see whether a change actually moved the underlying structure, rather than just feeling productive for a week. And it reframes the goal: the job is not to work harder inside the dependency, it is to lower the dependency itself.

How the number comes down

The index falls when work moves out of your head and into clear ownership. That tends to follow a predictable order:

1. Protect a block of focus time so the most important work stops being the thing that never happens.
2. Give each recurring meeting a clear job, or remove it. Most lost hours hide in coordination, not in the work itself.
3. Hand over one whole workflow, with its inputs, steps, output standard, and the few checkpoints that matter, and coach the gap instead of reclaiming the task.
4. Write down the decision rules that currently live only with you, so the business can answer its own questions when you are not in the room.

Each move lowers one of the underlying factors, and the score follows. The relief comes from the structure, not from doing more.

What good looks like

A healthy trajectory is a number that keeps falling, even slowly, while the business keeps growing. At some point the test changes from can I get through the week to can the business run a week without me, and pass it. That is the point of measuring dependency rather than activity: it keeps the goal on the thing that actually frees you.