The founders who taught a generation to publish their revenue dashboards are now quietly taking them down. Across the indie-hacker world, champions of radical transparency are scrubbing MRR screenshots, removing product links from bios, and adopting an emerging norm — share freely below $10K in monthly revenue, go quiet above it — to escape AI-armed copycats, tax scrutiny, and the mental tax of performing in public (1). The movement is not dying; it is maturing into a discipline about what to share rather than whether to. For East African founders the lesson lands with triple force, because publishing numbers here invites risks Western indie hackers never price: security exposure, kin obligation claims, and revenue authorities that now mine social media for lifestyle-versus-returns gaps (4, 5). The answer is not silence. It is a deliberate disclosure policy: build in public, bank in private.
Key Takeaways
- A documented counter-wave is running through the build-in-public movement: prominent indie hackers are deleting MRR updates and going stealth, converging on a norm of openness below roughly $10K MRR and silence above it, with only milestone posts past $30K (1).
- The drivers are concrete: copycats reliably appear once public revenue proves a market; AI tooling has collapsed cloning time from months to days; and founders report stress “amplified 10x” when their numbers are live for the world to watch (1, 2, 3).
- Transparency still works as marketing — publicly shared projects see roughly 30% higher community engagement, and revenue posts remain the highest-performing content type — which is precisely why the decision has become strategic rather than ideological (2).
- East Africa raises the stakes: Kenya’s revenue authority openly monitors Facebook, Instagram, TikTok, and X to match displayed lifestyles against filed returns, part of an IMF-linked commitment to recover taxes from high-net-worth individuals (4, 5).
- Publishing income in East Africa also amplifies kin-network obligation claims and physical security risk — costs with no Western equivalent in the build-in-public literature.
- The framework in this article — the Three-Drawer Disclosure Policy — sorts every piece of information into the open drawer (lessons, process, customer stories), the locked drawer (revenue, margins, growth mechanics), and the safe (security-sensitive facts), so founders capture transparency’s trust dividend without paying its tail risks.
Why Are the Most Transparent Founders Going Dark?
Build-in-public was one of the great marketing inventions of the indie web: founders narrating their journey in real time — revenue charts included — converted audiences into communities and communities into customers. Buffer published every salary; a generation of solo founders published every MRR milestone. The logic was sound and the data still supports it: projects shared publicly attract measurably more engagement, and nothing outperforms a revenue screenshot for reach (2).
So why are the movement’s own stars deleting their numbers? Four pressures converged.
Copycats got faster and better armed. The pattern observed across the community is consistent: clones appear once public MRR crosses roughly the $10K threshold — the point at which a stranger’s screenshot becomes a market-validation document (1). What changed is the cost of acting on it. A public dashboard plus a public feature list plus modern AI coding tools means a motivated copycat can ship a credible imitation in days, not quarters — the same collapse in build costs I have examined elsewhere in the cheap-code, scarce-judgment shift (3). Most clones fail, but they fail expensively for the original: discount pressure, customer confusion, and the founder’s attention diverted to defense. Radical transparency, in effect, became free market research for competitors who no longer face any build barrier.
The audience stopped being only customers. A public revenue chart is read by customers as social proof, by competitors as a roadmap, by platforms and suppliers as negotiating leverage, and by tax authorities as a filing to reconcile. The build-in-public pioneers wrote for the first audience and discovered, at scale, that the other three were also subscribed.
The numbers became a cage. Founders describe the psychological cost in consistent terms: a revenue dip that would be a quiet operational problem becomes a public event; stress is “amplified 10x” when the dashboard is live (3). Worse, the audience starts shaping the company — founders admit shipping features that look good in a thread rather than features customers asked for, the visibility tail wagging the product dog (3). Against a backdrop where a large majority of entrepreneurs already report mental-health strain, voluntarily installing a public scoreboard is a strange form of self-care (3).
AI scraping removed consent from the equation. Everything published — numbers, playbooks, pricing logic — now feeds training corpora and answer engines that will repeat it, stripped of context and attribution, to anyone who asks, including the next competitor researching the niche. The build-in-public deal was “I share my journey, you give me attention.” The new reality adds a silent third party that ingests the journey wholesale.
The result is not abandonment but stratification: share the journey, retire the dashboard. The emerging etiquette — open below $10K MRR, selective to $30K, milestones-only beyond (1) — is the community converging on something strategists would recognize as obvious in any other domain: disclosure is a decision, not a virtue.
Does Building in Public Still Work If You Hide the Numbers?
Yes — and understanding why rescues the practice from both its evangelists and its undertakers.
Decompose what build-in-public actually sold. The revenue screenshot was never the product; it was the costly signal — proof that the narrator was a real operator and not a guru. Audiences rewarded it because most business content is unfalsifiable. But the trust it generated attached to the narrative around it: the decisions, the failures, the reversals, the specific texture of real operation. That texture is reproducible without the dashboard. A founder who writes “here are the three pricing mistakes I made with institutional buyers, and the email that fixed one” is making a costly, falsifiable, operator-grade disclosure — without handing competitors the income statement.
The engagement data supports the decomposition: public projects outperform private ones by around 30% on community engagement, but the mechanism is the openness of process, not the spreadsheet itself (2). Lessons, customer stories, decision post-mortems, and live problem-solving all carry the signal. What they do not carry is the tail risk.
This matters double in low-trust markets. In East Africa, where institutional verification is thin — no reliable review infrastructure, limited consumer protection, widespread counterfeit and scam fatigue — a founder’s visible, consistent, specific public record functions as a trust prosthetic. It is often the only due diligence a customer, partner, or lender can perform. That is exactly the owned-distribution logic I built out in the founder is the funnel: visibility compounds into the region’s scarcest commercial asset, credibility. East African founders should therefore be more public than their instincts suggest about process — and far less public than the imported playbook suggests about money. The next section is about why.
Why Is the Go-Dark Logic Ten Times Stronger in East Africa?
Three regional realities convert the Western indie hacker’s mild caution into a hard rule.
The taxman is scrolling. The Kenya Revenue Authority openly operates social-media surveillance: dedicated teams reviewing Facebook, Instagram, TikTok, X, and Snapchat for lifestyles inconsistent with filed returns — luxury vehicles, lavish events, travel — as part of a commitment to the IMF to recover taxes from high-net-worth professionals and traders (4, 5). Influencers are explicitly in scope, with digital-service-tax liability attached to platform income (5). The KRA cross-references posts against bank records, import data, vehicle registrations, and utility accounts; consequences range from assessments to travel bans and prosecution (4). Uganda’s URA has signaled the same direction of travel. To be precise about the principle: the issue is not hiding income from legitimate taxation — pay your taxes; integrity is the strategy, and I have argued it is even a competitive one. The issue is that a self-published revenue claim is an audit trigger that bypasses every procedural protection. A boastful MRR screenshot — often rounded up for the algorithm, as founders admit — becomes presumptive evidence against you, and you will spend real money reconciling a number you inflated for engagement.
The kin network is also scrolling. In economies where extended-family obligation functions as the social safety net, public proof of business income reprices every relationship overnight. School-fees requests, funeral contributions, capital “loans” that are transfers — the claims are not malicious; they are the system working as designed, and I have mapped their real magnitude in the kin tax ledger. But the system keys off perceived surplus, and a published revenue chart is the loudest possible perception signal. Western founders going dark protect margins from competitors. East African founders going dark protect working capital from a claims cascade that can decapitalize a small firm faster than any copycat.
The security exposure is physical and digital. Publishing income in markets with thin rule-of-law protection creates target risk that no Silicon Valley thread has ever had to model: extortion, robbery, staff-targeted fraud. And the threat is upgrading — voice cloning and deepfake-enabled impersonation scams are already hitting regional businesses, using exactly the public material founders volunteer: voice, face, org chart, supplier relationships, and revenue scale. The defensive playbook I detailed in deepfake defense for small businesses in East Africa starts with minimizing the raw material; a founder who publishes revenue, key customers, and payment workflows has written the fraudster’s script. Every disclosure should pass a simple adversarial read: what would I do with this if I wanted to impersonate, extort, or defraud this company?
Add the three together and the asymmetry is stark. The upside of publishing numbers in East Africa is the same as anywhere — engagement and credibility. The downside is an audit trigger, a claims cascade, and an attack surface. Same dividend, triple tail risk. The rational policy follows.
What Should Founders Actually Share? The Three-Drawer Disclosure Policy
The framework I give founders is the Three-Drawer Disclosure Policy. Every piece of information about the business lives in one of three drawers, and the sorting is done in advance — in calm blood, as a written policy — never improvised at posting time, when the algorithm’s incentives are whispering.
The Open Drawer: share generously, on a schedule. Lessons and post-mortems; process and systems (how you run follow-up, how you price, how you hire); customer stories told with permission; market education — regulation explained, sectors mapped; opinions and frameworks; failures that are closed (the wound healed, the lesson extracted). This drawer builds the trust dividend, costs competitors nothing actionable, and gives authorities and kin networks nothing to reprice. Rule of thumb: the open drawer holds what you know, never what you hold.
The Locked Drawer: share selectively, deliberately, with named recipients. Revenue, margins, and growth rates — for lenders, investors, and key partners under specific conversations, where the disclosure buys something concrete; customer concentration and unit economics; growth mechanics — the specific channel arithmetic that actually works (publishing it is donating your moat); roadmaps and pending deals. If a locked-drawer item must go public — say, a milestone that anchors a fundraise — publish it once, rounded, dated, and historical, never as a live dashboard. A milestone is a fact; a dashboard is a feed.
The Safe: never public, period. Anything that maps the attack surface: banking and payment workflows, approval chains, who can move money; security arrangements, travel patterns, family details, home and premises information; staff personal data; disputes in progress; and any number that has not been reconciled with what you file. Items in the safe do not get summarized, hinted at, or celebrated obliquely. The safe has no algorithmically acceptable version.
Two operating rules make the policy durable. First, the drawer test precedes the draft: classify before you compose, because a well-written post argues for its own publication. Second, review the drawers annually: items migrate — a closed dispute moves from safe to open as a lesson; a growth channel that stopped working can be published freely as a post-mortem, converting a dead moat into live content.
And beneath the mechanics sits the question that decides whether any of this stays sane: who is the audience for, and who are you when they are watching? The founder who needs the dashboard public to feel real has a deeper problem than disclosure policy, one I have written about in quiet faithfulness versus platform ambition. The strongest reason to keep your numbers private is not the copycat, the auditor, or the cousin. It is that a business measured in public is eventually managed for the public — and the public is not your customer.
Build in public. Bank in private. Teach everything you know, and publish nothing you hold. That is not a retreat from transparency; it is what transparency looks like when it grows up — and for East African founders, it is the difference between visibility as an asset and visibility as an unpriced liability.
Frequently Asked Questions
Is build-in-public dead?
No — it is stratifying. Founders still share process, lessons, and journeys because public projects earn roughly 30% more community engagement. What is disappearing is live revenue disclosure: the emerging norm is openness below about $10K MRR, selective sharing to $30K, and milestone-only posts beyond that (1, 2).
Why are founders deleting their MRR screenshots?
Four reasons: copycats reliably appear once public revenue validates a market, and AI tools let them clone products in days; competitors, platforms, and tax authorities all read the same charts; live numbers amplify founder stress; and scraped content now trains the next competitor’s research assistant (1, 3).
Is it riskier to post revenue numbers in East Africa?
Considerably. Kenya’s revenue authority openly monitors social media to match lifestyles against tax returns, public income proof triggers kin-network obligation claims that can drain working capital, and published financial details feed extortion and impersonation fraud. Same engagement upside as the West, triple the tail risk (4, 5).
What should a founder share publicly, then?
Use the Three-Drawer test. Open drawer: lessons, process, customer stories, market education — what you know. Locked drawer: revenue, margins, growth mechanics — shared only with named recipients for concrete purposes. Safe: payment workflows, security details, family information — never public in any form.
Doesn’t hiding numbers undermine the trust that transparency built?
No, because the trust never attached to the spreadsheet — it attached to specific, falsifiable, operator-grade narrative around it. A detailed post-mortem of a pricing mistake signals authenticity as strongly as a revenue chart, without handing competitors, authorities, or fraudsters actionable intelligence.
Related Reading
- The founder is the funnel: personal brand as distribution
- Deepfake defense for small businesses in East Africa
- Quiet faithfulness versus platform ambition
- The kin tax ledger: family claims on business cash
Sources and Evidence
- Indie Hackers, 2025. “Is this the end of ‘Build in Public’? Here’s why top indie hackers are suddenly disappearing.” https://www.indiehackers.com/post/lifestyle/is-this-the-end-of-build-in-public-heres-why-top-indie-hackers-are-suddenly-disappearing-IhSJQBnXNuNwSuNTuz4t — Primary community documentation of the go-dark wave: founders deleting MRR updates, scrubbing product URLs, the copycat pattern at $10K+ MRR, and the emerging share-then-go-quiet norm.
- Indie Hackers, 2023–2025. “What is building in public, explained simply.” https://www.indiehackers.com/post/what-is-building-in-public-explained-simply-6541c681e0 — Source for the ~30% higher community engagement of publicly shared projects and the continued outperformance of revenue-number posts as a content type.
- Indie Hackers community threads, 2024–2025. “DON’T Build in Public!” and “Why founders burnout.” https://www.indiehackers.com/post/dont-build-in-public-d057543994 — First-person founder accounts of stress “amplified 10x” by live public numbers, audience pressure distorting product decisions, and the mental-health cost of public dashboards; community testimony rather than controlled research, weighted accordingly.
- Business Daily Africa. “KRA eyes rich tax cheats from social media posts.” https://www.businessdailyafrica.com/bd/economy/kra-eyes-rich-tax-cheats-from-social-media-posts-3611428 — Leading Kenyan business newspaper; source for KRA’s social-media surveillance of lifestyle-versus-returns gaps, the IMF-linked recovery commitment, cross-referencing with bank/import/vehicle records, and enforcement consequences.
- The Standard (Kenya). “KRA now goes after social media influencers.” https://www.standardmedia.co.ke/counties/article/2001400603/kra-now-goes-after-social-media-influencers — Source for the explicit targeting of influencers and digital-service-tax liability on platform income; corroborated by Citizen Digital reporting on KRA’s monitoring of Facebook, Instagram, TikTok, and X.
- Citizen Digital, Kenya. “KRA monitoring social media posts to nab tax evaders.” https://www.citizen.digital/article/kra-monitoring-social-media-posts-to-nab-tax-evaders-n286567 — Kenyan broadcaster; corroborating source for the platform list under surveillance and the lifestyle-audit methodology.