Build in Public: What the Data Actually Shows for Getting Customers
Build in public first customers data from 68 bootstrapped apps. What types of posts get customers, what gets noise, and how long before it compounds.
Build in public first customers data from 68 bootstrapped apps tells a more nuanced story than the Twitter highlight reel. Build in public is the most-used channel in the DistributionMarket database, appearing in 43 of 68 apps tracked. But the pattern of when it generates customers versus when it generates applause from other founders is specific and learnable.
The Raw Numbers
Build in public is not a niche strategy. It is the single most common channel across the entire database.
43 of 68 apps use it. That is 63% of the apps tracked across every revenue band from $0 to $100M. No other channel comes close. Product Hunt launches appear in 27 apps. Word of mouth in 24. Email newsletters in 30.
But usage rate is not the same as conversion rate. The question is not whether founders post in public. The question is whether those posts bring customers or bring followers.
Who Is Actually Watching
Before build in public generates customers, you need to understand who sees your posts.
The default audience for build in public content on X (formerly Twitter) and LinkedIn is other founders, makers, and indie hackers. They follow you because they are interested in your journey. They engage with your revenue milestones because they want context for their own path.
That audience is not your customer unless your customer happens to be a founder.
Senja, a testimonials tool, documented this explicitly. Its build in public posts on Twitter drove the first 1,000 customers because the ICP was indie hackers and makers who were already on that platform and trusted founders who shared vulnerably. The channel worked precisely because the buyers and the audience were the same people.
Journable, a journaling app, took the opposite position deliberately. The founder waited until $1M ARR before starting to post publicly, because the target customer (people who want to journal) does not follow indie hacker content. He called it "a deliberate inversion of the indie default."
The first question before you start posting is: does my buyer exist inside the build in public audience? If yes, this channel can drive customers directly. If no, build in public is a validation and credibility tool, not a customer acquisition channel.
Posts That Get Customers vs Posts That Get Noise
The database makes the pattern clear. Specific numbers outperform vague progress updates.
Testimonial.to's founder shared exact MRR milestones on Twitter in 2020 to 2022. A specific "$1K MRR" post attracted Andrew Gazdecki as a customer because the post was concrete enough to find in search and credible enough to signal the product was real.
TypingMind's founder spent two years building 97K followers before the product launched. When it did, 99% of the first $22K in revenue came from that audience. The posts that built the audience were specific: operational numbers, pricing decisions, exact revenue beats serialized over time.
The pattern is: revenue milestones, specific operational metrics, and honest struggle updates attract high-intent readers. "Day 47 of building my startup" attracts other builders who will never buy.
Specific numbers attract buyers. Vague progress updates attract other founders watching from the sidelines.
The distinction matters because the two types of posts feel similar to write and look similar in terms of likes and replies. The difference shows up in what the responders do next. Responses to specific posts often include "I have this exact problem" or "how do I sign up." Responses to progress posts include "keep going" and "following for updates."
How Long Before Inbound Becomes Consistent
The honest answer from the database is: longer than most founders expect.
AudioPen shipped roughly 15 small products publicly over 2-3 years before the product that hit 100 paying customers in 2 days. That track record of building in public, across 15 different experiments, created an audience of 10K niche followers who trusted the builder before they trusted any specific product.
Build in Public Mastery, a course business built around the practice itself, spent six months answering questions and sharing its journey before charging anything. Kevon Cheung turned that period into the trust infrastructure that pre-sold his first cohort.
The median pattern in the database for apps that credit build in public as a meaningful customer channel is 6 to 24 months of consistent posting before inbound becomes consistent. Outliers exist. Chatbase launched a 30-second demo tweet to 16 followers in February 2023 and hit $1M ARR in 117 days, but it launched during a paradigm shift in AI that amplified everything. That moment has passed.
For most products, in most categories, build in public is a compounding asset. The earlier you start, the more valuable it becomes. But do not expect it to replace a distribution channel in your first 90 days.
Validation Tool vs Distribution Channel: The Real Difference
Build in public serves two functions. The confusion comes from treating them as the same thing.
As a validation tool, build in public is fast. You post about a problem you are solving. If the right people respond saying "I have this problem too" or "I have been looking for exactly this," you get signal in hours. The feedback loop is immediate. This is why early-stage founders who are still finding product-market fit can get enormous value from posting even before they have a product.
As a distribution channel, build in public is slow. Converting followers into customers requires enough trust that someone who has watched you for weeks or months decides to pull out a credit card. That trust takes time to build. It also requires that your product solves a real problem well enough that the buyer expects it to work.
Uneed, a product directory in the database, used build in public primarily to reach other founders who had products to launch. That is both the validation audience and the customer audience at the same time. Revenue transparency posts and admitted failures on X drove trust, and that trust converted into listings. The channel worked because Thomas was selling to the exact people watching.
Data Fetcher shows the other side. The founder used build in public to post specific operational numbers: conversion rates before and after pricing changes, migration decisions, goal-setting. The audience was fellow bootstrappers. They became word-of-mouth advocates who recommended the product to their own networks. Build in public generated distribution indirectly, not directly.
Both modes work. They work differently and on different timelines.
What Does Not Work
Build in public fails in predictable ways.
The first failure mode is posting without a target audience. Random updates about building go into a void unless there is already an audience listening. If you have fewer than 500 followers and no existing community, build in public is a slow start. The faster early move is to participate in existing communities first, then port that audience to your own feed.
The second failure mode is posting in the wrong place for your buyer. If you sell to restaurants, dentists, or HR professionals, they are not reading X build in public content. Your posts will collect likes from other founders and generate zero inbound from the people who could actually pay you.
The third failure mode is treating consistency as a substitute for specificity. Posting daily vague updates is worse than posting weekly posts with concrete numbers. The database shows this repeatedly: founders who share exact metrics get more signal from their audience than founders who share narrative progress.
Finally, build in public in a competitive market can accelerate copycats. DistributionMarket's own data shows that Testimonial.to deliberately stopped sharing detailed MRR milestones once competitors started mirroring the playbook. Transparency has a cost when the market is crowded. Weight that before you publish your entire distribution strategy.
The Honest Assessment
43 of 68 apps in the database use build in public. That is because it is genuinely useful, not because everyone is following a trend.
But it is useful in a specific way: as a trust-building surface that compounds over time, works best when your buyer is also your audience, and generates customers through specific data-forward posts rather than general progress narratives.
The founders who get the most from build in public are the ones who treat it as a long game. They post specific numbers. They build in the community where their buyers already live. They start before they have anything to sell and use the feedback to shape what they build.
If you are at $0-10K MRR right now, start posting. Be specific. Target the right platform for your buyer. And do not expect it to replace outbound or referrals in the next 60 days. It compounds. Let it compound.
Frequently Asked Questions
Does build in public actually get you customers?
Sometimes. Build in public gets customers when your buyers are founders, developers, or makers who already follow indie hacker content. When your buyers are outside that world (dentists, event staffing agencies, families), build in public builds your audience but does not directly drive conversions.
What types of build in public posts get customers versus just likes?
Revenue milestone posts and specific operational numbers get customers. Vague progress updates and motivation posts get likes from other founders. Posts that name the exact problem you solve and show a concrete result attract people who have that problem. Posts that say 'day 47 of building my startup' attract other builders.
How long does build in public take to generate consistent inbound?
Most founders in the DistributionMarket database who credit build in public as a customer channel spent 6 to 24 months building an audience before the inbound became consistent. AudioPen shipped roughly 15 small products publicly over 2-3 years before the product that hit 100 paying customers in 2 days.
Is build in public a validation tool or a distribution channel?
Both, but they work differently. Build in public is a faster validation tool because audience reaction tells you whether people care about the problem. It is a slower distribution channel because converting followers into customers takes time and requires that your customers actually exist in that audience.
Stop Building, Start Selling
Full channel breakdowns, tactics, and revenue data. Free to join.
Validate Before Building
Saas distribution validation before building: test your channel in communities, run fake-door pages, and read signals that prove real demand. Data from 68 apps.
Channels 0-10K MRR
Data from 68 bootstrapped apps shows which channels appear most often at the earliest revenue stage, and which ones are almost never the primary driver.