You Already Have Systems. They're Just Locked In Your Head.

The Short Version: Most owners think systemising means building something from nothing. It doesn't. Your business already runs to a standard, and that standard is consistent, which means a system already exists. It just lives in one person's head instead of on paper. That's why it only works when you're in the room, and why the business rebuilds the same decisions from scratch every single time. You have probably already proved the standard can hold without you. You just didn't write it down, so it didn't count. The work isn't inventing a system. It's extracting the one you've got.

What this post covers:

• Why "we're too bespoke to systemise" is almost always wrong
• The evidence you already have, and why you keep discounting it
• What it costs to re-decide settled questions every week
• The real reason it stays in your head, which isn't time
• How to get it out, starting with one job
• What changes, including what your business is worth

An owner I was working with recently opened a quote that one of his own people had put together. He read it, then read it again, and couldn't work out what he was looking at. It wasn't wrong exactly. It was just built a completely different way to how he'd have built it.

What he said next has stuck with me. Something along the lines of: surely we should be able to price this kind of work without going back to first principles and asking ourselves what a quote even is.

They had been doing that work for years. Hundreds of times. And every time somebody new touched it, the business started the argument again.

That is not a business without systems. That is a business whose systems are stored somewhere nobody else can reach.

You Already Have A System. You Just Can't Hand It Over.

Ask an owner how they price an unfamiliar job and you'll get a version of the same answer. They find a similar one. They think back to something comparable, adjust for the differences, and land on a number. And they're usually right, which is the interesting part.

That's not instinct. That's a system. There are inputs, there's a comparison, there are adjustment rules, and there's an output that's consistent enough to run a business on. Every step of it is real. None of it is written down.

Which means it can only run when one specific person is available, awake, and not on holiday.

This is where the objection usually arrives. Our work is bespoke. Every job is different. You can't systemise what we do.

I've heard that from engineering firms, construction firms, events businesses and leisure operators, and it's nearly always wrong in the same way. The work varies. The decisions don't. The questions you ask to scope a job are the same questions every time. The information you need before you can price anything is the same information every time. The shape is stable even when the content isn't.

You're not being asked to invent anything. You're being asked to write down what you already do.

The bottom line: If your business produces a consistent standard, a system already exists. The only question is whether it's stored somewhere other people can use.

You've Probably Already Proved It Works

Here's the part owners miss, and I see it constantly.

An owner told me recently that he couldn't take a week off. Not that he'd rather not, or that it was awkward. That he couldn't. A few minutes later in the same conversation, without noticing he was contradicting himself, he described the week he did take off, at the busiest point of his trading year. They organised cover. It held. He was barely contactable and nothing fell over.

He had already done the thing he'd just told me was impossible, at the hardest possible moment, and he wasn't counting it as evidence.

It's the same pattern everywhere. An engineering business I know runs repeat jobs for long-standing customers, work they've done dozens of times, and they still wait for someone to reprint the drawing before the job can start. The knowledge that the job runs fine is sitting right there in the fact that it's a repeat job. Nobody has turned it into anything reusable.

Every one of these businesses has proof that the standard can hold. A week that worked. A job that runs itself. A quote that was right without anyone checking. And in every case it gets filed as a one-off rather than as evidence.

If it happened once by accident, it can happen every time on purpose. That's the whole gap.

The bottom line: You are probably sitting on proof that your business can run without you. It didn't count because nobody wrote down why it worked.

What It Costs To Re-Decide Everything

Every time your team rebuilds a decision you'd already made, you pay for it twice.

You pay in time, obviously. The hours spent scoping something you've scoped forty times before. The reprinted drawing. The quote built from a blank page instead of from the last one.

You pay in variance, which is worse. Three people price the same job three different ways, and now your margin depends on who happened to pick up the phone.

But the real cost only shows up under load. An owner described it to me almost perfectly. Every department has its own problems, and every problem has a workaround that mostly works. It's fine, right up until several of them arrive in the same week. Then the workarounds fail together and you're in crisis mode, with late customers and a team firefighting instead of working.

That's what an undocumented system actually is. It's a business held together by people making good calls under pressure. It looks robust because it usually holds. It's fragile because it has no capacity in reserve.

And when you're the one making most of those calls, this is the same trap as the £2m ceiling. Growth stops at the limit of your personal availability, because that's what the business runs on.

The bottom line: Undocumented systems don't fail on normal weeks. They fail on the week everything lands at once, which is the week you can least afford it.

Why It Stays In Your Head

Owners tell me it's time. They'd document it if they had a spare fortnight.

I don't think that's it. Plenty of owners with time still don't do it.

The honest version came out in a session a while back, and it took some courage to say. The owner accepted the principle completely: find whoever does the job best, then have everyone do it that way. Then he admitted the problem. He thought he was the one who did it best. He wanted everyone else to work the way he worked, and they didn't, and it bothered him.

That's the real obstacle, and it's more common than the time excuse.

Because writing it down means somebody else does the work. Somebody else doing the work means it gets done differently. Differently feels like worse. So the standard stays in your head, where you can protect it.

Except that isn't protection. If the standard only exists inside one person, the business doesn't have a standard at all. It has a dependency. The thing you think you're guarding is the thing most at risk, because it can only survive as long as you do the work personally, and you can't do all of it forever.

