Day 5: The Flywheel — From Building Apps to Selling Sprints
Stopped treating apps as the product. Started treating them as proof. The real revenue model is a productized AI development sprint, powered by a content flywheel that feeds itself.
Day 5 was the day the strategy crystallised.
For four days I built. Three apps, 159 commits, 21,000 lines of code, five Codex agents running in parallel. Good work. Real output. But building apps wasn't going to hit $10K MRR in 25 days.
Today I stopped building features and started building a business model.
The Realisation
Apps take months to monetise. You build, you launch, you market, you iterate, you wait for organic growth. Even good apps with real utility don't produce recurring revenue on day one.
But here's what four days of shipping did produce: proof.
Proof I can build production apps fast. Proof that AI-native development works at speed. Proof that a single developer with the right tools can ship what used to take a team weeks.
That proof is worth more than the apps themselves.
The Flywheel
Here's the model:
Build in public → Proves expertise → Drives leads
↑ ↓
More content ← Case studies ← Productized sprint
Every piece feeds the next. The experiment log you're reading right now? That's the top of the funnel. The 3 apps I built? That's the proof. The service I'm launching? That's the revenue.
It's not complicated. It's just disciplined.
The Offer: AI Development Sprint
I'm productizing what I've been doing all week.
What: I build AI workflows and product features in focused sprints. Fixed scope, fast delivery, measurable outcomes. You get production-ready automation, documentation, and optional ongoing optimization.
Three packages:
| Package | What You Get | Pricing |
|---|---|---|
| Audit | Workflow inventory, pain points, ROI scoring, 90-day roadmap | $1,500 one-time |
| AI Sprint | 2-week build, one automation or AI feature, integrations, QA, documentation | $5,000 one-time |
| Done-for-you | End-to-end: strategy, multi-workflow automation, monitoring, monthly optimization | $12,000 setup + $1,500/mo |
Why this works for clients:
- They get a working product, not a wireframe or proposal
- AI-native development is faster and cheaper than traditional agency work
- The build is documented — they understand what was built and why
- Same stack and approach that shipped 3 apps in 4 days
- Optional ongoing optimization means it keeps improving
Why this works for me:
- Two AI Sprints = $10K. That's the MRR target in two sales.
- Done-for-you clients = recurring revenue from day one.
- Every sprint produces a case study. Every case study drives more leads.
- Monthly retainers compound. 5–10 retainer clients = sustainable MRR.
Builder + Educator
The persona isn't "agency founder selling services." It's builder who educates.
Every piece of content does two things:
- Shows what I built (proof)
- Teaches something useful (value)
The experiment log is the perfect format for this. It's authentic, it's documented, and it's the kind of content that builds trust faster than any sales page.
The agent apps aren't the product to sell — they're the product to show. "Here's what I built in 4 days. Imagine what I could build for you in 2 weeks."
What We Also Built Today
The strategic shift didn't stop the building. We shipped infrastructure that makes the ecosystem real:
Points Economy (TaskBounty)
A complete in-app economy for AI agents:
| Event | Points |
|---|---|
| Registration | +100 |
| Welcome bonus | +50 |
| Daily claim | +10/day |
| Post bounty | -(25 to 250) |
| Win bounty | +(bounty amount) |
Full audit trail. Every point movement logged. Agents check balances, claim daily rewards, view transaction history — all through the API.
Agent Instruction Guides
Created AGENTS.md files for all 3 apps — machine-readable guides that tell AI agents exactly how to discover, register, and use each platform. One consistent pattern across three apps.
Public REST APIs (PromptDuels)
Building the HTTP endpoints agents need: browse challenges, enter duels, check leaderboards, view stats. Same auth patterns, same response format, same developer experience.
Day 5 Metrics
| Metric | Value |
|---|---|
| Files changed | 15+ |
| New API endpoints | 6 |
| New Convex tables | 2 |
| AGENTS.md files | 3/3 |
| Lines added | ~800 |
| Strategic documents | 1 (organic growth plan) |
The Plan — 25 Days Remaining
Phase 1: Foundation (Days 5–7)
- Define and publish the sprint offer
- Landing page on amirbrooksclean
- Deploy 3 agent apps as proof of work
- First LinkedIn posts with experiment framing
Phase 2: Content Engine (Days 8–14)
- Daily LinkedIn posts (experiment-framed)
- Build log updates on the site
- Twitter threads 2–3x/week
- First case study from the agent apps build
- Tutorial: "How I used Codex to build a full app in 8 hours"
Phase 3: Outreach + Conversion (Days 14–21)
- Warm outreach to LinkedIn connections (20 conversations)
- CTAs to landing page in all content
- Community sharing (3–5 relevant groups)
- Goal: first paying client
Phase 4: Deliver + Scale (Days 21–30)
- Deliver first sprint, document everything
- Write the case study
- Upsell to Done-for-you ($1,500/month ongoing)
- Refine the offer based on real feedback
- Plan month 2
Revenue Targets
| Week | Target | How |
|---|---|---|
| Week 2 | $0 | Foundation + content assets |
| Week 3 | $1.5K–$5K | First Audit or AI Sprint sale |
| Week 4 | $5K–$12K | Second sprint or Done-for-you client |
| End of month | $10K+ | Sprint + retainer combo |
What I Observed
The hardest part of this experiment isn't building. Building is the easy part — I have the tools, the stack, and the workflow dialled in. The hard part is turning building into revenue.
The flywheel solves this. It turns every hour of building into content, every piece of content into proof, and every piece of proof into a reason for someone to pay.
The agent apps are still getting deployed. The ecosystem is still getting wired together. But now there's a clear path from "things I built" to "money in the bank."
What's Next
- Landing page for AI Development Sprint
- Deploy the 3 agent apps (still blocked on
vercel login) - First experiment-framed LinkedIn post about the offer
- Content calendar for the next 7 days
Day 5 was the day I stopped building apps and started building a business.