Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Hit 10K MRR With a Painful Refund Policy
Transcript
- Lucas: So there's this solo developer—let's call him Mark—who launched a SaaS product aimed at small marketing agencies. It's a project management tool tailored for client work. And from day one, he put a refund policy on his pricing page that most founders would consider insane. Luna: Insane how? Like, 30-day money-back guarantee? Or even longer? Lucas: Longer. It's a full refund, no questions asked, at any time. Not within 30 days, not within 60 days. Any time. If a customer has been paying for 11 months and decides they're not happy, they can cancel and get every dollar back. Mark's rationale was that the product is so good, and the switching cost so low, that this policy would actually build trust and reduce objections during the sales process. Luna: But doesn't that open the door to people using the product for free indefinitely? They could subscribe, use it for a year, then ask for a refund when they're done. Lucas: That's the fear. But Mark's data shows that less than 5 percent of customers actually request a refund. And of those, most do it within the first three months. The ones who stay past that point tend to be sticky because they've integrated the tool into their workflow. So the refund rate is tiny, and the trust boost is huge. Luna: I can see that for the kind of customer he's targeting. Small agencies are super averse to long-term commitments. They've been burned by tools that lock them in. So offering an unlimited refund might be the exact signal that says 'we're not going to trap you.' Lucas: Exactly. And Mark's not alone. There's a small but growing trend among indie SaaS founders who use what's called 'full risk reversal.' The idea is that the cost of refunds is lower than the cost of lost sales due to hesitation. In Mark's case, his conversion rate went up about 20 percent after he introduced the policy. He hit $10K MRR within 9 months. Luna: Twenty percent is not trivial. But what about the accounting headache? If you have to maintain reserves for potential refunds, that can eat into cash flow for a bootstrapped founder. Lucas: Mark handles it by keeping a reserve fund equal to one month's MRR. So if he's at $10K, he sets aside $10K. In practice, he's never had to dip into it beyond a few hundred dollars. The actual refund liability is much lower than people assume. And the psychological benefit to the customer is enormous. It turns a subscription from a cost into a low-risk trial. Luna: So it's almost like a permanent trial period, but with the upside that once people start using it, they stay. I imagine the key is that the product has to deliver value quickly. If it takes months to see ROI, people might milk the refund window. Lucas: That's the catch. This strategy only works if your product has a fast time to value. Mark's tool helps agencies onboard clients and manage feedback loops. Within the first week, a new customer can see how much time they're saving. If your product takes three months to show results, an unlimited refund policy could backfire because people will leave before they experience the value. Luna: Right. So it's not a one-size-fits-all. But for Mark's niche, it was brilliant. Did he have to deal with any refund abuse? Lucas: He did have a couple of cases where someone used the product for a big project, refunded, and then came back six months later for another project. Mark honored the refund both times, even though internally he knew what was happening. But he decided that the goodwill from those customers—and from the community—outweighed the cost. And interestingly, one of those abusers later became a paying long-term customer after they realized the tool was worth keeping. Luna: That's a great story. So the policy becomes almost like a marketing expense. Instead of spending money on ads, you spend it on refunds that build trust. Lucas: Exactly. And Mark's customer acquisition cost is actually lower than his competitors because word of mouth referrals have gone up. Agencies talk to each other. They say, 'Try this tool, if you don't like it, you get your money back even a year later.' That kind of recommendation is gold. Luna: I'm curious about the pricing page itself. How did he frame it? Did he call it 'Lifetime Money-Back Guarantee' or something? Lucas: He actually kept it low-key. Just a simple line: 'Cancel anytime, get a full refund. No questions asked.' He didn't put a time limit. And he didn't make it a huge banner. It was just a normal part of the FAQ. But customers noticed. He also added a short video of himself explaining the policy, which made it feel personal. Luna: That personal touch probably matters a lot. Especially for a solo dev product. People want to know there's a human behind it who's not going to fight them over a refund. Lucas: For sure. And Mark's support emails are all from him. He responds within an hour. So the refund policy is consistent with the overall brand: transparent, human, low-friction. It's all of a piece. Luna: So what's the downside? Besides the abuse risk. Is there any scenario where this policy hurts more than helps? Lucas: If your churn is already high for reasons other than pricing, adding a generous refund policy won't fix that. It might even accelerate churn because people feel less guilty about leaving. Also, if your product is expensive—like over $200 a month—the reserve fund requirement becomes significant. Mark's product is $49 a month, so the math works. At $500 a month, the risk is higher. Luna: And I imagine if you're targeting enterprise customers, they might not care about a refund policy. They care about compliance and security. So it's really a play for smaller, more price-sensitive buyers. Lucas: Exactly. Mark's sweet spot is agencies with 2 to 10 people. They're the ones who are most risk-averse. For them, this policy is a powerful signal. And it's a signal that bigger competitors can't easily copy because their refund processes are often bureaucratic. Luna: Alright, I'm sold on the idea. But I want to know the numbers. He hit 10K MRR in 9 months. What was his refund rate in that period? Lucas: Over the first 12 months, his refund rate was 4.2 percent of total revenue. That means for every $100 in MRR, he paid back about $4.20. But his customer acquisition cost dropped by 30 percent because of referrals. So net, he came out ahead. And his customer lifetime value went up because people stayed longer—they felt trusted. Luna: Four point two percent is lower than I expected. So the fear of refund abuse is mostly theoretical? The data says people don't actually abuse it? Lucas: In Mark's case, that's right. He did have one person who tried to game the system, but it was a very small percentage. Most people are honest. And those who do request a refund often cite a legitimate reason: the product wasn't a good fit, or their business changed. Mark even asks them for feedback, which helps him improve the product. Luna: So it's also a feedback loop. You learn why people leave, and you can fix it. That's actually smart product development. Lucas: Absolutely. And Mark's story is a good reminder that sometimes the counterintuitive move—the one that seems risky—can be the differentiator. Especially for solo devs who can't outspend competitors on marketing. Luna: Before we wrap up, I want to circle back to something you mentioned earlier about funding. You said Mark is bootstrapped, right? No outside capital. Lucas: Yeah, completely bootstrapped. He's a solo dev working from home. No ads, no sales team, just the product and this policy. It's exactly the kind of story that makes you think about what's possible with limited resources. Luna: It really is. And speaking of limited resources, I think it's worth noting that keeping this show ad-free and independent is also a bootstrapped effort. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these episodes. We don't have a big media company behind us. Lucas: Yeah, it's true. And we appreciate every single one of those supporters. It keeps us free to dig into stories like Mark's without worrying about sponsors. But if anyone listening finds value in what we do, that link is there. No pressure, just the option. Luna: Exactly. And back to Mark: one thing I wanted to ask—did he ever consider offering a partial refund or a pro-rata refund instead of full? That might reduce the risk even further. Lucas: He considered it, but decided that partial refunds would complicate the trust signal. The simplicity of 'full refund, no questions asked' is what makes it powerful. Once you add conditions, the customer wonders, 'What's the catch?' So he kept it clean. And it worked. Luna: That's a good lesson. Sometimes less is more. So for anyone listening who's bootstrapping a SaaS, maybe the thing holding them back isn't the product or the marketing—it's actually the refund policy. Lucas: I think there's something to that. Mark's story shows that a generous refund policy can be a strategic asset, not a liability. But you have to pair it with fast time to value and a product that genuinely delivers. If you have that, it's worth testing. Luna: Alright, Lucas. I think we've given our listeners plenty to think about. Mark's approach might not be for everyone, but it's definitely a creative way to build trust on a bootstrap budget. Lucas: Absolutely. And that's what indie hacking is all about—finding creative edges where bigger players can't follow. Thanks for the great conversation, Luna.