On this page
Business operations are the repeatable systems that turn work you have won into money in your account. In a business of one there are six of them: getting paid, delivering the work, keeping a written record, handling legal and risk, protecting your time, and reviewing all five. Setting them up is a six-step process and takes an afternoon, not a quarter. The point is not efficiency. It is that every one of these becomes a decision you make badly under pressure if you have not made it in advance. The operations map below is the whole thing on one page, with a state next to each system so you can see what is missing before it costs you.
Almost everything written about business operations assumes a department. Process owners, RACI matrices, operations managers, a continuous improvement function. Search the term and half the results are job listings, because for most of the internet this is a career rather than a thing you do on a Thursday.
None of that survives contact with a business where the operations manager is also the person doing the work. But the underlying problem is real and it shows up in a specific way: something goes wrong that has gone wrong before, and you handle it from scratch again, badly, while a client waits.
Setting Up Business Operations: Six Steps, One Afternoon
Work through these in order. Each one produces a row in the map further down, and the map is the finished artefact you keep.
- Write down how money reaches you. Start here because it is the one that hurts soonest. What your terms are, what deposit you take, what you do on day 1, day 7 and day 14 of an overdue invoice. If those steps are not written, you will invent them while annoyed, which is the worst time. Tying payments to defined milestones is the version of this that holds up in a dispute.
- Write down how work gets delivered. What you send a new client and in what order, where "done" is defined, how many revisions are included, and what transfers at the end. Most delivery problems are scope problems wearing a costume. A written onboarding sequence does more of this work than any other single document.
- Write down what you do more than twice. Anything repeated is a candidate for a standard operating procedure. You are not documenting for a team. You are documenting so the version of you that is tired and behind does it the same way as the version that is fresh.
- Settle legal and risk once. Your structure, the contract you actually send, what client data you hold and for how long, and what insurance covers. These change rarely and cost enormously when wrong, which is exactly the profile of a thing to decide in advance. The structure decision sits underneath the rest.
- Protect the hours that produce revenue. Name when you do paid work and defend it. Name the first things you would hand off, before you are desperate enough to hand off badly. Deciding what to outsource is easier done calmly than in a crisis.
- Set a review date. Six months, or whenever you take on a client who does not fit the existing shape. Operations written for the business you had two years ago quietly describe someone else.
That is the whole process. It takes an afternoon rather than a quarter because you are not designing controls for other people to follow. You are writing down decisions you are already making, so that they stop being improvised each time.
Aziz's take: Do step one properly and let the rest be rough. Every other system on this list can be improved later at no cost, but the gap between "I will invoice at the end" and a written payment schedule is the gap between being paid and being an unsecured creditor with a nice relationship. I would rather someone had a scrappy map with a sharp money section than a beautiful one that left it vague.
The Operations Map
This is the artefact. Twenty-two systems across the six areas, each with a state so the gaps are visible rather than remembered. Fill in the highlighted values, mark what is missing, and you have an audit of your own business that takes ten minutes to read.
How to use this
Fill in
- Every highlighted value. Where a system does not exist yet, write MISSING rather than deleting the row.
- Section 01 first. It is the one with a cost attached to being vague.
- Be specific enough that a tired version of you could follow it without re-deciding.
Check before you file it
- Nothing marked Must exist is still blank.
- Every system names where it lives, not just that it exists.
- The review date in 06 is in your calendar, not only in this document.
What goes wrong
- Filling it in aspirationally. A map of the business you intend to run is worth nothing.
- Writing a process you do not actually follow, which is worse than an honest gap.
- Never reopening it, so it describes a client mix you stopped serving.
The Six Areas, and What Each One Breaks
Each area fails in a characteristic way. Knowing the failure is more useful than knowing the definition, because the failure is what you will actually recognise.
Getting paid fails quietly and late. Nothing appears to go wrong for weeks, and then you are carrying a client's costs interest free while deciding whether chasing them is worth the relationship. The fix is entirely upfront: terms written before the work, a deposit that covers your exposure, and a chasing sequence you do not have to invent. Cash flow is the symptom; this area is the cause.
Client delivery fails through undefined scope. The work expands, nobody agreed it expanded, and by the time it is obvious you are too far in to raise it comfortably. A written definition of done and a revision limit are what you point at later, which is why a difficult client conversation goes far better when you are quoting something agreed rather than asserting something new.
The written record fails invisibly until you are unavailable. It costs nothing while everything is fine and everything when it is not. This is the area people skip because it has no deadline attached, and it is the one that decides whether the business can survive you having flu.
Legal and risk fails rarely and expensively. Structure, contracts, data handling and insurance are low-frequency, high-consequence decisions, which is the exact profile of something to settle when calm. If you handle personal data on a client's behalf, a data processing agreement belongs here too, and if you use AI tools in the work, so does your own AI policy.
Your time fails by absorption. Admin expands into the hours meant for paid work, and because it is all your business it never feels like an interruption. Naming the protected hours and naming what you would hand off first are the two decisions that hold the line. Bringing in a virtual assistant or outsourcing payroll works far better against a list you wrote in advance.
Review fails by omission. Nothing forces it, so it does not happen, and the systems slowly stop describing the business. A date in the calendar is the entire mechanism.
The Types of Business Operations, and Why the Textbook List Does Not Fit
Most reference material splits business operations into four or five types: production or service delivery, supply chain, finance and accounting, human resources, and sometimes marketing or IT as separate functions. That division exists because in a larger company those are literally different departments with different people in them.
In a business of one the division is useless, because every function has the same person in it. Splitting by department tells you nothing about what to do on Monday. Splitting by what breaks, which is what the six areas above do, tells you exactly where to look when something has gone wrong twice.
The other thing the textbook framing gets wrong at this size is the goal. Operations in a large organisation are optimised for efficiency, because a percentage point across hundreds of people is real money. At your size the aim is different: you are buying back decision-making capacity. Every system you write down is a decision you no longer make from scratch, which is the scarce resource when the strategy function, the delivery function and the admin function are all one person with one week.
As the business does grow, the systems become the thing that makes growth survivable rather than the thing that gets abandoned during it. Scaling a service business is mostly a question of whether these six areas were written down before the volume arrived.
Where to Start If You Have None of This
Do not try to fill the whole map in one sitting. The order that works is the order of consequence.
Start with section 01, because an unwritten payment process is the only one on the list that is actively costing you money right now. Then section 02, because scope is the most common source of the work you do not get paid for. Then 03, because once the first two are written you have something worth documenting. Sections 04 to 06 can wait a week without anything going wrong.
One honest caveat: a map with gaps marked MISSING is genuinely more useful than a complete one filled in with intentions. The value is in seeing the real state of the business, and an accurate gap is information. A tidy fiction is not.