Building in isolation is slow. There’s no narrative connecting the projects, no compounding audience, no accountability forcing a shipping cadence. The cure is to invite people in before you’re ready. So I did.
The Problem
Side projects die in private. The build-in-public constraint solves this: when you tell people what you’re working on, you create a social obligation to finish. The audience doesn’t have to be large. It just has to exist.
What It Is
A 3-month public sprint documenting the process of shipping multiple apps while narrating every decision, cost, and mistake in real time. Content is native per channel: no verbatim cross-posting. LinkedIn gets the founder perspective. YouTube gets the developer series. Instagram gets the visual behind-the-scenes. X gets the raw takes.
The sprint is anchored by the Lists of 30 app as the flagship product. Everything else gets documented alongside it.
How It Works
- LinkedIn: founder perspective posts, what’s being built and why
- YouTube: developer series documenting specific technical decisions
- Instagram: visual behind-the-scenes of the build process
- X: short-form takes and real-time updates
- Cap of 3 hours per week on content to prevent it from consuming the build
Constraints
No monetization during the sprint window. The goal is trust-building, not revenue generation. An audience that watches you build is worth more than an audience you buy.