How to Write SOPs for Your Small Business (Without Overthinking It)
You’ve been meaning to write your SOPs for months.
Maybe years.
Every time it comes up — on a podcast, in a Facebook group, in your own head at 11pm when something slips through the cracks again — you think “yes, I really need to do that.” And then you don’t. Because it feels like a huge project. Because you don’t know where to start. Because your business is moving fast and sitting down to document how it runs feels like the least urgent thing on a very long list.
And yet. The thing that slipped through the cracks? It slipped because nobody else knew how to handle it. Because the process lived in your head and nowhere else.
That’s what SOPs fix. And they don’t have to be complicated.
Here’s how to actually write them — without turning it into a month-long project you abandon halfway through.
First, what even is an SOP?
SOP stands for standard operating procedure. Which sounds very corporate and very intimidating and very much like something a 500-person company has, not a founder running a lean service business with a small team.
But all an SOP really is? A document that answers the question: “How do we do this?”
That’s it. How do we handle a new client inquiry? How do we prepare for a weekly team call? How do we send invoices? How do we onboard a new client?
If you’ve ever had to explain the same thing twice — to a VA, a contractor, a new hire — you needed an SOP. You just didn’t call it that.
Why most small business SOPs never get used
Before we get into how to write them, let’s talk about why most SOPs fail. Because you might have tried this before. You might have a Google Drive folder full of documents nobody opens.
The problem is almost never that the SOPs were badly written. The problem is usually one of three things:
1. They were written for how things should work, not how they actually work.
There’s a version of your business that exists in theory — the clean, logical, step-by-step version. And then there’s the real version. The one with the quirks, the exceptions, the “we always do it this way because of that one client situation two years ago.” SOPs built on the theory version get ignored because they don’t match reality.
2. They’re too long and detailed to actually be useful.
If your SOP for responding to a new inquiry is a six-page document with screenshots and sub-bullets and an appendix, nobody is reading it. They’re going to ask you instead. Every time.
3. Nobody was trained to use them.
A document in a folder nobody visits is not a system. It’s a file. For an SOP to actually work, it needs to be part of how your team operates — not something they dig for when they’re stuck.
Keep these in mind as you build yours. They’re the difference between documentation that collects dust and documentation that actually runs your business.
Where to start: the one question that changes everything
Most people approach SOP writing by asking “what processes do I need to document?” and then staring at a blank page because the answer is “everything” and that’s overwhelming.
Start here instead: What’s the thing that keeps coming back to you?
The task you keep getting pulled into. The question your VA keeps asking. The thing that goes sideways when you’re not paying attention. The process that only works when you’re the one doing it.
That’s your first SOP.
Not the most important process. Not the most complex one. The one that’s costing you the most time right now because nobody else can run it without you.
Write that one first. Get it done. Then move to the next one.
How to actually write an SOP (the simple version)
Here’s a format that works for small service businesses. No templates required. No special software needed. A Google Doc is fine.
Step 1: Name it clearly
The title should describe exactly what the SOP covers. Not “Client Onboarding” — “How to Onboard a New Client From Signed Contract to First Call.” The more specific, the more useful.
Step 2: Write the purpose in one sentence
Why does this process exist? What goes wrong without it? Example: “This SOP ensures every new client receives a consistent, professional onboarding experience without the founder needing to be involved in each step.”
One sentence. That’s all you need.
Step 3: List who owns it
Who is responsible for running this process? Who does it get escalated to if something goes wrong? Clarity on ownership is what separates a process that runs from one that gets quietly ignored.
Step 4: Write the steps in plain language
Not how the process should work in an ideal world. How it actually works. Walk through it like you’re explaining it to someone smart who’s never done it before.
Short sentences. Numbered steps. No jargon.
If a step has a specific tool or template attached — link to it directly. Don’t make them go looking.
Step 5: Add a “watch out for” section
This is the part most people skip. What are the common mistakes? The exceptions? The things that seem obvious to you but won’t be obvious to someone new?
This is where the real institutional knowledge lives. Don’t skip it.
Step 6: Note when it was last updated
Processes change. Businesses evolve. An SOP from two years ago might be completely outdated. Date it so you know when to revisit.
How many SOPs do you need?
Less than you think.
Most small service businesses need somewhere between five and fifteen core SOPs to meaningfully reduce founder dependency. Not fifty. Not a hundred.
Think about the categories of work in your business:
- Client communication and follow-up
- New client onboarding
- Project or delivery management
- Invoicing and admin
- Team or contractor coordination
- Recurring weekly or monthly tasks
Pick the two or three highest-friction processes in each category. Start there. You can always add more later. A handful of well-used SOPs will do more for your business than a comprehensive library nobody reads.
The format question everyone asks
Google Doc, Notion, ClickUp, Loom video, voice note. Honestly, the format matters less than people think.
The best format is the one your team will actually use. If your team lives in Notion, put your SOPs in Notion. If your team is more visual, a short Loom walkthrough paired with a written summary can work better than a text document alone.
What doesn’t work: a format that’s hard to access, hard to search, or requires three clicks to find. If it’s not easy to get to, it won’t get used.
What to do after you’ve written them
This is where most people drop the ball. They write the SOPs, put them somewhere, and assume their team will find and use them.
They won’t.
Once you’ve written a new SOP:
Walk someone through it.
Don’t just send the link. Sit with your VA or team member and run through it together. Answer their questions. Update the document based on what comes up.
Make it findable.
Create a simple index — even just a Google Doc with links to each SOP organized by category. Name things consistently so they’re easy to search.
Use it immediately.
Assign the next instance of that task to the person the SOP is written for. Let them run it using the document. See what breaks. Fix it.
Revisit quarterly.
Set a reminder. Block an hour every quarter to review your core SOPs and update anything that’s changed.
The thing most people miss
Writing SOPs is only half the job.
The other half is building a business where people actually use them — where there’s enough context, enough clarity, and enough trust for someone to pick up a process and run with it without coming back to you at every step.
That’s where founders get stuck. Not because they can’t write a good SOP, but because the SOP exists in isolation. There’s no delegation map. No clear ownership. No onboarding structure that brings someone into the business properly before handing them a document and hoping for the best.
SOPs are just one piece of the foundation. If you’ve tried documenting your processes before and it hasn’t stuck, that’s usually why
The bottom line
Writing SOPs for your small business doesn’t have to be a massive project. Start with the one process that keeps coming back to you. Write it in plain language. Keep it short enough to actually be useful. And build from there.
Done is better than perfect. A simple, accurate SOP that gets used is worth ten beautifully formatted ones that collect dust.
And if you’re at the stage where you know you need this but don’t have the bandwidth to build it yourself, that’s exactly what we do at Story & Strategy. We come in, learn how your business actually runs, and build the documentation and systems that make it possible for someone else to help run it.
Book a discovery call if you want to talk through what that looks like for your business.
