Esc
  • Jump to
  • The board
  • All launchesSort and filter by week or category
  • Open statsEvery number, in public
  • Maker storiesApps that stopped hiding
  • Submit a launch
  • AICategory
  • AnalyticsCategory
  • API & BackendCategory
  • Audio & VoiceCategory
  • AutomationCategory
  • CommunityCategory
↑↓ to move↵ to openPress / anywhere
Sign in

What is Build in Public?

Sharing your product progress, design decisions, launch lessons, and real numbers openly online while you build so future users and peers can follow along from day one.

Updated · Launch & Distribution

Plain definition

Definition of Build in Public

Sharing your product progress, design decisions, launch lessons, and real numbers openly online while you build so future users and peers can follow along from day one.

Worked example

Suppose a made-up founder is building FormSnap, a form-to-PDF generator for independent physiotherapists. For eight weeks leading up to launch, the founder posts two short updates a week: one technical breakdown of fixing messy intake forms on mobile, and one plain look at what changed after interviewing clinic owners. Each post ends with a tagged link to a simple changelog and early-access page.

Across 16 posts, total impressions look modest, but 4 clinic managers reply with sample intake forms they hate retyping, and 38 readers join the early-access list. When FormSnap opens subscriptions at $25/month, 7 of those 38 readers sign up during launch week and 3 become paying clinics ($75 MRR), plus two more refer colleagues in their local association. Because every update showed the real problem being solved rather than generic startup motivation, the small audience matched the actual buyer.

Why it matters when you launch

Starting from zero followers makes launch day quiet unless people have context for why your tool exists. Documenting your work in public builds a searchable trail of demos, screenshots, and honest problem-solving before you ever ask for a credit card.

It also shortens feedback loops. Posting a 30-second screen recording of a rough feature often surfaces edge cases or clearer phrasing in two hours instead of two months. Just keep the focus on the customer's workflow and tangible product updates, because posts about coding setups mostly attract other builders rather than buyers.

Common mistakes

  • Writing exclusively for other indie hackers about frameworks and MRR milestones when your target buyers are accountants, recruiters, or shop owners.
  • Spending three hours a day polishing social threads while the product itself barely moves forward.
  • Publishing sensitive customer data, private client complaints, or unredacted billing dashboards in screenshots.
  • Turning every update into a sales pitch instead of showing concrete before-and-after progress, trade-offs, and honest misses.

Tools and guides that use it

Pritam Ghosh runs Hauntboard and maintains this glossary.

Published · Updated

Building something real? Launch it in public.

A person reviews every launch on Hauntboard, and every view and visit it sends your site is published on your launch page. Free to submit.

Launch free →

On the board

All →

Still hiding your app?

Put it on the board. Reviewed by a person, free to launch.

Launch free
Submit a launch