Science of Apps - Launchpad · Guide

Build in public:
a guide that drives users

Building in public means sharing how you build your startup (progress, numbers, decisions and mistakes) where your future users can see it. It drives users when the audience matches your customers and every post points to somewhere they can try the product. Post a short weekly update with one or two real numbers and one lesson, and link a permanent product page.

By , FounderUpdated 5 min read

Share

Quick answer: Does building in public work?

  1. What: progress, real numbers, decisions, mistakes.
  2. Where: where your users are, not just where founders are.
  3. How often: one weekly update you can sustain.
  4. Numbers: one or two you're comfortable keeping public.
  5. Convert: every post links to a page people can try.

Key takeaways

  • An audience of other founders only helps if founders are your customers.
  • Consistency beats virality.
  • Honest numbers, including bad ones, build trust.
  • Decide what stays private before you start.
  • Measure sign-ups from posts, not likes.

"Day 47 of building in public: 3 users, $0 MRR, still shipping." Thousands of these posts go out every week, and most reach the same few hundred founders, who like them, reply "keep going" and never become users. Building in public isn't the problem. Building in front of the wrong audience, with nothing to click, is. Done well, it gives you early users, honest feedback and a launch day where people already know your name. This guide covers what to share, where, how often, which numbers to publish and how to turn readers into users. Jump to what to share, the weekly template or turning followers into users.

Update a week, sustained
1
Real numbers per update
1–2
Link to a page people can try
1
Customer data or secrets shared
0

Does building in public work?

It works when your readers are your customers. If you sell to designers, posts that designers read bring users; posts only founders read bring encouragement. Decide who you're building for, then go where they are.

Comparison — What you gain: Early users and feedback before launch; Trust from visible, honest progress; A warm audience on launch day; Accountability to keep shipping. What it costs: Time each week; Competitors see your playbook; Bad weeks are public; An audience of peers, if you aim it wrong.
What you gain vs What it costs

What you gain

  • Early users and feedback before launch
  • Trust from visible, honest progress
  • A warm audience on launch day
  • Accountability to keep shipping

What it costs

  • Time each week
  • Competitors see your playbook
  • Bad weeks are public
  • An audience of peers, if you aim it wrong

What to share

Checklist: What to share — What you shipped; One or two numbers; A decision and why; A mistake; A question for readers; What's next.
What to share
  • What you shipped — with a screenshot or a 20-second clip
  • One or two numbers — the same ones every week
  • A decision and why — pricing, a feature cut, a channel dropped
  • A mistake — and what you changed
  • A question for readers — the best source of feedback
  • What's next — so they come back

Keep private: customer names and data without permission, security details, unannounced deals, and anything you're not ready to defend.

Which numbers to publish

Buffer Open page A transparent company since 2010 with monthly metrics for monthly active users, MRR, ARPU and ARR
Buffer's open dashboard: the furthest end of building in public.Image: Buffer · Screenshot shown for commentary, 17 Nov 2026 · source

Buffer says it has shared its finances and salaries openly since 2013, with a dashboard of monthly active users, MRR, ARPU and ARR. You don't need to go that far. Pick numbers you'll keep sharing when they fall.

StageNumbers worth sharing
Pre-launchWaitlist sign-ups, interviews done
Just launchedWeekly sign-ups, activation rate
Early revenueMRR, paying customers, churn
GrowingActive users, revenue by channel

Table: Numbers to share when building in public, by stage (editorial guidance)

Where to build in public

ChannelBest forFormat
LinkedInB2B buyersWeekly post with one chart
XTech and developer audiencesShort updates, threads
Indie HackersFounders and makersMonthly milestone posts
Show HNDevelopers, once it's tryableOne launch post
Your blog or listingEveryone, permanentlyWeekly or monthly changelog

