Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Hit 10K MRR With a Developer Tool and No Sales Team
Transcript
- Lucas: So there's this guy — let's call him Dan — who built a SQL query optimization tool as a side project back in 2024. By mid-2025, he was at $10,000 monthly recurring revenue, and he had never made a single sales call. Luna: No sales calls at all? So how did people even find it? Lucas: He launched on Hacker News with a technical blog post titled 'How I Cut Our Database Bills by 40 Percent.' It was a genuine case study from his own consulting work. The post hit the front page, stayed there for about six hours, and drove something like 15,000 visitors to his landing page. Luna: Right, so the classic 'show your work' approach. But a lot of HN launches fizzle after the initial spike. Did he have anything sticky? Lucas: He had a free tier that let you analyze up to a thousand queries per month. That's enough for a small project or a staging environment. So the curious developers who clicked through from Hacker News could actually try the tool without entering a credit card. About 500 of them signed up in that first week. Luna: And then what — he just waited for them to hit the limit? Lucas: Pretty much. He had a 30-day free trial for the paid tiers, but he didn't push it aggressively. The idea was that if your queries were slow enough to annoy you, you'd naturally want to run more than a thousand checks. The conversion rate from free to paid after 30 days was 18 percent, which is actually really solid for a developer tool. Luna: Eighteen percent is better than a lot of SaaS products I've seen. But was that enough to get to $10K MRR? Lucas: Not immediately. That first cohort gave him about $1,200 in MRR. The real growth came from a combination of two things: organic word of mouth and one very well-placed Reddit comment. Luna: Okay, I have to hear about the Reddit comment. Lucas: So about two months after launch, someone on r/programming posted 'What tools do you use to optimize slow queries?' and Dan's tool got mentioned in a thread. But the key was that the person who mentioned it wasn't Dan — it was a user who had genuinely saved his team hours of debugging. That comment got about 400 upvotes and drove roughly $2,000 in new subscriptions over the next month. Luna: That's the dream, right? A real user evangelizing your product. But it's also hard to manufacture. Lucas: Exactly. Dan's strategy wasn't to manufacture it — it was to make the tool so useful that power users would naturally talk about it. He also built a simple 'share your results' feature that let you generate a public link to a query analysis. That turned every optimization report into a tiny advertisement. Luna: So the product itself became the marketing channel. I love that. But what about pricing? Did he go with per-seat, per-query, flat monthly? Lucas: He went with usage-based pricing, but in a way that felt predictable. The free tier was a thousand queries a month. The first paid tier was ten dollars for ten thousand queries. Then fifty dollars for a hundred thousand. Then two hundred dollars for unlimited. That structure meant small teams could start cheap and scale up naturally — no sticker shock. Luna: And no enterprise sales process. That's smart for a solo dev who doesn't want to build a sales team. Lucas: Right. The average revenue per account was around thirty-five dollars a month in the first year. By the end of year one, he had about 285 paying customers. That's not huge in terms of customer count, but it's a really healthy base for a solo operator. His churn was under 4 percent monthly, which is excellent for a B2B SaaS tool. Luna: That low churn tells me the tool solves a real pain point. But I'm curious — did he ever consider raising venture capital to accelerate? Lucas: He did get approached by a couple of angel investors after the Hacker News post. But he turned them down. His reasoning was that he wanted to stay independent and keep the product focused. He didn't want to hire a sales team or expand into adjacent problems just to hit growth targets. He was profitable from month three. Luna: That's a trade-off, though. He probably left some growth on the table. But maybe that's okay if the goal is lifestyle or sustainability. Lucas: Yeah. And interestingly, he started getting inbound acquisition interest around month nine. A couple of database monitoring companies reached out. He didn't sell, but he did license his optimization algorithm to one of them for a five-figure annual fee. That's a nice side revenue stream that doesn't distract from the main product. Luna: So he's essentially running two businesses now — the SaaS and the licensing deal. That's a pretty good spot to be in. Lucas: It is. And it all started with a single blog post and a free tier. No sales team, no marketing budget, no enterprise contracts. Just a useful tool and a developer who understood his audience. Luna: You know, stories like this always make me think about the role of luck versus deliberate strategy. I mean, the HN front page is partly luck, but the free tier and the share feature were deliberate. Lucas: Absolutely. And I think that's the key takeaway — you can't control whether your post goes viral, but you can control whether your product is worth sharing. Dan built a tool that people wanted to talk about, and then he made it easy for them to do so. Luna: It's also worth noting that he didn't try to be everything to everyone. He focused on one specific pain point — slow SQL queries — and solved it really well. Lucas: Right. And that focus is probably why the churn stayed low. His users knew exactly what they were getting. No feature bloat, no confusion about pricing. It's a refreshing approach in an era where every SaaS seems to be adding AI features and enterprise tiers. Luna: Speaking of which, a lot of the listeners of this show are indie hackers trying to replicate this kind of success. If today's conversation gave you something useful — whether it's the free tier strategy, the pricing inspiration, or just the motivation to ship — we just want to mention that listener support is what keeps this podcast ad-free and independent. Lucas: Yeah, we've never run a sponsored ad, and we'd like to keep it that way. If you find value in these episodes, you can support the show at buy me a coffee dot com slash fexingo. That's all lowercase. And truly, no pressure — just a way for people who get something out of it to give back. Luna: Exactly. And now back to Dan's story — one more thing I wanted to ask: did he ever build a mobile app or was it strictly web-based? Lucas: Strictly web-based. He had a simple React front end with a Node backend that users connected to their databases via read-only credentials. No mobile, no native app. That kept his maintenance overhead incredibly low. He could spend maybe ten hours a week on the product and the rest on consulting or family time. Luna: So the lesson might be: pick a problem that doesn't require a huge interface. SQL optimization is analytical, not visual. You don't need a design-heavy app. Lucas: Exactly. He matched the complexity of the solution to the complexity of the problem. It's a DB tool — it doesn't need animations or a mobile version. That's a lesson a lot of founders learn the hard way after building too much too soon. Luna: So what's next for him? Is he just coasting at $10K MRR or does he have growth plans? Lucas: He's actually working on a v2 that adds support for PostgreSQL and MySQL monitoring in real time. He told me he expects that to double his addressable market. But he's doing it slowly, without hiring. He's funding the development out of cash flow. Luna: That's the beauty of bootstrapping. You can grow at your own pace and keep the quality high. Lucas: Yeah. And I think that's a fitting note to end on. Dan's story shows that you don't need a sales team or venture capital to build a sustainable, profitable SaaS. You need a sharp focus, a product that solves a real pain, and a distribution channel that rewards quality work. Luna: And maybe one well-timed Reddit comment. Lucas: Yeah, that doesn't hurt either.