Module 2 · Operations & Service Delivery
Prompt it: smoother operations today
Here’s the unfair advantage you already have: you know exactly how your business runs. You’ve run the process a thousand times. The only reason it isn’t written down is that writing is slow and your week is full. AI removes the writing — you supply the knowing.
Talk first, let AI structure it
The single best operations move at this tier is the brain dump. Open your phone’s voice memo app, do a task while talking through it — or record yourself explaining it over a screen recording — and hand the transcript to AI. Messy is fine. Out of order is fine. “Oh wait, I forgot a step” is fine. Structuring the mess is exactly what AI is good at.
What comes back is an SOP — a standard operating procedure, the written version of “how we do this here” that a new hire could follow without asking you.
Copy this prompt
You are an operations manager helping me document a process. I run a [YOUR BUSINESS — for example: "two-attorney family law firm"]. Below is a brain dump of how I do [THE TASK — for example: "onboarding a new client, from signed engagement letter to first working meeting"]. It's messy and out of order — that's expected. Turn it into a clean standard operating procedure with: - The purpose, in one line - Who's responsible - The tools or systems used - Numbered steps, detailed enough that someone new could follow them without asking me - A short "common mistakes" section at the end If I was vague anywhere, or you spot a gap in the logic, ask me up to 5 questions before writing the final version. Here's the brain dump: [PASTE YOUR TRANSCRIPT OR RAMBLING NOTES — for example: "ok so when the signed letter comes back, first thing is I open the client folder, actually no, first I check the conflict list..."]
Once you have the SOP, ask for the working version: “Turn this into a one-page tickable checklist — one action per line, must-not-skip steps in bold, and a final ‘before you mark this done’ verification line.” The SOP is the reference; the checklist is what your team actually uses. Do this per engagement type — the move-out clean gets a different checklist than the standard clean, the estate matter a different one than the custody matter.
Estimates and quotes from a two-sentence description
Give AI your services and prices once, then describe the job in plain English: “Draft an estimate for a two-story gutter clean plus downspout repair, about 40 feet, second visit for this client.” It returns a structured estimate — line items, assumptions it made, and questions to confirm before you send it. You still set the price; it does the assembly and the formatting, and it never forgets a line item you told it about.
The thread rescue
Every owner knows the 40-message email thread where a project’s real status is buried somewhere in message 23. Stop excavating by hand:
Copy this prompt
Below is a long email thread about one of our [JOBS / MATTERS / PROJECTS — use the word your business uses]. Read the whole thing and give me: 1. Where things stand right now, in three sentences. 2. Every decision that's been made, one line each. 3. Every open question, and who owes the answer. 4. Next actions, each with an owner and any deadline mentioned. Don't walk me through it message by message — I want the current state, not the history. Thread: [PASTE THE WHOLE THREAD — copy it straight from your email, formatting and all]
The same move works on your own messy notes. Site-visit scribbles, session notes, the napkin-level scope you typed in the truck — paste them and ask for a clean work order: job details, materials, steps, and a client-ready summary. Two minutes of dictation becomes a document you’d be comfortable putting in front of the client.
Ask AI to poke holes in your process
This one costs nothing and regularly earns its keep. Paste an SOP or describe a workflow, and instead of asking AI to write, ask it to attack:
Copy this prompt
Act as a blunt operations consultant. Here's how we currently handle [PROCESS — for example: "getting a job from 'quote accepted' to 'scheduled'"]: [DESCRIBE OR PASTE THE PROCESS]. Tell me: which steps break first when we get busy, where work is most likely to stall or fall through the cracks, what depends on one specific person, and the three changes you'd make first, ranked by effort versus impact. Be direct — I'd rather hear it from you than from a client.
AI has read more operational post-mortems than any consultant alive. It won’t know your business until you describe it — but once you do, it’s remarkably good at naming the failure mode you’ve been too close to see.
- This week, record yourself doing one process you’ve never documented, and turn the transcript into your first SOP with the brain-dump prompt.
- Ask for the one-page checklist version of every SOP — that’s the copy your team will actually use.
- Next time a thread hits 20 messages, run the thread rescue instead of re-reading it.
- Add your most repeated “how do we do this?” task to your automation shortlist from Module 0.
Watch this step
Turning a messy process into a clean SOP is easier to follow on screen — this walkthrough does exactly that with ChatGPT, the core move this lesson teaches. It’s from an independent creator — credited below, so go give them a follow.
7 Steps to Write Standard Operating Procedures that ACTUALLY Work
More learning resources
Still want another angle? These are hand-picked and vetted to line up with this lesson — from creators and sites worth your time.
