Your business runs on your memory. That is not a system. That is a liability with your name on it.

If you own an agency or a service business doing between $500K and $5M, some version of this is true right now: the invoicing process lives in your head, the client onboarding process lives in your head, and the "what we do when a payment is late" process lives in nowhere at all. Every week you re-answer questions you already answered. Every hire takes months longer than it should. And you cannot take two weeks off without the wheels wobbling.

Learning how to build SOPs for your small business fixes this. Not with a 200 page operations manual nobody reads. With short, punchy documents that let other people run the machine so you can work on the machine.

Here is how to do it.

Key Takeaways

• Undocumented knowledge is expensive. Every departure walks out the door with knowledge you paid for, and every new hire takes longer to ramp because none of it was written down.
• Document the money path first. Invoicing, collections, payroll, and the monthly close come before anything else. Protect the cash cycle before you polish anything cosmetic.
• An SOP is a recipe, not a novel. One page, one owner, one trigger, numbered steps. If a stranger cannot follow it, it is not done.
• Put up a scoreboard. Measure ramp time, error rates, and days in your cash cycle before and after. An SOP that does not move a number is decoration.
• SOPs buy you the two week test. The goal is a business that runs without you watching it. That is the whole point of bootstrap cashflow.

Why Does Your Business Still Run on Memory?

Because it worked. For a while.

At $200K in revenue, keeping everything in your head is efficient. You are the only operator, decisions are fast, and writing things down feels like homework. Stopping to document anything pauses the money machine, so you never stop.

The problem is that the habit does not scale, and most owners do not notice the moment it stops working. In Good Operator's client work with service businesses between $500K and $5M, roughly 7 in 10 owners are still the only person who fully knows how invoicing works on the day they come to us. Not sales. Not strategy. Invoicing. The thing that turns work into cash.

It gets worse when people leave. This is not just a productivity problem, it is a wealth problem. higher sale prices, and the gap is not small. Analysis of closed service business deals by M&A advisory firm Iconic found that owner-dependent companies. If your business earns $500K in EBITDA, that discount alone can be worth half a million dollars or more at exit.

Here is what running on memory actually costs you, whether or not you ever plan to sell:

• Your time. You are the help desk. Every "quick question" is a tax on the highest paid person in the company.
• Your quality and consistency. When someone takes vacation, things get dropped. What you sell and what you deliver varies wildly based on who works on it. Customers prefer "good enough every time" consistency to "better, sometimes."
• Your hires. New people ramp slowly and badly, then quietly do things their own way.
• Your exit options. A business nobody else can operate is not an asset. It is a job with overhead.

We wrote about this feeling in Your Business Feels Like a Mess. Is it? The mess is usually not the business. It is the absence of written systems around a business that is actually pretty good.

What Makes an SOP Worth Writing?

Not every task deserves a document. An SOP earns its place by passing three tests.

1. It repeats. The task happens weekly or monthly, forever. One-off projects do not get SOPs. They get a checklist and a funeral.
2. A pause breaks something. If nobody covers this task while someone is on vacation and things fall apart, an SOP is critical for backup coverage. If nothing breaks, it can wait.
3. Someone other than you could do it. If the task genuinely requires your judgment, it is not an SOP candidate yet. Break it down until the mechanical parts separate from the judgment parts, then document the mechanical parts.

The U.S. Chamber of Commerce's guidance on SOPs makes a point most owners skip. An SOP should be written so someone who has never done the task can complete it, and you test that by handing it to exactly that person. If they get stuck, the document failed. Not the person.

We have a saying at Good Operator.

"Hire A+ talent, but build systems a C- could operate."

Format matters less than people think. A good SOP fits on a page or two and contains:

• Goal: at the end of the day, what is important here? There will be outlier cases, so make sure someone can improvise their way to the goal.
• A picture: it is easier to follow a vision than a list. A visual gives orientation and context to the detail steps below.
• Trigger: what event starts this process. "Client signs contract." "It is the 25th of the month."
• Names: who owns each step. Every step gets a name attached, not a department.
• Process: what gets done, numbered, in order, with screenshots where clicks are involved.
• Systems used: where this happens. Is it an email, a meeting, a sequence performed in a specific software tool. Be specific.
• Checklists: note anything that has to happen and make a checklist.landmark study. If surgeons need a checklist for something they have done a thousand times, so does your team.
• Templates and examples: wherever possible, include an exact template or an example of what it should look like so there is less room for interpretation and misunderstanding.
• Done: what finished looks like, stated plainly. "Invoice sent, logged in the tracker, follow up scheduled for day 15."
• Escalation: what to do when something breaks, and who to tell.

That is it. Anything longer is a training manual pretending to be an SOP, and nobody will read it twice.

How to Build SOPs for Your Small Business in 6 Steps

Here is the process we use with clients. It works because it keeps it simple.

Step 1: Build a Systems Inventory

Do not let the name intimidate you. It is a list of all the functions that have to get done for the business to operate. Do not sit down and think of all the things you are supposed to do, want to do, or are responsible for. Write down for a couple of weeks what you actually spent time doing.

Bucket the tasks into functions like business development and sales, product or client work, and administrative work. Flag the things you are currently doing that are not critical to your current priorities but still have to get done. These get delegated first, since doing them wrong just creates more work for you.

Eventually you want documentation linked to every task in the inventory. For now, start with what has to move off your plate, then move to whatever needs coverage and backup the most.

Step 2: Draw It Out

