The idea behind building in public is simple: you share the messy middle of making your product, not just the polished launch. The revenue, the failures, the feature that flopped, the lesson you learned the hard way. Done right, it earns you an audience of people who feel like they’re part of the story. Done wrong, it’s a stream of vanity metrics nobody asked for, posted into a void. Most founders manage the second kind and quietly give up.
The gap between the two isn’t charisma or follower count. It’s whether you’re sharing things that are actually useful or interesting to someone other than you. Here’s how to do it so it pulls people in instead of bouncing off them.
Building in public works when you share the struggle, not the scoreboard
“MRR up 4% this week” means nothing to a stranger. It’s a number with no story. What people lean in for is the struggle behind it: the pricing change that scared you, the churned customer who told you exactly why they left, the bet that didn’t pay off. Share the decision and the doubt, not just the result, and suddenly people are following along because they want to know what happens next.
This works because other founders are fighting the same battles in private, and seeing someone narrate theirs out loud is genuinely useful. You’re not bragging, you’re reporting from a place they recognize. That’s the thing that turns a passive scroll into a follow.
Be specific or be ignored
Vague posts die. “Consistency is key” teaches no one anything. “I changed my onboarding email from three steps to one and trial conversion went from 9% to 14%” is something a reader can actually use. Specifics are what make building in public worth following, because they hand people something they can take back to their own product and try.
The fear is that being specific gives away some secret. It almost never does. Your edge is in the execution, not the tactic, and the goodwill you earn by being concretely helpful is worth far more than the imaginary advantage you’re protecting by staying vague.
It’s a slow channel, so treat it like one
Building in public almost never produces a viral moment that changes everything. What it produces is a slow accumulation of people who trust you, some of whom become users, some of whom send you users. Judge it on months, not days. The founder who posts honestly for a year ends up with something an ad budget can’t buy: a small crowd that actually cares whether you succeed.
That makes it a sibling of every other slow-compounding channel, where trust does the heavy lifting over time. The same logic runs through community-led growth for startups, where the point isn’t a spike of attention but a base of people who stick around and vouch for you to others.
Don’t let it replace actually selling
Here’s the trap nobody warns you about. Building in public feels productive, the likes feel like progress, and you can spend months posting while your pipeline stays empty. It’s a real channel, not a substitute for going out and finding customers directly. Treat it as the slow background hum, not the main engine, and keep doing the direct outreach that actually pays the bills this month.
That direct work, finding specific people who need you right now, is the part that’s hard to keep up while you’re also posting and building. It’s exactly what we built Unbound Compute to handle: surfacing the people openly showing your problem, so the audience-building can stay a slow side project while the real selling keeps moving. You build in public on your own time. We just make sure the pipeline doesn’t go quiet while you do.