SOP Template for a One-Person Business

An SOP for a one-person business needs four things: the trigger that starts the process, the numbered steps in order, the tools or accounts involved, and what "done right" looks like — written down once, under one page, so a repeating task gets done the same reliable way every time instead of being re-figured from memory. The point isn't bureaucracy; it's removing the small decisions a repeating task shouldn't require every time. Below is the template and a prompt that writes one from how you actually already do the task.

Why a solo business needs SOPs at all

It's tempting to think SOPs are for teams — a way to keep multiple people doing something consistently. For a one-person business, the reason is different but just as real: a written process is what stops a task from being quietly re-invented, and re-decided, every single time you do it. Onboarding a client the fourth time shouldn't require remembering what worked the first three times from memory; it should be a checklist you follow.

The second reason matters more over time: a written SOP is what makes it possible to eventually hand a task to a VA, a contractor, or future automation — something that's impossible if the process only ever lived in your head.

The four-part structure

1. Trigger — what starts this process. "A new client signs the proposal" or "the 1st of the month."
2. Steps — the actual sequence, numbered, specific enough that you (or someone else) could follow it without guessing.
3. Tools — what accounts, software, or templates are involved at each step.
4. Done looks like — the specific, checkable outcome that tells you the process is actually finished, not just started.

The template

SOP: [PROCESS NAME]

Trigger: [What starts this — an event, a date, an email.]

Steps:

1. [Step one]
2. [Step two]
3. [Step three]

Tools: [Accounts, software, templates used.]

Done looks like: [The specific, checkable outcome that confirms this is finished.]

Where to start

Don't try to document everything at once — that's the surest way to abandon the whole idea by the second SOP. Start with three:

• Client onboarding — a natural fit if you already have an onboarding checklist; turning that checklist into a formal SOP with a trigger and tools list is a short step from something you likely already do informally.
• Invoicing and payment chasing — trigger: project milestone hit. Steps: send invoice, log due date, follow the late-payment reminder template if it goes overdue.
• Whatever task you personally repeat most and dread most. The dread is usually a sign the process is being re-decided every time rather than followed.

Keeping SOPs alive, not just written once

A written SOP that never gets revisited goes stale — a tool changes, a step stops applying, and the document quietly becomes wrong. The fix isn't a big review project; it's a habit of updating one SOP whenever a task feels harder than it should, right when you notice it, rather than scheduling a separate audit. Folding "does any SOP need a two-minute update" into a weekly review is enough to keep them accurate without it becoming its own project.

The copy-paste prompt

Describe how you actually do the task, roughly, and this turns it into a proper SOP in the structure above.

You are a plainspoken assistant writing a standard operating procedure (SOP) for a
one-person business, based on how the owner actually already does a task.

Context:
- The task or process: [NAME]
- What triggers it (an event, a date, an email): [TRIGGER]
- Roughly how I currently do it, in my own words, doesn't need to be organised: [ROUGH
  DESCRIPTION]
- Tools, accounts, or templates involved: [TOOLS]

Task: turn this into a clean SOP with four sections — Trigger, Steps (numbered, specific
enough to follow without guessing), Tools, and "Done looks like" (a specific, checkable
outcome).

Constraints: under one page. Don't invent steps I didn't describe — if something's unclear
or missing, ask rather than filling in a guess. Number the steps in the actual order they
happen.

What it looks like written out

For a freelance photographer's "deliver final gallery" process, described roughly as "I edit the photos, upload them somewhere, then tell the client," the output tightens it into something actually followable:

Trigger: Final edit pass complete.

Steps:

1. Export final images at delivery resolution to the gallery folder.
2. Upload to the gallery platform, set expiry date per contract terms.
3. Send delivery email with gallery link and download instructions.
4. Log delivery date in the client tracker.

Tools: Lightroom, [gallery platform], client tracker spreadsheet.

Done looks like: Client has received the delivery email, gallery link is live and tested, tracker is updated with today's date.

Four steps that were already happening informally, now written down once — so step three never gets accidentally skipped on a busy week, and the process is ready to hand off the day it's needed.

FAQ

Do I actually need SOPs if I work entirely alone?

Yes, for a different reason than a team would — a written SOP is what lets you do a repeating task the same reliable way without re-deciding it from scratch, or hand it off later without it living only in your head.

How many SOPs should a solo business actually have?

Start with three: client onboarding, invoicing, and whatever task you personally repeat most and dread most. Add more only when a task's repeated inconsistently enough to actually cause a problem.

How long should one SOP be?

Under one page. If it's longer, it's usually covering more than one process and should be split — a long SOP is one people stop opening.

Writing these up is one of 30 ready-made workflows in the AI Business OS — describe the task roughly, and a clean SOP is ready in well under a minute, in our runs.