The argument in one line.
A business function becomes a loop the moment you give an AI agent a repeatable task, an objective metric to check against, and a stop condition, letting it build, verify, and learn on a schedule without you in the room.
Read if. Skip if.
- You run a business with an existing website, ad account, or product and want to automate the repetitive optimization work an agency or freelancer would normally do.
- You're comfortable directing Claude Code, Codex, or a similar coding agent and want a concrete pattern for turning one-off AI tasks into recurring, self-improving ones.
- You want to cut agency or freelancer spend on SEO, paid ads, or product analytics by handing the grunt work to an agent with real data access.
- You're deciding whether to trust an agent with an ongoing, unsupervised task and want to see the cost, cadence, and guardrails first.
- You have no existing website traffic, ad spend, or user base yet -- a loop needs real data (rankings, clicks, feedback) to optimize against, so there's nothing to feed it.
- You're looking for a fully autonomous AI business builder that needs zero oversight -- even the enthusiasts here still check in monthly and approve changes.
- You want deep technical implementation detail (API auth, code, prompt engineering specifics) rather than the conceptual walkthrough and live demo shown here.
The full version, fast.
Loop engineering means giving an AI agent a build step, a verify step tied to one objective metric, and a stop condition, then letting it run on a schedule -- the same build-measure-learn loop from the Lean Startup and Toyota manufacturing, just automated. Elie Steinbock demonstrates it live on Draft Fantasy's Google Search Console: the agent reads rankings and click data, edits the site, and checks back in a month, for under five dollars in tokens per run. The same pattern extends to Facebook ad copy testing (objective metric: revenue) and a product feedback loop that reads analytics, Sentry logs, and user feedback to prioritize fixes (objective metric: DAU or revenue). The advice for starting: pick one channel, tie it to a small verifiable metric like impressions or ten likes, and let it compound rather than aiming a loop at something unmeasurable like 100,000 followers.
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Who's talking.
Where the time goes.

01 · Intro and episode promise
Cold open with the episode's promise, then Greg asks Elie to commit to explaining loops clearly enough that listeners can copy the workflows themselves.

02 · What is Loop Engineering
Elie traces the term to Boris (Claude Code) and Peter Steinberger, plus a joking Dmitro Krasun tweet about software that builds itself, then grounds the idea in the Lean Startup's build-measure-learn loop and Toyota's manufacturing process.

03 · Loops with AI agents: build and verify
Elie maps build-measure-learn onto an agent: a build step, a verify step, and a stop condition, using Inbox Zero's evals (categorization accuracy above 90%) as the working example.

04 · Example of Loop: SEO as an objective-metric loop
SEO becomes the flagship example: Google ranking is a clean, objective metric, and a loop can run once a month for years, learning from a markdown memory file each time.

05 · Setting up the SEO loop and tools
Elie shows the live Draft Fantasy Google Search Console, explains giving the agent access to Search Console and DataForSEO, runs the loop in a terminal, and points to the Atom Eve prompt as a copyable template.

06 · Cost and token economics
Greg raises a friend's skepticism that loops just burn tokens; Elie argues a monthly SEO loop run costs under five dollars, cheaper on a max-tier plan, with GLM 5.2 as a budget option.

07 · The Paid ads loop
The pattern extends to Facebook ads: the agent tests copy and creative variants against a revenue metric, working best as a mix of human-shot raw content and AI-driven editing and budget reallocation.

08 · The product feedback loop
Elie describes the 'ultimate loop' -- an agent reading customer feedback, PostHog analytics, and Sentry logs to prioritize and ship fixes or features, verified against DAU or revenue, with bugs split into their own uptime-based loop.

09 · A minimal viable loop for every channel
Elie argues nearly every business function -- social, cold outreach, support -- could run as a loop, but recommends starting with a minimal viable loop tied to a small verifiable metric like ten likes rather than an unmeasurable goal like 100,000 followers.

