Build in Public: What Actually Counts as Proof

"Build in public" has quietly become a genre of theater. Screenshots of dashboards with the numbers cropped just right. Revenue milestones posted without context on whether that revenue is recurring, one-time, or a single friend's credit card. "Crossed $10K MRR" threads that don't say what MRR means to that particular founder, because the ambiguity is doing work the actual number can't. None of this is exactly lying. Most of it isn't even dishonest on purpose. It's just that "proof" and "a number that looks good in a tweet" have started to mean the same thing, and they aren't the same thing at all.

Here's a more useful way to think about what actually counts.

The question that separates real proof from vibes

Before posting a number, ask one thing: if a stranger asked "how do you know that's true," what's the honest answer? Not "trust me." Not "I checked my dashboard." An actual, specific answer - a payment processor confirming a charge, a user independently verifying they did the thing, a signed agreement with terms attached. If the honest answer is "because I said so," that's not disqualifying - self-reported numbers are still a real category of information - but it's a different category than something independently confirmed, and collapsing the two into one undifferentiated "proof" is where build-in-public content quietly stops being trustworthy.

Three tiers, and why keeping them separate matters

Most metrics people post in public fall into one of three buckets, whether or not anyone bothers to say which:

Self-reported. Your own account of what happened. "We have 40 active users" with no further detail. This is worth posting - it's honest, as far as it goes - but it should be labeled as what it is, not dressed up to look more solid than it is.

Independently confirmed. Something with a paper trail outside your own control. A Stripe receipt. A signed pilot agreement. Numbers here carry more weight precisely because they don't depend on the founder's own reporting being accurate or generous.

Confirmed by the people involved. Not you saying it happened - the actual users saying it happened, in their own words, even when the honest answer is "no, that's not quite right." This is the rarest tier, and also the one that actually earns trust, because it's the hardest to fake and the only one where an unflattering answer is still visible.

The tier matters more than the number. "12 VERIFIED users" is a stronger claim than "500 users," full stop, if the second number has no tier attached at all. Most build-in-public content never makes this distinction, which is exactly why so much of it stops working the moment a reader gets skeptical - there's nothing underneath the number to check. (Why upvotes count for less than activations.)

Labeling your own numbers, even informally

You don't need a formal system to start doing this better. The simplest version: whenever you post a metric, add one honest clause about where it came from. "40 signups (self-reported, from our own dashboard)" instead of just "40 signups." "12 paying customers, Stripe-confirmed" instead of just "12 customers." It costs you a few words and a little bit of the shine. It buys you something that actually compounds: the next number you post gets believed by default, because the last one was honest about its own limits.

This is the exact discipline launchduels builds into its structure rather than leaving to individual honesty - every number on the board carries a tag (ATTESTED, VERIFIED, or AUDITED) showing exactly how it's known (R-22), because a proof record that can't say how it knows isn't proof. You don't need a board to adopt the habit. You just need to stop letting "a number that sounds good" stand in for "a number someone could check." (The full tier breakdown.)

What this actually buys you

Founders who label their numbers honestly, including the unflattering self-reported ones, get believed faster over time than founders who post only the numbers that look clean. It's counterintuitive until you notice why: an audience that's been burned by unlabeled vanity metrics before starts discounting every number by default, confirmed or not. A founder who visibly separates "this is what I'm claiming" from "this is what's actually verified" gives readers a reason to stop discounting - not because the numbers are always bigger, but because they can finally tell which ones to trust.

Build in public if you want to. Just be honest, even to yourself, about which parts are proof and which parts are a number that happened to be true.

The indie board's proof database is this discipline made public - every number, its tier, append-only. The open chairs →