The '$0 to $62K MRR in 90 Days' Screenshots Are Lottery Tickets. Here's the Build-in-Public Timeline Nobody Posts.
Scroll your timeline for ten minutes and you'll see it: someone went from zero to a five-figure monthly revenue in a single quarter, posted the Stripe screenshot, and the replies are full of people asking for the playbook. The chart goes up and to the right so cleanly it looks like a physical law. It isn't. It's a lottery ticket someone cashed, posted because cashing it is the only outcome anyone screenshots.
The number that should actually shape your plan is duller and almost never trends: the median bootstrapper takes somewhere around a year to eighteen months to reach $10K MRR from their first paying customer. If you build your runway around the 90-day story, you'll run out of money and nerve about three months before the part of the curve where compounding starts to do its job.
Survivorship bias, mechanically
You hear from the winners because winning is the thing that gets posted. Nobody screenshots month fourteen of flat revenue. Nobody makes a thread out of "still grinding, still under $1K MRR, here's what I learned in the eleventh month of nothing happening." So the entire visible surface of indie hacking is selected for the outliers, and you end up calibrating your expectations on the tail of the distribution while believing you're looking at the middle.
The "$0 to $62K in 90 days" founder is real. He's also one data point at the far end of a curve whose median you never see, because the median is boring and boring doesn't get engagement. Treating his timeline as the expected case is like deciding to plan your retirement around a Powerball winner's press conference. The win is real. The base rate is not what the press conference implies.
What the numbers actually look like
The figures floating around the community (from places like Indie Hackers and MicroConf survey commentary) put the median path to $10K MRR somewhere in the twelve-to-eighteen-month range from first paying customer. Treat the exact months as soft; the surveys are self-reported and the sample skews toward people who stuck around to answer. But the shape is the honest part: it takes a lot longer than the highlight reel, and most of the time is spent below the line where anything feels like it's working.
The viral stories aren't lies. They're the right tail. The founder who hit day-one revenue after four months of building in public to a couple thousand followers did real work to get there. He just compressed it into a sentence that makes it sound like the four months were the easy part and the launch was the achievement. It's the other way around.
What build-in-public actually buys you
Here's where I'll defend the practice, because the survivorship critique can tip into "so don't bother," and that's the wrong lesson. Building in public works. It just doesn't work the way the screenshots imply.
What you're building when you post consistently isn't instant revenue. It's a distribution asset: an audience that knows what you're working on and will be there when you ship. That asset compounds on a months-long delay. The founder who launched to revenue on day one didn't get lucky on launch day. He spent months making launch day possible, building the audience that turned a launch into a number. The distribution was the work. The launch was the receipt.
So the practice is right and the timeline in your head is wrong. You're not posting to go viral this week. You're posting to have an audience in month twelve, when the product is finally good enough that having an audience matters.
What I'd actually do
Plan for the median, not the tail. If the realistic path to meaningful revenue is twelve to eighteen months, then your runway has to survive twelve to eighteen months of mostly-flat numbers, and the day-one-MRR fantasy is the exact story that talks you out of building that runway, because it whispers that you'll be profitable by spring.
Concretely: budget for the long version. Keep your burn low enough that month eleven of nothing isn't an emergency. Measure leading indicators instead of revenue while revenue is flat (audience growth, conversations, signups, the things that move before money does) so you can tell the difference between "this is the slow middle" and "this genuinely isn't working." And calibrate your emotional expectations off the base rate, not the timeline, so a quiet quarter reads as on-schedule rather than as failure.
The honest counter-take: some products genuinely do hit fast, and a founder with real distribution, a sharp wedge, and good timing can compress the curve in a way that makes the cautious version look like under-ambition. If you've already got an audience and you're shipping into a hot category, planning for eighteen months of flatness might be the thing that makes you too conservative to swing hard. Fair. But that's a bet you make from a position of strength you can name, not a plan you adopt because someone's Stripe screenshot made the fast version feel like the default. The screenshots are real. They're just not the distribution, and your runway has to survive the distribution, not the tail.
Author
Lukas
@lukcombinator