In this article
- Why most build in public advice stops at engagement
- The mistake: treating build in public as content, not GTM
- A building in public strategy for B2B SaaS founders that produces pipeline
- What to never share, no matter how tempting
- Real examples worth studying
- The first 30 days: how to start this week
- Frequently asked questions
Building in public strategy for B2B SaaS founders works when you treat it as a distribution channel with a conversion goal, not a diary. Most founders get this backwards: they post updates for months, build an audience that likes their content, and never turn a single reader into a customer.
I have watched this happen to founder after founder. The metrics posts get likes. The "day 47 of building" threads get replies. Then the founder checks their pipeline and finds nothing tied back to any of it, because nothing they posted ever asked for anything.
Why most build in public advice stops at engagement
Building in public means sharing your product decisions, metrics, and mistakes as you go, instead of staying quiet until launch. That definition is accurate and also useless, because it tells you nothing about what to post on a Tuesday when you have no big milestone to announce.
Most guides on this topic stop at "share your journey" and a list of ten inspiring Twitter threads. What they skip is the part that matters for a B2B SaaS founder specifically: which of those posts create a lead, and which just create an audience.
Those are not the same asset. An audience that likes your honesty will still bounce off your pricing page. A lead has a specific problem your product solves and a reason to talk to you this week. Build in public content only becomes GTM when it's engineered to produce the second thing, not just the first.
The mistake: treating build in public as content, not GTM
The founders who get nothing from building in public almost always do one of two things wrong.
First, they narrate instead of teach. "Shipped a new dashboard today" is narration. It tells your audience what happened to you. It does not tell a reader with the same problem what to do about it. Teaching content, framed around a specific problem your ICP has, does both: it demonstrates expertise and gives the reader a reason to click through.
Second, they never close the loop. A post about a hard decision you made is interesting. A post about a hard decision you made, with the actual before-and-after numbers, plus a line like "if you're wrestling with the same tradeoff, here's what I'd check first," closes the loop. It converts a passive reader into someone who has a reason to reply, DM you, or click to your site.
The gap between these two approaches is not effort. It's structure. Every post needs one job: either it teaches something specific enough to be useful on its own, or it makes a direct, low-friction ask. Posts that try to do neither are the ones that get likes and produce nothing.
A building in public strategy for B2B SaaS founders that produces pipeline
I've found a simple three-post-a-week rhythm works better than posting daily, because daily posting forces filler content, and filler is what erodes trust the fastest.
One lesson post. A specific, non-obvious thing you learned this week, told with a number attached. "Our trial-to-paid conversion dropped 40% after we added a required onboarding call" beats "onboarding matters" every time. Specificity is what makes a stranger stop scrolling.
One metric or milestone post. Real numbers, not vague progress language. If you're not comfortable sharing revenue, share a rate instead: activation rate, response rate on outbound, time-to-first-value. The number is the hook. The context around it is what builds trust.
One direct ask post. This is the one most founders skip entirely, and it's the one that actually generates pipeline. Not a hard pitch, a direct question: "If you've hit this problem in your own SaaS, I'd genuinely like to hear how you solved it, comment or DM me." This single post type does more for lead generation than the other two combined, because it explicitly invites a reply from someone with your exact problem.
Three posts a week, sustained for two months, will outperform daily posting for six weeks and then burnout. The founders who quit building in public almost never quit because it didn't work. They quit because they tried to sustain a pace that had no room for actually running the company.
What to never share, no matter how tempting
Two categories of information should stay private regardless of how much transparency your audience seems to want: anything a competitor could act on within a week, and anything that would materially change how an active customer or investor conversation goes if they read it before you told them directly.
Specific churn numbers before you understand why customers are leaving is a common mistake. It reads as confession, not insight, and it gives competitors a talking point in their own sales calls. Wait until you have the "why" and the fix, then share both together. That's a lesson post. The raw number alone is just exposure.
Fundraising status is the other one. Founders who post "closing our round" updates in real time create pressure that works against them at the negotiating table. Share the fundraise after it's done, not while it's live.
Arvid Kahl's breakdown of why founders quit building in public puts a finer point on this: the founders who stop usually don't regret being transparent, they regret being transparent about numbers before they had the context to explain them. That's the real filter. Share the story once you understand it, not while you're still inside it.
Real examples worth studying
Nathan Barry built ConvertKit's early audience by sharing revenue numbers and hard decisions publicly for years before it became a common practice, and that consistency is what built trust with an audience of creators who became his first paying customers.
Justin Welsh has credited building in public on LinkedIn with hundreds of direct sales for his digital products, and the mechanism is exactly the ask-post pattern above: he pairs lessons with a specific, low-friction way for a reader to buy or reach out. Buffer took the opposite extreme, publishing a full open revenue dashboard for over a decade, and it became one of their most-referenced trust signals with prospective customers.
Meanwhile, Mercury's own founder research points at the same conclusion from a different angle: building in public pairs best with founder-led, community-driven, and product-led motions specifically, and pairs worse with sales-led, enterprise motions where prospects and competitors read the same feed. If your GTM motion is founder-led B2B SaaS, this channel fits your buyer, not just your ego.
The pattern across every founder who has turned this into a real channel: they picked one platform, posted with a consistent cadence for months, and treated every post as a piece of content with a job, not a personal update. If you've already accepted that your founder story is a distribution channel, building in public is simply that story told in real time instead of after the fact.
The first 30 days: how to start this week
Pick one platform, LinkedIn or X, based on where your actual buyers already spend time, not where you personally prefer to post. Post three times a week using the lesson, metric, ask rotation above. Track one number: replies and DMs that reference something you posted, not likes. That's the only metric that maps to pipeline.
By day 30, you should have at least a handful of direct conversations that started because of a post. If you don't, the content isn't specific enough yet. Go narrower, not louder.
If you want a second channel running in parallel once this one is working, a newsletter is the natural next step: it lets you go deeper with the same audience your public posts are building.
Frequently asked questions
What does building in public mean for a startup?
It means sharing product decisions, metrics, and mistakes openly as you build, instead of staying quiet until launch or a big milestone. For it to work as GTM, each post needs to teach something specific or make a direct ask, not just narrate what happened.
Does building in public actually generate customers?
Yes, but only when posts are structured to convert, not just inform. A weekly rotation of a lesson post, a metrics post, and a direct-ask post consistently produces replies and DMs from people with the same problem your product solves.
How often should founders post when building in public?
Three times a week is a sustainable cadence that beats daily posting. Daily posting tends to produce filler content, which erodes trust faster than infrequent, high-quality posts.
What should founders never share when building in public?
Avoid sharing information a competitor could act on within a week, raw churn numbers before you understand the cause, and live fundraising status. Share the number and the lesson together, after you understand both.
Is building in public better for B2B or consumer startups?
It works well for founder-led, community-driven, and product-led B2B SaaS motions. Sales-led and enterprise motions usually favor more controlled messaging, since prospects and competitors are both watching the same feed.
How long before building in public produces results?
Expect direct conversations and DMs by around 30 days if your content is specific enough. If nothing is happening by then, the posts are too general. Narrow the topic instead of increasing the frequency.
Building in public strategy for B2B SaaS founders isn't a content calendar exercise. It's a pipeline channel with unusually low production cost, and it only pays off when every post is built to earn a reply, not just a like. Start with three posts a week, track replies instead of likes, and give it thirty days before you judge whether it's working. If you'd rather have someone build and run this system alongside your GTM work instead of doing it solo, here's how to start.