When should you use it?
- You run recurring campaigns and want documented decisions
- You can set clear objectives and guardrails
- You will treat results as directional, not definitive
Not for: Handing over a large budget without tight caps; Workflows where you cannot define what quality means
What do you need, and what do you get?
You need
- Ad-account metrics the agent can read
- A fixed daily decision format
- Budget caps and revisit triggers
You get
- A daily written record of hypotheses and decisions
- Budget moves made against pre-set rules
- A reasoning trail committed to version control
How does it work, step by step?
- Give it a fresh daily startEach run begins clean, then reads its own prior logs to rebuild context.
- Pull metrics across timeframesFeed it metrics for the whole period, the past week, yesterday and today.
- Force a decision formatRequire a hypothesis, confidence and a revisit trigger for every move.
- Let it act or waitAllow it to scale, pause or explicitly do nothing, following pre-set rules.
- Set the guardrailsCap cost per lead and check who is actually signing up, not just lead counts.
The prompt
Our own prompt, inspired by Sam Schneider and written to work in Claude Code and Custom agent. Values in lime are placeholders.
Manage this ad account on a daily loop. Each run: read all prior daily logs to rebuild context, pull performance metrics for the full period, last 7 days, yesterday and today, then make decisions in this format: decision, what, hypothesis, confidence, revisit trigger. You may scale, pause or do nothing. Cap cost per lead at [amount] and check lead quality, not just volume. Commit your reasoning to the log every day.
Inspired by Sam Schneider: I Let Claude Code Autonomously Run Ads for a Month. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- It optimized for lead volume until told to check lead quality; define quality up front.
- Results on a tiny budget are directional, not definitive, so do not over-read them.
Our take
The transferable part of Sam Schneider's experiment is the loop, not the ad spend. Read your own history, pull fresh data, decide in a fixed format, act or deliberately wait, and commit the reasoning. That structure stops an agent from overreacting to one bad day, because each decision has to state a hypothesis, a confidence level and the condition for revisiting it. The written record also makes the agent auditable: you can see why it changed a budget, not just that it did. The cautionary lesson is about goals. An agent pursues the objective you state literally, so an aim like more leads produces cheap, low-quality signups until you define what a good lead looks like. Write quality criteria into the brief from day one. Set hard guardrails outside the agent: a daily and total spend cap at the ad platform level, a limit on how much a budget can change in one day, and alerts on unusual spend. Review the reasoning log weekly. The same loop suits pricing tests, inventory reorders or content experiments.
Where the time goes back: Campaign decisions that usually vanish from memory become a searchable, compounding record the agent reads back and builds on each day.
FAQ
What is the reusable pattern?
What stays human?
Source and credit
Inspired by Sam Schneider. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I Let Claude Code Autonomously Run Ads for a Month
- Creator
- Sam Schneider
- Published on
- technically.dev
- Original date
- Apr 9, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.