Create a visual map of how things need to flow. Put it into workflow software or draw it on paper. It does not matter which, but it is easier to follow written instructions when your brain has a visual map to navigate from first.

Step 3: Record Yourself Doing the Task Once

Do the task like normal with a screen recorder running, narrating as you go. Twenty minutes of recording beats four hours of staring at a blank template. Then hand the recording to whoever will own the process and have them write the first draft.

The owner writes it. You edit it. That ordering matters, because the person doing the work spots the steps you do on autopilot and never mention.

Step 4: Replace "Except in This Instance" With "At the End of the Day"

There will always be examples that break the process. A detailed playbook covering every variant becomes a binder, one for each function. If you were NASA running the Apollo missions, protocols for everything that could go wrong would make sense. Thank goodness they had them.

That is not you. Your team will have to improvise from time to time, so make sure they know the priorities and what ultimately has to happen. If things go sideways but they know where it needs to end up, they will figure it out.

Step 5: Test It on Someone Cold

Hand the document to someone who has never done the task and say nothing else. Where does it break? What did you think was intuitive that they did not? What read as ambiguous or misleading? Fix those.

Step 6: Assign an Owner and a Review Date

Every SOP gets one owner and a review date each quarter. Processes drift. Software changes. An SOP that was accurate in January and wrong in June is worse than no SOP, because people trust it. Fifteen minutes per quarter per document keeps the library honest.

Run this loop three processes at a time. In two quarters you will have the ten to fifteen documents that cover 80% of your operations. That pace is deliberate. Spend with intention, not less, applies to your hours too. Ten SOPs that get used beat fifty that get skimmed once.

Measure It Like a Scoreboard, Not a Report

A report tells you what happened last month. A scoreboard tells you what is happening right now and what to do about it. SOPs only earn their keep if you are tracking one.

Before you write a single document, pull three numbers for the process you are about to standardize:

• Ramp time. How long until a new hire runs this task without help.
• Error rate. How often the task gets redone, refunded, or apologized for.
• Days in the cash cycle. For anything touching invoicing or collections, how many days from work delivered to cash in the bank.

Write the SOP. Run it for a full cycle. Pull the same three numbers again. In Good Operator's work with agency clients between $500K and $5M, the accounts receivable SOP alone typically shaves several days off the average collection period within the first two billing cycles, simply because follow up stops depending on whoever happens to remember. If a number does not move, the document is decoration, not a system. Rewrite it or cut it.

The Mistake Most SOP Advice Gets Wrong

Most SOP advice centers on creating order and peace of mind. It is about freeing up your time and getting control over your business. That is not wrong. But that is really delegation.

The SOP is about making the best version of something the standard. The best practices of your best players get distributed across everyone else on the roster, instead of staying locked in one person's head.

It is not about creating instructions around basic tasks. It is about creating a machine. So focus on the most mission critical parts of that machine that need to happen consistently and at a high degree of quality. Start there.

We wrote about this same trap in a different context in An Intangible Edge. The things that are hardest to put a number on are often the ones worth investing in anyway. A well written SOP will never show up as its own line on a P&L. It shows up in every other line instead.

Build the Machine, Then Step Back

We named the business Good Operator, but most people think of operators as owners who are still neck deep in the business. We do not.

If you operate a lawn mower, are you spinning the blades by hand? Of course not. A good operator does not do the job of the machine. They build it, maintain it, steer it, and get the benefit from the work it does, because otherwise they would have to do that work themselves. That is the operator we mean.

Before you can hand things off, before you can productize and replicate the work you have created, before you can step away and let the machine run, you have to create systems and standards for how it should work. And those standards need to be documented. The IMA's overview of SOPs for small businesses makes the same case from the finance side: documented procedures are one of the clearest ways to protect continuity when key people leave, whether that departure is planned or not.

If you want help building the version of this that actually gets used, our monthly partnership work is built around exactly this kind of systemization, not just closing your books.

Want the operating playbook every week? Subscribe to Bootstrap Cashflow, our operating manual for cashflow machines, at goodoperator.beehiiv.com.

Frequently Asked Questions

How many SOPs does a small business actually need?

Fewer than you think. Focus on the 20% that deliver 80% of the value, then systematically knock out the next one on the list. The playbook database gets large when clients need their own version. We have one main accounts receivable SOP, then individual ones per client, since tools, terms, and payment structures differ. That way, if anyone had to take unexpected leave, someone else could step in and maintain that client's standards.

Who should write the SOPs, the owner or the team?

The person who does the task writes the first draft, and the owner edits it. The doer catches steps the owner performs on autopilot, and the owner catches shortcuts that should not be standard. If you are still doing the task yourself, record your screen once and have your first hire turn the recording into the document.

What tools do we need to build SOPs?

Nothing fancy. A shared drive or a free Notion workspace, a screen recorder, and a naming convention beat any expensive SOP software when you are starting out. The tool is not the system. The habit of writing, testing, and reviewing is the system.

How often should SOPs be reviewed?

Do a quick scan quarterly, by the named owner of each document, in about fifteen minutes per SOP. They probably only need to be meaningfully changed once a year, maybe less. Also review any SOP immediately after the process it describes fails, because a miss is free intelligence about where the document is wrong.

What is the difference between an SOP and a checklist?

A checklist confirms steps happened. An SOP explains how to perform them, in what order, and what to do when something breaks. For simple processes a checklist can be the whole SOP, but anything involving decisions or handoffs needs the fuller document with an owner and an escalation path.

‍