Make your business run without you

Most founders who ask how to make their business run without them want to keep control of what matters. They want to decide which decisions stay theirs, give the rest a named owner, and have their team carry the day to day to their standard.

That takes a sequence of steps. Skip one and the work either never starts or does not last. This is Changeover, the four-phase method I use with founders of established businesses of 10 to 100 people to move the work from one person’s head to a system their team runs.

The details shift for every business, but the shape holds: survey where the business still leans on you, design the system that carries it, transfer the decisions to named people, then test that the handover holds.

Phase 1. Survey: see where it still leans on you

It starts with a clear-eyed look at the business as it actually runs today, rather than the version in your head. The Survey uses 20 indicators across five areas: customers, decisions, knowledge, team, and systems and authorities. Together they show where decisions pile up on you, where work cannot move without your say-so, and where the team reaches for you out of habit rather than need.

You have felt all of it. Now it gets named and measured. Each area takes the colour of its weakest indicator, and there is no single score to average the weak spots away. Most founders find the picture sharper, and the gaps more fixable, than they expected.

What you walk away with: relief. You finally see the shape of the thing, and a map of where the dependency concentrates across the five areas.

Phase 2. Design: decide who owns and decides what

Before anything moves, get clear on what you want from this. There is no single right answer:

• Some founders want to sell.
• Some want to step back but keep the ship.
• Some just want to stop being the person everything runs through.

Your version of freedom shapes the design. There is no point building towards an exit you never intended to make.

The design then covers five things, written down so the team can use them every week:

1. Who owns what. Clear roles and accountability, so every outcome belongs to someone.
2. Who decides what. You keep the decisions that matter most; the rest have a named owner, with clear limits.
3. How work flows. Sales, customer communication and suppliers redesigned and owned, so the knowledge comes out of your head and into the business.
4. When the team meets. A steady weekly rhythm, so the business can be steered without being watched.
5. The numbers. What to measure, how, and who owns each number.

Software comes second, and only where a step needs it.

What you walk away with: a design that is yours rather than a template’s. The rest of the method is built around it.

Phase 3. Transfer: hand the decisions to named people

This is the part that actually moves things. You do not rebuild the whole business at once. You start in one area, hand its decisions to named people, and coach the managers who take them on. Then you move to the next.

Your team builds it with you, so by the time an area is done, they own it. It is quieter than it sounds. A decision that used to come to you gets made well by the person who now owns it. Then another.

What you walk away with: the first time something important happens and nobody needed to ask you.

Phase 4. Test: prove the handover holds

The change only matters if it lasts past the work. So every handover is tested: a task counts as handed over only when a named person has run it for four weeks without the founder stepping in. Along the way, you check:

• Does it still run when you are not watching?
• Does it hold under a hard week, an absent founder, a key person away?

When the business can carry its own weight, the work is done. What is left goes deeper than software you bought or a person you hired: a business that no longer needs you in every room, and a founder who gets to decide, for the first time, what they actually want to do with that.

What you walk away with: control without the load. You keep the decisions that matter most; the rest have a named owner. By choice, and before you burn out.

How long does each phase take?

For an established business of 10 to 100 people, this is a multi-month arc rather than a sprint:

Phase	Typical shape	Depends on
1. Survey	1 to 2 weeks of honest assessment	Your willingness to see the real picture
2. Design	Built with your team before anything moves	Clarity on what you want
3. Transfer	The bulk of the time, months per area	Breadth of the dependency
4. Test	Four weeks for each handed-over task	How well phase 3 was built

For Mike’s property business, a real client with a turnover of around £40M a year, the core build took about 12 months, from founder-run to founder-led. Ten of his 20 recurring decisions moved off his desk, and in October 2026 he left for a four-week holiday. (Approximate figures.)

The mistake most attempts make

The instinct is to reach for a tool (a CRM, project software, an AI assistant) and impose it on the business. It almost never works, because the tool has nothing to carry. Nobody has designed how the business should actually run, so the software just digitises the chaos.

Process design comes first. Software comes second, and only where a step needs it. That ordering is the whole game.

---

Want to see where your business still leans on you before you start? Take the free Self-Check: 20 questions across the same five areas, about ten minutes, with a red, amber or green colour for each area and a short list of where to start. The report appears on screen; no email needed.

Frequently asked questions

How long does it take to make a business run without its founder?

For an established business of 10 to 100 people, the typical arc is about 12 months from founder-run to founder-led, working one area of the business at a time. Each area has to be designed, handed over to named people and tested, which is why progress is measured in months per area rather than weeks.

Is making a business run without you the same as selling it?

No. Selling is one possible reason to do the work, and stepping back, taking real time off or simply no longer being the bottleneck are equally valid. The method produces a business that runs on its system while the founder keeps the decisions that matter most; what the founder does with that freedom is a separate decision.

Do you need to hire more people to make the business run without you?

Often no. Founder dependency is usually structural rather than a headcount problem: the playbook lives in the founder's head, decision rights are implicit, and the team lacks the system to carry the work. Hiring without building that system only moves the dependency onto someone new.

What happens if you skip the testing phase?

The change does not hold. A task counts as handed over only when a named person has run it for four weeks without the founder stepping in, and skipping that test is why most autonomy efforts quietly revert within a quarter.

Do I have to do all four phases?

No, but skipping the Survey or the Test is where most attempts fail. The Survey tells you what to change; the Test tells you whether it worked.

Can I run the Transfer across the whole business at once?

You can, but I would not. Running it in one area first, as a small prototype rather than a manifesto, lets it prove itself before it touches the rest. Earned trust scales; imposed change does not.

Is this the same as hiring an operations consultant?

The output is different. A typical consultancy flies in, takes a look, and leaves with a templated report. This method builds the system with your team, using your own tools, and proves the handover, so it stays after the engagement ends.

What if I do not want to sell or step back, and just want my life back?

That is the most common reason, and it is a completely valid version of "freedom". The Design starts from what you want, so the method serves your definition rather than a default.