Solo Guide No. 004 · Operations · October 2026
Where does a person need to approve my AI workflows? Anywhere a customer sees the result.
Keep a person approving anything a customer will see, and anything you could not undo. Let the rest run on its own, with a log and an off switch.
Why approval is where your judgment goes. It is not a sign you distrust the AI.
AI made drafting, sorting and sending cheap. Deciding what is good enough to go out under your name did not get cheaper. That decision still belongs to a person, and the approval step is how it stays there.
There are two ways to get this wrong. If nothing is approved, one bad message or payment carries your name before anyone notices. If everything is approved, the approver starts clicking Approve without reading, and you have the delay without the safety. The fix is to put the person where a mistake would cost you, and nowhere else.
Three levels. Pick one for every task.
- Run automatically.The AI does the task and logs it. Nobody checks each item. This fits internal work that is easy to undo and cheap to get wrong, like filing and labeling. It still needs a log you can read, an alert when something fails, and an off switch.
- Spot-check.The AI does the task and a person reviews a sample: every item for the first couple of weeks, then a handful each week. This fits internal work where a mistake would cost something or take effort to reverse, like ordering materials.
- Approve every time.The AI prepares the work and stops. A person approves each item before it goes out or happens. This covers anything a customer sees, and anything costly or hard to undo.
Five steps. Most of the work is the list.
- 1
List what the AI touches
Write down every task you want AI to do, or already use it for: replies, quotes, scheduling, invoices, reminders, reports. One line each, with who or what receives the result.
- 2
Ask the three questions
- Does a customer see it? A reply, quote, review request or reminder is customer-facing, even when it goes out from a template.
- Can you undo it? A label can be changed. A sent email, a payment or a deleted record cannot.
- What does a mistake cost? Think refund, lost job, an awkward call, or nothing at all.
- 3
Pick the level
If a customer sees it, a person approves it every time. If not, weigh how hard it is to undo and what a mistake costs. Low on both runs automatically, a middle score gets a spot-check, and high on both gets approved every time. The sorter below does this for you.
- 4
Make approving take seconds
Put drafts where the approver already works: the inbox, the CRM or a chat message. Show the draft, the facts it used, and three buttons: approve, edit, reject. Name one approver and one backup. If nobody answers, the item waits. It never sends itself.
- 5
Review it every month
Read the log. If a spot-checked task has needed no changes for a month, consider letting it run. If any mistake reached a customer, move that task up a level. Tasks a customer sees do not move down. They stay with a person.
The approve-or-automate sorter. List your tasks and rate them.
Type your own tasks over the examples and tap an answer for each of the three questions. Every task gets one level. The examples are sample tasks. Your entries stay in this browser only.
| Task | Customer sees it | Can you undo it | Cost of a mistake | Level | Remove |
|---|
Logged, with an alert on failure and an off switch.
A person reviews every item at first, then a sample each week.
A person approves each one. Anything a customer sees is always here.
Reading the example: replying to a new web lead is customer-facing, so a person approves it every time, however safe it looks. Sorting incoming email into folders is internal, easy to undo and cheap to get wrong, so it can run on its own.
Next guide
Get the next guide. One email when it is out.
Plain-English guides for owners, free to read. We'll email you when the next one is published. No tracking scripts on this form.
03A worked example · Operations
Six approvals a day become three.
A home-services company starts by approving everything the AI does. Sorted with the three questions, two tasks run on their own, one gets a weekly spot-check, and three keep a person approving every time. The approver's queue is half as long, and everything a customer sees is still checked.
Measured against: mistakes that reached a customer, and minutes spent approving. Sample tasks and counts for illustration, not results.
| Task | Before | After |
|---|---|---|
| Sort incoming email | Waits for a person | Runs on its own |
| Update job status | Waits for a person | Runs on its own |
| Order materials | Waits for a person | Spot-check |
| Reply to a new lead | Waits for a person | Approve every time |
| Send the quote | Waits for a person | Approve every time |
| Pay a supplier | Waits for a person | Approve every time |
What to avoid
- Approving everything, forever.If the approver clicks through without reading, shorten the list so each approval matters.
- An approval with no owner.Name a person and a backup. A queue nobody opens is a stalled business.
- Calling it automatic when it is unwatched.Automatic still means a log, an alert when something fails, and an off switch.
- Loosening a customer-facing task because the last ten looked fine.Looking fine is not the same as being safe. Anything a customer sees stays with a person.
- Putting the approval where nobody looks.Use the inbox or chat they already check, not a separate dashboard.
Do it yourself, or get help?
Do it yourself when
- The workflows live in one or two tools.
- One person has a few minutes a day to approve.
- You can read the log yourself.
Bring in help when
- Approvals have to work across email, a CRM and a calendar.
- Nobody has time to own the queue.
- You want the log, the off switch and the monthly review set up properly.
That is the work Solo Studios does. A senior strategist decides where AI pays, we build it in the tools you already use, and a person approves anything a customer sees. Every action leaves a record, and you own what we build.
Questions
Won't approvals slow everything down?
Not much, if the draft is waiting where the approver already looks and takes one click. Set a daily window for routine items and send a notification for urgent ones. If approvals pile up, too many tasks are probably at the top level, so revisit the sorter.
Who should approve?
Someone who knows the customer and can speak for the business, usually the owner or a manager at first. Name a backup so nothing stalls when one person is out.
Can anything a customer sees run without a person?
At Solo Studios the rule is that a person approves anything a customer sees. The one nuance is a fixed message you wrote and approved once, such as an appointment confirmation with the date filled in. There the person approves the template, and any change to the template goes back to a person.
What should the approver see?
The draft, the facts it was built from, and why it was flagged. Then three actions: approve, edit, reject. Keep a record of who approved what and when.
How do I know a task can move down a level?
When the task is internal, cheap to get wrong and easy to undo, and the log shows a month without changes. Move one step at a time and keep reading the log.
Next step
Bring your list. We'll sort it with you.
Book a discovery call with your sorted tasks. We'll check which workflows are worth building first and where a person stays in the loop.