Building in Public as a SaaS Founder: What Actually Works and What Creates Noise
Building in public has become its own genre. Monthly revenue updates, launch day threads, failure post-mortems. The format is familiar and the audience for it is real. What is less clear is whether doing it actually builds a business, or just builds an audience of other founders who will never buy your product.
The honest answer is: it depends entirely on what you are building in public and for whom.
The Two Versions of Building in Public
There is a version of building in public that is valuable and a version that is a distraction, and they look almost identical from the outside.
The valuable version is building in public for your actual customer. You share the thinking behind your product decisions, the problems you are solving and why, and your perspective on the domain your product operates in. Your audience is made up of people who have the problem you are solving. When they see you working through it, they self-identify as potential customers. When they see your product in context, the conversion from audience to customer is short.
The noise version is building in public for other founders and startup enthusiasts. You share your MRR updates, your growth charts, your tools list, your productivity setup. Your audience is made up of aspiring founders, students, and people who are interested in the startup world. Almost none of them are your customer. Building a large audience in this way is a form of validation that feels like progress but does not translate to revenue.
The diagnostic question: would my ideal customer find the content I am sharing useful, or would they find it confusing because it is not about their problem?
What Actually Drives Growth from Building in Public
The founders who get real business results from public building share a consistent pattern. They share content that demonstrates domain expertise in the problem space before demonstrating the product. They talk about the problem more than the solution. They publish specific insights, not just personal updates.
A founder building a product for restaurant operators who shares their perspective on the economics of food waste reduction, the incentive structures that prevent operators from fixing it, and the specific workflows that make the problem persist is creating value for their target customer. That content is also the most compelling possible case for why their product exists.
A founder who shares that they hit two thousand MRR this month and are hiring for the first time is sharing content that restaurant operators have no reason to read or care about.
The Channels That Compound Differently
Not all building in public compounds the same way. The channel determines how much the content accumulates value over time.
Twitter and LinkedIn posts have a shelf life of twenty-four to forty-eight hours. They are excellent for reaching warm networks and starting conversations, but they do not compound. The post from three months ago contributes almost nothing to today's visibility.
Written articles indexed on search engines compound indefinitely. A piece explaining a specific problem your customer has will be discoverable via search for years. Each new piece of content builds on the previous one and the total domain authority increases.
Community posts in relevant forums, subreddits, or Slack groups have a medium shelf life. They reach concentrated audiences and drive referral traffic but depend on the community's activity.
The most effective building-in-public strategy for early-stage SaaS combines short-form content for reach and conversation with long-form indexed content for compounding discovery. The short-form drives audience. The long-form drives customers who find you through search when they have a specific problem.
What to Share and What to Keep Back
The builds-in-public-everything approach produces audiences but rarely produces customers. A more selective approach produces better results.
Share: your perspective on the problem space, the reasoning behind specific product decisions, the specific customer insights that have changed how you think, the honest assessment of what is working and what is not in the domain context.
Keep back or delay: specific partnership conversations, competitive intelligence, internal team conflicts, metrics before you understand what they mean.
The principle behind this selection: share what makes a potential customer trust your judgment about their problem. Keep what would make a competitor smarter or a partner negotiation harder.
For the distribution thinking that makes this work strategically rather than tactically, the distribution before features piece covers why discoverability decisions need to happen before product decisions. The GTM strategy article covers how early-stage founders should think about channel selection. The resources page has external reading on content-led growth from founders who have done it.