Is it actually unethical to run a business without proper systems?

Not in any legal sense. But there's a quieter ethical question worth taking seriously. If you know what genuinely serves your client and your team can only deliver it when you're personally involved, the days you're not in the room they're getting a lesser version. The client paid the same price either way. That gap, between what you promise and what your operation can consistently deliver, is the moral case for systemising. It's not about being a bad person. It's about closing the gap between the promise and the actual experience the client receives.

How is this different from just hiring better people or training harder?

Better people and better training help, but they don't close the structural gap. A great new hire still needs to know what good looks like in your business specifically, the welcome ritual, the response time, the polish step, the follow-up cadence. Without documentation, that knowledge lives in the most experienced person's head, usually yours. Hiring well or training hard without systemising means every new team member has to absorb the standard by osmosis, and the standard drifts every time someone leaves. Systems make the standard explicit, durable, and transferable. Hiring and training then become reinforcement, not reinvention.

Doesn't systemising make the business feel cold or robotic to clients?

Only if you systemise the wrong layer. Templates that dictate exact words and strip out human nuance produce robotic experiences. Templates that document structure (the points to address, the response cadence, the rituals at each milestone) actually free your team to be more present with the client because they're not improvising the operational scaffolding every time. Crow Estate Planning systemised every stage of their client journey and the experience became more human, not less, because the team had bandwidth to focus on the emotionally important part of each conversation. Good systemisation removes the overhead. Bad systemisation replaces the humanity.

How do I know which system to build first?

Start with the system that protects your client experience the most. Usually that's the client onboarding flow or the post-purchase follow-up cadence, because those are the points where inconsistency hurts the relationship fastest. The Systems Strength Test maps nine dimensions of your operation and tells you specifically where the largest gap is between your promise and your consistent delivery, so the choice isn't a guess. Whatever you choose, focus on the system that, if it stopped working, would damage the client relationship the fastest.

What if my industry is too custom or specialised to systemise?

Every owner who runs a custom service believes their work can't be systemised. Then they meet a peer in their industry who has documented the recurring patterns underneath the apparent variation, and the peer is taking longer holidays and earning higher margins. Custom industries (legal, accounting, allied health, custom construction, complex consulting) often have more leverage from systemisation, not less, because the consequences of an inconsistent client experience are higher in those industries. The custom layer sits on top of a systemised foundation. Document the foundation; protect the custom.

Why should I systemise my business if it's already profitable?

Profitable and saleable are not the same thing. A profitable business that depends on the owner being in the room sells for a salary buyout, not a multiple. A profitable business with documented systems that any competent operator can run sells for 3-5x earnings or more. Beyond exit value, systemising a profitable business protects what you've built. Profit margins compound when the team can deliver consistently without the owner micromanaging. New hires ramp faster. Existing clients stay longer because the experience is the same on every interaction. Profitable is the right time to systemise, not a reason to delay it.

The Moral Case for Systemising Your Business

Most owners think systemising is a productivity move. It's not. It's the only way to stop quietly stealing from your clients.

A few years back, the business strategist Jay Abraham told a story I haven't been able to shake.

Imagine, he said, that I run a water bar. A man walks in. He's dehydrated. His brain is foggy. His skin is dry. His body is screaming for water but he doesn't quite know it.

He puts a couple of dollars on the counter and says, "I'd like half a bottle of water."

I have a choice. I can take his money, hand him half a bottle, and watch him walk back out. Or I can stop him. I can tell him what I actually know. That his body needs at least seven more bottles today. That his focus, his energy, his patience with his kids tonight, all of it depends on what he drinks in the next few hours. I can be honest with him about what's at stake.

If I take the money and stay quiet, Jay said, I'm not just under-serving him. I'm stealing from him. I'm stealing his clarity. I'm stealing his energy. I'm stealing his evening with his family. I'm stealing the better version of his day.

Now replace water with what you sell.

