Bootstrapping passive income — month 0

3 min read
Also available in:中文

Bootstrapping passive income — month 0

I've been writing code for a decade. Go, Python, Flutter, Rust. Distributed systems, cloud-native, containers, and the past two years on AI infrastructure.

I'm good at shipping things. The problem: I've only ever shipped them for other people.

What I want has been crystal clear for years: passive income, time freedom, not being tied to a job. This isn't the romantic "quit your job and travel" version. It's the boring version — having a real choice in what to work on, when, and with whom.

February 2026. Time to stop planning and start shipping.

Why now

A few things lined up.

AI changed the economics of content. Ten minutes to outline a post, AI expands it into a draft, I spend thirty minutes adding actual experience and judgment. What used to take four hours now takes one.

The raw material has been compounding for years. Technical notes, project ideas, open-source code — all sitting in a Markdown repo, collecting dust. It's past time to convert knowledge into output.

The automation layer is finally ready. I run a small multi-agent system that handles monitoring, research, and drafting. It's been waiting for me to feed it.

The direction

AI × developer tools.

Reasoning:

  • I use these tools daily; I know them better than I know anything else
  • Developers have real willingness to pay
  • The AI-tools market is still wide open
  • Content compounds into my open-source projects and products

Content strategy

One core post per week. 1–2 hours of writing. AI fans it out across platforms. Distribution tooling handles the rest. Total weekly time: 5–8 hours.

Three-tier distribution:

  • Primary (manual + AI-assist): Twitter/X, personal blog, GitHub
  • Auto-sync: Juejin, Zhihu, Xiaohongshu — AI rewrite + one-click publish
  • Later: YouTube / Bilibili once I have video content worth shipping

Month 0 numbers

Brutal honesty:

  • Twitter: 0 followers (new account @jiusanzhou)
  • Blog visits: effectively zero
  • GitHub stars (combined across all projects): ~500
  • Revenue: $0
  • Published content: 0

Starting from absolute zero. I want a public record of the whole journey, so this is the baseline.

Month 1 goals

  • 200 Twitter followers
  • 4 blog posts
  • 8 Twitter threads
  • 1 new open-source project (a content-distribution CLI)
  • Revenue: still $0, not expecting any
  • Under 8 hours/week total

Monetization path

Not chasing revenue in month 1. The long view:

  • Months 1–3 — build an audience, establish a publishing cadence, get people using my open-source work
  • Months 3–6 — first revenue: GitHub Sponsors, light technical consulting
  • Months 6–12 — scalable revenue: paid courses, a SaaS product
  • Year 2 — compounding kicks in: multiple revenue streams, content production largely automated, 3–5 hours/week of maintenance

What I'm not going to do

  • Not quitting the day job. Not yet.
  • Not chasing viral content.
  • Not buying followers or running ads.
  • Not paying for tools — free and open-source only.
  • Not obsessing over perfection. Ship first, iterate.

The stack

All free or open-source:

  • Blog: zoe.im, my own static-site generator
  • Knowledge base: a Markdown repo on GitHub
  • AI assistant: multi-agent system on top of OpenClaw + Claude
  • Distribution: distro, my own CLI
  • Analytics: TBD

What's next

This is the month-0 report. I'll publish one every month with real numbers: follower counts, revenue, hours spent, what worked, what didn't.

No cherry-picking. Just data and honest retros.

Follow @jiusanzhou or subscribe at zoe.im. See you in month 1.

Zoe

Written by

Zoe

AI Infra Engineer · LLM Serving · GPU/RDMA · indie hacker, obsessed with shipping tools

Comments