Lesson 004Field guide · AI for Small Business
Simple SOPs with AI
Get processes out of your head and into teachable documents.
You'll learn
- Why processes stuck in your head cost you every week
- The talk-it-out method: you describe, AI structures
- The four things every usable SOP contains
- How to keep SOPs current without a documentation project
01Section
The business that lives in your head
How do you close up the shop? How do you onboard a new client? What exactly happens when an order comes in? If the honest answer is "I just know," then every one of those processes exists in exactly one place: you.
That's fine until you hire, take a vacation, or get sick. Then "I just know" becomes an hour of explaining, a string of texts on your day off, or a job done wrong. Writing processes down is the fix — and it's the job owners put off forever, because sitting down to write documentation feels like homework.
Plain-language definition
SOP (standard operating procedure) — a short written document that lets someone else do a task the way you'd do it, without asking you. Despite the corporate name, it can be half a page.
The reframe
An SOP isn't paperwork. It's a clone of the five minutes you spend explaining the same task — written once, reusable forever.
Checkpoint
02Section
The talk-it-out method
Here's why this finally gets done with AI: you don't have to write anything. You explain the task the way you'd explain it to a new hire standing next to you — rambling, out of order, with all the "oh, and one more thing" moments. The AI's job is turning that ramble into a clean, ordered document.
You already give this explanation out loud several times a year. The only new step is giving it to an AI once, in writing or with voice dictation, and keeping the structured result.
Pick one task: Something you've explained to another person more than once. Closing routine, order intake, the weekly supply run.
Brain-dump it: Type or dictate the whole thing as it comes to you. Don't organize, don't polish — order and gaps are the AI's problem.
Let AI structure it: It turns the ramble into numbered steps, flags the vague spots, and asks about anything missing.
Correct the draft: Read it as if you're the new hire. Fix what's wrong — you're the only one who knows what right looks like.
The SOP interview prompt
I'm going to describe a task from my business the way I'd explain it to a new employee — messy and out of order. Turn it into a clear SOP with: a one-line purpose, who does this task, the tools or things needed, numbered steps in the right order, and a short "what good looks like" section describing the finished result. If any step is vague or something seems missing, ask me about it before finalizing. Here's the task: [DESCRIBE IT HERE]
Privacy note: Real processes involve real logins. Write "log in to the booking system" and keep the actual passwords, door codes, and account numbers in your password manager — they never belong in an AI chat.
Checkpoint
03Section
What a good SOP contains
A usable SOP answers four questions. If the document answers all four, someone can do the task without calling you — which is the only test that matters.
Steps
Numbered, in order, one action each. "Wipe down the machines" is a step; "tidy up" is a wish.
Owner
Who does this task, and when it's triggered — every close, every new order, every Friday.
Tools
What's needed: the app, the key, the checklist, the supplier's phone number. Named, and where to find them.
What good looks like
How to know it's done right — "the till matches the report, doors locked, alarm light is green." Without this, done means "I stopped."
An SOP that still needs you
"Closing: clean up, sort the register, lock everything, set alarm." Four vague steps, no owner, no tools, no definition of done — the new hire is texting you by 8:15.
Key takeaway
The test of an SOP is simple: could someone do this task tomorrow without messaging you? If not, it's notes, not an SOP.
Checkpoint
04Section
Keeping them current
An outdated SOP is worse than none — it teaches the old way with full confidence. But keeping SOPs current doesn't mean scheduled documentation reviews. It means one habit: when a process changes, the SOP changes the same week, while the difference is fresh in your mind.
Two small practices make that easy. Put a "last updated" date at the top of every SOP, so stale ones announce themselves. And whenever someone follows an SOP and hits a step that's wrong or confusing, that's not an annoyance — that's your review process working. Fix it that day.
Where should SOPs live?
Wherever your team already looks — a shared folder, a pinned note, a binder by the register. The fanciest wiki loses to a printed page that's actually where the task happens. One rule: one home. An SOP that exists in three versions in three places is three ways to do the task wrong.
Pause and think: Which task in your business gets explained most often — and who's stuck explaining it every time?
Checkpoint
Prompt exercise
Document one real process, start to finish
Copy this prompt into ChatGPT, Claude, Gemini, Copilot, or whichever AI tool you have access to — the website doesn't run AI itself. Pick a real task you've explained to another person before. Describe processes and tools freely, but keep passwords, codes, and customer details out of the chat.
You're helping a small-business owner turn a process from their head into a written SOP. Interview me one question at a time: what the task is, when it happens and who should do it, then walk me through it step by step, asking follow-ups whenever a step is vague ("clean up" — clean what, with what, to what standard?). When you have the full picture, produce the SOP with: title, last-updated date, purpose (one line), owner, tools needed, numbered steps, and "what good looks like." Plain language a brand-new hire could follow.Reflection: Read the finished SOP as if it's your first day. Every place you'd still have a question is a step to sharpen — then put the document where the task actually happens.
Quick check
3 quick questions — no pressure
There's no pass or fail here. Answer them all, and we'll show you the answers either way.