Every founder pays a tax the company does not put on the income statement. It is the cost of running every decision through one operating mind. The cost compounds as the company grows. It is invisible until the company stops scaling, and then it is the first thing every honest diagnostic finds.
We have run this diagnostic dozens of times. The number is always larger than the operator expects. Usually by an order of magnitude.
How the dependency forms
It does not happen because the founder wants control. It happens because the founder is faster. In the first phase of every company, the operator's brain is the fastest decision system in the business. The team learns to route everything through it because that is the fastest path. The founder reinforces the pattern because the wrong decision is more expensive than the slow process.
This works through the first phase. It begins to break in the second. By the third, it is the dominant constraint on the company.
The team is not slower than they were. The founder is not less capable than they were. The cap is structural. Decisions queue at the founder, and the queue is the company's actual throughput. Everything downstream of the queue runs on the queue's clock.
The company runs at the speed of the founder. Until the founder is not the speed limit any more, the company cannot scale past them.
What the dependency costs
We measure it by removing it. Eight weeks into most engagements, the founder takes seven full days off. No Slack, no calls, no async. The team runs the business.
The numbers from the seven days are the diagnostic. If the company degrades in any structural way, the dependency is alive. If the company holds the line, the dependency is broken. We grade the engagement on what the team did, not on what the founder felt.
The companies that pass this test are worth several multiples more than they were eight weeks earlier. Not because the business has changed. Because the operating risk has.
Where the dependency lives
It lives in three places. Each one has to be addressed differently.
It lives in decisions the team does not have permission to make. This is the easiest to fix. We write the rails, the founder signs them, the team uses them.
It lives in decisions the team does not have visibility to make. Harder. The team needs the same view the founder has of the business. Dashboards, reports, weekly rituals. Most companies skip this layer entirely because the founder did not need it. The team does.
It lives in decisions the team does not have judgment to make. Hardest. This is not a documentation problem. It is a hiring problem, a development problem, sometimes a culture problem. It takes the longest to fix and is the most leveraged when it is fixed.
What it looks like when it is removed
The founder still works. The work is different. Less queue management, less routine decision-making, less inbox. More strategy, more capital allocation, more category creation. The work the team cannot do.
The team is also different. Not bigger. Different shape. The bottleneck roles get more authority. The non-leveraged roles get rebuilt or removed. The whole structure runs lighter at the same revenue.
The first sign the work landed is the founder's calendar. The second sign is the team's confidence. The third sign is the line on the financials that bends upward over the next three quarters.
What we look for
We engage on this work where the operator is at a million a month or above, recognises the dependency, and wants it dismantled with the same rigour they used to build it. The work is structural. It takes weeks, not days. The companies that do it well are worth several times more inside a year than they were when the work started.
The cost of being the founder is real. The cost of remaining the bottleneck is larger.