Peter Boolkah put the mechanism well on a podcast recently. Every time you work really hard, he said, you're training the business to be dependent on you. You don't intend it. It happens anyway, one decision at a time. It's the argument running through his book, Your Business Sucks, which came out earlier this summer.

The bottom line: It stays in your head because handing it over feels like lowering the standard. In reality, keeping it there is what puts the standard at risk.

Getting Close Enough To See It Isn't Going Backwards

There's a fair objection here. I spend a lot of time telling owners to get out of the detail, and extracting a system means going straight back into it, at a level of detail most owners haven't touched in years.

Both things are true, and the distinction matters.

Getting close to diagnose is leadership. Getting close to operate is the trap.

You're going into the detail to describe the work, not to do it. You go in, you see it clearly, you fix the structure, and then you get back out. That's a different activity to picking up the job yourself because it's faster than explaining it, which is the habit that put you here.

If you can't describe how the work gets done, you can't delegate it. You can only do it or abdicate it.

The bottom line: Go into the detail to describe the work. Never to do it.

How To Actually Get It Out

Start with one job. Not a process map, not a manual, not a project. One real job you've recently completed.

Narrate it end to end. Talk through what actually happened, from first contact to finished work, out loud, to someone who'll ask awkward questions. Owners are often surprised by how useful this is on its own. One said to me halfway through that he could hear himself out loud for the first time, and that it suddenly made sense.

Fix the language before anything else. In one session we spent a good while separating an enquiry from a quote, because the business had been using the words interchangeably and it turned out everything downstream depended on the difference. Nothing else works until the words mean one thing.

Ask what someone else would need. Not what you need. You've got twenty years of pattern matching in your head. The question is what minimum information would let a competent person who isn't you produce the same result.

Get a second version. Ask whoever's next best at the job to write their own. Compare them. The overlap is your system. The differences are the conversation worth having, and sometimes their way is better.

Then build the shortcuts. Once you can see the pattern, most of your work resolves into a manageable number of standard shapes with a few variables each. That's where templates and bundles come from, and that's when it starts saving real time.

Then measure something. Pick one or two numbers and track them. A system you can't see the results of is just paperwork.

The bottom line: Extraction beats invention. Start with one real job and describe what already happened.

What It's Actually Worth

Boolkah tells a story about his years running restaurants, where he'd trust a twenty one year old to run a three million pound site but wouldn't trust the same person with a company car. The restaurant had a system. The car didn't. The person was identical.

That's the whole argument. Capability isn't the constraint. Structure is.

When the system is out of your head, the business stops depending on your availability. Your team can make decisions without waiting. Standards hold when you're not there, because they exist somewhere other than in your judgment. You can take the week off deliberately instead of discovering by accident that it would have been fine.

And there's a harder commercial point. When an owner eventually comes to sell, buyers pay for what runs without the founder and discount heavily for what doesn't. A business that only works when you're in it isn't really a business. It's a well-paid job with customers attached. That gap between what an owner thinks their business is worth and what a buyer will pay is, in my experience, almost entirely a systems gap.

You don't have to be thinking about selling for that to matter. The same things that make a business saleable make it calmer to run.

The bottom line: The business only becomes an asset at the point it stops depending on you being available.

Frequently Asked Questions

What does it mean to systemise a business? It means capturing how work actually gets done in a form somebody else can follow and repeat. For most owners it's documentation and standardisation rather than software, and it starts with describing what already happens rather than designing something new.

My work is bespoke. Can it still be systemised? Almost certainly. The output varies. The decisions rarely do. The questions you ask to scope a job, the information you need before pricing, and the stages work moves through tend to be stable even in highly custom businesses.

How long does it take to document a process? Narrating one real job end to end takes a couple of hours. Turning that into something usable takes a few more. The mistake is trying to document everything at once. Start with the process that's costing you most time or causing most variance.

Where should I start? With whatever currently can't happen without you. Quoting, scoping and onboarding are common answers, because they sit at the front of the work and everything downstream inherits their errors.

What if my team don't use the system once it's written? Usually that means they weren't involved in writing it. Getting a second version from whoever else does the job, and reconciling the two, does more for adoption than any amount of enforcement afterwards.

Isn't this just bureaucracy? Bureaucracy is process that exists for its own sake. This is the opposite. You're writing down decisions you already make so that they don't have to be made again from scratch every time.

Key Takeaways

• If your business produces a consistent standard, you already have a system. It's just stored in a person rather than on paper.
• You have probably already proved the business can hold without you. Look at the week that worked, or the job that runs itself.
• Undocumented systems hold on normal weeks and fail on the week everything arrives at once.
• It stays in your head because handing it over feels like lowering the standard. Keeping it there is what actually puts the standard at risk.
• Go into the detail to describe the work, never to do it.
• Start with one real job. Narrate it, fix the language, ask what someone else would need, then get a second version.
• A business that depends on your availability is a job. A business that doesn't is an asset.

If you're not sure how much of your business currently runs through you, that's worth knowing before you decide what to fix first.

The Leadership Compass takes about three minutes and shows you where the gaps are: https://sean-ljbifr8u.scoreapp.com

If you'd rather talk it through, a conversation about which process is costing you most usually takes half an hour and gives you somewhere obvious to start.