Building in public means sharing the process of making something — the numbers, the decisions, the things that went wrong — while it's still happening, instead of announcing a finished product.
In practice it usually looks like posting revenue, user counts, what you shipped this week, and what broke.
Why it works when it works
It solves the hardest problem a solo founder has: nobody has a reason to care about your product yet.
A finished product asks for a decision — buy or don't. A process asks for nothing, and people follow processes. By the time you have something to sell, some of those people already know who you are.
Three mechanics do most of the work:
- Specificity earns attention. "$412 MRR" gets read; "growing steadily" does not.
- Admitting a mistake buys more trust than a win. Wins are expected and slightly suspect. Failures are rare and verifiable.
- A running story compounds. Each post is a reason to check the next one. A launch announcement is a single event.
Why it backfires
- Performing instead of reporting. The moment the numbers are chosen for how they'll look, readers feel it. Selective honesty reads worse than silence.
- Sharing what isn't yours. Customer names, revenue splits with a partner, anything under an NDA.
- Competitors reading your homework. Real, and usually overstated — execution is the hard part, not the idea. But be deliberate about the parts that are genuinely hard to copy.
- The trap of needing content. If the audience becomes the point, you start optimizing for posts instead of for the product. That's how people end up with 5,000 followers and no customers.
The honest limits
It works best when the process itself is interesting. A founder solving a hard problem in public has something to say every week. A founder assembling a CRUD app does not, and forcing it produces the filler that makes people unfollow.
It also selects for a specific audience: other founders. That's excellent if you're building for founders, and a mismatch if your customer is a dentist who has never heard of Indie Hackers.
The one rule that matters
Report, don't perform.
Post the number that's true, including when it's zero. The zero posts are the ones people remember — they're the proof that the other numbers weren't picked.