How to Write Your First SOPs Without Losing a Month: A Practical Guide for Small Service Businesses
If your phone lights up all day with "Quick question, how do I…", you already know the problem. In a 2–15 person service business, most processes live in the owner's head. Every invoice, every new-client welcome, and every refund ends up waiting on you.
The usual fix is "we should write SOPs," followed by a blank document and the feeling that this will take a month you don't have. It doesn't have to. Here's a way to get your first useful standard operating procedures written in small pieces, during normal work.
Why the owner becomes the bottleneck
It's rarely because the team can't do the work. It's because the steps, the exceptions and the definition of "done" were never written down. So people do the sensible thing and ask the person who knows. Each question takes two minutes, but twenty of them a day take your focus. An SOP is simply a way to answer the question once.
Start with the questions you answer most
Don't start with an org chart or a list of every process you have. For one week, keep a note open and jot down every time someone asks you how to do something. Tally repeats.
At the end of the week, you'll usually see a handful of tasks that cause most of the interruptions. Those are your first SOPs. Common ones in service businesses include:
- Sending and following up on invoices
- Onboarding a new client
- Answering a complaint or refund request
- Posting to social media
- Getting a new hire set up on day one
Write the SOP while you do the task
The slowest way to write an SOP is to sit down and try to remember a process. The fastest way is to write it while you're doing it. Next time you send an invoice, keep a doc open and note each step as you go. Or record your screen and talk through it, then turn the recording into steps later.
This catches the small things memory skips: which folder, which template, which field people always forget.
Keep every SOP to one page with the same parts
Consistency matters more than polish. If every SOP looks the same, people learn where to find things. A simple structure that works:
- Purpose: one sentence on why this task exists.
- Owner: the person responsible for keeping this SOP accurate.
- When: the trigger. "When a job is marked complete," not "regularly."
- Steps: numbered, one action per line, with links to tools or templates.
- Done looks like: how someone knows they finished correctly.
If it runs past a page, it's probably two SOPs.
Test it with someone who didn't write it
Hand the draft to a team member and ask them to follow it without asking you anything. Every question they ask is a gap in the document. Fix the gap, not just the answer. Two rounds of this usually turns a rough draft into something usable.
Roll it out without a revolt
Teams sometimes hear "SOPs" as "you don't trust us" or "more paperwork." A few things help:
- Explain the goal plainly: fewer interruptions and fewer surprises for everyone, including you.
- Ask the people who do the task to help write or edit it. They often know shortcuts you don't.
- Introduce a few at a time rather than fifty in one meeting.
- Treat SOPs as living documents. If a step is wrong, the person who finds it should say so.
Give every SOP an owner and a change log
SOPs go stale when nobody is responsible for them. Keep one simple sheet listing each SOP, its owner, when it was last reviewed, and a short note of what changed. A quick review during a weekly or monthly team meeting is often enough to keep things current.
A realistic first month
- Week 1: Track the questions you get asked.
- Week 2: Write SOPs for the top three while doing those tasks.
- Week 3: Have someone test each one; revise.
- Week 4: Set up your ownership sheet and pick the next three.
That's a manageable pace alongside normal work, and each SOP is useful the day it's done.
If you'd rather not start from a blank page
We made the Small Business SOP Starter Library for owners who want a head start. It includes fifty fill-in-the-blank SOPs across hiring and onboarding, customer service, sales and follow-up, bookkeeping and invoicing, marketing and social posting, and weekly review and reporting, plus a guide to rolling SOPs out with your team, a blank SOP template, a change log and ownership sheet, and a next-steps section. You'll still need to adapt each one to how your business actually works. It's $39: https://knowfinch.com/p/small-business-sop-starter-library
Written with AI assistance and reviewed by a person. More articles