How to make your business run without you

If you stepped away for two weeks, what would stop?

When did you last take a real break? Not a long weekend with your phone in your hand. A proper one, where the business kept going without you.

For most owners, it's been a while. And if you're honest, there isn't one coming any time soon. In a recent survey of 2,000 Australian small business owners, one in four said they don't have time for a holiday, and half said they hold back on time off because of what it does to the business.

It's rarely because the team can't do the work. It's because how things should be done lives in your head. So every question comes back to you.

Many owners try to fix this by hiring a manager. The manager learns the rules from you, and then the rules live in their head instead of yours. If they leave, the rules leave with them, and the salary was there the whole time.

Letting go is hard. In my experience, most owners know they should delegate. What stops them is that handing a task over feels slower and riskier than doing it themselves, so they keep doing it.

The way out is writing down how the business runs, one task at a time, so the rules belong to the business, not to one person. Then you hand each one over properly.

Why everything still comes to you

In my experience, it's usually one of these:

• The rules aren't written anywhere. Can we give this regular customer a discount? Which supplier do we call when stock runs out? What do we tell a customer whose order is late? Who can approve overtime? Can we swap this item for a different size? And so on. Only you know, so only you can answer.
• Nobody owns it, everyone thinks they do, or nobody knows they can decide. If nobody owns a task, it comes back to you. If three people all think it's theirs, each one does it their own way. The results don't match, things get more chaotic, and it still ends up on your desk. And even when someone knows exactly what to do, they wait for you because nobody told them they can decide.
• You fixed it once and never wrote it down. The same problem comes up next month, and you fix it again.
• It's quicker to do it yourself. True today. Not true the 50th time.

What to write down first

Don't start by writing down everything. Start with what keeps landing on you. Here's how we start at KATOS.

For one week, note every question, task and project that comes to you. Then sort them:

• It happens often: stock reorders, customer complaints, supplier follow-ups, staff rosters.
• It's costly when it goes wrong: a wrong order, a late payment, a missed delivery.
• Only you know how to do it right now. Including the projects and launches you're still running yourself.

The ones that tick two or three of these go on the list. Most owners end up with a list of 3 to 5. Start with the top 2 or 3.

What a useful SOP has in it

A standard operating procedure (SOP) is a written answer to "how do we do this here?". The useful ones are short and foolproof: someone new can follow it without asking you. A one-page checklist that gets used beats a 20-page manual nobody opens.

Here's what one needs, using reordering stock as the example:

• What starts it. Stock of an item drops below its reorder level.
• The steps, in order. Check stock every Monday. Raise a purchase order for anything below its reorder level. Send it to the supplier. Log it in the PO sheet.
• Who does it, and who owns it. One name, not "the team". For example, the ops lead.
• The rule for decisions. If an item is below its reorder level, order the standard quantity from the approved supplier at the agreed price. No approval needed.
• Where to find the information. The stock dashboard (it flags what's running low), the supplier list, the PO sheet.
• When to escalate. An order above a set amount, a supplier who can't deliver on time, or a product being discontinued. Only these come to you.

That last step is the one most people skip. Without it, every unusual order still comes back to you, and you're the bottleneck again.

Hand it over, then check it's used

Writing it down is half the job. The other half is making sure it's actually used.

• Walk through it together once. Let the person do the task while you watch, and fix the steps that don't make sense.
• Step back. When a question comes to you, point them to the SOP instead of answering it.
• Check after a few weeks. Is it being followed? Is anything missing? Update it.
• Keep them in one place where the team can find them.

Doing this before your next busy period helps most. That's when the questions double.

What it brings you

Once the business runs on written systems:

• You get time back. You stop answering the same questions every day.
• You can take a real break. The business keeps running while you're away.
• Decisions get faster. The team decides within the rules instead of waiting for you.
• Results get consistent. The same task is done the same way, with fewer mistakes and fewer customer complaints.
• You can grow without more of your hours. New sales don't mean more work landing on you.
• New people learn faster. They learn from what's written down, not from you.
• The business is worth more. One that runs without its owner is easier to grow, hand over or sell.

What we've seen

It works across very different businesses:

• Food business. It was relaunching with recipes and routines in two or three people's heads. We wrote down its 5 core processes, with a named owner for every step, and set up sheets that calculate themselves: a weekly sales summary, a stock sheet that flags what to reorder, and a dashboard. The owner went into the relaunch able to see sales, stock and cash. (Read the job)
• Certification authority. We started by reviewing how the process really ran, step by step. Every client waited the full cycle, however simple their case. We split it into two tiers and wrote one standard across 4 markets. Turnaround dropped from 66 to 20 working days, 70% faster, with lab testing integrity kept at 100%. (Read the job)
• Marketplace and logistics franchise. We built written operating models and standard procedures for both, and brought 7 business units under one point of accountability. (Read the job)

What this actually takes

To do this properly, you track where your time goes, pick the right tasks, map how each one really runs today (not how you think it runs), agree who owns each step, write it so someone new can follow it, test it with the team, train them, and keep it up to date as the business changes.

Writing one SOP takes hours. Getting the team to follow it every time takes weeks. A full set that the business actually runs on takes months.

You need it. The business can't grow past you without it. But it's slow, careful work, and it has to happen while you're still the one everyone is waiting on.

---

This is the kind of line-by-line work we do at KATOS. See how we handle it →

Frequently Asked Questions

Sources

• AMP: Small business owners "always on" while much of Australia enjoys the summer holidays (19 Jan 2026)