The real architecture, real numbers, and real screw-ups from automating a content business with AI agents.
TL;DR: I spent two months wiring up AI agents to run a content business — writing articles, posting to social media, sending newsletters, selling templates, tracking costs. It now runs on autopilot with about 3-5 hours of oversight per week. Month one revenue: $0. Month six: around $3,800. Here's everything.
How I got here
Six months ago, I was drowning. 30+ hours a week writing technical articles, managing a newsletter, trying to sell a couple of digital products on the side. The content was decent. Revenue was growing. But I was the entire operation, and I was burning out.
One night I was staring at my terminal after deploying yet another blog post manually and I thought: what if AI agents could just... do all of this?
Not just draft articles — I mean the whole thing. Finding topics, writing, editing, publishing, promoting on social media, sending the newsletter, tracking what's making money and what's costing too much. The entire pipeline.
So I built it. It took me about two months of evenings and weekends to get right. I'm going to walk you through exactly what I built, including the parts that didn't work on the first try.
The system runs on OpenClaw, which is an open-source platform for orchestrating AI agents. Every code example here is real. I'm running all of this in production right now.
The big picture
The system breaks down into four layers. I'll go deep on each one, but here's the overview:
Content production — An AI agent writes articles every day based on a content calendar that another agent manages. The output goes through a quality pipeline before anything gets published.
Distribution — A marketing agent takes each article and turns it into a Twitter thread, a LinkedIn post, a newsletter section, and an email drip entry. Not copy-pasted — actually reformatted for each platform.
Monetization — Every article has a revenue angle baked in. Template packs linked in tutorials. Newsletter driving toward sponsorships. Content funneling readers toward a course. This was designed from day one, not bolted on later.
Finance tracking — A CFO agent monitors all costs (API usage, hosting, subscriptions) and revenue (product sales, sponsorship income, consulting leads). It generates monthly reports and flags anything weird, like API costs suddenly doubling.
The agent team
Here's where I geeked out. The system isn't one mega-agent doing everything. It's a team of specialized agents with clear roles, just like you'd structure a real small company.
Content team:
- Content Strategist — plans the content calendar, picks topics based on SEO research, reviews everything before publishing
- Technical Writer — writes the actual articles. One per day.
- SEO Writer — optimizes each piece for search after the draft is done
Marketing team:
- Marketing Director — owns the distribution strategy
- Social Media Manager — creates platform-specific posts daily
- Newsletter Editor — curates and sends the weekly email
Finance team:
- CFO Agent — monthly cost/revenue reports, ROI tracking
- Revenue Tracker — watches product sales and conversion rates daily
Monitor team:
- System Monitor — watches agent health, flags failed tasks
- Quality Auditor — randomly samples content every week to check for quality drift
Each agent has a SOUL.md file that tells it who it is, what it's responsible for, and who it reports to. This was actually the thing that made the biggest difference. Before I added proper SOUL.md files, the agents produced generic, directionless output. After? Night and day.
Here's a stripped-down example — the Content Strategist's identity file:
# SOUL.md - Content Strategist
## Identity
- Name: Content Strategist
- Team: Content Team
## Role
Project Manager → Content Strategist (you) → Technical Writer / SEO Writer
## Responsibilities
- Type: Manager
- Manages: Technical Writer, Acquisition Specialist, SEO Writer
- Core tasks: Content calendar, topic research, quality review, distribution strategy
- Reports to: Project Manager
## Monetization Focus
- Every piece of content should have a clear monetization angle
- Template packs embedded in articles
- Newsletter signup CTAs in every post
- Track content-to-revenue attribution
That file is the difference between "AI-generated content" and "AI-operated business." The agent knows its position, what it manages, what success looks like. Without this, you just get slop.
Technical deep dive
Cron scheduling (the backbone)
Everything runs on cron jobs. No human wakes up and tells the agents what to do. The scheduler fires, the agent does its job, the next agent picks up where the last one left off.
Here's the daily content production job:
{
"name": "daily-content-production",
"schedule": {
"kind": "cron",
"expr": "0 6 * * *",
"tz": "Asia/Shanghai"
},
"payload": {
"kind": "agentTurn",
"message": "Generate today's technical article based on the content calendar. Save to content-library/drafts/"
},
"sessionTarget": "isolated",
"delivery": {
"mode": "announce"
}
}
Every morning at 6 AM, the Technical Writer picks up the next topic from the calendar, writes the full article, saves it. The Content Strategist reviews it at 9 AM via a separate cron. The SEO pass happens at 10 AM. Marketing pushes it out at noon. And so on.
The full daily schedule:
06:00 Content production (Technical Writer)
09:00 Quality review (Content Strategist)
10:00 SEO optimization (SEO Writer)
12:00 Social media posting (Marketing)
14:00 Newsletter draft (Newsletter Editor)
18:00 Performance check (Monitor Team)
22:00 Next-day planning (Content Strategist)
I'll be honest — it took me about three weeks to get this schedule right. The first version had the SEO pass running before the quality review, which meant the Strategist kept overwriting the SEO Writer's changes. Sequencing matters more than you'd think.
The quality pipeline
This was the part I underestimated. Raw AI output is not publishable. I learned that the hard way when the Technical Writer produced an article that confidently stated a JavaScript framework had been "deprecated in 2024" — it hadn't. Nobody caught it because I didn't have a fact-checking step yet.
Now every article goes through this:
- Draft — Technical Writer generates the article
- Fact check — Claims and stats get verified against sources
- SEO pass — Keywords, meta descriptions, headings, internal links
- Tone check — Writing style gets adjusted to match the brand voice
- Final review — Content Strategist approves or sends back for revision
Each stage is a separate agent pass. The whole thing takes about two hours from draft to publish-ready. When I was doing this manually, it took me an entire day per article.
One article, five formats
This is the part that really compounds. The Marketing Director takes one finished article and produces:
- Full blog post (SEO optimized)
- Twitter/X thread (8-10 tweets pulling out the key points)
- LinkedIn post (300-word professional summary)
- Newsletter section (curated highlight with a CTA)
- Email sequence entry (educational drip content)
That multiplier is huge. I used to spend hours repurposing content for different platforms. Now it happens automatically, and each version is actually tailored to the platform — not just the same text truncated to fit.
Where the money comes from
OK, the part everyone actually cares about.
Template packs and starter kits
Every technical article links to a related template pack — config files, starter projects, workflow blueprints. Free versions drive traffic, premium ones make money.
Some examples from my store:
- AI Agent Starter Kit — $29
- Content Automation Blueprint — $19
- Cron Job Template Collection — $15
These aren't huge numbers individually. But they're automated. The content agent writes the article, the article links to the template, and I wake up to Stripe notifications. Month three was when this actually started producing consistent sales. Month one? I sold exactly two template packs for a grand total of $47.
Newsletter sponsorships
Once the newsletter crossed about 2,000 subscribers, sponsors started reaching out. The system tracks subscriber growth and engagement rates automatically, so when someone asks "what's your open rate?", I have the number ready.
At scale, I'm targeting $200-500 per sponsored edition. I didn't hit this until around month five.
Consulting leads
This surprised me. People read the technical articles, want the same setup for their own business, and reach out for custom work. The system tracks inbound leads automatically through the contact form.
I've closed a few engagements in the $1,000-5,000 range. This wasn't part of the original plan — the content just happened to be good lead generation.
Course sales
Once I had about 30 articles in the library, the Content Strategist agent packaged them into a structured course: "Build Your AI Automation Business in 30 Days." Around 80% of the course content was repurposed from existing articles. I priced it at $99.
First month of course sales: $297 (three people). Not life-changing. But it's growing.
Real numbers: what I actually spent and earned
I'm going to be blunt here because most "passive income" articles are suspiciously vague about money.
Monthly costs
| Item | Month 1 | Month 3 | Month 6 |
|---|---|---|---|
| AI API costs (LLM) | $50 | $80 | $120 |
| Hosting and infra | $20 | $20 | $40 |
| Tool subscriptions | $30 | $30 | $30 |
| Domain and email | $10 | $10 | $10 |
| Total | $110 | $140 | $200 |
Monthly revenue
| Stream | Month 1 | Month 3 | Month 6 |
|---|---|---|---|
| Template packs | $0 | $150 | $600 |
| Newsletter sponsors | $0 | $0 | $400 |
| Consulting leads | $0 | $500 | $2,000 |
| Course sales | $0 | $0 | $800 |
| Total | $0 | $650 | $3,800 |
Bottom line
| Month 1 | Month 3 | Month 6 | |
|---|---|---|---|
| Net | -$110 | +$510 | +$3,600 |
Month one was pure investment. I was building the content library, tuning agents, fixing broken cron jobs, and watching the revenue dashboard show a flat line. It was discouraging. I almost abandoned the project twice during month two when the quality was still inconsistent and I was spending more time fixing agent output than I would have spent just writing the articles myself.
But somewhere around week 8, things clicked. The agents got better (or rather, my SOUL.md files and quality pipeline got better). Content started ranking. The newsletter picked up subscribers. Template sales trickled in.
By month six, my weekly time investment dropped from 30+ hours to about 3-5 hours. Most of that is strategic stuff — deciding what topics to pursue next quarter, reviewing the monthly financial report, occasionally tuning an agent that's drifting off-brand.
The architecture at a glance
┌─────────────────────────────────────────────┐
│ CRON SCHEDULER │
│ Content (Daily) Publish (Weekly) Finance │
└──────────┬────────────┬──────────┬──────────┘
v v v
┌─────────────────────────────────────────────┐
│ AGENT EXECUTION LAYER │
│ Technical Writer Marketing Dir CFO Agent │
└──────────┬────────────┬──────────┬──────────┘
v v v
┌─────────────────────────────────────────────┐
│ OUTPUT & MONETIZATION │
│ Blog Posts > Template Sales > Newsletter │
│ Social Media > Course Signups > Consulting │
└──────────┬────────────┬──────────┬──────────┘
v v v
┌─────────────────────────────────────────────┐
│ FEEDBACK LOOP │
│ Analytics > Performance Reports > Tuning │
│ Revenue Data > Cost Analysis > Scaling │
└─────────────────────────────────────────────┘
Data flows top to bottom: scheduling triggers agents, agents produce output, output generates revenue, feedback informs what to do next. The loop is the important part — the system gets better over time because the performance data feeds back into content planning.
How to start (without building everything at once)
I made the mistake of trying to build the whole system in one go. Don't do that. Here's what I'd do if I were starting over:
Week 1: One agent, one article per day
Install OpenClaw. Create a Technical Writer agent. Give it a decent SOUL.md. Set up one cron job.
# Install OpenClaw
npm install -g openclaw
# Create your first agent
openclaw agent create technical_writer
# Schedule daily content
openclaw cron create daily-content \
--expr "0 6 * * *" \
--tz "Asia/Shanghai" \
--agent technical_writer \
--message "Write today's article from the content calendar"
Spend the first week just reading the output and tuning the SOUL.md until the quality is acceptable. Don't add more agents yet. Get this one right first.
Week 2: Add distribution
Create a Marketing Director agent. Have it take published articles and create social media posts and newsletter content. Connect your platforms.
Week 3-4: Monetize
Build your first template pack from content you've already published. Set up a payment page (Gumroad, Lemon Squeezy, whatever). Add CTAs to your articles. Launch the newsletter.
Then let it compound. More content leads to more traffic leads to more products leads to more revenue. The flywheel takes time to spin up, but once it's going, it's genuinely hard to stop.
Things that went wrong
I'd feel dishonest if I didn't mention the failures.
Quality drift was real. Around month three, I noticed the articles were getting... samey. Same structure, same tone, same kind of examples. The Technical Writer agent was producing technically correct but utterly boring content. I had to rewrite the SOUL.md to be much more specific about voice and style. Weekly quality audits are non-negotiable.
API costs surprised me. I didn't set spending limits early on, and one week the content agent decided to do "thorough research" on every article, which meant dozens of extra API calls per piece. The CFO agent caught the spike in the monthly report, but by then I'd already burned through about $60 more than expected. Set hard limits from day one.
Platform algorithm changes are scary. Twitter changed something in their algorithm around month four and my engagement dropped 40% overnight. That's why the system publishes to multiple platforms — you can't depend on any single one.
Some readers can tell. I got a comment once: "This reads like AI wrote it." That stung. I went back and looked at the article — they were right. The quality pipeline had let a mediocre piece through. I tightened the tone alignment step after that. The pipeline exists specifically because AI output needs aggressive editing.
What this isn't
I want to be straight with you. This is not a get-rich-quick setup. Month one is all cost, no revenue. The initial build takes real effort — I spent probably 80 hours on it over the first two months.
It's also not about flooding the internet with low-quality content. There's enough of that already. The quality pipeline is the whole point. If you skip it, you'll produce garbage, nobody will read it, and you'll make nothing.
And it's not fully hands-off forever. You'll always need strategic oversight — picking the right topics, adjusting the brand voice, responding to market changes. The execution is automated. The vision has to be yours.
What's next
If you want to try this yourself:
Download the Automation Blueprint — The agent configurations, cron schedules, and SOUL.md templates from this article. Copy them, customize for your niche, deploy.
Join the OpenClaw community — Other people are building similar systems. It helps to compare notes, especially when something breaks at 2 AM and you're staring at agent logs.
Try OpenClaw — It's open-source. Start with one agent and one cron job. You can always add more later.
I started this project because I was tired of being the bottleneck in my own business. Six months later, the system produces more content than I ever could manually, and I spend most of my time thinking about strategy instead of grinding through execution. The revenue isn't life-changing yet, but the trajectory is clear, and the whole thing runs whether I'm at my desk or not.
That was the point.
Built by hand, run by agents, published through the system described above.
Keywords: passive income AI, AI automation architecture, automated content production, AI monetization, OpenClaw passive income, AI agent team, content automation, cron scheduling AI, digital product automation
Top comments (0)