Build in public

Why makers do it

An audience that has followed the story is the most reliable launch audience there is. People who watched a product take shape want to try it, give feedback and tell others. Sharing in public also forces clear thinking, attracts other founders who help, and creates a record of the work.

What to share

Real numbers, even small ones: sign-ups, revenue, churn. Decisions and why you made them. Things that failed. Screenshots of the product as it changes. Questions you are stuck on. The posts that work best teach something other makers can use.

Nobody has to share everything. Many founders keep customer data and exact revenue private and share the trend instead.

Building in public and launching

A few weeks of public building before a launch gives you people to tell on launch day and a story for the maker comment. On Indie Hackers and X in particular, "I built this alone and here is what happened" is a strong introduction.

The risks

Sharing numbers invites comparison, and sharing plans can help competitors. Some founders find the pressure to post distracts from building. A simple rule helps: share what you learned and what changed, keep anything that belongs to customers private, and post on a schedule you can keep rather than every day.

Example

A solo founder posts weekly updates with sign-up numbers and screenshots for two months, then launches to the few hundred people who followed along.

Questions people ask

Does building in public help a launch?

Yes, mainly by giving you an audience that already knows the product and wants it to succeed, which is what the first hours of a launch need.

Where should I build in public?

Where your future users and peers already are: X and Indie Hackers for makers, LinkedIn for B2B audiences, and a blog or newsletter you own.