Most business owners know they should have written processes. They just never write them. Not because they’re lazy. Because sitting down to document how you do something, when you’re the person who already knows how to do it, feels like the most pointless use of an afternoon imaginable.
I know this because I did it too. I had a folder called “SOPs” for two years. It had four files in it. None of them were finished.
That changed when I started using AI to write them for me. Not to think for me, not to invent a process I don’t have, but to pull the steps out of my head and put them into a format that actually works. The whole thing now takes about 30 minutes per process, sometimes less.
Here is exactly how to do it.
What a good SOP actually needs
Before you write anything, it helps to know what you’re aiming at. A standard operating procedure that actually gets used has six things in it:
- Purpose. One sentence. What does this process produce?
- Trigger. What starts the process? A client signs up, an invoice is sent, a Monday arrives.
- Frequency. How often does this run?
- Steps. The actual sequence, with who does what and which tool they use.
- Expected output. What does “done” look like?
- Notes. Edge cases, exceptions, things that go wrong.
That is it. No one needs a 12-page document for a process that takes 20 minutes to run.
Step one: pick one process
Not five. One.
Pick the thing you do most often that you have never written down. For most small business owners that is something like: sending a proposal, onboarding a new client, writing and sending a weekly report, or briefing a subcontractor.
I am going to use client onboarding as the example here, but the method works for anything.
Step two: do a brain dump first
Before you touch Claude, spend three minutes writing out the steps yourself. Just type them, don’t worry about order or detail. Something like:
“Client signs contract. I send a welcome email. I set up their folder. I send a questionnaire. I book a kickoff call. I add them to my project management tool. I send a calendar invite.”
That is your raw material. It does not need to be good. It just needs to be real. The brain dump is what makes the AI output actually match your process rather than some generic version from the internet.
Step three: the prompt
Open Claude. Paste this, with your brain dump in the brackets:
I need you to write a Standard Operating Procedure for the following process in my business. Use the steps I have listed below as the basis. Do not invent steps that are not in my list. Format the output with these sections: Purpose, Trigger, Frequency, Steps table (with columns: Step number, Action, Who, Tool, Output), Expected output, Notes.
My process steps: [paste your brain dump here]
My business: [one sentence about what you do and who your clients are]
That last line matters. Without it, Claude will write a generic SOP. With it, the language will match your actual context.
What the output looks like
Within about 30 seconds, you will get something like this for the client onboarding example:
Purpose: To bring a new client from signed contract to active project status within 48 hours.
Trigger: Client signs the service agreement.
Frequency: Per new client.
Steps:
| Step | Action | Who | Tool | Output |
|—|—|—|—|—|
| 1 | Send welcome email from template | You | Gmail | Email delivered |
| 2 | Create client folder structure | You | Google Drive | Folder ready |
| 3 | Send onboarding questionnaire | You | Typeform | Questionnaire link sent |
| 4 | Add client to project board | You | Notion | Client row active |
| 5 | Send kickoff call invite | You | Calendly | Calendar invite sent |
Expected output: Client is in the system, questionnaire is sent, kickoff call is booked. All within 48 hours of contract signing.
Notes: If the client does not complete the questionnaire within 3 days, send one follow-up. If no response after 5 days, flag as at-risk.
Not bad for 30 seconds of work.
Step four: review it properly
This is where people rush and end up with a useless SOP. Spend 10 minutes on this part.
Read through every step. Ask yourself:
- Is this actually how I do it?
- Is there a step missing?
- Does this reflect the tool I actually use, not a generic one?
- Are the notes capturing the real edge cases?
Change anything that does not match. Add anything that is missing. The AI gives you the structure. You give it accuracy.
The version that comes back from Claude is about 80{a935142a1389e3b085cdb10902f36b38bc6d85407e37e393e69a3cb0d2c4e616} right. Your 10-minute review gets it to 100{a935142a1389e3b085cdb10902f36b38bc6d85407e37e393e69a3cb0d2c4e616}. That is a much better ratio than starting from a blank document.
Step five: save it somewhere it will actually be used
An SOP in a folder no one opens is just a longer way to waste an afternoon. Where you save it matters.
If you have a team, that means your project management tool or a shared drive. If you have a virtual assistant, it means a folder they have access to. If it is just you, it means somewhere you will find it when you need it, not somewhere that feels tidy today.
The SOP also needs a clear file name. Client onboarding SOP v1 2026.md is findable. Process doc final FINAL is not.
How long does this actually take?
Here is how 30 minutes breaks down:
- 3 minutes: pick the process and do the brain dump
- 2 minutes: set up the prompt and paste it in
- 1 minute: wait for Claude to output the draft
- 10 minutes: review and edit
- 5 minutes: save, name, and file it correctly
- 9 minutes: enough buffer for the inevitable distraction
That is one process documented per session. Run this once a week for a month and you have four SOPs. Run it twice a week and by the end of the month you have a proper process library.
What to document first
If you are starting from zero, here is a simple order of priority:
- Highest frequency first. Whatever you do most often. Even a 15-minute task done daily adds up to 60+ hours a year.
- Whatever you most dread someone asking about. If a team member or VA asked you to explain your proposal process right now, would you struggle? Document that one.
- Anything with real consequences if done wrong. Billing, contracts, client communication.
Start there. Leave the edge cases and the rarely-run processes until you have the core ones covered.
The compounding effect
Here is the part no one talks about.
A single SOP saves you 20 minutes the next time you do that task with a new team member. Ten SOPs means you can onboard a virtual assistant in a day instead of a week. Twenty SOPs means the business starts to run on documented process instead of knowledge that lives only in your head.
That is worth the 30 minutes.
If you want AI to write your SOPs automatically
The method above works well as a manual process. But if you want something faster, and you want the SOP to feed directly into an AI automation, there is a smarter way to do it.
The brain build includes a skill called brain-sop. You describe the process, answer a few questions conversationally, and it produces a complete SOP saved directly into your business brain. Every step is classified: what runs automatically, what needs a human, what uses an external tool. It also flags automation potential before you ask.
If you are building a library of processes anyway, doing it inside the brain means each SOP is ready to be automated the moment you decide you want that.
More on how that works: Clever Operators Brain Build.
FAQ
Can I use ChatGPT instead of Claude for this?
Yes. The prompt works with any capable AI. Claude tends to produce cleaner structured output, which matters when you are creating a table format, but the method is the same.
Do I need Claude Code, or will Claude.ai work?
Claude.ai at claude.ai works fine for writing SOPs manually. Claude Code is needed if you want the process to integrate with an automated brain build system.
How detailed should each step be?
Detailed enough that someone who has never done the task before could follow it. If a step needs more than one sentence to explain, it should probably be split into two steps.
What if my process is different every time?
If there is no consistent pattern, it is not a process, it is judgement. You cannot SOP judgement. But most things that feel variable actually have a consistent core. Start with the core and note the exceptions.
How do I keep SOPs up to date?
Add a review date when you create the file. Every 90 days, open each SOP and check whether the tools or steps have changed. Most will not need much. The ones that do will be obvious because your team will be going off-script.
What is the biggest mistake people make when writing SOPs?
Making them too long. An SOP is not a training manual. It is a checklist for someone who knows the basics. If it takes more than 10 minutes to read, it will not get used.
