Back to Blog
revenue sharingmrrbuild in publicghost mode

Build in Public Revenue Sharing: When to Share, When to Stop

Sharing MRR publicly works below $10K/month. Above it, the math inverts. The specific guidance — anchored to Belogubov's Feb 6, 2025 thresholds — for when to share and when to stop.

··6 min read

Build in Public Revenue Sharing: When to Share, When to Stop

TL;DR

  • Sharing MRR publicly is high-value below ~$10K/month and starts inverting above it. Belogubov's Feb 6, 2025 framework is the canonical 2026 guidance.
  • The mechanism: below the threshold, public revenue builds trust and attracts the right audience. Above it, it attracts opportunists, copycats, regulatory attention, and tax / partnership complications.
  • The transition to ghost-mode-on-revenue should be planned, not reactive. Most founders should map the threshold transition into their public commitment.

Sharing revenue publicly is one of the most-debated topics in build-in-public. The 2019 Pieter Levels-era pattern was "always share." The 2026 framework is more nuanced — and the data favors the nuanced version. This cluster sits inside our build in public pillar.

Belogubov's threshold framework

The Feb 6, 2025 tweet (@alexbelogubov) codified the rules:

  • Stop sharing MRR once you cross ~$10K/month.
  • Drop product mention from your bio once you cross ~$30K/month.

These thresholds are heuristics, not absolutes — adapt to your specific business — but they capture the median case.

Why below ~$10K MRR sharing works

Three mechanisms favor sharing at low revenue levels:

  • Trust building. A public $400 MRR + 6 paying users is more credible than a private $400 MRR. Operators evaluate the founder + product based on the trajectory they can see.
  • Audience attraction. The "follow the journey" audience self-selects when revenue is publicly visible. Many of these followers convert to customers later.
  • Conversion data. Sharing publicly produces feedback you would not get from silent operation. Operators DM with questions, suggest features, refer friends.
  • Accountability. Public revenue creates a small but real accountability loop with your audience.

The cost at low levels (some attention, occasional stress) is low relative to the benefit. Math favors sharing.

Why above ~$10K MRR sharing inverts

Three mechanisms produce the inversion:

  • Opportunist attention. Public $50K MRR attracts agencies, "consultants," would-be acquirers, and outright scammers in ways that public $5K MRR does not. The signal scales faster than the customer acquisition benefit.
  • Copycat motivation. Competitors are more motivated to clone a $50K MRR business than a $5K MRR one. Public revenue accelerates the clone-and-undercut dynamic.
  • Regulatory / tax / partnership complications. Public revenue at scale creates secondary effects: tax authorities notice, partnership negotiations anchor on your numbers, investor conversations become harder if your aggressive valuation does not match your shown MRR.

The cost at high levels (specific opportunist / copycat attention, regulatory exposure) is non-trivial. Math inverts.

The transition mechanics

The right approach is planned transition, not reactive ghost mode:

Stage 1: $0 - $10K MRR (public)

  • Monthly MRR posts on X / LinkedIn
  • Specific numbers in monthly retros
  • Product in bio
  • Honest revenue trajectory in launch / retrospective posts

Stage 2: $10K - $30K MRR (selective transparency)

  • Stop specific monthly MRR posts
  • Quarterly aggregate updates only
  • Product stays in bio
  • Replace MRR transparency with cost transparency (per vibe coding marketing)

Stage 3: $30K+ MRR (ghost mode)

  • No revenue specifics
  • Drop product from primary bio (or move to secondary account / brand account)
  • Customer-story content with permission
  • Quarterly or annual retros only, with non-specific framing

The transition is gradual; each stage signal triggers the move to the next.

The honest cost-benefit at each stage

At $1K MRR

  • Benefit of sharing: large (trust, audience, accountability)
  • Cost: minimal (some comparison-trap exposure)
  • Math: share

At $5K MRR

  • Benefit: still large (validates trajectory, attracts followers)
  • Cost: small (occasional opportunist attention)
  • Math: share

At $10K MRR (the inflection)

  • Benefit: declining (audience already validated)
  • Cost: rising (more attention, more comparison)
  • Math: stop the MRR-specific sharing, continue workflow content

At $30K MRR

  • Benefit: minimal (audience does not need the number)
  • Cost: significant (opportunists, copycats, regulatory attention)
  • Math: full ghost mode on revenue

Past $100K MRR

  • Benefit: near-zero (any new audience built here is not buyer audience)
  • Cost: high (acquisition / partnership / regulatory implications)
  • Math: complete ghost mode + brand account only

What does not work

  • Sharing inflated MRR. Caught quickly by operators with access to your billing provider patterns; credibility collapses.
  • Sharing then deleting when bad months happen. Audience notices; trust drops.
  • Stopping sharing too early (pre-$10K). Loses the trust-building benefit before you have captured it.
  • Continuing to share past $30K. Costs exceed benefits in ways that take 12-24 months to become visible.
  • Inconsistent sharing. Sharing strong months and hiding weak ones is dishonest framing that erodes audience trust.

The cost-transparency substitute

When you stop sharing MRR but want to maintain transparency content, cost transparency works:

  • "OpenRouter spend this month: $X. Down from $Y last month after implementing Anthropic prompt caching."
  • "Stack cost: hosting $A, AI $B, domains $C. Total monthly: $D."
  • "Hourly cost to run [feature] for an active user: $E."

The cost-content provides transparency signal without exposing revenue. Operators find it useful; competitors cannot extract dangerous information from it.

Sibling clusters

FAQ

Should I share my MRR if I am pre-revenue or below $1K MRR? Yes for most cases. Even tiny revenue ($200 MRR) is more credible-when-shared than hidden. The exception: products with potential VC-funding plays where small numbers might anchor future valuation negotiations.

What if my MRR fluctuates significantly (B2B with lumpy deals)? Share trailing 3-month average or aggregate, not monthly volatility. Monthly numbers that swing 30% confuse the audience; aggregate trajectory is more honest.

Should I share annual revenue / ARR or monthly MRR? Below ~$10K MRR: monthly is fine. Above: ARR aggregate occasionally if at all. Specific monthly past the threshold creates the inversion problems above.

What if competitors share their MRR and I do not — does that hurt me? Maybe in the short-term (some audience comparison). In the long-term, no — the founders who transitioned to ghost mode generally outperformed the ones who kept sharing at scale. Your competitor's strategy is not necessarily right for you.

Can I share negative trajectory honestly? Yes, with caveats. Sharing "MRR dropped 30% this month because [reason]" can build credibility (honest about real businesses). But: if the negative trajectory is sustained, consider transitioning to less-specific framing to avoid the dashboard becoming a stress driver per build in public burnout.

Building is no longer the bottleneck. Visibility is. buildinpublic.so is narrative infrastructure that runs inside your building workflow — Loudy drafts the cost-transparency content that substitutes for MRR-transparency at later stages, Vibey schedules quarterly aggregate retros that work at both sides of the Belogubov threshold, and Vibe Journal captures the private reflection that does not have to become public to be useful.