A founder bottleneck is a leader who has become the mandatory checkpoint of their own company. Decisions, approvals and exceptions all route back to them. The consequence is measurable: the company no longer moves at the speed of its market, it moves at the speed of one person's calendar. This is not a character flaw — it is what happens when the behaviour that created traction stays in place after it has stopped producing returns.
The 30-day test
Leave for a month. Genuinely: no phone, no Slack, no "just one approval". Then look at what stopped.
What stops while you are away is the exact list of what depends on you. Not what you believe you delegated — what actually stands up without you. Most founders I ask hesitate before answering. That hesitation is already the answer.
Why it happens — and why it is not your fault
Early on, being the bottleneck is an advantage. You decide in thirty seconds what a committee would take three weeks to settle. You know every customer, every cost line, every bug. That concentration is what makes the company exist.
Then the volume changes. The number of decisions to take grows faster than the number of available hours, and there is no moment where someone tells you: "as of today, this skill costs you more than it returns." The switch is silent. You never see it in the P&L; you see it in the delay between a decision that could be taken and the moment it is.
The most reliable signal is not your workload. It is the average waiting time in front of you: how long a decision sits blocked because it is waiting on your opinion. A team of three waiting two days loses six person-days per decision. That is the real cost — not your own hours.
The two faces of the founder bottleneck
It shows up in two forms, and most leaders only have one of them.
1. The operational bottleneck — everything goes through you
Approvals, arbitrations, exceptions, closing, customer escalations. Your calendar is the company's critical path. The visible symptom: when you take a holiday, nothing explodes — everything stacks up, waiting for you. You come back to four hundred messages and three decisions that should have been taken two weeks ago.
The number that matters here: the share of your time spent in operations. Past 60%, you are no longer the leader — you are your company's best individual contributor.
2. The decision bottleneck — you say yes to everything
This one is harder to see, because it looks like ambition. There is cash, good ideas everywhere, four or five projects in parallel. Every "yes" is defensible on its own. It is their sum that kills focus: nobody on the team knows what matters most any more, so everybody comes back to ask you.
The decision bottleneck manufactures the operational one. A blurred strategy turns every executor into a requester of arbitration.
Self-diagnostic: ten questions
Answer yes or no, honestly. Nobody reads your answers.
- 1A decision worth under €5,000 of impact regularly waits for your approval.
- 2You are still in the loop on at least one customer deal a week.
- 3You cannot name, without thinking, the person accountable for each of your three main numbers.
- 4Your team asks you questions it already knows the answer to — it is looking for cover, not information.
- 5There is at least one process documented nowhere that only you can execute.
- 6More than 60% of your time goes into delivery, support or approvals.
- 7You have four or more significant initiatives running at the same time.
- 8One week away produces more than one week of catching up.
- 9Your latest hires increased your workload instead of reducing it.
- 10You know the answer to "what is the company's main constraint" — but nobody else on the team would give the same one.
This scale is a reading aid, not a measurement: ten binary questions do not replace a diagnostic on your real numbers. It tells you whether there is a subject, not which one.
The four false remedies
These are the most common reflexes. They are all rational and they all fail for the same reason: they add capacity somewhere other than the bottleneck.
- Hiring. Every hire opens another channel back to you. Without changing how decisions get made, a bigger team produces more requests, not more autonomy.
- A tool. A CRM, a project tracker or a dashboard makes the bottleneck more visible and better organised. None of them removes it.
- Working more. It works — for a few months. Then the bill arrives, and it rarely arrives alone.
- Documenting everything first. The "let's formalise our processes" project always starts and rarely finishes, because it demands exactly the time the bottleneck does not have.
What works: four moves
1. Find THE bottleneck, not the bottlenecks
A company has one main constraint at any given time. One. Widening everywhere at once is the best way to unblock nothing and exhaust the team on the way. The useful question is not "what is wrong?" — that list is infinite — but "what, once fixed, unblocks everything else?"
2. Delegate the decision, not the task
Delegating a task frees nothing: it comes back to you at approval time. What frees you is handing over the right to decide, with three things made explicit: the criterion (what a good decision looks like), the limit (how far without talking to you), and what happens when it goes wrong. Without those three, it is not delegation, it is a guessing game.
3. Make the number visible before making the person accountable
You cannot hold someone accountable for a number they cannot see. One owner per indicator, the indicator visible to everyone, a review on a fixed cadence. From there, trade-offs get made on data instead of by asking you.
4. Fix what only you can do
Write the list. It is shorter than you think: usually direction, key hires, irreversible decisions and a few relationships. Everything not on that list is delegable — including, at first, imperfectly.
It took me years to get out of delivery at Sortlist. The unlock: listing what only I could do — and delegating everything else, even imperfectly at first.
My one-pager did not exist in 2016 — which is exactly why I hit the wall: everyone optimised their corner, nobody held the same map. Since then: one page, one owner per line, a quarterly review. A frozen one-pager is a poster.
Year one: zero sales experience on the team. We invested €2,000 per person in sales training before anything else — 15 clients signed in 15 days, €500k raised right after, then 9 countries on the same transferred system. Not charisma: structure.
What the books that matter say
This subject is not new. Four books say the essential part, each from a different angle — and they complement each other more than they disagree.
The E-Myth Revisited
Most companies are started by excellent technicians who end up imprisoned by the craft they wanted to practise. The cure is not working harder in the business, but building the business: documenting, systematising, making reproducible what today exists only in your head.
The Goal
A system's throughput is set by its constraint, not by the sum of its parts. Improving anything other than the bottleneck produces no real gain — only inventory piling up in front of it. If the constraint is you, no hire anywhere else will unblock the company.
The Great CEO Within
The CEO's job is a finite list of things nobody else can do. Everything else gets delegated — in writing, with a named owner and a date, otherwise it is not delegation, it is hope.
CEO Flow
Making your teams autonomous is not a gift you hand out when you have time: it is the only way a leader gets their own time back. Autonomy is designed, not declared.
Frequently asked
Does hiring fix it?
Rarely, and often the opposite. Every hire opens another channel back to you. As long as decision-making stays centralised, a bigger team produces more requests, not more autonomy.
How long does it take to get out?
Getting out entirely takes years — it is a change of role, not a project. But lifting the main constraint is measured in weeks: the job is to identify THE bottleneck, not to reorganise the whole company at once.
Do I have to document everything before delegating?
No. Waiting for perfect documentation is the most common way of never delegating. Delegate a decision with its criterion and its limit, then document what practice reveals.
Is this a growth problem or a founder problem?
Both, in that order. The behaviour that created traction — deciding fast, holding everything, letting nothing go — is exactly what caps the company afterwards. It is not a character flaw; it is a skill that has reached the end of its returns.
What if my real problem is elsewhere — pricing, cash, the team?
That is common, and exactly why the diagnostic comes before the remedy. Founder dependency is sometimes the cause, sometimes the symptom of an economic or commercial constraint. Deciding which without looking at the numbers is guessing.
Does this also apply to companies that are doing well?
Especially those. A struggling company looks for solutions. A growing company absorbs the dependency inside its growth — until the plateau where that same growth demands an organisation nobody built.