The enterprise is worth what it is worth without you

Dependence on one leader is usually discussed as a workload problem: the calendar, the bottleneck, the CEO who can't take a holiday. That framing understates it. Being indispensable is a commercial condition. It shows up in how fast the business can move, what kinds of transactions it can credibly pursue, and what a buyer, board, or lender believes they are actually acquiring.

I spent years as a CFO before this work. In every diligence process I have been part of, the same question sits underneath the model: how much of this performance is the enterprise, and how much of it is one person? That answer changes the valuation.

Where the cost actually shows up

Decision latency. When consequential calls queue for one calendar, the real cost isn't the meeting. It's the time the organization spends waiting, hedging, and re-litigating in the interim. At scale, that slowness eats into margin, and it comes from how decisions are distributed, not just how fast any one person makes them.

Deal capacity. Complex transactions require several senior people who can carry authority into a room simultaneously. An enterprise with one such person can only run one such process at a time, and only at the pace that person can sustain.

Preparation for growth. I have seen CEOs build leadership capacity before growth exposes the need for it. Developing judgment and transferring authority early reduces dependence on the CEO and gives the enterprise more capacity to absorb what comes next.

Risk premium. Concentration of judgment in one individual is a risk that gets priced, in multiples, in covenants, in the structure of an earn-out. CEOs often discover this at the least convenient moment.

Why it persists

Indispensability is built out of things that once worked. The instinct to hold the hardest decision was correct when the company was small and the margin for error was thin. The habit of reviewing the detail was correct when the detail was the differentiator. These behaviors are earned, and they are the very ones that stop working as the company grows.

There is also another reason. For many CEOs, being needed is part of how they know the enterprise matters, and how they know they matter themselves. Delegating the work is straightforward. Delegating the identity that came with it is much harder. That is the part that stalls most transitions, and it is rarely named in a strategy session. The company has grown past the version of you it needed at the start. Naming that openly is often the most important conversation I have with a CEO, and one they rarely get to have with anyone inside the company.

What unwinding it requires

Unwinding takes three things, in order. First, an honest map of which decisions truly require the CEO and which have simply never been moved. Second, a real transfer of authority along with the tasks. People don't step up into responsibility they suspect will be reversed the first time they use it. Third, a leadership bench with enough depth that authority has somewhere to land, formally and informally, throughout the organization.

Done properly, this is one of the highest-return pieces of work available to a CEO. It converts personal capability into institutional capability, and institutional capability is what the market pays for.

The question worth sitting with is this: If you were unavailable for ninety days, what would slow down, and what would simply stop?

Whatever stops is still part of you, not yet part of the enterprise.