Ask most owners how the business would run if they took three weeks off with no phone. Most can't answer cleanly. Not because they haven't thought about it. The honest answer is uncomfortable. The business would slow down, some decisions would simply wait, and a few things would quietly go wrong. That gap between "the business runs" and "the business runs without me" is a real number. Almost nobody measures it.
What the Number Actually Is
Owner-dependency isn't a feeling. It's the share of decisions, relationships, and approvals that currently route through one person by habit rather than by design. It shows up in specific places: the client who will only deal with the owner directly, the pricing exception nobody else is authorized to grant, the vendor relationship that lives in the owner's head and not in a contract, the one employee who quietly translates the owner's intent for everyone else.
None of that is a character flaw. It's how almost every owner-led business gets built. The owner is the fastest path to a decision, so more and more decisions route that way over time. The problem isn't that it happened. It's that it usually isn't tracked, so nobody notices how large it's gotten until an outside event forces the question: a health scare, a sale conversation, a family succession decision, or simply the owner wanting fewer hours.
Why This Is Different From "I Should Delegate More"
Delegation is a to-do list. Owner-dependency is a measurement problem, and you can't fix what you haven't measured. "Delegate more" produces a vague intention. A dependency count produces a specific, falsifiable list: these fourteen things currently require the owner personally, ranked by how much damage it would do if the owner were unavailable for a month.
That distinction matters because it changes what the fix looks like. Generic advice says build a management team. A real dependency count might show the actual bottleneck is three vendor relationships and one pricing decision, a much smaller, much more finishable project than "build a management team."
How to Actually Count It
Walk one ordinary week. For every decision, approval, or relationship touchpoint that came through the owner, write down two things: could someone else have made this call with the information they currently have, and would the business have noticed if the owner hadn't been reachable that day. Anything where the answer is "no" to the first question is a real dependency, not a preference.
Sort the list by consequence, not by frequency. A daily habit that anyone could pick up in an afternoon matters less than a once-a-quarter decision that only the owner has the context to make correctly. The second kind is where succession risk actually lives.
The Succession Version of This Question
For an owner without a formal succession plan, this number is the plan, or the missing first page of one. A business can't be handed to a successor, sold, or even safely stepped back from, faster than its owner-dependency number shrinks. Every unresolved dependency is a thing a successor would have to rebuild from scratch, under pressure, without the owner there to ask.
This is also why succession conversations stall. "Who takes over" is the wrong first question if the honest answer to "what would they actually be taking over" is a set of relationships and judgment calls that exist only in the current owner's head. Naming a successor doesn't transfer that. Only deliberately moving each dependency out of the owner's hands, one at a time, does.
Isn't some owner involvement just normal for a business this size?
Some is. The question isn't whether the owner is involved. It's whether that involvement is a deliberate choice or an accumulated default nobody has reviewed. The count tells you which.
What if the dependency list is longer than expected?
That's common, and it's better to know now than to discover it during a sale process or a health emergency. A long list isn't a verdict on the business. It's a prioritized to-do list with the highest-consequence items at the top.
Does this replace a formal succession plan?
No. It's the diagnostic step that makes a succession plan realistic instead of aspirational. A plan built without this number tends to name a successor and skip the actual transfer of judgment, which is the part that usually fails.
