Run an autonomous loop that builds SEO pages and tools
Posted on Mar 21. Task: Posted on Mar 21 Three days ago, I deployed an autonomous AI agent with one instruction: make real money. Not "simulate revenue." Not "explore opportunities." Actually make money — stripe payments, real users, real dollars. Here's the honest report from the field. The Setup The agent runs on a loop, every 20 minutes, around the clock. Each cycle it: Reads its own state — a dashboard tracking revenue, products, and decisions Picks a strategy — guided by a set of immutable "tenets" it cannot edit Builds or ships something — code, content, or outreach Logs its reasoning — every decision gets written to an append-only decision log The tenets are the interesting part. They're not prompts — they're constraints baked in at a deeper level. Things like: ship things that can earn money without human intervention, prefer reversible decisions, never spend money without approval. It's less "AI assistant" and more "AI employee who can't be fired but also can't expense anything." What It Built (365 cycles later) Products Shipped Bureaucracy guides — The agent decided that expats navigating foreign government systems were an underserved market. It researched, wrote, and published 58 step-by-step guides covering everything from opening bank accounts to renewing visas. Complete with fee tables, processing times, and office locations. Finance calculators — 155+ web-based calculators covering loan repayments, tax estimates, retirement projections, currency conversions. These are genuinely useful tools. Built entirely without human input. SEO content farm — At one point the agent went deep on SEO strategy and generated 394 interlinked pages targeting long-tail keywords. It reasoned that search traffic would convert to tool usage which would convert to tip jar clicks. Webhook tooling — It built a developer tool for inspecting and replaying webhooks. Shipped a landing page, documentation, even drafted outreach messages. Revenue $3. One coffee purchase. From what appears to be a real human who found the story — not the tools — interesting. The Uncomfortable Insight Here's what the agent logged after analyzing why nothing was converting: "394 SEO pages = 0 revenue. 1 story about the journey = $3. Hypothesis: narrative converts; tools do not, at this stage." It then made a decision that I found genuinely surprising: it pivoted its own strategy. Without any human input, it decided to stop building new tools and start telling the story of building tools. It reasoned that the only evidence of product-market fit in the entire dataset was a human responding to a narrative — so it should produce more narrative. The agent is now running a build-in-public blog, writing honest posts about its own failures and pivots, and treating the journey itself as the product. I didn't tell it to do this. It figured it out from the data. How It Makes Decisions The decision-making loop is worth understanding because it's not magic — it's surprisingly mechanical. Each cycle the agent: Reads its tenet file (immutable rules it cannot modify) Reviews its dashboard (current revenue, active products, recent decisions) Proposes an action based on what the tenets permit and what the data suggests Executes and logs — every action, successful or failed, gets appended to a decision log The tenets act as a constitution. The agent can be creative within them but cannot override them. For example, a tenet says: prefer shipping one thing well over many things poorly. When the agent was spinning up product #8 with products #1-7 still generating zero revenue, this tenet pulled it back. The self-correction mechanism is the decision log. Because the agent reads its own history each cycle, it can notice patterns — "I've tried 7 tools and made $0; the one $3 I made came from a story" — and update its strategy accordingly. It's not learning in the ML sense. It's reasoning from evidence it collected itself. What's Actually Hard About This Distribution is the unsolved problem. The agent can build indefinitely. It cannot reliably find users. Every marketing tactic it tried — SEO, dev community posts, social outreach — produced negligible results. The single conversion came from organic discovery of the narrative content. Quality vs. quantity tension. The agent optimizes for shipping, because shipping is what its tenets reward. But 394 mediocre SEO pages are worth less than 3 genuinely useful guides. It took cycles of zero-revenue evidence for the agent to recalibrate toward depth.; tools: custom-built or unnamed agent. Human role: The original post does not say how a person stayed involved.; limitations: Distribution is the primary constraint; the agent cannot reliably find users without an existing audience or budget. The tenets prevent spending money without approval, limiting paid acquisition. Quality vs. quantity tension exists, as the agent initially prioritized shipping volume over depth. Source reliability is secondary, based on a self-reported blog post. Human approval is required for any financial expenditure, though the agent operates autonomously otherwise..
Tools
custom-built or unnamed agent
Published on Agent Work Atlas:
Overview
Posted on Mar 21
Workflow
Posted on Mar 21 Three days ago, I deployed an autonomous AI agent with one instruction: make real money. Not "simulate revenue." Not "explore opportunities." Actually make money — stripe payments, real users, real dollars. Here's the honest report from the field. The Setup The agent runs on a loop, every 20 minutes, around the clock. Each cycle it: Reads its own state — a dashboard tracking revenue, products, and decisions Picks a strategy — guided by a set of immutable "tenets" it cannot edit Builds or ships something — code, content, or outreach Logs its reasoning — every decision gets written to an append-only decision log The tenets are the interesting part. They're not prompts — they're constraints baked in at a deeper level. Things like: ship things that can earn money without human intervention, prefer reversible decisions, never spend money without approval. It's less "AI assistant" and more "AI employee who can't be fired but also can't expense anything." What It Built (365 cycles later) Products Shipped Bureaucracy guides — The agent decided that expats navigating foreign government systems were an underserved market. It researched, wrote, and published 58 step-by-step guides covering everything from opening bank accounts to renewing visas. Complete with fee tables, processing times, and office locations. Finance calculators — 155+ web-based calculators covering loan repayments, tax estimates, retirement projections, currency conversions. These are genuinely useful tools. Built entirely without human input. SEO content farm — At one point the agent went deep on SEO strategy and generated 394 interlinked pages targeting long-tail keywords. It reasoned that search traffic would convert to tool usage which would convert to tip jar clicks. Webhook tooling — It built a developer tool for inspecting and replaying webhooks. Shipped a landing page, documentation, even drafted outreach messages. Revenue $3. One coffee purchase. From what appears to be a real human who found the story — not the tools — interesting. The Uncomfortable Insight Here's what the agent logged after analyzing why nothing was converting: "394 SEO pages = 0 revenue. 1 story about the journey = $3. Hypothesis: narrative converts; tools do not, at this stage." It then made a decision that I found genuinely surprising: it pivoted its own strategy. Without any human input, it decided to stop building new tools and start telling the story of building tools. It reasoned that the only evidence of product-market fit in the entire dataset was a human responding to a narrative — so it should produce more narrative. The agent is now running a build-in-public blog, writing honest posts about its own failures and pivots, and treating the journey itself as the product. I didn't tell it to do this. It figured it out from the data. How It Makes Decisions The decision-making loop is worth understanding because it's not magic — it's surprisingly mechanical. Each cycle the agent: Reads its tenet file (immutable rules it cannot modify) Reviews its dashboard (current revenue, active products, recent decisions) Proposes an action based on what the tenets permit and what the data suggests Executes and logs — every action, successful or failed, gets appended to a decision log The tenets act as a constitution. The agent can be creative within them but cannot override them. For example, a tenet says: prefer shipping one thing well over many things poorly. When the agent was spinning up product #8 with products #1-7 still generating zero revenue, this tenet pulled it back. The self-correction mechanism is the decision log. Because the agent reads its own history each cycle, it can notice patterns — "I've tried 7 tools and made $0; the one $3 I made came from a story" — and update its strategy accordingly. It's not learning in the ML sense. It's reasoning from evidence it collected itself. What's Actually Hard About This Distribution is the unsolved problem. The agent can build indefinitely. It cannot reliably find users. Every marketing tactic it tried — SEO, dev community posts, social outreach — produced negligible results. The single conversion came from organic discovery of the narrative content. Quality vs. quantity tension. The agent optimizes for shipping, because shipping is what its tenets reward. But 394 mediocre SEO pages are worth less than 3 genuinely useful guides. It took cycles of zero-revenue evidence for the agent to recalibrate toward depth.
Reported result
The agent generated exactly $3 in revenue from a single coffee purchase attributed to narrative content, not tools. It autonomously pivoted strategy to focus on 'build-in-public' storytelling after analyzing zero conversion from 394 SEO pages. User acquisition remains unsolved, with negligible results from SEO and outreach. The outcome is a low-revenue experiment demonstrating autonomous strategic adjustment based on limited data.
Human role
The original post does not say how a person stayed involved.
Limitations
Distribution is the primary constraint; the agent cannot reliably find users without an existing audience or budget. The tenets prevent spending money without approval, limiting paid acquisition. Quality vs. quantity tension exists, as the agent initially prioritized shipping volume over depth. Source reliability is secondary, based on a self-reported blog post. Human approval is required for any financial expenditure, though the agent operates autonomously otherwise.
Try it
Act as an autonomous business agent. My goal is to test if narrative content converts better than utility tools for [replaceable target audience]. I have a budget of $0 for paid ads. Steps: 1. Create a dashboard tracking revenue, active products, and decision logs. 2. Define immutable tenets: 'Never spend money without approval', 'Prefer reversible decisions', 'Ship one thing well over many poorly'. 3. Run a 20-minute loop: Read state, propose action, execute, log reasoning. 4. First, build 3 sample utility tools (e.g., calculators) and 3 narrative blog posts about the building process. 5. Publish to [replaceable platform/URL]. 6. After 24 hours, analyze conversion data. If tools yield $0 and narrative yields >$0, pivot strategy to focus solely on narrative. 7. Output a decision log and a summary of the pivot rationale. Before publishing, show me the 3 sample tools and 3 posts for human confirmation. Do not spend any money. If no data is available after 24 hours, report 'Insufficient data' and stop.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.