The SOP Library for a One-Person Business — Document Once, Delegate (or Automate) Forever
Solo founders document nothing because "it’s all in my head and I’m not hiring". But SOPs are not just for employees: they are how you automate a process (the SOP is the automation spec), how you sell the business someday, and how you survive a week of flu without the business flatlining.
This guide builds a library that stays alive: the capture habit, the 20-minute SOP format, the priority order, and the path from document to automation.
The short answer
- The top 10-15 recurring processes cover most of a solo business’s operational hours.
- A written SOP is the prerequisite for automation — you cannot automate a process you cannot describe.
- Businesses with documented operations sell at meaningfully higher multiples: the buyer purchases a system, not a job.
Who this playbook is for
Built for solo founders whose processes live in their head and whose future VA (or automation) has nothing to inherit.
Step 1: Capture processes as you do them, not in a documentation retreat
The habit: next time you do something recurring, record your screen (Loom) while narrating decisions. That recording is the raw SOP. Documentation retreats die; capture-as-you-go survives because it costs two extra minutes during work you were doing anyway.
Step 2: Use the 20-minute SOP format
Per SOP: purpose (one line), trigger (what starts this), steps (numbered, with screenshots), decisions and their rules ("if invoice > $5k, call first"), tools with links, and the failure path (who to alert when it breaks). Twenty minutes per SOP keeps them short enough to maintain and specific enough to delegate.
Step 3: Prioritize by frequency and risk
Document in this order: weekly recurring (invoicing, reporting, publishing), client-facing with quality risk (onboarding, delivery handoffs), and rare-but-critical (backup restore, outage response, payment issues). Your morning email ritual can wait; the thing that breaks the business when you have flu cannot.
Step 4: Convert SOPs to automations deliberately
Every SOP gets an automation audit: which steps are mechanical? Those become an n8n/Zapier recipe with the SOP as its spec and documentation. The SOP shrinks to the judgment steps. This is the real payoff loop: document → automate → redocument → next process.
Step 5: Review SOPs on a schedule, not on a crisis
Quarterly, thirty minutes: run down the library, update anything drifted, delete anything dead. SOPs rot silently — the outdated invoice SOP that references the old bank account is discovered exactly when a new VA follows it. The quarterly pass is thirty minutes of insurance.
Your weekly operating rhythm
| Day | Action | Time |
|---|---|---|
| As work happens | Screen-record recurring processes | 2 min extra |
| Weekly | Turn one recording into one SOP | 20 min |
| Quarterly | Library review and drift cleanup | 30 min |
| Per automation | Audit steps; build the recipe; redocument | 2-3 hrs |
KPIs that tell you it is working
| Metric | Healthy target | Why it matters |
|---|---|---|
| SOPs in library | 10-15 within a quarter | The core coverage target |
| Documentation freshness | Reviewed quarterly | Stale SOPs are worse than none |
| Processes automated from SOPs | 1+ per month | The document-to-automation conversion rate |
| Delegate-ready processes | Growing share | Anything a VA could run tomorrow |
Common mistakes to avoid
- Writing perfect prose SOPs. Nobody maintains novels; the format’s job is transfer, and screenshots with numbered steps transfer better than paragraphs.
- Documenting everything before automating anything. The audit-first order wastes effort — document, then automate the mechanics, then redocument what remains.
- SOPs with no failure path. The most important field is "when this breaks, do X" — undocumented failure handling is exactly what lives only in your head.
A tool stack that fits a one-person budget
| Tool | Where it fits |
|---|---|
| Loom | The capture layer — narrated screen recordings |
| Notion / Scribe | The library; Scribe auto-builds step docs from captures |
| n8n / Zapier | The automation layer SOPs feed |
| A quarterly review reminder | The freshness mechanism |
Keep going
Use these internal references while implementing this guide:
- One Person Company Hub
- How to Start a One Person Company
- Solopreneur Operating System
- The Decision Journal for Solo Founders
- The 45-Minute Weekly Ops Review
- Energy Management for Solopreneurs
FAQ
Q: Isn’t this overkill for a business of one?
The library pays you directly three ways: automation specs (every SOP audited for automation), sale value (documented businesses command real multiples), and continuity (your flu week). "Team of none" is exactly when documented systems matter most — you are the single point of failure.
Q: How detailed should SOPs be?
Detailed enough that a competent stranger produces your quality: exact tools, exact steps, decision rules with thresholds. The test is the "stranger test" — hand it to a friend in your field and watch where they stall. Those stalls are the missing fields.
Q: What if my processes change constantly?
Then capture-as-you-go is even more important: recordings make updates a two-minute re-record instead of a rewrite. High-change processes also signal automation candidates — manual churn is expensive precisely because it keeps changing.
Q: Can SOPs help me raise prices?
Indirectly but really: documented operations free your hours toward the work clients pay premium rates for, and they make delegation (VA, automation) affordable. Most founders price around their own bottleneck; the SOP library is how the bottleneck dissolves.
Get the weekly operating brief
Every Monday: 3 moves, 5 minutes. Actionable strategy for your one-person company — no fluff, no filler.