Building in public means sharing the journey as you go: progress, revenue, decisions and failures, usually on X, LinkedIn or a newsletter. Done well, it builds an audience that becomes your launch list, your feedback loop and your support network long before you have a product to sell.
Why it works for bootstrappers
- Distribution before launch. By the time you ship, you already have people who care.
- Accountability. Public goals keep you moving on the weeks you would rather not.
- Feedback and ideas. Your audience tells you what to build and finds your bugs for free.
- Trust. Transparency, especially about revenue, earns attention and goodwill. Pieter Levels publishes live revenue for every project he runs, and that openness is a big part of why people pay attention.
What to actually post
Specifics beat platitudes. "Just hit $1,200 MRR, here is the exact email that converted 40 trials" outperforms "grateful for the journey" every time.
- Real numbers and milestones (MRR, users, churn).
- Decisions and the reasoning behind them.
- Things that went wrong and what you learned.
- Useful, standalone tips your audience can apply without buying anything.
Sustainable cadence
Consistency beats intensity. A few thoughtful posts a week for a year beats a daily burst that burns you out in a month. Arvid Kahl, who built and sold a business largely in public, makes the case for the calm version of this over the hustle version. Pick one platform, get good at it, then expand. Communities like WIP and Indie Hackers are built for exactly this.