What $2,000 MRR Actually Feels Like

Frictionwell crossed $2,000 in monthly recurring revenue in April, eleven months after I started charging for it, and I want to write down exactly what that number felt like, because the version of this milestone I'd absorbed from other people's build-in-public threads was almost entirely wrong. It did not feel like validation. It did not feel like the business had "worked." It felt, mostly, like a slightly less anxious version of the exact same uncertainty I'd had at $200.

The number, honestly

$2,000 MRR, at Frictionwell's pricing of six dollars a month, is a little over 330 paying subscribers, out of roughly 4,800 total registered users — a conversion rate a bit under seven percent, which is respectable for this category but not remarkable. Churn runs around four percent a month, which means I'm losing something close to thirteen paying subscribers every month and need to replace them just to stand still, before any of the growth I'd like to see. After payment processing fees, my App Store cut on the iOS subscriptions, and the modest infrastructure cost of running the backend, the actual cash landing in my account each month is closer to $1,550.

That number, run against my actual monthly expenses — which include, notably, nothing resembling a market-rate salary for the hours I put into this — covers a meaningful chunk of what I'd need to live on if this were my only income, but not all of it, and not comfortably. I still do freelance consulting work roughly one week a month specifically to cover the gap. $2,000 MRR is real money and a real signal that people are willing to pay for what I built. It is not, on its own, a living.

What the curve doesn't show

The chart above is the version of this story that's satisfying to look at — up and to the right, more or less, with a nice acceleration at the end. What it can't show is how flat and uncertain most of those eleven months actually felt while I was living through them. Months three through six sit almost dead flat on that curve, and I remember that period as the hardest stretch of the entire build, not because anything was going obviously wrong, but because nothing was going obviously anywhere. New subscribers roughly matched churned subscribers most weeks. I had no reliable way to tell, from inside that plateau, whether I was one good feature away from a breakout or slowly building something that had already found its ceiling.

"The flat months don't feel like a plateau while you're in them. They feel like evidence you've built the wrong thing, and the only way to find out you're wrong about that is to keep going long enough for the curve to tell you."

The pricing change in month six — moving from a flat five-dollar price to a slightly more considered six-dollar price with an annual option — caused a visible short-term dip, a handful of existing subscribers churning out rather than accepting the increase, before the curve resumed climbing on the back of better unit economics. I'd read enough advice beforehand to expect that dip and not panic about it, which is one of the few pieces of received indie-hacker wisdom that held up exactly as advertised.

What actually moved the needle

The steeper climb in the final quarter, the part of the chart that actually looks like the "hockey stick" people picture when they imagine crossing a revenue milestone, traces almost entirely to retention work rather than acquisition work — the kind of unglamorous fixes described elsewhere on this desk, tightening the streak mechanic, adding the graduated soft-reset allowance, cutting a feature that was quietly hurting the numbers it looked like it was helping. New user acquisition, over the same eleven months, grew only modestly and mostly through word of mouth and a small amount of organic App Store search traffic I never paid to accelerate. The lesson I keep re-learning, and keep having to relearn because it's counterintuitive every single time, is that at this scale, fixing the leaky bucket is a better use of a month than trying to pour more water in through the top.

What $2,000 MRR doesn't fix

I want to be honest about the part of this milestone that disappointed me, because I think the disappointment is more useful to another builder than the celebration would be. I'd assumed, somewhere in the back of my mind, that crossing a real, meaningful revenue number would resolve a specific anxiety I'd been carrying since I quit consulting full-time to build this — the anxiety of not knowing whether the business was real. It didn't resolve that anxiety. It just changed its shape slightly, from "is anyone going to pay for this" to "will enough people keep paying for this, forever, for this to actually work as a way to make a living." The second anxiety is, if anything, harder to sit with than the first, because the first has a clean yes-or-no answer and the second doesn't resolve on any single day — it just keeps needing to be re-answered, month after month, by a churn number that never fully stops being able to surprise you.

"I thought $2,000 MRR would feel like an answer. It felt like a slightly quieter version of the same question I'd been asking since month one."

The week I actually told my partner the real number

There's a smaller, more personal thread to this milestone that I almost left out of the essay because it felt too far from the numbers, and then decided belonged here precisely because it doesn't show up on any chart. For most of the eleven months, when my partner asked how the business was doing, I gave some version of "it's growing, slowly" — true, but carefully vague, because the precise number felt too small to say out loud next to what I used to earn consulting full time. The week Frictionwell crossed $2,000 MRR was the first time I actually opened the dashboard, turned the laptop around, and showed her the real figures — subscriber count, churn, the after-fees cash number, all of it.

Her reaction surprised me. She wasn't impressed by the milestone in the way I'd braced for needing her to be. She was relieved, specifically, that I'd finally shown her a real number instead of a mood, because the vague reassurances had been quietly worse for her peace of mind than an honest, unglamorous figure would have been all along — she'd been filling the gap in what I wasn't saying with worse guesses than the truth actually warranted. That conversation did more for how sustainable this whole project feels than the revenue itself did, and it's the clearest personal example I have of the same principle that runs through the business side of this essay: a real number, even a modest one, is almost always more useful to the person receiving it than a comfortable vague description standing in for it.

"I'd been protecting her from a number that turned out to be less scary than the vagueness I'd been substituting for it. The real figure was a relief. The mood I'd been managing instead of the number was the actual source of the anxiety."

If I could send one piece of information back to the version of me who'd just gotten the first handful of paying subscribers, it wouldn't be a growth tactic. It would be a reframe of the timeline itself: the eleven months between the first dollar and the two-thousandth were not, in any meaningful sense, wasted time spent failing to grow fast enough. They were the actual work — the plateaus, the pricing experiment, the dozen small retention fixes — compounding in a way that was genuinely invisible from inside any single month of it. I spent a lot of that period comparing my curve, quietly and unfavourably, against build-in-public threads showing steeper trajectories, almost none of which, I'd guess now, were being honest about their own flat months in the same post.

The number I'd want that earlier version of me to have, more than any tactic, is simply permission to trust that a flat month is data, not a verdict — and that the only way to find out which one it actually was is to keep going long enough for the next chart to tell you, which is a much less satisfying answer than a growth hack, and the only one I've found that's actually held up across eleven real months of building this thing.

Why I'm writing this number down at all

The honest reason I'm publishing the exact figures here, rather than a vaguer "we crossed a meaningful milestone" post, is that the vague version is what almost everyone else publishes, and the vague version taught me nothing useful when I was reading other people's build logs at $200 MRR trying to figure out whether what I was building had a shot. A concrete number — conversion rate, churn, the actual cash after fees, the freelance work still propping up the gap — is a number another builder can actually compare their own situation against. A milestone announcement with no numbers in it is, functionally, just a mood, and moods don't help anyone build the next thing. Building small enough that I can afford to publish the real number, unflattering plateaus and all, is most of the point of writing on this desk in the first place.

I'll keep publishing this figure as it moves, in both directions, including whatever version of it exists if churn ever wins a month outright and the line on the chart actually falls. That's the deal I've made with myself for writing here at all: the number goes up on the page whether or not it's flattering, because the flattering-only version of this genre has already produced enough noise, and the honest version, plateaus and small dips included, is the only one that was ever going to be useful to someone reading it at $200 MRR, wondering whether the thing they're building has a real shot or not, or whether the flat month they're staring at right now is a verdict instead of just data they haven't finished collecting yet.