What the bottleneck actually is

Every year, somewhere between $1M and $3M, founder-led businesses hit the same wall.

The business isn't failing. The founder knows what needs to happen. There's a plan, there are goals, there's a team. And yet the same items show up on the quarterly review that were on last quarter's. The team is capable individually and stalls the moment the founder steps back. Eleven Slack messages before 9am, all of them decisions that someone else should be making.

I've watched this pattern repeat across seven Inc 5000 runs and two companies. It looks different on the surface each time, a product company, a services firm, a SaaS business, but the underlying structure is always the same. The founder has become the bottleneck.

Not through any failure of effort or intelligence. Usually because of the opposite.

The question I ask early

There's one question I ask every founder I work with early on. It surfaces the problem faster than any audit or org chart review: if you were unavailable for five days (genuinely unavailable, phone off, no messages), what breaks first?

Most can answer immediately. They don't have to think. And what they describe isn't a technical crisis or a client emergency. It's decisions. The team doesn't know which client to prioritise. The head of sales doesn't know whether to proceed with the proposal. The marketing lead wants sign-off on something that shouldn't need it. Everything that usually goes through the founder, stops.

That's the bottleneck. Not the strategy, not the product, not the market. The decision-routing.

Why founders misdiagnose it

When a business stalls here, the instinct is to hire better people, work harder, or build a better strategy. Sometimes those things help. But the constraint is usually none of them.

What's actually missing is the operating layer: the structures that mean decisions get made without the founder, the planning rhythms that create alignment without constant check-ins, the accountability systems that keep things moving when you're not in the room, the clarity about who owns what so the team doesn't need permission to act.

I spent nine years at The ASK Method Company building exactly this. Revenue went from $2M to $24M, the team from 5 to 100+, and at some point Ryan stopped being the bottleneck. Not because he stepped back or stopped caring. Because we built the machine that didn't need him at the centre of every decision.

Most founders don't have a COO doing this. Most don't need a full-time one. But most also don't have the operating layer, so the business stays stuck at whatever size the founder can personally hold together.

What to do with the five-day test

Whatever you named as the thing that breaks is the first thing to fix.

If it's decisions, you need decision rights. If it's alignment, you need a planning rhythm. If it's accountability, you need a review structure. If it's everything at once, you need a sequenced 90-day plan before you need anything else.

None of this requires a restructure or a new hire. It requires being specific about what the operating layer needs to look like and building it deliberately, rather than hoping it assembles itself over time.

The business doesn't need you to work harder. It needs the part of you that it currently runs through to exist somewhere outside of you.

If you want a faster read on where the bottleneck actually sits, the two-minute scorecard shows you which of the four areas is the constraint.