Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Built a SaaS With No Marketing Budget
Transcript
- Lucas: So the thesis for today's episode is pretty extreme: build a SaaS product with literally zero marketing budget. Not a small budget — zero. No paid ads, no sponsored content, no PR firm, no freelancer writing blog posts. Luna: That sounds either incredibly disciplined or totally reckless. I'm guessing there's a story behind it. Lucas: There is. It's a solo developer I've been following for about a year. He built an api first tool for developers — think something like a simplified version of Twilio for sending SMS notifications. He launched in early 2025, and by March of this year, he hit fifteen thousand dollars in monthly recurring revenue. And I can verify that number because he publishes transparent revenue reports on his blog. Luna: Wait — fifteen K MRR with zero marketing spend? How is that possible? Even a basic content strategy usually requires some investment. Lucas: His approach was almost monastic. He had three channels, and none of them cost money. First: his API documentation itself functioned as SEO content. He wrote incredibly thorough, example-heavy docs — not just 'here's the endpoint,' but 'here's why you'd use this in a real-world scenario.' Those pages started ranking for long-tail queries like 'send SMS notification from Node.js.' Second: he was extremely active on GitHub. He built open-source libraries that wrapped his API, and those repos got traction on Hacker News and Reddit. Luna: So the open-source libraries acted as lead generation. That's clever — developers trust a tool they can inspect the code for. Lucas: Exactly. And the third channel was what he called 'support-driven development.' Every single customer support email he got, he treated as product research. If three different people asked for the same feature, he built it. If someone complained about confusing pricing, he simplified it. He didn't outsource support — he answered every email himself. And over time, those customers became his biggest advocates. Luna: But that sounds incredibly time-consuming. How does a solo dev balance support with actually building the product? Lucas: He was very disciplined about batching. He'd spend the first two hours of his day on support, then the rest on development. And he was ruthless about saying no to features that didn't align with his core use case. The product intentionally does one thing — send SMS notifications — and does it well. No dashboard analytics, no team accounts, no enterprise features. Luna: That must have hurt sometimes. I imagine he got requests from potential customers offering to pay more for those features. Lucas: He did. And he turned them down. His reasoning was that adding complexity would dilute the product's brand and increase support burden. He wanted to stay lean. And honestly, that discipline might be the real secret weapon here. Most founders can't resist the temptation of a bigger check. Luna: So the question becomes: can this scale? Fifteen K MRR is impressive for a solo founder, but what happens when he wants to hit fifty or a hundred K? Lucas: That's the tension. He's now at the point where organic channels alone might not sustain growth. He's already ranking for most of the obvious keywords. The low-hanging fruit is gone. He's told me in an email that he's considering hiring a part-time content writer. But he's reluctant because it would break his 'zero marketing budget' principle. Lucas: I think that's exactly right. The zero-budget phase forced him to be creative and to build a product that genuinely solved a problem. But at a certain scale, paid marketing is just a tax on growth. If the unit economics work, it's irrational not to spend. Luna: It's also worth noting that his 'free' channels weren't truly free — they cost his time. Writing excellent documentation takes hours. Engaging on GitHub takes hours. Answering support emails takes hours. So the opportunity cost is real. Lucas: You're describing what economists call 'sweat equity.' And he was willing to put in that sweat because he had no other option. He bootstrapped the company with about three thousand dollars of his own savings. No investors, no loans. So he couldn't afford to throw money at ads and hope something stuck. Luna: That's a very different risk profile from a venture-backed startup. If you have millions in the bank, you can experiment with paid channels. If you have three grand, you have to be surgical. Lucas: Exactly. And I think that constraint actually improved his product decisions. Because he couldn't afford to fail, he made sure every feature was something real customers wanted. He didn't build on speculation. Luna: Alright, but let's get specific. What was the actual growth curve? Did it start slow and then accelerate? Lucas: It was a classic hockey stick, but the flat part lasted longer than you'd expect. He launched in February 2025 and for the first four months, he averaged about two hundred dollars MRR. Then in June, one of his open-source libraries got featured on the front page of Hacker News. That drove a spike to about two thousand MRR. Then it plateaued again for a few months before gradually climbing as his SEO content matured. Luna: So patience was critical. If he had given up after six months, he'd have missed the breakout. Lucas: Absolutely. And that's one of the hardest things for indie hackers to hear. Everyone wants the overnight success story, but the reality is usually months or years of slow, unglamorous work. Luna: Speaking of unglamorous work — let's talk about the donation segment. Because honestly, if today's episode gave you a useful framework or even just one concrete tactic, that's the reason listener support exists. It's buy me a coffee dot com slash fexingo. No pressure, no perks — just keeping this show ad-free and independent. Lucas: Yeah, it's a small ask for a big impact. We don't run ads, and that's only possible because some listeners choose to chip in. So if you found value in today's deep dive, that's the link. Luna: Alright, back to the story. So after that Hacker News spike, what changed? Did he deliberately try to recreate that success? Lucas: He tried, but you can't engineer a Hacker News front page. Instead, he focused on what he could control: improving his documentation, adding more code examples, and responding quickly to every GitHub issue. He also started a small newsletter — purely organic, no lead magnets — just sharing what he was learning. That newsletter now has about three thousand subscribers. Luna: Three thousand subscribers from zero marketing budget is impressive. How did people find it? Lucas: Mostly through his documentation. At the bottom of every API doc page, he had a subtle call to action: 'Want to hear when we add new features? Subscribe to our changelog newsletter.' No pop-ups, no annoying modals. Just a simple link. And because people already found his docs useful, they trusted him enough to subscribe. Luna: That's a great example of product-led growth applied to content. The docs are the product, and the newsletter is the upsell. Lucas: Exactly. And he's now exploring a similar tactic with his API itself. He's considering adding a 'webhook for new features' — basically a programmatic way for developers to subscribe to updates. That's a very developer-native approach. Luna: I love that. It's consistent with his audience and his product philosophy. So what's next for him? Does he plan to stay solo forever? Lucas: He's conflicted. He enjoys the autonomy of being a solo founder, but he acknowledges that to reach the next level — say, fifty K MRR — he'll likely need help. His current bottleneck is support. He's spending about four hours a day on emails, which leaves less time for building features that could drive growth. Luna: That's a classic solo founder dilemma. You get trapped in the day-to-day operations and can't step back to work on the business. Lucas: Right. He's considering hiring a part-time support person, but he's worried about losing the direct customer feedback loop that helped him build such a tight product. It's a legitimate concern — once you delegate support, you risk becoming disconnected from your users. Luna: Maybe he could start with a very part-time contractor, like ten hours a week, and still handle the most critical tickets himself. That way he keeps a finger on the pulse. Lucas: That's exactly what I suggested. He's mulling it over. But I think the broader lesson for other indie hackers is that there's no shame in spending money once you've proven product-market fit. The zero-budget phase is a forcing function, not a permanent state. Luna: Let's zoom out for a second. What's the one concrete takeaway you hope listeners get from this episode? Lucas: If you're bootstrapping a SaaS with no budget, focus on three things: make your documentation your best marketing asset, engage deeply in communities where your users already hang out — for developer tools, that's GitHub, Reddit, Hacker News — and treat every support interaction as free market research. Do those three things consistently for six months, and you'll have a foundation that paid marketing can't easily replicate. Luna: And if you try it, let us know how it goes. We'd love to feature your story on a future episode. Lucas: Absolutely. That's a wrap for today. Thanks for listening, and we'll see you next time.