When a founder should leave

The answer is not on the calendar

The question of when a founder should leave the company almost never enters the coaching room in those words. It arrives in disguise: growth is said to need a different kind of leader, tiredness is mentioned, an investor's expectation of professional management is relayed. And when the sentence is finally spoken, it is spoken as if it wanted a date — as if the right answer could be a quarter, an anniversary, a revenue threshold. We looked at how a handover actually works in a separate essay; this one sits with the question that comes before it: when.

A calendar cannot answer it, because the question is not really about the company. Whether the company is ready is something other people can tell the founder — the leadership team, the investors, even the numbers. What nobody can say on the founder's behalf is what is happening inside the founder's own day. That is why the question ends up at our table; it belongs to the family of questions whose answer lives in the person asking it.

Whose question it is

The honest form of the question is not about the company at all; it is about the day: how much of what I did this week could only have been done by me. Answering it requires looking not at the calendar but at the day — and the day is the place a founder examines least.

An audit of the day

Empty a founder's week out honestly and two kinds of work appear. The first is creation: things that would not exist without them — a product call, trust built with a critical customer, a correction of course nobody else could see. The second is approval: things that would happen anyway, only more slowly — signatures, last words, reviews. The date the question is looking for hides in the ratio between the two.

• Creation leaves a trace: a sentence or a decision that did not exist before that week, and visibly came from the founder.
• Approval leaves a queue: decisions waiting at the founder's door, and a company that speeds up and slows down with one person's calendar.

The speed limit

When the day turns to approval, the founder becomes — usually without noticing — the company's speed limit. Decisions wait; the owners of waiting decisions learn to wait; the best people start managing the founder instead of the work. The sign that the time is near is not that the company cannot manage without the founder, but that the founder's day has filled with approval. If the company still brings everything to the founder, that is evidence of how the system was built, not of how indispensable its builder is.

Between too early and too late

The distribution we see in practice is not symmetrical: founders who leave too early are rare, and founders who leave too late are common. The delay is seldom about money or power; it is about identity. The company is the answer the founder has spent years giving to themselves — this is who I am, this is what I built. Stepping away from that answer reads as a loss at any revenue figure, and a person can find a fresh reason to postpone a loss every quarter.

The signature of each mistake

Leaving too late carries the signature described above: a calendar turned to approval, waiting decisions, a team that manages its founder. Leaving too early carries a different one: the founder moves away from something rather than toward something. An unresolved tension between partners, an unexamined exhaustion, a decision that will not close — a company left in order to escape these finds its founder again in the new day. The simplest test of timing is a test of direction: is the leaving away from something, or toward something.

Leaving is not one door

The word leaving inside the question misleads too, because it is spoken as if there were a single door. The options are a range: handing over the CEO role and staying on the board, keeping only the product, staying in the company while genuinely giving up the last word, or walking out entirely to build something new. Which door is right is decided as much by what the founder wants their day to hold as by what the company needs.

The day must change, not the title

The shared trap across these options is a title that changes while the day does not. A founder who becomes chairman but still sees every decision has walked through no door at all; only the name on the door has changed. Whether a leaving has actually happened is told not by the title but by an audit of the founder's new week. This is why, in our work, the conversation about the day comes before the conversation about the title; the way we work is built around that order.

From the field

What the founders who time it well have in common is that they do not ask the question once, and large. They start asking it in small doses, years earlier: a month of distance is tried, a single veto is handed over, a meeting is deliberately missed. Each experiment returns information — not about the company, but about the founder's own response to absence.

The honest form of the question

The second observation: taken honestly to its end, the question changes shape. When should I leave the company becomes, as it is worked, what do I want my day to be made of; and the second, unlike the first, is a question that can be answered. The date then appears on its own, as the shadow of that answer.

And last: the hardest moment is not the decision but its first test — the day the first big decision taken in the founder's absence turns out to be wrong. The founder who does not walk back in on that day has answered the question. The date of leaving is never written on a calendar in advance; it is recognised afterwards, in the first day the founder did not come back.