The month my big launch flopped at $13K MRR

Quick answer (2026): A launch flop is what happens when you pour months into a big release, ship it to Product Hunt and your list, and watch your revenue barely move. It is more common than the highlight reels suggest. In one 2024 survey of founders who launched on Product Hunt, 16% reported no registration spike at all, and only about a third saw a significant one. The uncomfortable lesson from my own flop at $13K MRR was that the growth I already had came from unglamorous retention work, not launch days. Acquisition spikes fade in a week. The customers you keep compound for years.

I want to tell you about the month my big launch flopped, because the launch itself is the least interesting part of the story. What happened in the four weeks after is the part I still think about.

The setup: boring, profitable, and quietly growing

My product is a scheduling and billing tool for independent instructors. Music teachers, driving instructors, personal trainers. People who run a real business out of a calendar and a bank account and do not want to think about software.

By early this year I was at $13,000 MRR. Around 430 paying customers, most on a $29 plan, a handful on a $79 team plan. I had built it alone over two and a half years. It was profitable. It covered my rent, my health insurance, and left something over.

It was also, if I am honest, boring me.

The month-to-month growth was real but slow. A few hundred dollars of net new MRR most months. It came from nothing dramatic. A better onboarding email. Fixing the thing that made people rage-quit during setup. Answering support fast enough that people upgraded instead of leaving. None of it felt like progress while it was happening. It felt like janitorial work.

So I did what a lot of founders do when the boring numbers stop being exciting. I decided to swing big.

The build: three months heads-down

The plan was a version 2. A redesigned calendar, a proper mobile experience, and a genuinely new feature: group classes, so a yoga instructor could sell one session to eight people instead of eight separate bookings. I convinced myself it would unlock a whole new customer segment.

I gave it three months. And for three months I did almost nothing else.

Here is the part I did not admit to myself at the time. During those three months I stopped doing the janitorial work. Support replies that used to take two hours took two days. The onboarding email that I kept meaning to improve stayed broken. A billing bug that annoyed maybe a dozen customers sat in my backlog because it was not part of the launch.

I was tired in the specific way that only a self-imposed deadline can make you. If you have felt that particular grind, I wrote about where it led me in a separate diary about burnout at $15K MRR. The launch build was where mine started.

Launch day: the graph that barely moved

I did it properly. Or I thought I did.

I lined up a hunter. I wrote the Product Hunt post, made a demo video, prepared the gallery images. I emailed my whole list. I posted in three communities where my customers actually hang out. I took the day off from my day, which as a solo founder means I did nothing but refresh dashboards.

Here is what happened.

• Product Hunt: a respectable but not top-of-day placement. A few hundred visitors.
• Signups that day: 41 free trials.
• New paying customers from the launch, tracked over the following two weeks: 6.
• Net new MRR directly attributable to the launch: roughly $190.

Three months of work. One hundred and ninety dollars a month.

I kept the analytics tab open for a week, waiting for the delayed wave everyone promises. It did not come.

I am not special in this. When I later went looking for data, that 2024 Product Hunt survey put a number on my feeling: most launches produce a modest bump or none at all, and the ones that go viral are the exception people write threads about. A launch is a spike. Spikes are not a business.

The group-class feature, the thing I bet the quarter on? A handful of existing customers tried it. Almost nobody in the imagined new segment showed up, because I had built the feature before I had found a single person in that segment who wanted it.

The month after: the bill for what I ignored

The flat launch did not hurt. What hurt came two weeks later.

My churn that month was the worst it had been in a year. Not catastrophic, but clearly up. When I actually read the cancellation notes instead of skimming them, the pattern was obvious. These were not people rejecting version 2. These were people I had ignored for three months. The slow support. The billing bug I deprioritized. The onboarding that was still broken for new trials that whole quarter.

I had spent three months chasing customers who did not exist yet and neglecting the ones paying my rent.

There is a statistic I now keep taped to the wall. Acquiring a new customer costs five to twenty-five times more than retaining an existing one, and lifting retention by just 5% can raise profit anywhere from 25% to 95% (Yotpo, 2025, citing Bain). I had run my quarter as if the exact opposite were true. I had treated the expensive, low-odds motion as the main event and the cheap, high-odds one as a chore.

If you want to see how fast quiet churn can eat a growing MRR number, I traced one of those months in painful detail in a retention diary about the month my churn quietly doubled. Same lesson, different year.

What actually grew my revenue

Here is the twist that took me embarrassingly long to see.

I went back and looked at where my growth from $9K to $13K MRR had actually come from. It was not a single launch. It was the janitorial work. The onboarding fix alone had lifted trial-to-paid by a few points. Faster support had visibly slowed churn. A tiny price change on the team plan had added revenue with zero new customers.

The unglamorous work was the growth engine. The launch was ego wearing the costume of strategy.

Once I accepted that, the fix was almost boring. I spent the following month doing nothing but fixing what I had let rot. Cleared the support backlog. Shipped the billing fix. Rewrote the onboarding email I had been avoiding for a year. Churn came back down within two months. Net new MRR from that unglamorous month was $610, more than three times what the launch produced, from work that took a fraction of the effort.

The group-class feature is still live. Two customers use it. I do not regret building it, exactly. I regret building it first, before I had earned the right to ignore my existing customers, which is to say never.

The one practical takeaway

Before you spend a quarter on a launch, spend a week on your churn. Read every cancellation note from the last three months. Fix the top reason. Then decide whether the big new thing is still the highest-leverage work, or whether you are just bored of the boring work that is quietly paying your rent. Nine times out of ten, the boring work wins, and it is not close.

A launch can be a nice spike on a business that already works. It is a terrible substitute for one.

---

This is a composite, anonymized founder diary. The specific product, segment, and dates have been changed to protect the founder's privacy, and the revenue figures are self-reported and rounded. The pattern, the numbers' relationship to each other, and the lesson are drawn faithfully from real solo-founder accounts. External statistics are linked to their original 2024 to 2026 sources.