SOPs for Small Business: Why Your Standard Operating Procedure Is Step One for Every Automation That Works

When it comes to standard operating procedures, I need you guys to lock in. I LOVE SOPs. They're what let me feel confident that the specific outcome I want actually gets carried out. And yes, SOPs for small business matter too, even if it's just you and a VA. A standard operating procedure for small business is how the process gets out of one person's head.

Most founders have one of two relationships with SOPs. Either they don't have them, and the process lives in their head, in a Loom video from 2022 that nobody's watched since, in a Notion doc that's technically there but three updates behind. Or they wrote one once, and it's gathering dust. SOPs are the backbone of a business, and they OFTEN end up like that. If one gets written at all, it's hard to get the team to read it, let alone rely on it.

Why small businesses need SOPs

Picture this. Your onboarding email goes out with last year's pricing. The VA says the automation sent it. The automation says nothing. You find out when a client asks why the invoice doesn't match. Nothing broke, exactly. Nobody owned it, so nobody caught it.

If a process has no name next to it, nobody owns it. And the AI will just apologize. That's what the Owner line and the RACI in an SOP are for.

I always say operations is an information problem, and the SOP is where that information lives. Without it, every ping, login and "quick question" costs more than the minute it takes, because you also lose the time it takes to climb back in. Harvard Business Review found people lose around four hours a week just reorienting after switching between apps.

Which SOPs to write first

This might sound weird coming from an operations person, but you do NOT need to systemize your business as much as you think. 20% of your systems create 80% of your efficiency.

Map your business in six boxes: attract, inquire, purchase, onboard, deliver, and repeat or refer. Then ask three questions. Which step pulls you out of flow, or do you dread the most? Which step is the most practical to automate: repeatable, rule-based, done the same way every time? And which step, once fixed, would lift the whole business more than any other? Once you've found them, the first move is writing the SOP for each one.

How to write an SOP for a process

The SOP I teach is the Automated Beast SOP, and it's built to fix the dust problem at every stage: a set template so it actually gets written, content written for humans and AI agents alike, and a review rhythm that keeps it alive. Write it for the newest person on your team, with action verbs. The anatomy of an SOP:

• Owner and last reviewed date at the very top.

• Prerequisites: tool access and tasks done before you start, so nobody gets stuck halfway because they were missing a login or a file.

• Purpose: one clear, repeatable way to do this work, so everyone knows why it matters and notices when it drifts.

• Workflow: a diagram near the top, because most people only need the big picture. When they know they can skim it, they're more likely to reference it at all.

• Procedure: step by step, with videos, tools and links. Anyone can follow it and get the same result.

• Roles and responsibilities (RACI): responsible, accountable, consulted, informed. No one wonders who owns it.

• Policy: naming, format, where it lives, the standard. Quality stays the same no matter who does the work.

Why you should write your SOP by hand

Recorders like Scribe capture your clicks and turn them into steps. It's fast, and it skips the part that makes an SOP work. Writing it is how you FULLY understand it: the why, the exceptions, the hand-offs, not just where to click. A recording shows what one person did once. It can't tell you the standard, who's accountable, or what to do when it breaks. A recorder can supply the screenshots, but it can't be the owner, and the whole team, owner included, needs to know the process belongs to someone who fully understands it. That's what makes it safe to let go of.

So the procedure and the RACI get written by hand, by the person who owns the process, straight from the template, no AI draft. Writing the procedure especially binds you to the work, body and mind, so new ideas fit the process instead of fighting it when you scale. MIT Media Lab put EEG caps on 54 people writing essays, and the ChatGPT group showed the weakest brain connectivity of any group. Most couldn't quote what they had just written. Doing the work runs the other way: you review, you notice, you keep thinking about it. Perspective comes from contact, not from a summary, and a recording is a summary of one run.

Some friction is the point: the pause where judgment, taste and creativity happen. I wrote more about that in systems and what creativity has to do with it.

Why you need an SOP before you automate

Before you start automations, you have to do it manually first, perfect it, and then you can automate it. It's sooo easy to jump straight to "I need to automate this, I need to automate that". But your standard operating procedures are the first step for creating automations that work, at the same quality.

In my clients' businesses, I audit the actual work, remove redundant steps and clarify ownership. Then we build SOPs that are as non-intimidating as possible to read, and the team keeps them alive so there's no drift between the SOP and the work they actually do. Then it's time to automate. I wrote about that order in why I'm reclaiming the word optimized.

Because an Automated Beast SOP is written for humans and AI agents alike, it can go straight to an agent in Claude, ChatGPT or a custom bot. It runs the process, like client onboarding from start to finish. It answers the team, so a new hire asks the agent instead of messaging you. It checks the work against your policy before anything goes out. And when someone is out or moves on, it keeps following the SOP while the RACI shows who's accountable. A person writes and owns it; the agent works from it and reviews against it. That makes the SOP the heart of the process: less drift, and a real respect for the process itself.

Nothing client-facing, financial or legal should leave without a named person approving it. That person is the A in your RACI, and it's never the model.

How to keep an SOP from gathering dust

In my clients' businesses, each SOP lives in their project management tool as a recurring task, assigned to its owner, with a quarterly reminder. At each review we ask: what's working, what's breaking, what can we automate next? On top of that, an agent watches for drift: where the team's real work no longer matches what's written, the steps that have quietly started slowing everything down, and new procedures that need an SOP of their own. The reminder makes sure it gets reviewed. The agent tells you what to review.

That's a big part of what a fractional COO does: making sure every process has a name next to it and a document that's true to how the business actually runs today.

Tell me in the comments: which process in your business still lives only in your head?

And if you're wondering what it costs to build your SOPs with me, every offer and price is in my free pricing guide.