Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Priced His SaaS at $9 and Hit 5K MRR
Transcript
- Lucas: So there's this solo dev named Marcus Chen. He built a time-tracking SaaS called Minute. Nothing flashy — just a stopwatch, a few project tags, a weekly report emailed to you. The kind of thing a freelancer could use. And he priced it at exactly nine dollars a month. Luna: Nine dollars. Not nine ninety-nine, not ten. Nine even. That's... specific. Lucas: That's the whole episode right there. Why nine? Marcus says he was sitting in a coffee shop, looked at the tip jar, and saw someone had written '$9 — feels like under ten.' And he thought — that's the anchor. If I price at nine, the customer's brain rounds down. Ten dollars feels like double digits. Nine is still single digits. Luna: But nine dollars a month for a time tracker — that's cheap. How many users did he need to make real money? Lucas: He needed about 560 paying users to hit five thousand dollars a month MRR. That's the target he set for himself before he'd even consider quitting his day job. And he hit that number in eleven months. No advertising, no content marketing — just a Product Hunt launch and some forum posts. Luna: So the low price was a conversion lever. It lowers the barrier to entry, especially for a tool that's not exactly sexy. Lucas: Exactly. Minute has a fourteen-day free trial. No credit card required. Marcus found that about twelve percent of trial users converted to paid. And of those, the monthly churn rate hovered around four and a half percent. That's a lifetime value of roughly two hundred dollars per customer at nine bucks a month. Luna: LTV of two hundred dollars — that's actually not bad for a tool that costs him next to nothing to run. What's his hosting bill? Lucas: About eighty dollars a month on a small DigitalOcean droplet and a managed PostgreSQL database. So his gross margins are north of ninety-eight percent. The real cost is his time — he spends maybe ten hours a week on support, bug fixes, and a once a month feature release. Luna: But here's the thing I wonder about — at nine dollars, does the customer actually value the product? I've read that too-low prices can increase churn because people don't feel invested. Lucas: Marcus actually saw that. For the first six months, his churn was closer to six percent. He did exit surveys. A lot of people said 'it's only nine bucks, I just didn't need it anymore.' There was no sunk-cost friction. So he added a small thing — he started sending a 'your weekly summary' email that looked really polished, with a graph of hours logged. That alone dropped churn to four and a half percent. Luna: So he increased the perceived value without raising the price. That's clever. But did he ever worry that nine dollars left no room to grow? Like, you can't cut it further, and raising it later might piss people off. Lucas: He sat on nine dollars for eighteen months. Then, about six months ago, he raised it to eighteen dollars a month for new customers. Grandfathered existing users at nine. He lost exactly six percent of new sign-ups in the first month — but the conversion rate actually improved slightly. The higher price signaled more seriousness, apparently. Luna: So the nine-dollar anchor worked as an acquisition tool, and then the eighteen-dollar price became the sustainability point. That's a pretty clean two-step strategy. Lucas: It's a textbook example of what pricing pros call 'pennies versus psychology.' Nine dollars is not a penny less than ten — but it lives in a different mental bucket. Marcus told me he's seen competitors price at seven ninety-nine or eight ninety-nine, and he thinks that's a mistake. Those prices scream 'I'm trying to be cheap.' Nine dollars says 'I'm straightforward and fair.' Luna: Interesting. So the exact number matters more than the discount. I wonder if that applies to other price points too — like, is there a magic number for B2B SaaS? Lucas: There's a whole literature on it. But Marcus's case is especially instructive because he didn't overthink it. He picked a number that felt honest to him, tested it, and stuck with it until he had enough data to adjust. He didn't A/B test fifty price points. He just launched at nine and watched what happened. Luna: And what happened was five thousand MRR from a single feature-light app. That's the dream, right? Lucas: It is. And it's replicable if you understand the principle: your price is a signal. It tells the customer whether you're a commodity or a considered purchase. Marcus's nine dollars said 'I'm a tool you use without thinking.' That's exactly right for a time tracker. Luna: So for a solo dev listening right now — what's the one takeaway? Pick a price that feels almost too low, but not arbitrary? Lucas: I'd say: pick a round number that has a psychological edge. Nine, nineteen, forty-nine. Avoid the.99 trap — that's for retail, not SaaS. And commit to that price for at least six months before you tweak it. Let the market tell you if it's wrong, not your anxiety. Luna: Speaking of the market telling you things — Marcus eventually raised the price. What happened to that six percent who dropped off? Did they leave bad reviews? Lucas: A few grumbled on Twitter, but mostly they just left quietly. And the new customers who came in at eighteen dollars? They churn at a lower rate — about three percent. So the higher price actually improved the quality of the user base. Marcus says his support tickets dropped by a third after the price change. Luna: Higher price, better customers, less support. That's a virtuous cycle. But it only works if you've already built the trust at the lower price. Lucas: Exactly. The nine-dollar price built the base. The eighteen-dollar price optimized it. And now Marcus is at about seventy-two hundred MRR, still solo, still working ten hours a week on it. He's thinking about adding a team plan at twenty-nine dollars per seat. Luna: If today's episode gave you a useful framework for thinking about your own pricing, or just a good story to share with a founder friend — these conversations stay ad-free because of listener support. You can buy us a coffee at buy me a coffee dot com slash fexingo. Lucas: Yeah, it's a small thing that keeps the lights on and the podcast independent. And honestly, every contribution — even a single coffee — makes a difference. We don't run ads, so this is what keeps us going. Luna: Alright, back to Minute. Lucas, you mentioned Marcus is thinking about a team plan. How would that change his pricing psychology? Lucas: That's a whole other episode. But the short version — team pricing is about value per seat, not per user. If a team of five saves ten hours a week, twenty-nine dollars per seat is a no-brainer. Marcus is actually running a beta with ten teams right now, charging them fifteen dollars per seat to test willingness to pay. Luna: So he's essentially repeating the same playbook: start low, build trust, then optimize. That's a pattern worth remembering. Lucas: Exactly. And that's the indie hacker way — iterate on one variable at a time. Price is just another feature.