For most owners of small businesses, the first ten years are an exercise in being needed. Decisions queue up because you're the one who knows the customer, the supplier, the contract, the awkward history with the bookkeeper. You become the person everything routes through, and for a long time that feels like control. It feels like the work itself. Then, somewhere around the twentieth hire, that same instinct stops protecting the business and starts capping it.

This is the founder bottleneck. It isn't laziness or arrogance or a missing skill. It's the slow drift from being someone who can do anything to being someone who has to do everything. The two are very different positions. The first builds a business; the second prevents it from growing.

The pattern that works at five and breaks at twenty

At five people, being in every decision is fine; it's why the work is good. The team is too small for delegation to make sense, the cost of a bad call is high, and you're closer to the customer than anyone else. Founder-as-decision-maker is the right model for that stage.

At twenty, the same pattern is the constraint. The discount approval queue stretches. The supplier swap waits for your call. A new hire's first-week question goes to you because nobody else has been allowed to answer one. Growth at this stage is capped by managerial capacity, not market demand. The thing that grew the business now slows it down, and the team — the same team you hired to take work off you — learns to wait for you instead of move without you. Ask the Banker put a name to this in their 2026 report — the small-business execution gap — and it's the same pattern EINEdge has been writing up under the heading of founder discipline: owners carrying the day-to-day judgement load past the point at which their week can hold it.

The founder model fades rather than fails. There's no day it breaks, and so for a long time you tell yourself you're being thorough.

The week audit

The fix starts with looking at what's actually on your week. Most owners have never done this — we plan in lists and we measure in feelings. A week's worth of calendar, sorted into four categories, tells the truth:

  1. Decisions only you can make. The contract a director signs. The hire at executive level. The bet-the-business call. Maybe five per cent of the week, often less.
  2. Decisions you happen to be making. Pricing on a job. A supplier swap. A discount approval. These could be made by someone with the right context, but you're the one who has it.
  3. Work you find yourself doing. Drafting the proposal. Approving the social post. Fixing the spreadsheet. There's no judgement here that requires you; you do it because you've always done it.
  4. Work you're hiding behind. The inbox. The status calls. The “quick look” at the design before it goes out. We tell ourselves these are oversight. Most of the time they're anxiety dressed as activity.

Categories three and four are the bottleneck. They feel productive, which is why they survive. They're also the reason the team can't move without you.

The discipline of letting go

Dan Amos has run Aflac for 36 years and gave HBR an interview last month that contained a line worth keeping. Asked what he had learned about leadership across that time, he said: listen for the silence. When a meeting goes quiet, it isn't because everyone agrees. It's because people don't want to disagree with the person in charge. The longer you're in the room, the more silence you create.

This is the founder bottleneck phrased in a different language. Being needed narrows the conversations around you. People stop bringing the hard call to your desk because they've learned the answer is “leave it with me.” And the business slowly reshapes itself around your inbox.

Letting go doesn't mean stepping back. It means choosing which decisions still need you, deliberately, and then trusting the team to live with the others. That trust has a cost — they'll make calls you would have made differently. Some will be worse. A few will be better. The first time a team member makes a decision that costs you a customer, the temptation to take the work back is almost physical. What you're aiming for is movement; the business needs decisions made, not decisions held back for the one person who isn't free to make them. Where the line falls between trust and abdication is rarely obvious — I'm still not sure I always read it right, and the founders I know best say the same.

This is the place where “working on the business” becomes a discipline rather than a slogan — a weekly choice about what work you accept as yours, made fresh every Monday.

What this actually looks like

You audit the week. You name the bottleneck out loud, first to yourself and then to the team. You move category-three work out, with a proper handover and an agreement on what “done” looks like. You move category-four work out too, and you accept the discomfort of not being copied in. You set a rule for category two: if someone has the context, the decision is theirs, with a written threshold so that “I wasn't sure if I should ask” stops being a recurring conversation. And you protect category one with both hands, because that's the work only you can do.

There's no project plan in there. You sit down on a Monday with the week ahead and ask, of every meeting and approval, which of these genuinely need me — and which of these are me, being needed.

The founders who broke through

The owners I've watched break past the twenty-person ceiling didn't get better at managing. They got worse at being indispensable. They made themselves a little harder to reach, a little less central to the day-to-day, and the business — given the space — grew into it. Being needed felt like the job for a while; somewhere around twenty people, it became the cap on the work they actually wanted to do, and they had the discipline to recognise the swap.