What to Delegate at Each Stage: A Founder's Timeline
A visual timeline of what a founder typically needs to hand off at 5, 15, 30, and 50 people — and the common trap of holding on past the point it's serving anyone.
Delegation for a founder isn't a single decision made once — it's a series of specific handoffs that need to happen at fairly predictable points as a company grows, each one uncomfortable in a slightly different way.
The timeline
Why each stage is uncomfortable in a different way
~5 people, letting go of admin: The easiest stage in principle and still commonly delayed, because routine tasks feel fast to just do personally rather than explain to someone else — even though the explaining pays for itself almost immediately once the task recurs.
~15 people, letting go of delivery oversight: Harder, because it means trusting the actual quality of work the founder used to personally guarantee. This is the stage where the stakes/familiarity framework becomes genuinely useful — not everything gets released at once, but the direction has to shift from doing to reviewing.
~30 people, letting go of individual hiring approval: Uncomfortable because hiring feels uniquely consequential, and a founder who's approved every hire personally has a real, earned sense that this matters too much to delegate. Past this size, though, being the bottleneck on every hire slows the business down in a way that a well-briefed hiring manager, given real criteria and trust, usually doesn't.
~50 people, letting go of being the default decision-maker: The hardest and most identity-linked stage — for many founders, being the person everyone naturally brings decisions to has become part of how they experience their own role, and stepping back from that is a genuine loss, not just a logistical handoff.
The trap: waiting for a feeling of readiness
The honest, common failure mode isn't delegating too early — it's the founder waiting for a feeling of readiness that often never arrives on its own, since there's always a reason this particular moment feels like the wrong time. The stages above work better as headcount- or workload-triggered decisions than as something deferred until it feels emotionally comfortable, because that comfort tends to arrive, if at all, only after the delegation has already happened and proven itself.
What holding on too long actually costs
Beyond the founder's own capacity — which a time audit will surface directly — holding onto a decision past the point the business has outgrown needing the founder specifically also slows down whoever's waiting on that decision, and can quietly signal to a capable hire that they aren't yet trusted with something they're actually ready for. The cost isn't only the founder's bottlenecked time; it's the accumulated frustration and underused capability of everyone waiting on the other side of that bottleneck.
Using this timeline honestly
The specific headcounts are directional, not a fixed schedule — a business with unusually complex, high-stakes work might need to hold certain approvals longer; a simpler, more standardized business might delegate earlier than the stages suggest. The more useful exercise than matching the exact numbers is checking, honestly, whether the founder is still personally doing something on this list well past the point the business has grown beyond needing them to.
Co-founders don't always move through this at the same pace
In a company with more than one founder, it's common for each person to be at a different point on this timeline for their own area — one co-founder may have fully let go of individual hiring approval while the other is still personally reviewing every candidate for their function. This isn't necessarily a problem, but it's worth naming explicitly between co-founders rather than assuming both are progressing at the same rate, since a mismatch can create real friction if one co-founder's team feels more closely managed than the other's for reasons nobody's actually discussed.
The short version
Founder delegation isn't one decision — it's a predictable sequence of handoffs, each uncomfortable for a different reason, moving from doing the work personally, to overseeing it, to no longer being the default decision-maker at all. The common failure is waiting for delegation to feel comfortable before doing it, when the more reliable trigger is a specific headcount or workload signal — and the more common cost, by far, is holding on too long rather than letting go too early.
Frequently asked questions
Is there a right time to start delegating as a founder?
Earlier than most founders do, based on how often 'I'll delegate once things calm down' turns out to mean 'never' — the honest trigger is usually a specific headcount or workload signal, not a feeling of readiness that may not arrive on its own.
What's the most common thing founders hold onto too long?
Final approval on decisions that a capable hire could own outright — not because the founder distrusts them, but because letting go of a decision they used to make personally feels riskier than it actually is.
Does this timeline apply the same way to every business?
The stages and general direction apply broadly, but the exact headcount where each transition happens varies by business complexity and growth rate — use it as a directional guide, not a fixed schedule.
What happens if a founder delegates too early, before the business is ready?
It's a real risk, but the more common failure by far is delegating too late — most founders err toward holding on longer than the business actually needs them to, not the reverse.