What's actually happening on the bad days?

Most business owners I work with are not under-serving on purpose. They genuinely care. They got into business because they're good at something and they wanted to help people with it.

But here's what's actually happening on the inside of their business.

Their best work is delivered when they personally touch the job. The team does fine, but only fine. Sometimes they catch the small things, sometimes they don't. The client onboarding ritual that makes such a difference. The follow-up call after job completion. The polish step on the deliverable. The question that gets the brief 80% sharper. Those things happen when the owner is in the room. When the owner is on holiday, on a sales call, or simply too busy, those things often don't happen.

The client doesn't know what they didn't get. They paid the same price either way.

That's the half-bottle of water.

Why systemise your business at all?

If the moral case isn't enough on its own, here's the operational one. A systemised business runs without the owner being the bottleneck. New hires onboard against a documented standard, not the founder's memory. Holidays become possible. The business becomes saleable for a multiple instead of a salary buyout.

Most owners hear "systemise your business" and picture more SOPs in a folder no one reads. That's not what we mean. (If you want the operational version of this argument, here's how to systemise your business in 90 days.)

The moral case sits underneath all of those outcomes. The team can deliver the standard. The client gets the version they paid for. The owner gets to step away without the business shrinking. Three things people usually treat as separate goals, all powered by the same mechanism.

Can hiring better people close the systemisation gap?

There's a stance I keep coming back to inside SYSTEMology. It's always the system's fault first.

When a team member misses a step, when a client gets the B-day version instead of the A-day version, when something falls through the cracks, the question isn't "who screwed up?" The question is "what was the system supposed to be, and where did it fail to hold?"

Most owners hear that and assume it's about being kind to the team. It is. But it's also about being honest with the client.

Because if your team can't consistently deliver what you sell, you're not really running a business. You're running a lottery. And your clients are paying full price for tickets.

The good days they get the A-version. The bad days they get the B-version. They have no way to tell which day they're going to land on. The only person who knows that gap exists is you, the owner. And you live with it because the alternative, documenting what you do until the team can deliver it without you, sounds like bureaucracy.

It isn't bureaucracy. It's the only way to stop overcharging your clients on the bad days.

Why does Jay Abraham say "client" instead of "customer"?

Jay Abraham makes a sharp distinction that's worth pulling in here.

