tech
SOP (Standard Operating Procedure)
Documented step-by-step process for a repeatable workflow.
Definition
An SOP is written instructions for how a specific task gets done - the exact steps, tools, decisions, and quality checks. Most service businesses have zero documented SOPs - everything lives in the founder's head, which caps the business at founder bandwidth. The discipline: document the 5 most-repeated workflows first (onboarding, proposal, invoicing, support escalation, hiring screen). Once written, test the SOP by having someone new follow it - the gaps reveal themselves immediately.
Anatomy of a useful SOP
A useful SOP has six sections. One, purpose: one sentence on why this process exists and what outcome it produces. Two, owner: the named person responsible for the SOP and its updates. Three, when to use: the trigger that starts the process. Four, steps: numbered, action-oriented, with screenshots or links to tools where applicable. Five, decisions: explicit branches when 'if X then Y, if Z then W' matters. Six, quality check: the final verification before complete. SOPs over 2 pages are usually too long - the team will not read them. SOPs under 5 steps are usually too vague - they assume context the reader does not have. The sweet spot: 1 to 2 pages, 8 to 25 steps, plus 1 to 3 decision points.
Where to store SOPs
Choice of platform matters more than founders expect. Best US options: Notion (most popular for SMB, good search, free for small teams, 8 dollars per user per month for business plan), Confluence (Atlassian, strong for engineering teams, 5 to 11 dollars per user per month), Guru (purpose-built knowledge base with Slack integration, 12 to 18 dollars per user per month), Trainual (designed specifically for SOPs and training, 99 to 199 dollars per month flat). Avoid: Google Docs folder structure (no search discipline, link rot, version sprawl). Whatever platform, enforce one rule: every SOP has a named owner and a last-reviewed date visible at the top. Without ownership, SOPs decay within 6 months.
Using AI to draft SOPs faster
ChatGPT, Claude, and Loom-with-AI dramatically cut SOP creation time. Workflow: record a Loom video of yourself doing the task (5 to 15 minutes), use Loom's auto-transcript or Otter.ai for the text, feed the transcript to ChatGPT or Claude with a prompt like 'turn this into a numbered SOP with sections for purpose, steps, decisions, and quality check.' Edit for clarity. Total time: 30 to 60 minutes per SOP versus 3 to 5 hours writing from scratch. The AI-drafted SOP is 80 percent of final quality; the human edit adds the institutional knowledge that the video did not capture (why this step, what to avoid, edge cases). This workflow makes documenting 20+ SOPs in a month realistic.
Common SOP failures and how to avoid them
Three recurring failure modes. One, SOPs written from imagination rather than observation - founder writes how the process 'should' work, but actual practice differs. Fix: write the SOP while doing the task, not from memory. Two, SOPs that capture every edge case become unreadable. Fix: separate the 80 percent path (main SOP) from edge cases (linked exception handling documents). Three, SOPs that are never updated decay into wrong instructions, which is worse than no instructions. Fix: every SOP has a mandatory quarterly review with the owner; review can take 10 minutes but the review itself is mandatory. Set calendar reminders.
FAQ
How many SOPs does a small business actually need?
For a US service business under 20 employees, 20 to 40 SOPs covers 90 percent of recurring work. Above 50 employees, 60 to 100 SOPs. The Pareto principle applies: 20 SOPs cover 80 percent of repeated workflows, beyond that is diminishing returns. Top SOPs to write first: new customer onboarding, proposal generation, invoicing, payment chasing, support ticket triage, hiring screening, new hire onboarding, monthly close, weekly team meeting, quarterly review. Each unlocks specific delegation. Do not try to document everything; document what is repeated and currently in the founder's head.
Should SOPs be text or video?
Both, paired. Video (Loom, Tella) is fastest to create and best for learning the first time. Text is fastest to reference once you know the process. Best practice: short video (5 to 10 minutes) embedded in a text SOP, with the text version as the searchable, updatable source of truth. Pure video SOPs fail because they are not searchable and they go stale faster than text (an interface change makes the video wrong). Pure text SOPs fail for visual or complex processes. The combination outperforms either alone.
Who should write the SOPs - founder or team?
The person doing the work writes the first draft. Then the founder or process owner reviews and edits. If the founder writes every SOP, two bad things happen: founder bandwidth becomes the bottleneck for documentation, and the SOPs reflect founder's mental model rather than how work actually happens. Better workflow: each team member documents their own top 3 to 5 workflows during a focused 'SOP sprint' (one week, 5 hours per person), then reviews happen across the team. This builds documentation culture and produces more accurate SOPs.
How do I get the team to actually use SOPs?
Three moves. One, integrate SOPs into the daily tool flow - if the SOP lives in Notion but the work happens in Asana, link from Asana task templates to the relevant SOP. Two, make SOP-following part of performance review and onboarding ramp; the new hire's 30-day check-in includes 'which SOPs did you use this month.' Three, when something goes wrong, the post-mortem asks 'was there an SOP, was it followed, what should the SOP say differently.' This frames SOPs as living improvements, not bureaucratic compliance. Teams that experience SOPs as helpful actually use them; teams that experience them as policing ignore them.
When should an SOP become an automation?
When the SOP is followed more than 10 times per week, has clear decision rules, involves digital tools with APIs, and the task takes more than 5 minutes per execution. Common candidates: lead routing, invoice sending, status update emails, calendar booking, data syncs between tools. Tools: Zapier (most common, 20 to 800 dollars per month), Make (formerly Integromat, cheaper, more powerful), n8n (open source, technical). Rule of thumb: any SOP repeated more than 50 times in its lifetime saves money by being automated. Below that volume, the build cost exceeds the time savings.
In your business
- →Start with the 5 most-repeated workflows
- →Write the SOP, then have someone new follow it - the gaps reveal themselves
- →Review and update quarterly based on real use