Building in Public: What to Share and What to Hold Back

A founder posts “$47,212 MRR, up from $31,800 last month” and gets 400 replies. Another founder posts almost the same numbers a month later and gets crickets. The difference usually isn’t the numbers — it’s whether the founder has been posting the boring, unglamorous middle of the story for the six months before that spike, or whether they showed up once with a big number and no context. Building in public rewards continuity and punishes drive-by transparency. Before you decide what to share, you need a filter for what’s actually worth sharing, because the instinct to post everything or nothing are both wrong.

The Three Questions That Filter Everything

Before any post, run it through three questions. First: does this help someone else make a decision? A churn number without context (“lost 3 customers this month”) helps nobody; a churn number with the diagnosis (“lost 3 customers this month, all three had been on the free trial past 45 days without activating a core feature — we’re moving trial length to 14 days”) teaches something transferable. Second: does this cost you anything if a competitor reads it tomorrow? Some things genuinely do, and pretending otherwise is naive. Third: is this actually true, fully resolved, and something you’re willing to stand behind in six months if someone screenshots it back at you? A lot of founder content fails on this third question — it’s speculative, half-true, or a decision made yesterday that could easily reverse next week.

Anything that passes all three is generally safe and often valuable to share. Anything that fails the second question needs a pacing decision, not a ban — you can usually share it later, once the competitive window has closed. Anything that fails the third question shouldn’t be shared at all until it’s actually settled.

What’s Almost Always Safe to Share

Revenue milestones, once you’ve cleared the point where the number itself would tip off a competitor to your exact playbook, are close to free marketing. “$10K MRR” and “$100K MRR” posts work because they’re legible progress markers everyone understands instantly, and because the actual dollar figure rarely tells a competitor anything actionable about how you got there. Pair the number with one specific lesson from that stretch of growth rather than just the number alone — “$100K MRR, and the thing that actually moved the needle was cutting our onboarding from 9 steps to 3” gives readers something to take with them.

Operational lessons learned the hard way are the highest-value category of building-in-public content, precisely because they’re expensive to learn firsthand and cheap to read about. A founder who posts “we spent $40K on a rebrand that didn’t move a single metric, here’s what we’d do differently” is giving away something genuinely useful, and the vulnerability of admitting a costly mistake reads as more credible than any polished case study. The specificity matters enormously here — “marketing didn’t work” teaches nothing, but “we ran the same ad copy on Google and Meta for six weeks assuming they’d perform the same way, and Meta CPCs were triple what we expected because we hadn’t adjusted for a colder audience” teaches something a reader can immediately apply.

Hiring decisions and the reasoning behind them build trust with future candidates and current team members alike. Explaining why you passed on a candidate with a stronger resume in favor of one with less experience but better founder-market fit, or why you decided to hire a fractional CFO before a full-time one, shows judgment in action rather than just asserting you have good judgment.

Product decisions and the tradeoffs behind them — why you killed a feature that had real usage but pulled the team in a direction misaligned with the roadmap, why you raised prices and what the churn impact actually was — read as confident and specific in a way that vague “we’re always improving” language never does.

What to Hold Back, and Why

Anything that hands a competitor a specific, actionable edge belongs in the hold-back category, at least for now. This isn’t the same as “anything a competitor could theoretically use” — nearly everything qualifies under that standard, which makes it useless as a filter. The better standard: would this specific piece of information meaningfully shorten a competitor’s path to catching up? Your exact CAC by channel, broken down finely enough that a competitor could reverse-engineer your media buying strategy, crosses that line. A rough directional statement like “paid social has gotten more expensive for us this year” doesn’t.

Unresolved team conflict is the category founders get wrong most often, usually in the direction of oversharing too early rather than staying quiet too long. A cofounder dispute, a key hire who isn’t working out, tension about equity or roles — these need to be resolved internally, with the people involved, before they become content. Posting about conflict while it’s still live turns a private negotiation into a public one, which almost never improves the outcome and often poisons it. The version of this story that’s safe to tell is the retrospective one, told after resolution, with enough distance that it reads as a lesson rather than a live grievance. “We almost lost our second engineer over a disagreement about technical direction, here’s how we worked through it” is fine to post eight months later. The same story mid-conflict is not fine to post at all.

