The founder bottleneck (and how to dissolve it)
Most scaling problems are really one problem in disguise. A short framework for spotting where the founder is the constraint.
Most founders think they have a scaling problem.
They don't.
They have a control problem disguised as a scaling problem.
The uncomfortable truth
At some point, every business slows down.
Things start to feel heavier.
- decisions take longer
- execution stalls
- simple tasks become bottlenecks
So the instinct is:
"We need more people." "We need better tools." "We need to optimise."
But most of the time… the founder is the constraint.
Why this happens (and why it feels right)
In the early stages, this is exactly what works.
The founder:
- makes every decision
- drives every action
- holds everything together
Speed comes from centralisation.
But what creates momentum early… becomes the bottleneck later.
The moment it hit me
I realised this the hard way.
I was deep in things I shouldn't have been doing:
- hosting webinars
- dealing with technical setups
- managing logistics
- trying to make everything run perfectly
Not because I was the best person for it. But because I was the one who could do it.
And that's the trap.
The real problem
The issue isn't workload. It's dependency.
When everything:
- needs your input
- requires your approval
- depends on your involvement
You don't have a business. You have a system that runs through you.
And that doesn't scale.
The reframe
Where the bottleneck actually lives
Strip it back, and the founder bottleneck shows up in three places.
Approvals, direction, prioritisation. Nothing moves without your input — so everything slows to your speed.
You hold the context. Conversations, relationships, history. People keep coming back to you because you are the source of truth.
You're doing work you shouldn't be doing. Emails, coordination, repetitive tasks, technical setups. It feels productive — but it's misallocated effort.
The shift
The question that changes everything is:
Why does this depend on me at all?
Not "How do I do this faster?" Not "How do I get better at this?"
But: "Why am I in this workflow in the first place?"
The framework: spot yourself as the bottleneck
Three honest questions. Answer them and you'll see the constraint clearly.
What only moves when I move?
Look at what's waiting on you — approvals, decisions, green lights. That's your decision bottleneck.
What only exists in my head?
Look at where you are the system — knowledge, relationships, context. That's your information bottleneck.
What am I doing repeatedly?
Look at what keeps coming back to you — emails, coordination, manual tasks. That's your execution bottleneck.
How to dissolve it
This isn't about stepping away. It's about redesigning how things work.
Not every decision should require you. Define rules, create frameworks, reduce ambiguity — so decisions happen without you.
If it lives in your head, it doesn't scale. Document thinking, store information, make it accessible — so others (or systems) can use it.
If something repeats, it shouldn't be manual. Automate, template, delegate to a workflow — not to your inbox.
The role of systems (and AI)
Before, the only way to remove yourself was to hire people, delegate tasks, build teams.
Now there's another layer.
That's the shift.
The part nobody talks about
Being the bottleneck feels good. It makes you feel needed, important, in control.
Letting go means trusting systems, accepting imperfection, giving up control.
But holding on is what keeps you stuck.
Why this matters now
We're entering a world where execution is faster than ever, tools are more powerful, and opportunities move quickly.
Which means bottlenecks become more visible.
And the biggest one is usually 👉 the founder.
What I'm learning
Most scaling problems aren't operational. They're structural.
Because the real constraint isn't the business. It's how much of the business depends on you.
The Console — my personal newsletter, in your inbox.
Long-form pieces, frameworks, teardowns, and the thinking behind what's being built. Stay close to the work — and to what's next.
Read by founders, operators, and people building what's next.