A customer is someone who buys a commodity. A client is someone under your care, your protection, your well-being. The first is a transaction. The second is a fiduciary relationship. (We've written about the difference between a customer and a client before, because the choice of word reflects the actual relationship.)

When you call someone a client, you're making a promise. You're saying, "I'm not just here to sell you something. I'm here to look after you. I'm in your corner."

That's a beautiful thing to mean. But you can only mean it consistently if your operation can deliver on it consistently. And that means everyone on your team, on every day, when every client walks in, has to be able to extend the same care, the same standard, the same attention to detail.

There's only one way that happens at scale. The way you serve has to live somewhere outside your head. It has to be documented, trained, observable, and improvable. It has to be a system.

A promise without a system to back it is just a marketing line.

What does it take to be a trusted advisor at scale?

Jay calls the goal preeminence. The label sounds dated, but the idea is straightforward. You become the most trusted advisor your client will ever have. The only viable choice in their mind. The person they'd never think to compare to a cheaper option, because the relationship is too valuable.

Owners love this idea. It's flattering. It also feels achievable. Most of us, on our best day, can absolutely show up as our client's most trusted advisor.

The problem is the gap between our best day and our average day. Being the most trusted advisor is not a state you summon when you feel like it. It's a standard the client gets to expect every single time, from anyone on the team, on the worst week of the quarter.

If only you can deliver it, it's not the standard. It's charisma. And charisma doesn't scale.

The thing that actually delivers the standard at scale is, unsexily, a documented Critical Client Flow. The same welcome, the same diagnostic conversation, the same delivery rituals, the same follow-up cadence, every time, by anyone on the team.

That's the operational layer that lets the moral promise survive contact with reality.

What it looks like when the morality matches the operation

Callie Saulsburry, the Systems Champion at Crow Estate Planning, on how the firm built consistency into legal work where the stakes are high and the variance is higher.

John Crow runs Crow Estate Planning and Probate, a US law firm with 15+ staff across three locations, specialising in estate plans, trusts, and the procedural mountain of probate.

The work the firm does is, by its nature, morally heavy. Clients are sitting across the table thinking about their parents, their kids, what happens to the people they love when they're not here. There's no room for a B-day version of a firm like this. The half-bottle of water in this industry is a probate that drags on for an extra eighteen months because nobody picked up the next step on the matter, or a beneficiary distribution that goes to the wrong person because nobody documented the family tree right at intake.

John saw that early. He had a big vision for scaling the practice across the Southeast US, but he was trapped in the owner's seat. Legal work is highly procedural and also highly variable (probate alone runs across 95 different counties, each with its own rules), so systemising it from the founder's chair felt impossible.

So he made a decision that turned out to be the moral one as much as the operational one. He stopped trying to be the system himself. He appointed a Systems Champion: Callie Saulsburry, an educator by background, to lead the systemisation. Callie used the SYSTEMology book as her guide. They documented the Critical Client Flow for estate planning first, then used the same framework to tackle probate, county by county. The systems live inside systemHUB as the firm's single source of truth.

That isn't bureaucracy. That's a moral position made operational.

The firm has built consistency and accuracy into how legal work gets delivered. New hires onboard faster. The team now proactively asks for new systems to be built. Clients get the same standard of care from the most junior paralegal as they get from the founder. (Here's the longer write-up of how Crow built this as a customer care system.)

Three things people usually treat as trade-offs: the firm grows, the clients are better served, and the founder gets his life back. They're not trade-offs. They're the same outcome, viewed from different angles.

The moral self-audit

If this argument lands at all, here are five questions worth sitting with for ten minutes this week.

What's the gap between my best day and my average day with a client? Be specific. What gets dropped? What conversation doesn't happen? What polish step gets skipped?
Who on my team can deliver my best day right now? If the honest answer is "only me," that's the systemisation gap.
If a client got the average-day version of our work this week, would they know they didn't get the best version? If the answer is no, that's the silent refund. They paid full price for partial delivery.
Where in my operation am I privately saying "we'll catch it on the next round" or "I'll just handle that one personally"? Those moments are the small leaks that, over a year, add up to a meaningful amount of stolen value.
If I left for ninety days, what would my clients quietly stop getting? Not the catastrophic stuff. The small things. The notes I'd never write down because they're too obvious. Those are the systems that don't yet exist.

This isn't about catching yourself out. It's about the gap between the promise and the consistent delivery. That gap is where systems live.

How dependent is your business on you? Owner Dependency Score

Score the gap between what your business promises and what it can deliver without you in the room. Two minutes; no email required.

Where to start

I'm not going to pretend systemising a business is fast or comfortable. It isn't. It takes most owners six to twelve months to do it properly, and the first ninety days are uncomfortable because you're forced to look at how much of the operation has been quietly held together by your personal involvement.

But the alternative isn't standing still. The alternative is continuing to deliver the half-bottle on most days, while quietly believing that one of these days you'll find the time to fix it. Most owners stay in that loop for years. Some stay in it forever.

If you want a starting point that doesn't require a six-month commitment, take the Systems Strength Test. It's a short diagnostic across nine dimensions of your operation. It tells you specifically where the gap is between the promise and the delivery, so you know which system to build first.

Your clients are paying for your A-day version. They deserve to get it.

The good news is, you don't have to be in the room for them to get it. You just have to make it possible for someone else to deliver it the same way. That's all systems are. Not a productivity hack. Not bureaucracy. Just the operational form of keeping your word.