Solo business operations
How to Build a One-Page SOP for a Solo Business in Six Steps
A practical method for turning repeated work held in the founder's memory into a one-page SOP with six fields: trigger, completion standard, steps, exceptions, record location, and next owner.
Create the manual when work repeats, not when you hire
A solo founder often feels the process is obvious because the same person handles it every time. Rebuilding quotes, payment checks, or delivery notices from memory creates decision fatigue and inconsistent omissions. Treat a task as an SOP candidate when it repeats for the third time. The goal is not more documentation; it is a faster, consistent next execution.
The six fields of a one-page SOP
- Trigger: state the event that starts the work.
- Done definition: define what must be verified before the task is complete.
- Steps: list only five to seven actions, each beginning with a verb.
- Exceptions and decisions: record branching rules such as amount, deadline, or customer status.
- System of record: name where the result is stored.
- Next owner or action: state who continues the flow and what happens next.
Write decision rules before explanations
Manuals become long when background explanation dominates. Lead with a rule that makes two readers choose the same action, such as: If there is no reply within two business days after the quote, send one check-in. Screenshots age quickly as interfaces change, so use them only as support and preserve the decision checkpoint in text.
Test whether someone else can execute it without explanation
The author automatically fills missing details from memory. Give the document to someone unfamiliar with the task and revise every point that triggers a question. Questions are not failure; they expose hidden steps and ambiguous completion criteria. Apply only the changes revealed by one execution, then test again to prevent the document from becoming unnecessarily complex.
Manage the version and review date in one line
At the top, keep only owner · last updated · next review. Do not rewrite the SOP immediately for every exception; collect observations and apply them during a weekly review. Store one source of truth instead of copies in multiple folders, and link to that original wherever the process is referenced.
Email workflows become clearer when triggers and records are separated
The same structure works for inquiry-to-quote and payment-to-delivery email flows. A message arrives in the inbox is the trigger, while customer status and the next contact date are recorded is the done definition. When connecting company email to other services, use the OfficialMail external integration guide to separate automatable steps from decisions that need a person.
Frequently asked questions
Which task should become an SOP first? Start with work that repeats at least three times a month and affects customers or cash flow when missed.
How long should it be? Begin with one page and move supporting material behind links.
Is it useful when I work alone? Yes. Write it as a handoff to your future self to reduce mistakes after a break or during busy periods.
When should I automate? After the process and exceptions fit reliably on one page, automate repeated entry and reminders first.
Related operating guides
Use the weekly priority guide to choose which SOP to build first. See the customer inquiry handoff guide for transferable workflows and the customer FAQ guide for turning repeated questions into standard answers.
Start with OfficialMail
Start operating with one official primary mailbox.
Use one primary mailbox as your company's official address and review every domain-connection value directly in the mailbox.