Business Operations for a Business of One

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.

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.

Examples of Business Operations, by Area

These are the operations a one-person business actually runs: twenty-two systems across six areas, each marked as something that must exist or is recommended. Read down the list and note which ones you do not have yet; the gaps are the useful part.

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. Most of that agreement is made in one meeting, the project kickoff, before any work starts.

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. A runbook is the version of this someone else can actually follow for a week.

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 money half of this has its own rules, which the financial controls checklist sets out in full.

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 getting paid, because an unwritten payment process is the only one on the list that is actively costing you money right now. Then client delivery, because scope is the most common source of the work you do not get paid for. Then the written record, because once the first two are written you have something worth documenting. Legal and risk, your time, and review can wait a week without anything going wrong.

One honest caveat: an honest list of what is missing is genuinely more useful than a complete one written as intentions. The value is in seeing the real state of the business, and an accurate gap is information. A tidy fiction is not.

Once the work runs the same way every time, check it the same way every time. A quality control checklist puts a pass condition on every check, so the result does not depend on who checked.

How to Scale a Service Business Without Burning Out

A service business usually stops growing for a reason that has nothing to do with demand. Clients keep arriving, every one of them needs more of your hours, and eventually the week is full and revenue flattens. That ceiling is capacity, not the market, and it is structural: extra effort moves it for a month and then it comes back.

Scaling is mostly the six areas above, applied under load. The moves that lift the ceiling go in this order, because each one depends on the one before it.

1. Productise the offer. A custom quote for every client means you are needed on every sale: a new scope, a new price and a new plan each time. A fixed package with defined deliverables, a set price and a set timeline turns delivery into a process, and only a process can be handed to someone else. It does not have to remove customisation. It puts the customisation inside a frame, as add-ons to a defined core. Pricing it so the margin is actually there matters more at this stage than winning more clients.
2. Automate the repeat admin before hiring anyone. Invoicing and payment reminders, scheduling, the onboarding emails, client status updates. These are sections 01 to 03 of the map running without you. Automation costs little, can be changed next month and creates no obligation, which makes it the lowest-risk way to buy back hours.
3. Bring in a contractor before an employee. A contractor is paid per project, out of the revenue of the client that project serves, so there is no salary to cover in a quiet month. Take a deposit before work begins and the client funds the delivery rather than your bank account. Hand off delivery first and keep selling yourself, because delivery is where your hours go.
4. Hire when the written record can do the training. The test is whether someone capable could deliver the work from your written procedures without asking you a question. If they could not, write it down before you recruit: a hire into an undocumented business learns everything from you, which costs the hours you were trying to free. When you do hire, hire for the role that absorbs most of your low-value time, usually admin, client communication or one repeatable part of delivery.

The shift underneath all four is moving from doing the work to building the thing that does the work. It is the hardest part, because it means accepting that someone else's version will differ slightly from yours. The six areas are what make that acceptable: when the standard is written down, you are checking work against a document rather than against your own instinct.

Frequently Asked Questions