Unverified claims are the fastest way to torch credibility you’ve spent months building. A founder who posts “we just crossed $1M ARR” based on annualized run rate from a single unusually good month, then has to quietly walk it back three months later when growth normalizes, has taught the audience to distrust every future number from that account. If you wouldn’t put a number in a board deck or an investor update without a footnote, don’t put it in a public post without one either. This applies just as much to softer claims — “our churn is basically solved” after one good month of retention data is a claim you don’t yet have the evidence to make.

Customer-specific details, even when the intent is a positive case study, need explicit permission before they go out, and “explicit” means asking the actual person, not assuming implied consent because they’re a happy customer. Naming a customer, describing their internal process, or quoting a Slack message they sent you privately, without asking first, is a trust violation that costs far more than the credibility the post would have earned.

Pacing: The Dimension Most Founders Skip

Most guidance on this topic treats it as binary — shareable or not shareable — and misses that timing is often the actual lever. A pricing change is competitively sensitive the week you make it and completely harmless to discuss a quarter later, once competitors have had the same amount of time to notice and react regardless of whether you posted about it. The same is true of a new distribution channel that’s working unusually well — worth protecting for the first few months while the edge is fresh, and worth writing up in detail once it’s become common knowledge in your space anyway.

A useful habit: keep a running list of things you’re not ready to share yet, each with a rough condition for when it becomes shareable (“once we’ve hired the replacement,” “once this quarter closes,” “once two more competitors have obviously caught on”). This does two things. It stops good content from being lost to the moment — six months later, “we’re thinking about doing X” has usually turned into either a genuinely resolved decision or a scrapped idea, both of which make better content than the uncertain middle. And it keeps you from the opposite failure mode, where founders sit on interesting material indefinitely because they can never quite convince themselves the moment is right.

Two Composite Patterns Worth Recognizing

Consider a founder who posted weekly for a year: small wins, real setbacks, specific numbers with context, admitted mistakes without over-apologizing for them, and quietly never mentioned a single customer by name without asking first. By month ten, replies to posts outnumbered the founder’s own outbound outreach for lead generation. The pattern here wasn’t one viral post — it was the compounding effect of specificity and consistency, where each individual post was only moderately interesting but the body of work built a reputation for being a reliable, honest source on a particular kind of problem.

Contrast that with a founder who posted a triumphant “$500K raised!” announcement, then six weeks later posted a defensive, visibly frustrated thread about a cofounder split, naming specific grievances in real time. The raise announcement did fine. The conflict thread got engagement too, but of the wrong kind — screenshots circulating out of context, prospective customers asking sales reps uncomfortable questions, and a next round of fundraising conversations where investors brought up the thread unprompted. The content itself wasn’t the mistake; the timing was. The same story, told a year later after the split had actually resolved and with the sharper edges sanded off, would have been a perfectly reasonable and even valuable post.

A Simple Pre-Publish Checklist

Before hitting publish on anything building-in-public, it helps to run through a short, concrete checklist rather than relying purely on instinct in the moment:

• Is this fully resolved, or still live and unpredictable?
• Would a specific competitor reading this tomorrow gain something actionable, or just something vague?
• Does this involve another person’s private information, words, or business, and if so, did I ask them?
• Am I sharing this because it’s useful to someone else, or because I want the appearance of momentum?
• If this gets screenshotted and shown to a customer, investor, or employee out of context six months from now, am I still comfortable with it?

That last question does the most work. Nearly everything genuinely risky about building in public fails it, and nearly everything genuinely valuable passes it easily. The founders who get the balance right aren’t the ones with some secret formula for what to post — they’re the ones who’ve internalized that question well enough to apply it instinctively, post after post, long after the initial excitement of building an audience has worn off.