How long does the founder-to-CEO transition take?

The first visible changes — a decision transferred, a process written, a weekly rhythm running — take weeks. Reaching the point where the business genuinely operates without you for a fortnight usually takes a year or more of consistent practice, because it depends on other people becoming more capable, not only on you changing.

Do I need to hire a general manager first?

Rarely, and not first. Hiring a manager into a business with no documented process and no performance framework tends to produce an expensive disappointment, because the new person inherits the same ambiguity you were living with. Build the system, then hire into it.

What if my team resists taking decisions?

Usually they are not resisting; they are protecting themselves. In a business where decisions have historically been reversed by the owner, the safest behaviour is to wait and be told. That changes when you leave a decision alone and back the person publicly the first time they get it slightly wrong.

How to Move From Founder to CEO (A Practical Sequence)

Most advice about becoming a CEO is written for people who were appointed to the job. Founders are not appointed. You reach a point where the business needs a CEO, notice that nobody else is going to be it, and then get on with the same day you had yesterday.

What follows is a sequence that works in an ordinary owner-led business — no board, no HR department, no budget for consultants. It assumes you have between four and forty staff and no spare hours in the week.

Week one: find out where your time actually goes

Do not redesign anything yet. For five working days, write down what you did in thirty-minute blocks. Keep it on paper or in a notes app; do not build a system for it.

At the end of the week, mark each block with one of four letters. D for work only you can do because it genuinely requires the owner — a bank negotiation, a hiring decision, direction. S for work someone else could do if they were shown how. N for work nobody needed to do. L for leadership work: thinking, planning, developing someone, looking at numbers.

Almost every founder who does this exercise honestly finds the same pattern — a week that is 70% S, a little N, some D, and almost no L. That is not a character flaw. It is the natural result of a business that grew around one person. But it tells you exactly what has to change, and it gives you a baseline to compare against in three months.

Week two: transfer one decision, not one task

The instinct is to start delegating tasks. Tasks come back. What actually reduces your load is transferring a decision, because a task delegated without decision rights just returns to you for approval.

Pick one recurring decision from your S list that is low-risk and high-frequency. Discounts up to a limit. Which supplier to use for a routine order. Whether to accept a customer return. Then write down four things and give them to the person taking it on:

The decision they now own, stated plainly.
The boundary — the amount, the circumstance, or the threshold beyond which they must ask.
What a good outcome looks like, so they can judge themselves before you do.
When you will review it together — a specific date, not "let’s see how it goes".

Then, and this is the difficult part, stop being consulted on it. If the person comes to you inside the boundary, hand it back: "That is yours now — what are you going to do?" Say it warmly and say it every time. Delegation fails far more often through the founder quietly resuming the decision than through the employee refusing it.

Week three: write down one thing that only lives in your head

Choose the process whose failure would embarrass you most in front of a customer. Describe it out loud as though you were teaching a competent new hire, and write what you said. Two pages is plenty. Number the steps, mark the two or three points where things usually go wrong, and note what to do when they do.

Then have someone follow it while you say nothing. Every place they hesitate is a gap in your writing, not a failure on their part. Fix those gaps and you have your first real system.

Why two pages beats a manual

Founders often postpone documentation because they imagine a full operations manual. Nobody in a busy business reads a manual. One clear page per process, written in the words your team actually uses, gets followed. Start with the process that hurts, not with the process that is easiest to describe.

Week four: install a rhythm so you can stop checking constantly

Founder dependency is often just an information problem. You stay involved in everything because it is the only way you know what is happening. A management rhythm replaces surveillance with reporting.

The minimum viable version is one thirty-minute meeting a week with the two or three people who run things, covering the same four questions every time: what moved, what is stuck, what do you need from me, what is coming next week. Written notes, circulated the same day, with who-does-what-by-when.

It feels thin for the first fortnight. By the second month, problems start arriving in that meeting instead of arriving as emergencies on a Saturday.

Month two: learn your own numbers

A CEO who cannot read the accounts is a very well-informed operator. You do not need an accounting qualification. You need to be able to answer four questions without calling anyone: what did we sell, what did it cost us to deliver, what did it cost us to exist, and how much cash do we have relative to what we owe in the next thirty days.

If those answers are unavailable or take a week to assemble, that is the finding. Fixing it usually starts with insisting on a simple monthly summary you actually understand, and asking your accountant to explain one line of it each month until nothing is mysterious.

This is where many founders discover that their most popular product is their least profitable. It is an uncomfortable month and a valuable one. More detail: cash flow versus profit.

Month three: protect the leadership block

By now you should have a little time back. It will disappear immediately unless you claim it. Put two hours in the same slot each week, before the business is fully awake if necessary, and use them only for L work: hiring, performance, pricing, direction, developing someone.

Treat it exactly as you would treat a meeting with your largest customer. The business will test this boundary constantly, and how you respond in the first month decides whether it survives.

The founder asks how to get everything done. The CEO asks why it needed them at all.

What this looks like when it is working

The signal is unglamorous. Decisions get made without you and you find out afterwards, and you agree with most of them. Problems surface in a meeting rather than in a crisis. A new person reaches competence in weeks instead of months. You know your margin.

The real test is the one B2CEO opens with: take a full week away and see what you come back to. That is not a reward at the end of the process — it is the diagnostic.

Where this fits in the wider transition

The sequence above deliberately touches four of the six areas that determine whether an owner-led business can scale: people, performance, process and profit. The full framework, including productivity and the practical use of AI, is set out under the six-pillar framework, and the broader concept is explained on from founder to CEO.