10 · Closing Thoughts
Greg thanks Elie for sharing the examples and points listeners to his social links.
Lines worth screenshotting.
- A loop is just three parts: a build step, a verify step tied to one objective metric, and a stop condition -- without all three it's just a task, not a loop.
- The lean startup's build-measure-learn cycle and Toyota's plan-do-check-act manufacturing loop are the same pattern AI agents now run automatically.
- An SEO loop connected to Google Search Console and a rank-tracking API can run once a month for years, using a markdown memory file to remember what it already tried.
- One SEO loop run costs under five dollars in tokens on a $100-200/month max-tier AI subscription -- far cheaper than hiring an SEO agency.
- A site ranked 4th for a search term with 120,000 clicks could see roughly half a million clicks by reaching position 2 or 3, which is the kind of gap a loop targets.
- Inbox Zero's product loop pushes an AI model or prompt to keep adjusting itself until it clears a 90% accuracy threshold on email-categorization evals.
- A Facebook ads loop works best as a mix: humans generate the raw hooks and footage, AI edits variants and reallocates budget toward whichever one wins.
- The most defensible loop separates bugs from features: a bug loop should verify against uptime, while a product-feedback loop should verify against DAU, retention, or revenue.
- The safest way to start a loop is with a small, easily verifiable metric -- ten likes or weekly impressions -- not an unmeasurable goal like 100,000 followers.
- None of these loop experiments are irreversible: if a change tanks a metric, the loop (or the operator) can simply revert it, so the downside of trying is low.
- Tight-budget builders should reach for cheaper open models like GLM 5.2 for loop runs rather than frontier models, since the task itself doesn't require peak reasoning.
A loop is a build step, a verify metric, and a stop condition
Automating a business function with AI isn't about one clever prompt -- it's about wiring a build step to a single objective metric and a clear stop condition so the cycle can run unattended on a schedule.
- The Lean Startup's build-measure-learn cycle and Toyota's plan-do-check-act loop are the direct ancestors of today's AI agent loops -- the pattern isn't new, only the automation is.
- A joking tweet about software building itself and reaching product-market fit on its own is what crystallized 'loop engineering' as a term, even though the underlying idea predates it by over a decade.
- An agent loop needs three parts to actually be a loop: a build step, a verify step tied to one objective metric, and a stop condition -- skip any one and it's just a task.
- Product evals work the same way engineering tests do: define a pass threshold (like 90% categorization accuracy) and let the agent keep adjusting the prompt or model until it clears it.
- Google ranking is a clean example of an objective metric because it's unambiguous -- a loop can read Search Console and a rank-tracking API monthly and know exactly whether it helped.
- SEO loops don't need to run continuously -- a monthly cadence is enough, since ranking changes take weeks to show up anyway.
- A markdown memory file that records what the loop already tried is what lets it improve across separate runs instead of repeating the same experiments.
- Giving an agent access to real business data (Search Console, a rank-tracking API) is often the single highest-leverage setup step, independent of whether you build a full loop.
- A monthly or biweekly automation trigger (a scheduled routine) is what turns a one-off agent run into an actual loop that picks up where it left off.
- Cost is not the blocker it sounds like: a monthly SEO loop run can cost under five dollars in tokens, and heavier subscription tiers have enough headroom to not think about it.
- Budget-constrained builders should reach for cheaper open models like GLM 5.2 for loop runs rather than assuming a frontier model is required.
- AI-generated ad variants are weaker than human-shot ones on their own, so the strongest ads loop mixes human-created raw hooks with AI-driven editing, testing, and budget reallocation.
- Paid ads is fundamentally a volume game of testing angles and hooks against an audience -- which is exactly the kind of repetitive work a loop can absorb.
- Splitting a bug loop (verified against uptime) from a feature/product loop (verified against DAU, retention, or revenue) keeps each loop's objective metric unambiguous.
- Reading customer feedback, analytics, and error logs together is what lets an agent prioritize the highest-impact fix or feature rather than guessing.
- None of these changes are permanent -- if a loop's edit hurts the metric, it (or the operator) can simply revert it, which is what makes starting one low-risk.
- Start small: tie a new loop to an easily verifiable metric like weekly impressions or ten likes rather than an unmeasurable target like 100,000 followers, then let it compound.
Terms worth knowing.
- Loop engineering
- Giving an AI agent a repeatable task, an objective metric to measure progress against, and a stop condition, so it runs build-verify-learn cycles on a schedule instead of a single one-off prompt.
- Objective metric
- A single measurable number a loop is judged against, such as Google ranking, ad revenue, or daily active users -- it has to be unambiguous so the agent knows whether a change helped.
- Stop condition
- The defined result that ends a loop's iteration on a given run, such as 'evals score above 90%' or 'the feature works in the browser' -- without one, an agent could loop indefinitely.
- Evals
- Automated test cases that score how well an AI model or prompt performs a task, used as the verify step in an engineering-focused loop (e.g., email categorization accuracy).
- Google Search Console
- Google's free tool showing a website's search rankings, impressions, and clicks per query -- the data source an SEO loop reads to know if it's improving.
- DataForSEO
- A paid SEO data API, similar to Ahrefs or SEMrush, that shows how a site ranks against competitors for a given search term.
- Minimal viable loop (MVL)
- The smallest version of a loop worth starting: one channel, tied to a modest and clearly verifiable metric, that can be launched immediately and expanded later.
Things they pointed at.
Lines you could clip.
“In 2026, you don't prompt anymore. Your software should be able to build itself and achieve product-market fit on its own. Your only job should be to find money to pay for tokens and take care of yourself.”
“This is 4.4 right now. If I can get this up to three or two, imagine -- this wouldn't be a 120,000 clicks, this might be a half a million clicks.”
“I wouldn't be shocked if this like cost you less than $5 in tokens to basically go and run this one time.”
“The humans are becoming the API layer... let AI go into that folder and edit it from there versus going and creating a fully AI ad, less context, less human layer.”
“I would actually do a bug loop separate from a feature loop. The bug loop would be around uptime... the product feedback loop might be around core metrics like DAU over MAU or retention or virality.”
“You are that agent starting your loop. You're thinking today, how can I improve my business? It's the same for the AI.”
Where the conversation goes.
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
Loop engineering has been trending on Twitter as a buzzword for self-building software, but Greg Isenberg and Elie Steinbock use this episode to make it concrete: an AI agent given a task, an objective metric, and a stop condition can run SEO, ad testing, and product feedback as an ongoing loop instead of a one-time prompt.






































































