Building in Public as a Growth Tactic
Building in public is not the same thing as having a founder brand. A founder brand is about you as a person. Building in public is a specific tactic inside that: publishing your real metrics, revenue, and decisions as they happen, in public, on a schedule.
That distinction matters because the tactic has its own rules, its own payoff, and its own very real risks.
Quick Summary
- Building in public means sharing specific, verifiable numbers (MRR, users, churn) and decisions, not just opinions or life updates
- Pieter Levels built a $3.1M ARR portfolio and 600K followers partly by tweeting his revenue and code in public for over a decade (Starter Story, 2025)
- Founder posts with visible vulnerability, failures, pivots, real numbers, get 2 to 3x more engagement than polished announcement posts (SeedScope, 2025)
- By 2026, the daily "MRR screenshot" ritual is in visible decline as audiences tuned out and founders felt the stress outweighed the payoff (Build in Public 2026 Guide)
- The tactic works best as a cadence, not a mood, weekly or monthly updates on a fixed schedule beat sporadic bursts of transparency
What It Actually Is
Building in public is the practice of sharing your company's real, checkable numbers and real, in-progress decisions with an audience before the story is finished.
Think of the difference this way: a founder brand is a magazine profile written about you. Building in public is a live scoreboard you post updates to every week, wins, misses, and all.
The tactic only works because the numbers are real. A vague "great momentum this month!" post gets scrolled past. A screenshot showing MRR went from $4,200 to $3,850 because you lost your biggest customer gets replies, because it is specific and it is true.
What to Actually Share
Not everything belongs in public. The useful build-in-public update sticks to a short, repeatable list.
- Revenue and growth numbers: MRR, ARR, user counts, week-over-week percentage change
- Product decisions in progress: what you are building next and why, before it ships
- Real mistakes: a feature that flopped, a hire that did not work out, a pricing change you reversed
- Roadmap tradeoffs: what you chose not to build and the reasoning behind it
- Milestones and misses: hitting a number is a post; missing a target you announced earlier is also a post
The mistakes and misses matter as much as the wins. A feed of only good news reads like marketing copy, and readers can tell the difference within a few posts.
What to Keep Private
Transparency is a choice, not an obligation to publish everything. Some categories should almost never go public, no matter how tempting the engagement.
- Anything that hands a competitor a working playbook: exact ad spend by channel, the specific integration or growth trick your edge depends on, if it could be cloned in a weekend from your tweet
- Individual customer or employee details: names, salaries, or specifics that identify a real person without consent
- Numbers you have not verified: a projected number posted as if it were actual creates a credibility problem later
- Anything under active negotiation: funding terms, an acquisition conversation, a partnership before signatures
The rule of thumb from founders who have been burned: if a competitor reading this post tomorrow would know exactly what to copy, do not post it yet (The Bootstrapped Founder, 2025).
Why It Works: The Trust and Attention Payoff
Specificity is what makes the loop spin. A round number like "growing fast" is forgettable. A precise number like "$38K this month, up 9% from last" is the kind of detail people screenshot and share, because it reads as evidence, not marketing.
Non-technical founders who build in public on LinkedIn and X see roughly 2.4x higher engagement on business-narrative posts than on feature-announcement posts, and posts showing real vulnerability, failed experiments, reversed decisions, get 2 to 3x more engagement than branded content (SeedScope, 2025). Founders who build in public around a launch report 3 to 5x more early adopters than founders who launch traditionally (PeerPush, 2025).
The compounding is slow but durable. Most build-in-public success stories run 5 to 10 years, not months, and momentum built over 12 to 18 months of consistent updates keeps generating inbound attention long after the posting pace slows down.
The Real Risks
The tactic has gotten riskier since its early-2010s heyday, and pretending otherwise sets founders up to get burned.
Competitor visibility. Once a product has real traction, the same openness that built early trust can hand a fast follower your exact playbook, the channel that is working, the pricing test that lifted conversion, the integration nobody else had thought of yet (The Bootstrapped Founder, 2025).
Pressure to perform on a schedule. Publishing a number every week means every bad week is also public. That pressure is real, and it has pushed some founders to quietly stop.
Oversharing fatigue. The daily MRR screenshot, once a genre unto itself, is now in visible decline. Audiences tuned out, engagement dropped, and the dopamine hit of posting a dashboard collapsed for both the poster and the reader (Build in Public 2026 Guide).
Confusing volume for connection. Posting daily numbers with no story around them reads as noise. A monthly update with context beats seven shallow daily screenshots.
Knowing the risks does not mean avoiding the tactic. It means choosing a cadence deliberately instead of drifting into either silence or oversharing.
A Cadence Framework That Holds Up
Pick one of these rhythms and stay with it for at least two quarters before judging results.
| Cadence | What to post | Best for |
|---|---|---|
| Weekly | One decision or one small number update, short and specific | Early-stage, pre-revenue, building an audience from zero |
| Monthly | Full metrics recap: MRR, users, churn, one win, one miss | Post-revenue, steady growth, avoiding daily-number fatigue |
| Milestone-based | Only when a real threshold is hit or missed ($10K MRR, 1,000 users, a target you publicly missed) | Later-stage, smaller audience appetite for constant updates, higher signal-to-noise per post |
Most solo founders and small teams do best with monthly recaps. It is frequent enough to keep an audience engaged, infrequent enough that each post has something real to say.
Real Examples
Pieter Levels, Nomad List and Photo AI (2014-2025): Levels has tweeted his revenue, code, and product decisions in public for over a decade, with zero outside funding. By 2025 his portfolio reached $3.1M in total ARR across products, with Photo AI alone generating $138K in a single month, and Nomad List compounding to roughly $38K monthly after 11 years of public building. His audience of 600K followers did not form around a single viral moment, it accumulated one honest update at a time (Starter Story, 2025).
Indie SaaS earners, public revenue as proof (2025-2026): A cluster of solo-built tools, Tally (around $150K MRR), Typefully (around $113K MRR), Rezi (around $200K MRR), Pallyy (around $85K MRR), and Submagic (around $83K MRR), publish revenue numbers openly as part of their marketing. Each public number functions as proof the product works, doing the job a testimonial or case study would normally do, at zero production cost (Build in Public 2026 Guide).
The stealth counterexample: Not every high-growth company builds in public. Stripe, now valued near $70 billion, grew its payments infrastructure with minimal public fanfare in its early years, proving the tactic is a choice tied to audience and category, not a requirement for growth.
Common Mistakes
1. Posting only good news. A feed of exclusively positive updates reads as marketing, and readers disengage within a few posts once they notice the pattern.
2. Sharing your actual moat. The specific growth channel or integration that is currently working is the one detail that should stay private until the advantage has run its course.
3. Switching cadence constantly. Daily one week, silent for a month, then a burst of five posts, breaks the trust that a predictable schedule builds.
4. Treating it as a substitute for a real audience-building plan. A number posted into a feed with 40 followers does not compound. Building in public works because it stacks on top of an existing distribution effort, not instead of one.
5. Never revisiting a missed target in public. Announcing a goal and going silent when you miss it erodes exactly the trust the tactic is supposed to build. Post the miss, explain it, move on.
Key Takeaways
- Building in public is a specific tactic, sharing real, checkable numbers and decisions, distinct from general personal branding or thought leadership
- Share revenue, growth numbers, product decisions, and real mistakes; keep exact growth channels, unverified projections, and anything under negotiation private
- Posts with real vulnerability get 2 to 3x more engagement than polished announcements, but the daily MRR-screenshot format has fallen out of favor by 2026
- Pick one cadence, weekly, monthly, or milestone-based, and hold it for at least two quarters before judging whether it is working
- The biggest risk is not embarrassment, it is handing a fast-follower competitor your exact playbook before you have built a durable lead