Back to Blog
build in publicpre-revenueghost mode

Build in Public Without Sharing MRR: The Pre-Revenue and Ghost-Mode Playbook

Most build-in-public content assumes you have revenue to share. Pre-revenue founders and ghost-mode founders need different content. The workflow-content playbook that compounds without numbers.

··5 min read

Build in Public Without Sharing MRR: The Pre-Revenue and Ghost-Mode Playbook

TL;DR

  • Most build-in-public content assumes you have MRR to share. Pre-revenue founders and ghost-mode founders need different content — both use the same playbook: workflow-in-public.
  • Workflow content (commits, prompts, decisions, customer stories) compounds without requiring revenue numbers. Often more durable than MRR theater.
  • The Belogubov thresholds apply on both ends: do not share MRR pre-revenue (because you have none); stop sharing above ~$10K/month (because the marginal cost exceeds the benefit).

A common misconception: build-in-public requires public MRR. It does not. Many of the most-followed indie hacker accounts in 2026 do not share MRR at all — either because they are pre-revenue or because they have transitioned to ghost mode. This cluster sits inside our build in public pillar.

Two cases for not sharing MRR

Case 1 — Pre-revenue. You shipped a product yesterday. You have zero paying users. There is no MRR to share. Posting MRR is not an option.

Case 2 — Post-threshold (Belogubov). You crossed ~$10K MRR. Per Belogubov's Feb 6, 2025 framework, the marginal cost of public revenue (opportunists, copycats) now exceeds the marginal benefit (customer acquisition). Sharing should stop.

Both cases run the same playbook: workflow-in-public without numbers.

What replaces MRR posts

Five content categories that compound without revenue numbers:

1. Ship posts (daily). Every meaningful commit becomes a post. The content engine runs on git activity, not on revenue.

2. Workflow content (weekly). Prompts, .cursorrules, Claude Code session transcripts, design decisions, architecture notes. Durable content that produces SEO + trust.

3. Customer-story posts (when applicable). "A consulting firm using [our tool] cut their action-item review from 30 minutes to 2." Specific stories, anonymized when needed. Higher signal than MRR numbers.

4. Operational stories. "Migrated off [tool A] to [tool B] at user 200. Here's what we learned." Builder content that compounds.

5. Honest cost transparency (the 2026 substitute for MRR transparency). "$X in OpenRouter spend this month. $Y in hosting. Total stack cost: $Z." The honest-economics content that produces trust without revenue exposure.

Combined, these produce the same audience compounding as MRR posts — often higher quality.

The pre-revenue playbook specifically

For founders who shipped recently and have no paying users yet:

Weeks 1-4 post-launch:

Weeks 5-12:

  • First customer stories (when you have customers)
  • Honest learnings from the first 10 users (when you have 10)
  • Pattern observations from sales conversations

The discipline: do not invent revenue or signal numbers you do not have. Operators detect inflation. The honest framing ("30 days post-launch: 4 paying users, $200 MRR, here's what I'm doing") outperforms inflated framing.

The ghost-mode playbook specifically

For founders who crossed Belogubov's thresholds and stopped sharing MRR:

  • Daily ship content continues
  • Weekly demos continue
  • Quarterly retros replace monthly (lower cadence, deeper content)
  • Customer stories with permission
  • Workflow content (prompts, decisions, systems) continues unchanged
  • No specific MRR numbers in any post

The audience built during the public-MRR phase persists. The compounding continues. The stress cost (per when to go ghost mode founder) drops.

The honest workflow-content advantage

Workflow content has properties MRR content does not:

  • Harder to fake. Anyone can fake an MRR screenshot; almost nobody can fake a real Claude Code session transcript or a meaningful commit log.
  • More teachable. MRR numbers are an outcome; workflow content is process that other founders can adopt.
  • Compounds in SEO. Long-form workflow posts index well; MRR screenshots do not.
  • Survives platform changes. A post about your .cursorrules works on X, LinkedIn, dev.to, your blog. An MRR screenshot only works on X.

These advantages make the workflow-content playbook often better than the MRR-content playbook, not just a substitute for it.

What does not work without MRR

  • Pretending to have revenue you do not have. Operators detect; credibility collapses.
  • Inflating signal numbers (signups, impressions, follower counts) to substitute. Different problem, same credibility issue.
  • Reverting to generic motivational content because you have no specific data to share. Fills the void with worse signal.
  • Disappearing entirely when you cannot share MRR. The audience needs content to stay engaged; workflow content fills the gap.

Sibling clusters

FAQ

Will people stop following me if I do not share MRR? Some yes, mostly no. The audience that follows specifically for MRR-screenshot content drops off; the audience that follows for workflow content stays and grows. Net effect: more durable audience, lower stress cost.

Should I share MRR ever, then transition to ghost mode? Common pattern. Below ~$10K MRR, sharing builds trust. Above the threshold, transition. The transition is normal, not a failure.

What if I genuinely want to share revenue and it does not affect my business negatively? Then share it, with caveats. Be aware that public MRR creates opportunist / copycat attention even when it does not affect your business — it can attract attention to your category that brings additional competitors. The cost is sometimes invisible.

Is workflow content enough to drive trial signups without MRR transparency? Yes, empirically. Workflow content produces conversion through different mechanism (operator trust + technical credibility) than MRR content (social proof). Both work; the workflow path is more sustainable.

How do I know if I am ready to ghost-mode on MRR? Belogubov's thresholds (~$10K to stop sharing, ~$30K to drop from bio) are the heuristic. Additional signals: posting MRR makes you anxious, you are attracting opportunists, the marginal customer-acquisition value is dropping per dollar of MRR shared. Any of these is a signal to consider the transition.

Building is no longer the bottleneck. Visibility is. buildinpublic.so is narrative infrastructure that runs inside your building workflow — built for the workflow-in-public version: Dev Cards produces ship content from commits without requiring revenue context, Loudy drafts customer stories and workflow content in your voice, and Vibe Journal captures the daily reflection that fuels monthly retros without MRR theater.