Free guide - The 5 Levels
Every business runs on a system, whether anyone built it on purpose or not. These are the five levels that system goes through, and what it actually takes to move up one.
The video told you what the levels are. This tells you how to get from where you are to the next one, including the tools I’d actually use.
Start here
Find your level first
You can’t climb a ladder until you know which rung you’re on. Read these in order and check the ones that are honestly true today. The first one you can’t check is your level.
- Someone other than you can say what’s happening today without asking you.
- Your top five recurring jobs get done the same way no matter who picks them up.
- A new client goes from inquiry to scheduled without anyone retyping the same information.
- You can look at one screen and know if the business is healthy this week.
- You went a full week without being the person a decision waited on.
Be honest on that last one. Most owners want to check it and can’t.
Level 1 to Level 2
Get it out of your head
You’re stuck here if
You’re the only one who knows what’s happening today. Every question comes to you because you’re the only place the answer lives. If you got sick tomorrow, the week would stop.
Build these, in this order
- One list of the work. Every job or client, and what stage it’s at. One place, not five. A spreadsheet is fine to start.
- One calendar the team can see. Not your personal one. The one that says who is doing what, and when.
- Write down how you price. You already have rules for this in your head. Get them on paper, even if they’re rough.
- One front door for new work. One inbox, one form, one number. Not four channels you check when you remember.
Don’t buy anything yet
Use what you already pay for. A shared spreadsheet and a shared calendar will carry you through this entire level. Software at Level 1 is a way of feeling productive without deciding anything.
You don’t need help for any of this either. If someone tries to sell you a consultant at Level 1, they’re selling you software.
Done looks like
Someone can answer “what’s happening today” by opening something, instead of by asking you.
The trap
Buying software before you’ve written down how you actually work. The tool becomes a second place to look, and now there are two versions of the truth. Write it down first. Pick the tool second.
Level 2 to Level 3
Make the work repeatable
You’re stuck here if
Things are written down somewhere, but every person does them a bit differently. Quality depends on who picked up the job. This is where most businesses stop, and it’s why a competitor your size does twice your volume with the same number of people.
Build these, in this order
- Interview the people doing the work. Not just yourself. You remember how the process is supposed to go. They know how it actually goes, including the workarounds nobody told you about. Sit with each person and have them teach you their job like you’re the new hire. This is the step everyone skips and it’s the one that matters most.
- Map it before you write it. Draw the process as a diagram first. A picture exposes the gaps and the loops that a document hides, and you’ll find handoffs nobody owns.
- Turn each map into an SOP. Same five headings every time: what it’s for, when to use it, a recording of someone doing it, the written steps, and what done looks like.
- Own SOPs by seat, not by person. Write them for the chair, not for Sarah. Two people in the same seat run the same SOPs, and when Sarah leaves the process doesn’t leave with her.
- Write down the decisions you keep re-making. When you discount, when you say no, when you escalate. Those are policies, and they’re what actually stops people needing you.
Tools for this level
To map processes: Whimsical or Miro. Whimsical is faster to learn and better for flowcharts. Miro is better when you want one big live board the whole team works on together. Either is fine, pick one and stop shopping.
To store everything: Notion or ClickUp. This is the one place SOPs, policies, and processes live, and it needs to be somewhere people already have open.
When we build this for clients we use Notion, every time. That’s a deliberate choice, not a preference. Notion is the only tool we ask a client’s team to genuinely learn, because one operating home the whole company works out of beats five specialist tools nobody opens. We embed the diagrams straight into it so there’s still only one place to look.
Done looks like
A new hire does the job correctly in their second week, working from the document, without you sitting next to them.
Where this gets hard on your own
Interviewing your own team. People tell the owner what they think the owner wants to hear, and you can’t interview yourself at all. Someone from outside gets the real process in a couple of hours, because there is nothing at stake in telling them. If you’re doing this yourself, at minimum have someone sit in who isn’t their boss.
The trap
Trying to document everything at once. You’ll write forty documents nobody opens and you’ll never want to look at an SOP again. Start with the five jobs that happen most. Five that get used beat forty that don’t.
Level 3 to Level 4
Connect it and take out the busywork
You’re stuck here if
The work happens the same way every time, but people are still carrying it between systems by hand. Copying the client from the CRM into the invoice, then into the calendar, then into a spreadsheet.
Build these, in this order
- Map the handoffs. Every point where work passes from one person or one tool to another. That list is your whole to-do list for this level.
- Let AI find the automations for you. Give it your SOPs and a list of every tool you pay for, then ask it where the busywork is and what should be automated. It reads your whole process in a minute, and it will spot the double entry you stopped noticing years ago. Then have it help you build them.
- Kill the double entry first. Anywhere someone types the same thing twice is an automation waiting to be built. Start with the one that happens most often, not the one that’s most interesting.
- Connect marketing to sales to delivery. A lead should become a scheduled job without anyone rekeying it.
- Build the AI workspace properly. One project per department, each loaded with that department’s SOPs and policies. A saved prompt for each recurring job. Connected to the docs, sheets and calendar it needs to read, with permissions so people see their own department. Keep it internal, pointed at your team and never at your customers.
A word on CRMs
I’m not going to name one. This is the tool choice that genuinely depends on your business, and anyone who tells you there’s a single right CRM is selling one.
A field service company needs scheduling and dispatch. A consultancy needs pipeline and proposals. A high-volume business needs automation depth. Pick for how you actually sell and deliver, not for the review site.
The test that matters: can it hold your process, and will your team really use it? A CRM nobody updates is worse than the spreadsheet it replaced.
Done looks like
A new client moves from inquiry to scheduled and invoiced without anyone copying information from one screen to another.
Where this gets hard on your own
Two things. Auditing the whole customer journey end to end, from first contact to paid invoice, because you are inside it and you stopped seeing the friction years ago. And automation past the simple stuff. Connecting two tools is a weekend. Building a layer that handles the exceptions, fails safely, and doesn’t quietly break when someone renames a field is a different job.
The trap
Automating a process that’s still broken. You’ll get the wrong outcome, just faster and in more places. If a job isn’t reliable when a human does it, it isn’t ready to be automated.
Level 4 to Level 5
Hand over the running of it
You’re stuck here if
The machine works, but you’re still the one watching it. You are the dashboard. Everything runs well right up until you look away.
Build these, in this order
- Choose the few numbers that tell you the business is healthy. Five or six, not twenty. If you can’t explain why a number matters, cut it.
- Put them somewhere live that updates itself. A number someone has to rebuild by hand every week is a number that stops getting built.
- Give every seat an owner and a job. Not a job title. What that seat is accountable for, and what it gets to decide without asking you.
- Give each owner their own number. One they can actually move. That’s what turns a responsibility into ownership.
- Set the rhythm. A short weekly on the numbers and what’s blocked. Same day, same shape, every week.
Don’t buy a dashboard tool
You almost certainly don’t need one. The team is probably already keeping the numbers somewhere. Put them in one sheet, embed it where people already look, and you’re done. Boring, and it works.
If you want something that reads well on a phone, have AI build a simple page that pulls from that same sheet. You get the view without buying and learning a reporting platform.
Either way the sheet stays the source of truth. Start there and only move up if you outgrow it, which takes longer than people think.
Done looks like
You can miss a week and find out what happened by looking at the dashboard, not by getting a phone call.
Where this gets hard on your own
A dashboard on genuinely live data. A sheet someone updates by hand is fine, and it is where you should start. Pulling numbers automatically out of your CRM, your accounting, and your delivery tool into one view that is true every morning takes plumbing most owners don’t want to build or maintain.
The trap
Building all of it and keeping the final call on everything anyway. If every real decision still routes through you, you’ve built yourself a very nice dashboard and kept the job.
One test
Before you add any tool
Ask this every time, at every level: does my team have to create an account, learn it, and manage it?
If yes, it has to earn its place. If no, because you run it in the background or they already use it, it’s basically free to add.
Most stacks get bloated because nobody applies that test. The team should genuinely learn two things: the place the work lives, and the AI workspace. Everything else should be invisible to them.
Next
What to do this week
Go back to the checklist. Find the first thing you couldn’t honestly check. That’s your level, and the section under it is your work.
Then do the first build item in that section. Just the first one. Most owners stall because they try to jump two levels at once, and the level you skip is the one that breaks later.
Scale without the chaos
Ready to build a business that doesn’t depend on you?
Start with a call. We’ll find the bottlenecks and the dependencies that keep the business tied to you, and you’ll leave knowing what to fix first whether you work with us or not.