I run small media businesses where AI agents do most of the daily work.
Every publishing and ad workflow ends with my approval.
Agents draft every newsletter and send none of them. The deal engine checks flight fares every day and files a report instead of posting. My ad pipeline built the creative, wrote the copy, verified the fare, and uploaded the ads to Meta as paused drafts for me to activate.
October 4, 2026 update: The current ad pipeline prepares the creative and copy and verifies the fare. Its Meta connection is read-only. I enter and launch the ads myself.
I call this the approval queue pattern, and it is the single most important design decision in everything I’ve built.
Labor and judgment are different jobs
Here’s what 20+ years of sales taught me before I ever touched an agent: every serious deal has an approval chain, and nobody thinks that’s weird.
The rep does the work. Someone with skin in the game signs. We invented this pattern long before AI because humans are also fast, tireless, occasionally confident, and occasionally wrong.
Agents are all of those things turned up to eleven. They will happily do six hours of work in four minutes, and about once a week they will do it confidently in the wrong direction.
A wrong draft can be rejected before it becomes a live ad spending money.
So I split every workflow into two piles.
Labor: researching, drafting, rendering, scheduling, monitoring, reconciling. Agents get this pile without restriction.
Judgment: is this true, is this on-brand, is this worth money, could this embarrass me. This pile is mine, and it’s protected by a queue.
The four rules
After running agents across three businesses, the pattern has settled into four rules.
The gate sits at the last irreversible moment. Not earlier. If you review work at the halfway point, you’re a manager doing check-ins, and you’ve reinvented meetings. Let the agent finish. Review the finished work while rejecting it still prevents a publish or spend.
Approving has to be nearly free. My approvals happen from my phone. A finished newsletter shows up, I read it over coffee, I tap yes. If approving takes real effort, one of two things happens: you become the bottleneck, or worse, you start rubber-stamping. A gate you rubber-stamp is set dressing.
Everything before the gate is fair game. This is the part people get backwards. The queue isn’t there to slow the agents down. It’s there so I can speed them up with a clear conscience. Because publishing, list sends, and ad spending need my approval, I can let agents run overnight, unsupervised, aggressively. That gate lets me automate the work before it.
Log everything. Every run, every draft, every rejection. When something gets weird, and something always eventually gets weird, the log tells you whether it was a bad day or a bad pattern.
The failure modes
You can get this wrong in three directions.
Gate too early, and you’re doing the agent’s job with extra steps.
Too many gates, and approval fatigue turns you into a rubber stamp. That’s worse than no gate, because you still feel safe.
And no gate at all is how you end up as one of those screenshots where a company’s chatbot is selling trucks for a dollar.
The dollar-truck stories get the headlines. But rubber-stamping is the failure mode that actually gets operators, because it fails silently while your name is still on everything.
The score so far
Two live media businesses, with agents doing the daily work in both.
Number of unapproved publishes, list sends, or ad spends: zero.
The publishing and ad-spend permissions stay with me.