Operations · SOPs
AI SOP Generator
An SOP (standard operating procedure) is a written set of steps for doing a task the same way every time. Describe how you do it now, in your own words, and get an SOP a new team member could follow on day one.
Example
See what you get back
A sample run: Onboarding a new client at a cleaning company. Your result is written for your own details.
What went in
Process name
Onboarding a new cleaning client
Type of business
Commercial cleaning company
How you do it now
After they sign I add them to Jobber, call to get the alarm code and key details, do a walk-through with the team lead, then send the schedule. Sometimes we forget to ask about parking and the first clean starts late.
Who does it
Office manager
Tools
Jobber, Google Sheets
Purpose and scope
This SOP makes sure every new cleaning client is set up the same way before the first clean. It starts when the client signs the agreement and ends when the first clean is booked and the client has the schedule. The office manager owns this process.
Before you start
- The signed client agreement
- Access to Jobber
- The client contact sheet in Google Sheets
- The team lead's availability for a walk-through
Step-by-step
- Add the client to Jobber with their address, contact name, phone and email.
- Call the client to collect access details.
- Alarm code and who to call if it goes off
- How the team gets keys
- Where the team can park
- Record the access details in the client contact sheet.
- Book a walk-through with the team lead and the client.
- Walk the site with the team lead. Note any special rooms, materials or requests.
- Create the cleaning schedule in Jobber.
- Send the schedule to the client. [check: by email, or through Jobber?]
- Brief the team lead on access, parking and special requests before the first clean.
Quality checks
- The client is in Jobber with correct contact details.
- Alarm code, keys and parking are recorded in the contact sheet.
- The walk-through notes are saved.
- The client has confirmed the schedule.
Common mistakes
- Forgetting to ask about parking. The first clean starts late. Ask about parking on the access call every time.
- Access details only in someone's phone. Always record them in the contact sheet.
- Skipping the walk-through. The team arrives without knowing special requests.
What could be automated
- A form the client fills in after signing could collect access and parking details, so the call is shorter.
- Jobber could send the schedule to the client automatically once it is created.
- A checklist in Jobber could remind the office manager of each step.
How it works
Three steps, about a minute
01
Describe the task
Write how you do it now, in plain words. Add who does it and the tools you use.
02
Get a clear SOP
You get the purpose, what you need, numbered steps, quality checks, common mistakes and ideas for what to automate.
03
Fill the gaps and share
Answer any [check: ...] notes, paste it into your handbook or shared drive, and give it to the team.
Who it is for
Who uses an SOP generator
Any small business where the owner is the only one who knows how things are done. Writing SOPs is how you hand work over without losing quality.
Cleaning and home service companies
Write how a job is set up, done and checked, so every team does it the same way.
Clinics and salons
Document opening and closing, booking rules and how to handle a no-show.
Agencies
Write how a new client is onboarded or how a monthly report is made.
Online shops
Document how orders are packed, how returns are handled and how stock is counted.
Restaurants and cafes
Write opening checklists, cleaning routines and how deliveries are checked in.
Anyone hiring their first employee
Turn what you do every day into steps a new person can follow.
Guide
How to write an SOP your team will actually use
A good SOP is short and easy to follow while doing the task. These tips help you write one your team will open and use.
1.
Pick one process at a time
Start with a task that happens often and goes wrong when you are not there. One SOP for one process. "Onboarding a new client" is a good size. "How we run the business" is too big. A good way to choose: list the questions your team asks you most often. Each common question is usually a process that needs an SOP.
2.
Write down how it is done today
Write how the task is done now, then improve it later. The fastest way is to talk it through or write it as you do the task. Do not worry about good writing at this stage. Notes, half sentences and lists are fine. The structure comes later, and this tool can do that part.
3.
One action per step
Each step should be one thing to do, starting with a verb like "Add", "Call" or "Check". If a step has "and" in it twice, split it. Keep steps in the order they really happen. If a step depends on a choice, add a short sub-point such as "If the client has no alarm, skip to step 4."
4.
Say what "done right" looks like
Add quality checks at the end. These tell the person how to know they did it correctly, without asking you. Good checks can be seen or counted. "The client has confirmed the schedule" is a good check. "The client is happy" is too vague to check.
5.
Write down the common mistakes
You already know what usually goes wrong. Put it in the SOP with how to avoid it. This is often the most useful part for a new person. Add the reason each mistake matters. People follow a rule more carefully when they know what goes wrong if they do not.
6.
Test it with someone new
Give the SOP to someone who has not done the task. Watch where they get stuck or ask a question. Fix those parts. Do this once when the SOP is new, and again whenever the process changes. An out-of-date SOP can cause more mistakes than having none.
7.
Keep it where the work happens
Put the SOP in a shared drive, your job software or a printed sheet at the workstation. An SOP nobody can find does not get used. Add the date it was last updated and who owns it at the top. Then everyone knows who to ask when something changes.
8.
Look for steps to automate
Once a process is written down, you can see which steps are repeated typing or reminders. Those are often easy to automate with your existing software or simple AI tools. Start with one small step, such as a reminder email or a form that collects information. Small changes that save time every week add up.
What a pack buys
How many runs each pack gives you
Tokens are the only thing you buy, and they work on every tool here. This is what they turn into on this one — pick a model down the side, read across to the pack.
Questions
Before you start
It is free to try. Your first SOP needs no account. After that, a free account gives you free tokens, with no card needed. When those run out, you can buy a token pack. There is no subscription.
SOP stands for standard operating procedure. It is a written set of steps that shows how to do a task the same way every time.
The tool does not guess. Where something is unclear, it adds a step marked [check: ...] so you know what to fill in.
Yes. Copy it into Word, Google Docs, Notion or your handbook and change anything.
We save what you typed and the result with your run so you can see it again and so we can fix problems. We do not sell it or share it with other users. The text is sent to an AI model provider to write the SOP.
As short as possible while still complete. Most small business SOPs fit on one or two pages. If it gets longer, split it into two processes.
What we actually do
This tool is the small version. We build the whole thing.
The sop generator does one job, for free, for anyone. Our actual work is building AI systems that run inside a business — the automations, the internal tools your team uses every day, and the parts that talk to the software you already have.
Not sure what is worth automating?
Write one paragraph about your business. We read it, ask a few questions, and show you which work a computer can do for you — and which work it should not touch. Free, and there is nothing to install.
About five minutes
Results by email
No sales calls
Already know what you want built?
Tell us in one line. We will say whether we can build it, what it would take, and we say no if it is not a fit.
Same people who built the tool you just used.