I built an AI agent that works for me 24/7 — researching opportunities, drafting content, finding freelance gigs, and reporting progress to my phone. Total investment: $0.
No servers. No paid APIs. No coding bootcamp. Just free tools, a clear strategy, and a lot of structured thinking.
Here's exactly how I did it, and how you can too.
The Problem: Time Is the Real Currency
Everyone talks about making money online. Few talk about the real bottleneck: you can't scale yourself.
You can write one blog post. You can scan one job board. You can research one niche. But doing all three consistently, every single day, while tracking what works? That's where most side-hustle attempts die — not from lack of ideas, but from lack of bandwidth.
I wanted a system that could:
- Research trending topics and draft articles automatically
- Scan Reddit, Hacker News, and freelance platforms for opportunities
- Track everything in a structured way — what's working, what's not
- Report to me via Telegram so I could steer from my phone
The Architecture: 18 Files, Zero Code
Here's the counterintuitive part: my agent isn't a Python script. It's a collection of markdown files that turn an AI assistant into an autonomous worker.
The system has three layers:
1. Config (the DNA)
Three files define what the agent does:
- strategies.md — Four money-making strategies with weighted priorities (Content Creation 60%, Lead Finding 25%, Micro-Task Hunting 15%, Digital Products 0% until unlocked)
- platforms.md — Every platform cataloged: URL, auth status, rate limits, monetization path
- persona.md — Writing voice, bio templates, niche rankings, content pillars
2. Memory (the brain state)
Eight files track everything:
- state.md — The "save game." Current phase, active task, strategy weights
- earnings.md — Revenue ledger with per-strategy breakdowns and milestones
- content-log.md — Every article: title, URL, views, revenue
- leads.md — Pipeline from FOUND to CONTACTED to CONVERTED
- opportunities.md — Freelance gigs scored by fit
- experiments.md — Structured hypothesis testing (not random guessing)
- daily-log.md — Append-only journal. Even if other files get corrupted, the history survives
- lessons.md — Extracted patterns: what works, what doesn't
3. Templates (the playbook)
Five reusable formats for blog posts, Reddit comments, freelance pitches, outreach DMs, and product listings.
The Loop: How It Actually Runs
Every cycle follows the same sequence:
- Read state — Where did I leave off?
- Decide — What's the highest-priority action right now?
- Execute — Research, draft, scan, or analyze
- Update memory — Log everything
- Report — Send results to Telegram
- Wait — Pause until next trigger
The decision logic is a priority waterfall:
- User instruction? Do that first.
- Pending decisions? Follow up.
- Unpublished drafts? Finalize them.
- Otherwise, pick a strategy based on weights.
The weights aren't static. Every 7 cycles, the agent reads its own earnings data and adjusts. If content is generating views but leads aren't converting, it shifts weight toward content. The system optimizes itself.
The Escalation Matrix: Autonomy with Guardrails
This is the part most people get wrong. A fully autonomous agent with no guardrails will eventually do something stupid. A fully restricted agent is just a chatbot.
My solution: a three-tier escalation system.
- Green (autonomous): Research, drafting, memory updates, analysis. The agent does these without asking.
- Yellow (notify + proceed): Publishing to approved platforms, changing topics. It tells me and keeps going unless I object.
- Red (block and wait): Creating accounts, contacting people, spending money, strategy pivots. It stops and waits for explicit approval.
This means I can check my phone once or twice a day, approve the important decisions, and let the agent handle everything else.
Day 1 Results
On its first cycle, the agent:
- Scanned Medium's trending AI articles and found 8 content ideas
- Browsed Reddit r/forhire and logged 4 leads (2 with strong fit scores)
- Identified that "AI content creation" is the hottest intersection of our skills and market demand
- Drafted this article (yes, this one)
Total time spent by me: about 10 minutes of setup and review.
Try It Yourself
You don't need to be a developer. You need:
- An AI assistant (Claude, ChatGPT, or similar)
- A folder structure for config, memory, and templates
- A communication channel (Telegram, Slack, email)
- Clear rules about what the agent can and can't do autonomously
The total cost is zero. The total time to set up is about an hour. The potential upside is an always-on system that compounds your effort while you sleep.
The hardest part isn't the technology. It's the discipline to build the system instead of just doing the work yourself.
This article was drafted by an AI agent as part of a zero-to-revenue experiment. Follow along for transparent updates with real numbers — no hype, no shortcuts.
Top comments (0)