The SOP Template I Use for Every Process in My Solo Business (Free)

There's a thing that happens about 18 months into running a solo service business. You get sick. Or you take a long weekend. Or your brain just has a forgetful day. And three things fall through the cracks — a client question goes unanswered for four days, a content post doesn't go up, an invoice gets sent a week late.

You realize, quietly and uncomfortably, that the entire business lives in your head.

SOPs fix that. And not the corporate 40-page PDF kind of SOP. The "I wrote this for myself on a Tuesday" kind.

What an SOP actually is (and isn't)

A Standard Operating Procedure is a document that tells you (or anyone) how to do a repeatable task, step by step, the way you want it done.

It's not a legal-grade binder. It's not a manual a new hire could read cover-to-cover. It's a recipe card.

Think of the best handwritten recipe in your family: you can follow it and reproduce the dish, even though it's not particularly formal. That's the right mental model for a solo business SOP.

Why solo operators still need SOPs

"I'm the only person doing the work" is actually the best reason to write SOPs, not the reason to skip them.

SOPs help you specifically because:

• They eliminate decision fatigue. "How do I send an invoice again?" is a small tax — taken 50 times a month it compounds. SOPs replace remembering with reading.
• They catch automation opportunities. The moment you write down steps 4-7 of a process, you usually spot which ones a tool could handle.
• They stabilize quality on bad days. Sick, tired, rushed — you still produce A-grade work when you're just following the checklist.
• They're the onboarding doc for any future help. A $25/hour VA following your SOPs is worth more than a $60/hour contractor you have to train from scratch.
• They let you take actual time off. The ones that matter are the ones that don't fall apart while you're in Portugal for 10 days.

The SOP template (one page, six fields)

Here's the exact structure I use for every SOP in my business. No more, no less.

PROCESS NAME
(What you call this thing — "New client onboarding," "Weekly content publish," etc.)

TRIGGER
(The event that starts this process — "New client signs contract," "Sunday 4pm")

ESTIMATED TIME
(How long this takes end to end, in minutes)

TOOLS
(Everything you need open to run this — Gmail, Notion, Stripe, etc.)

STEPS
1. [What to do]
   Tool: [Which tool]
   Output: [What should exist when this step is done]
   Time: [Rough minutes]
2. …

QUICK CHECKLIST
□ [Condensed version of each step — one line each, no detail]
□ …

That's it. No cover page, no change log, no approval signatures. One page. Read top to bottom in 60 seconds.

The "Quick Checklist" at the bottom is the secret weapon. When you know the process already, you don't re-read the whole thing — you just tick boxes. When you're new to it (or it's been a month), you read the full steps.

The 5 SOPs to write first

If you only write five SOPs in your first quarter, write these. They're the ones that touch the most money and the most client experience.

1. New client onboarding

Trigger: new client signs contract (or whatever your "start" signal is).

Covers: welcome email, intake form, project folder creation, kick-off call scheduling, adding them to your CRM/dashboard, sending the first invoice.

If you automate this one (I broke down a free-tool onboarding flow here), your SOP becomes "verify the automation ran correctly" — which takes 2 minutes instead of 2 hours.

2. Project delivery (per package type)

Trigger: kick-off call completed.

Covers: research/discovery steps, creation steps, review steps, delivery steps, handoff, and the post-project follow-up.

This one's the longest SOP in your business. Don't try to write it in one pass. Write it next time you deliver a project — step by step as you go. First draft in 90 minutes, refined over 2-3 projects.

3. Invoicing and payment follow-up

Trigger: deliverable is accepted OR specific date (monthly retainer).

Covers: generating the invoice, sending it, logging it in your accounting, and the follow-up sequence if it's not paid within 14 and 21 days.

If you've ever forgotten to chase a late invoice, this SOP pays for the entire SOP-writing effort in one month.

4. Content creation and publishing

Trigger: new content piece in progress.

Covers: outline, draft, edit, publish, promote, repurpose.

This is the SOP most solo consultants don't have, which is why their content schedule is inconsistent. Batching alone won't save you — I wrote about the full batching flow — but a content SOP is the other half of consistency.

5. Weekly business review

Trigger: every Friday 4pm (or your equivalent slot).

Covers: review the client pipeline, check accounts receivable, review content calendar, update Notion dashboards, close open loops from the week, set the next week's priorities.

This is the 30-minute weekly habit that does more for the business than anything else. Without an SOP it falls off whenever you're busy. With an SOP it happens every Friday.

The fastest way to write an SOP (do this)

The mistake that kills SOP projects is thinking you have to write them in one sitting from memory.

Here's the faster path:

1. Wait for the next time you do the task. Don't try to write it cold — wait for the natural trigger.
2. Hit record in Loom. Screen record + your voiceover. Do the task exactly as you normally would. Don't try to be polished.
3. When done, stop the recording. Don't re-do it. Messy is fine.
4. Watch the Loom back at 2x speed the next morning. Pause and type each step into the template as you hear it.
5. Read it once. Anywhere you wrote "I usually…" or "it depends…" — get specific. SOPs can't have ambiguous steps.

Total time for a first draft: about 20-30 minutes beyond the task itself. Next time you do the task, use the SOP, and tweak what was unclear. By the third use, it's close to perfect.

Where to store SOPs

Two rules:

Everything in one place. One Notion workspace, one Google Drive folder, one Coda doc. Scattered SOPs are unfindable SOPs.

Searchable. Whatever tool you use needs full-text search. That's why Notion and Coda win for most people — Google Drive search is okay but SOPs live inside docs, not as filenames.

I use a single Notion database with two properties: category (Client Work / Marketing / Admin / Finance) and status (Active / Draft / Archived). Every SOP is a page. The database view is my table of contents.

How to know your SOPs are working

Three signals:

• You reach for the SOP instead of remembering. If you still do the task from memory, either the SOP is bad or you haven't internalized using it.
• The SOP gets shorter over time. As you automate steps, the SOP shrinks. A 10-step SOP that becomes a 3-step SOP means 7 steps got automated, which is the real win.
• You take a week off and nothing breaks. The ultimate test. If things still hit the fan, your SOPs don't cover enough yet.

What to skip

• Flowcharts for everything. Text + checkbox is plenty. Flowcharts are for processes with real branching; most solo-business processes are linear.
• Video SOPs as the primary format. Video is great for the first draft; text is what you actually refer to weekly. Never make video the only version.
• Versioning. You're not running an ISO audit. Update the SOP and move on.

Frequently asked

How many SOPs does a solo service business need? Most solo operators settle around 15-25 SOPs total. More than that and you're probably over-documenting; fewer and you're still running things from memory.

How often should I update them? Whenever something changes (new tool, new service, new pricing). I also do a 30-minute SOP review every quarter — click through each one and update anything stale.

Should I make SOPs public to share with clients or audience? Some of them, yes. "Here's how we run onboarding" is a trust-builder worth sharing. "Here's how I generate invoices" is private operations. Use judgment.

The single easiest way to make this real: write the weekly business review SOP this Friday. It's the shortest, fastest to use, and it'll immediately change how you end your week.