How to build in public for marketing
Share your product's progress as you go to earn early users, feedback and trust.
- Impact
- High
- Effort
- Low
- Filed under
- Awareness, Social Media, Acquisition
- Updated
Build in public means sharing your product's progress while you work on it: what you shipped, what broke, what you decided and why, sometimes even revenue and traffic. It works best for small products with a founder who will keep posting, because the audience that follows along is also your first set of users and feedback. It is slow, low-cost marketing, not a launch tactic.
How to do it
- Choose one place where your future customers already read. That might be X, LinkedIn, a niche forum, a subreddit, your own blog, or a newsletter. Start with one, not five.
- Turn each real piece of work into one post. A new feature becomes a short write-up of the problem, the fix, and a screenshot. A hard technical problem becomes a longer post. A usability mistake you fixed becomes a before-and-after.
- Share numbers only when you are willing to be held to them. Signups, revenue and traffic are the classic things people post. If you post one, post it on a regular schedule, including the bad weeks.
- Ask for something specific in each post: feedback on a design, which of two names is better, whether anyone has hit the same bug. Replies are the point.
- Link to the product where it fits, in the post or your profile, and give each post one clear next step for a reader who wants to try it.
- Keep a simple log of what you post and what it brought: replies, signups, referral clicks. After a month, keep the formats that brought people in and drop the rest.
You can also get more than one piece of content out of every feature. A technical write-up can go to a technical audience, a design write-up to designers, a metrics post to founders. Each audience sees the product as new.
Examples
Buffer. Buffer's about page says "Since 2013, we've shared Buffer's finances, team salaries, and other key metrics openly," and links to open pages for its metrics and salaries. That is building in public at company scale, and it is a deliberate brand choice more than a growth trick.
Plausible Analytics. Plausible's docs say site stats are private by default, and that turning on the visibility setting gives you a public dashboard URL. Plausible shows its own traffic on a live demo page. A small product can do the same with any analytics tool that supports public dashboards.
When it backfires
- Promotion rules. Many communities restrict self-promotion. Hacker News guidelines say "Please don't use HN primarily for promotion" and "It's ok to post your own stuff part of the time." They also say "Don't solicit upvotes, comments, or submissions." The Show HN rules exclude "blog posts, sign-up pages, newsletters, lists, and other reading material" and say "Please don't ask friends to upvote or comment." If you post a Show HN, our Show HN timing data shows which day and hour did best over the last year. Read a community's rules before posting there.
- Sharing too much. Public revenue and roadmaps show competitors your pricing, your traction and your plans. Do not share customer names, private data, or anything covered by a contract.
- A thin audience. Posting only to other founders builds followers, not customers. Check whether the people replying could buy.
- Consistency. A feed that stops after three weeks looks abandoned. Pick a pace you can keep, such as one post a week.
- Overselling. If you post about progress that is not real, people will check. Share the real state.
Questions people ask
What does build in public mean? It means sharing your work as it happens, in posts, threads or a changelog, so people can follow, give feedback and try the product early.
How do I build in public as a founder? Start with one channel, post about one real change each week, and ask a specific question. See celebrate milestones for turning wins into posts.
Does build in public work for marketing? It can bring in early users and feedback for small products. There is no reliable public data on how often it pays off, so judge it by the signups and replies you track yourself.
Sources
- About Buffer, read Oct 8, 2026
- Plausible docs: open up your website stats to the public, read Oct 8, 2026
- Plausible live demo of plausible.io stats, read Oct 8, 2026
- Hacker News guidelines, read Oct 8, 2026
- Show HN guidelines, read Oct 8, 2026
Launching soon? This is one of the pre-launch marketing tactics, listed in the order to start them.