Table: Where to build in public (editorial guidance; check each community's rules)

Indie Hackers homepage with founder posts about revenue, customers and marketing
Indie Hackers: founders sharing strategies and revenue numbers.Image: Indie Hackers · Screenshot shown for commentary, 17 Nov 2026 · source

The weekly update template

Week [n] of [product]: [one-line headline] Shipped: [feature], [screenshot] Numbers: [metric] [this week] (last week [x]) Learned: [one lesson in two sentences] Question: [one thing you want readers' input on] Try it: [link to your product page]

Turning followers into users

Diagram of 6 steps for turning followers into users: 1. Link every post; 2. Invite, don't just report; 3. Reply to every comment; 4. Collect emails; 5. Measure sign-ups by source; 6. Launch to the audience.
Turning followers into users
  1. Link every post — to one product page, not your profile.
  2. Invite, don't just report — "Looking for 10 clinics to try this" beats "Day 47".
  3. Reply to every comment — that's where users come from.
  4. Collect emails — a waitlist or newsletter, so you're not dependent on one platform.
  5. Measure sign-ups by source — UTM links per channel.
  6. Launch to the audience — they've watched it being built; ask them on launch day.

Mistakes

Checklist: Mistakes — Writing for founders when you sell to someone else; Vanity numbers; Posting daily, then stopping; No link; Oversharing.
Mistakes
  • Writing for founders when you sell to someone else
  • Vanity numbers — followers and impressions instead of users
  • Posting daily, then stopping — weekly and steady wins
  • No link — every post is a dead end
  • Oversharing — customer data and security details stay private

Ready to build in public?

How we know

Buffer's open-metrics details come from its public dashboard, read on 17 November 2026. The template, channel table and stage-by-stage numbers are our editorial guidance; check each community's rules before posting.

Key terms, defined

  • Build in public: sharing a startup's progress and numbers openly.
  • MRR: monthly recurring revenue.
  • Activation rate: the share of new users who reach a first result.
  • UTM link: a link tagged so analytics shows where a visit came from.
  • Changelog: a public list of what changed in the product.

Frequently asked questions

What is building in public?

Sharing the process of building your startup openly: what you shipped, numbers like users or revenue, decisions and mistakes, usually in regular posts on social media, a blog or a community like Indie Hackers.

Does building in public work?

It works when your audience overlaps with your customers and posts link to something people can use. It can build trust, bring early users and feedback, and make launches easier. It doesn't work when you only reach other founders selling to someone else.

What should I share when building in public?

What you shipped this week, one or two real numbers, a decision you made and why, something that went wrong, and what's next. Skip customer data, security details and anything you'd regret competitors seeing.

Which metrics should I share?

Ones you can keep sharing when they go down: weekly active users, MRR, sign-ups or a key activation rate. Buffer, for example, shows MRR, ARR, active users and ARPU on a public dashboard.

Where should I build in public?

Where your customers spend time: LinkedIn for B2B buyers, X for tech audiences, Indie Hackers for founders, Reddit or niche communities for specific users. Cross-post a weekly summary to your own blog or listing so it lasts.

What are the risks of building in public?

Competitors see your playbook, bad weeks are visible, and it can eat time. Decide upfront what stays private and cap the time you spend on it.

Sources

  1. Buffer — Open metrics (checked 17 Nov 2026)
  2. Indie Hackers
  3. Hacker News — Show HN guidelines
  4. Science of Apps — Launchpad: launch your product free
  5. Checked November 17, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free, forever

Launch day ends. Your listing shouldn't.

A free, permanent Launchpad profile is the public home for your build: every post links to it, people find it by the problem you solve, and it's ranked by relevance, never payment.

Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free PDF · 188 pages · 2 editions

Unmistakable: the logo book

How the world’s greatest logos are made, chosen and kept — and how to make yours. 98 short lessons and 19 true stories for founders, designers and the curious. By Sushant Singh, founder of Science of Apps.

  • 98 lessons
  • 19 true stories
  • 60+ real logos

Why did a $35 sketch become the Swoosh, and why did Gap lose its nerve in six days? It’s all inside.

Pick your edition