Building in public means openly sharing the journey of making your product: the numbers, the decisions, the wins, and the mistakes. It started with a few indie hackers posting their revenue on Twitter. Now it's one of the most dependable ways for a small founder to build an audience without an ad budget.

This guide covers why it works, what to share, and how to make it a habit instead of a burst of posts that fizzles out after two weeks.

Why building in public works

People root for people, not products. A logo launching a feature is an ad. A person explaining why they spent three weekends rebuilding onboarding, and what happened to activation afterwards, is a story. Stories get followed.

It compounds. Every post adds a little to the trust people have in you. Your 200th update reaches a much bigger and warmer audience than your first, and that audience becomes your beta testers, your first customers, and the people who share your launch.

It keeps you accountable. Saying in public "I'll ship billing this week" makes it much more likely you'll do it.

It attracts opportunities. Founders who share openly get inbound from investors, acquirers, collaborators, and journalists, because they're easy to find and easy to understand.

What to share

You don't have to share everything. The most engaging building-in-public content falls into a handful of types:

  1. Milestones. First customer, $1K MRR, 1,000 users, one year in. These are your highest-reach posts, so make them visual. A milestone card shows the number at a glance.
  2. Metrics updates. A regular monthly post with MRR, customers, and churn. Consistency matters more than the numbers being impressive.
  3. Lessons and mistakes. "We lost 30% of trials at the credit card step. Here's what we changed." Failure posts often beat success posts on engagement.
  4. Decisions. Pricing changes, feature cuts, pivots. Show your reasoning and invite opinions.
  5. Behind the scenes. Screenshots of messy work in progress, your actual to-do list, the dashboard you check every morning.
  6. Thank-yous. Credit the customers and peers who helped. It's generous and it spreads.

What not to share

  • Customer data. Never post screenshots that reveal customer names, emails, or private messages without permission.
  • Anything that helps a competitor clone you. Your exact acquisition channel and keyword list can wait until the moat is built.
  • Vanity without context. "10K page views!" means little. "10K page views, 2.1% signup rate, 14 paying customers" teaches something.
  • Things that stress you to share. If posting revenue makes you anxious, share growth percentages or user counts instead. Building in public is a tool, not an obligation.

A sustainable weekly routine

The founders who benefit most aren't the loudest. They're the most consistent. A routine you can keep for years:

  • Monday: share one goal for the week.
  • Midweek: post one piece of work in progress, like a screenshot, a snippet, or a decision you're weighing.
  • Friday: a short recap of what shipped, what didn't, and what you learned.
  • Monthly: a metrics update with a card, and a short reflection on the month.
  • On milestones: a dedicated post with the story behind the number. See how to write a milestone post.

Batch it if you need to. Twenty minutes on Sunday can draft the whole week.

Choosing your platform

  • X (Twitter) is still the home of the indie hacker and SaaS crowd. Short, frequent posts work best.
  • LinkedIn works well for B2B products. Posts that are a bit longer and more reflective do well there.
  • Indie Hackers and Reddit are good for long, detailed write-ups. Respect each community's self-promotion rules.
  • A newsletter or blog is the one channel you own. Repost your best threads there so the work isn't trapped on a platform.

Measuring whether it's working

Track followers, sure, but more importantly track signups and revenue that came from your audience. Add "How did you hear about us?" to your signup form. If after six months of consistent posting nobody mentions you, change what you share, not whether you share.

Getting started today

Write one post introducing what you're building, who it's for, and your current numbers, even if they're all zero. "Day 1: $0 MRR, 0 users, one idea" is a great opening post. The best time to start building in public was when you started building. The second best time is today.