Ask ChatGPT for "a marketing plan" and you get 12 bullet points about authenticity. Give it a job, with evidence and a boundary, and you get work you can ship. Four moves, then repeat:
1Brief it. Outcome, evidence, boundary, deliverable. Write the job so another person could tell whether the result is right, so ChatGPT can too.
2Ground it. Put your real customer messages and your offer page in a Project, which means it answers what people actually asked, not what it imagines.
3Run it. Turn the insight into finished pieces: an FAQ answer, a reply to a lead, a 3-step process graphic, so you're not left holding homework.
4Check it. Make ChatGPT list the source of every claim and promise, then verify the important ones yourself, so no invented "7 days" ever reaches a customer.
↻Repeat weekly. Add new messages to the same Project and ask whether the concern is still showing up. That's why it's a loop, not a prompt.
Free: The Operator Loop prompt packEvery prompt from this video, ready to copy. One email unlocks it, plus the kits from every other video.
The four moves look simple. These are the details that decide whether they work in your business, so you get the fix and not just a nicer-sounding chat.
1 A brief has four parts, not one
Most prompts only state a topic. A brief that works names four things:
Outcome: the one thing you need found or made. "Find the friction", not "marketing ideas".
Evidence: the real material it must use, attached, not described from memory.
Boundary: what it must never do. "Do not invent delivery times or customer quotes."
Deliverable: what comes back, in a form you can review in five minutes.
Skip the "act as a genius consultant with 30 years of experience". You don't need a character. You need a job.
2 A Project is a filing cabinet, not a crystal ball
Projects keep related chats, files and instructions together. They are not unlimited memory, and they don't replace checking the files. Strip names and contact details from customer messages before you upload them, then add one instruction:
Project instruction
Treat these files as the primary source. Separate customer statements from your interpretation. If a claim is not supported, say what is missing.
Three messages can suggest a fix. They can't prove it. If your files don't show a pattern, don't force one.
3 Finished work, not another task
The sample web studio didn't need 30 ideas. It needed to answer the question three people were already asking: when will my site be live? So the run produces three things you can review today: an FAQ answer that explains how timing gets set, a short reply to the lead, and a three-step graphic of what happens after the form.
Then give it a success measure, like fewer inquiries asking about timing next month. That's a test, not a claim that it already worked.
4 Confidence is not evidence
"Your website will be live in seven days" sounds decisive. It's also invented: it's not in the offer and nobody scoped the project. Run a claim check, then open the source and verify dates, prices, quotes and turnaround times yourself.
Claim check
For every factual statement and promise in these drafts, identify its source. Put unsupported statements in a separate list. Rewrite those statements without guessing.
Paste this boundary into every customer-facing task: "Draft it. Do not send or publish it without my approval." The owner still owns the promise.
Prove it
Could you run the loop tomorrow?
Five quick ones. Nobody's grading you. It's a dry run, so the first real loop goes smoothly.
Free resource
The Operator Loop prompt pack
4 moves, 12 copy-ready prompts, worked examples for a coach, a shop and a consultant, and a 20-minute plan for tonight. Grab the page or the PDF, so you can run your first loop before bed.
