Write the SOP First: Do This Before You Automate Anything
Written by Kamran, Founder, 3xRevenue. Last updated · 7 min read.
Before you automate any process with AI, write down how it works today. That written process, the standard operating procedure (SOP), must answer six questions, and the automation follows it. A clear SOP separates an AI project that works in two weeks from one that drags on for months.
Why AI automation needs a written SOP first
The SOP is the blueprint for the automation. It is also the most skipped step in AI projects. People jump straight to the tool: "Let's put an agent on it."
Then they find out the process lives in someone's head. Three people do it three different ways. Every good workflow automation project we run starts one step earlier, with a written process.
An SOP is a short, written description of how a task is done, step by step. Anyone can follow it the same way. For AI, it does one more job. Every trigger, decision and hand-off in your workflow automation comes from it.
Without an SOP, the person building the automation has to guess, and guesses turn into bugs. With one, the build is mostly translation.
The six questions every SOP must answer
Every SOP that can be automated answers the same six questions. Each answer maps to one part of the build.
| Question | Why it matters for automation | Example (new lead from the website) |
|---|---|---|
| What triggers the task? | This becomes the automation's trigger | A new form submission |
| What are the steps, in order? | Each step becomes an action | Add to CRM, send welcome text, assign to sales |
| What information is needed at each step? | Defines the data the automation must pass along | Name, phone, service, budget |
| What does done look like? | Tells you how to test it | Lead in CRM, text sent, owner assigned |
| What are the exceptions? | Becomes the rules for branches and errors | No phone number, existing customer, spam |
| Who decides when something does not fit? | Becomes the hand-off to a person | The sales manager |
Source: our own SOP checklist, used on client automation projects.
Get your first process automated
Six steps to a one-page SOP your automation can follow
Pick one task, watch it, write it, and test it by hand. The six steps below take a frequent task from habit to a page anyone can follow.
1. Pick one task
Choose something that happens at least weekly and follows rules. Good candidates are answering new leads, sending invoices or onboarding a client. Quick check: can you describe it in under ten steps?
2. Watch it being done
Sit with the person who does it, or record their screen once. Write down every click and decision, not what the process is supposed to be. Quick check: did anything surprise you?
3. Write the six answers
Use the table above. Keep sentences short and use the real names of fields and apps. Quick check: could a new hire follow it without asking?
4. List the exceptions
Most broken automations fail on the cases nobody wrote down. Ask "what happens when..." until you run out of answers. Quick check: you have at least three exceptions.
5. Simplify before you automate
Remove steps that exist only because of habit. Fewer steps means a cheaper, more reliable automation.
6. Test the SOP by hand
Have someone else follow it once, exactly as written. Fix whatever confused them.
A one-page SOP template you can copy
A good SOP fits on one page with eight short sections. Copy this outline into a doc and fill in each line.
- Name and owner. The task name and the one person who keeps the SOP current.
- Trigger. The single event that starts the task, such as "form submitted" or "invoice due".
- Inputs. The data you need before step one, with the exact field names from your apps.
- Steps. A numbered list, one action per line, each starting with a verb.
- Done looks like. The checks that prove the task finished correctly.
- Exceptions. Each "what if" case and what happens next.
- Decision maker. Who gets the case when it fits no rule, and how they are told.
- Last updated. The date and what changed.
Write each step so it names the app, the action and the field. "Add lead to CRM" is vague. "Create a CRM contact with name, phone and service from the form" is something a builder can wire up.
Keep a separate line for anything that needs judgment. Those lines become the hand-offs to a person, not the parts you automate.
Example: one SOP for 40 quote requests a week
This example shows a home services company that gets about 40 quote requests a week. Before the SOP, each request was handled differently depending on who saw it first. Some waited a day for a reply.
The SOP fit on one page. It listed the trigger (form submitted), five steps, the data needed and what done looks like. It named four exceptions (no phone, out of area, existing customer, spam) and the manager as decision maker.
The automation built from it replies within a minute. It routes out-of-area requests to a polite decline and sends anything unusual to the manager. Most of the build time went into the exceptions the SOP had already listed.
From first SOP to first automation in four weeks
One task, one week per stage, gets you from a list of chores to a working automation. Use this checklist:
- ☐ Week 1: list your ten most repeated tasks and pick the most frequent one
- ☐ Week 2: watch it being done and write the one-page SOP
- ☐ Week 3: simplify it and have someone test it by hand
- ☐ Week 4: automate it, then check our Zapier vs Make vs n8n guide to pick the tool
After week 4, pick the next task on your list. The second SOP is faster because the format is already set.
How to keep the SOP and the automation in sync
Store the SOP next to the automation and change them together. If they drift apart, nobody knows which one is right.
Give every SOP one owner. When a step, a field name or an app changes, the owner updates the SOP the same day. Then the automation gets the same change.
Review each SOP when something breaks or a new exception shows up. Add the case to the exceptions list before you fix the automation. That way the next builder sees why the rule exists.
Five mistakes that break SOP-based automations
Most failed automations trace back to one of these five gaps in the SOP.
- Writing the ideal process instead of the real one. Watch it being done first.
- Skipping exceptions. They are where automations break.
- Making it too long. One page beats ten. Link to details instead of pasting them in.
- Letting it go stale. When the automation changes, update the SOP the same day.
- No owner. Every SOP needs one person who keeps it current.
FAQ
What is an SOP?
A standard operating procedure is a short written guide to how a task is done, step by step. It makes sure the task is done the same way every time, by a person or by software.
Why do I need an SOP before using AI?
An AI agent or automation can only follow instructions that exist. The SOP is those instructions. Without it, the build is guesswork and the results are inconsistent.
How long should an SOP be?
For most tasks, one page. If it runs longer, the task is probably several tasks and should be split.
Can AI help write the SOP?
Yes. Record yourself doing the task, transcribe it, and ask an AI assistant to turn the transcript into the six-question format. Then check every step yourself. Our prompt optimizer can help you write the request.
Which tasks should I write SOPs for first?
The frequent, rule-based ones: lead follow-up, scheduling, invoicing, onboarding and reporting. They pay back fastest when automated.
What if my process is different every time?
Then it is not ready to automate yet. Write down the parts that repeat and mark the rest as decisions for a person. Automate the repeating parts first.
Why skipping the SOP costs more than writing it
Write the SOP first. It takes an hour or two and usually shows you how to simplify the process. It turns an AI project from guesswork into a straightforward build.
Skip it, and you pay for the missing hour many times over in fixes.
Want your processes mapped and automated?
We write the SOP with you, then build the automation on top of it. It is part of our custom AI systems and AI lead follow-up. Book a free strategy call.