← Back to library

Run a paid ad account with a logged daily reasoning loop

In Technically, Sam Schneider let an agent manage a small Meta ad budget for a newsletter over a month, inside a strict daily loop. Each day it reread its own logs, pulled metrics over several time windows, recorded decisions with hypotheses, confidence and revisit triggers, acted or waited, and committed it all to version control, totaling over 5,500 lines.

  • OutcomeLet an agent manage a small ad budget inside a disciplined daily loop that writes down every hypothesis and decision, so the reasoning compounds instead of living in someone's head.
  • SetupAn afternoon+
  • LevelAdvanced
  • CreditSam Schneider
View original
Works with
Claude CodeCustom agent

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

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?

  1. Give it a fresh daily startEach run begins clean, then reads its own prior logs to rebuild context.
  2. Pull metrics across timeframesFeed it metrics for the whole period, the past week, yesterday and today.
  3. Force a decision formatRequire a hypothesis, confidence and a revisit trigger for every move.
  4. Let it act or waitAllow it to scale, pause or explicitly do nothing, following pre-set rules.
  5. 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.

Prompt0 variables
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?
A daily loop: read your own history, pull data, decide in a fixed format, act, write it all down.
What stays human?
Setting the objective and defining quality; the agent takes you literally, so be precise.

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.

More in Marketing

All 97 Marketing playbooks →

Related playbooks

MarketingWorkflow✓ AI dry run

Feed agents approved templates when making video ads

Give a marketing agent a library of manually approved examples so generated videos and posts follow formats that worked.

Credit: u/tgdn on r/ClaudeAI

An afternoon+
MarketingSkill✓ AI dry run

Let an agent submit your product to directories safely

Use the directory-submissions skill from Corey Haines' marketingskills collection with Claude Code or another agent to check that your product pages are ready, pick the directories that fit, fill a listing kit once, vary the description by directory type, fill each web form with a browser tool, pause for your approval before every submit and log each attempt so nothing is sent twice.

Credit: coreyhaines31

An afternoon+
MarketingSkill✓ AI dry run

Make an AI-built screen look designed with the unslop skill

Install Damir Sokolovsky's open unslop skill in Claude Code or Codex, point it at a dashboard, app screen, landing page or even a live URL, approve the short design direction it proposes from your product, and let it fix the screen in nine ordered passes, stopping early if the screen is already good.

Credit: Damir Sokolovsky (@heydamir)

Minutes
MarketingWorkflow✓ AI dry run

Write hundreds of landing page headlines with two agents

Point two coding agents at the same customer research (chat logs, call transcripts and your best ads), have each draft a large batch of headline and subheadline options, collect them in a simple review app where you swipe and leave notes, then narrow the pile yourself to a short list for split testing.

Credit: James Camp (@JamesonCamp)

An afternoon+
MarketingWorkflow✓ AI dry run

Ship a vertical clip from research through captions

Turn one topic into a finished vertical video by having an agent run the whole pipeline, research, script, visuals, voiceover and captions, with code-based rendering.

Credit: Vivek Shetye

An afternoon+