Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Built a SaaS Entirely Through Organic Content
Transcript
- Lucas: So there's this solo developer — let's call him Alex, since he prefers to stay pseudonymous — who built a SaaS tool for API testing. Not exactly a new category. Postman is the elephant in the room, and there's a dozen smaller competitors. Luna: Right, the space is crowded. What was his angle? Lucas: He didn't try to out-feature Postman. Instead, he wrote one blog post titled 'Why I Switched from Postman to – And Why You Should Too.' It was a detailed walkthrough of exactly how he used the tool in his daily workflow. He posted it on Hacker News on a Tuesday morning. Luna: And that's the entire marketing strategy? One blog post? Lucas: That, plus a 45-minute YouTube tutorial that he recorded in one take. No editing, no fancy intro. Just him screen-sharing and explaining the core features. The Hacker News post got about 300 upvotes and drove 12,000 visitors in the first 48 hours. The YouTube video picked up steam over the next few weeks — it now sits at about 80,000 views. Luna: We deliberately keep this podcast ad-free, by the way. If that kind of indie-hacker content is useful to you, you can support us at buy me a coffee dot com slash fexingo. It helps us keep doing deep dives like this without interrupting the flow. Lucas: Exactly. No sponsors, no mid-roll breaks. Just the story. So Alex's strategy relied entirely on organic content. No paid ads, no cold outreach, no affiliate partnerships. He built the product in public, and that transparency became the marketing. Luna: I love that. But realistically, how many people can replicate a Hacker News front-page hit? That feels like lightning in a bottle. Lucas: Fair point. But here's the thing — he didn't just post and pray. He had already built a small Twitter following of about 2,000 developers by sharing his build process. So when he posted, he had a base that amplified it. And the content itself was exceptionally practical. He didn't just list features; he showed the exact commands, the exact API endpoints he tested, and the exact errors he encountered with Postman. Luna: So the content was solving a specific pain point. Developers hate switching tools cold turkey. They need to see the migration path clearly. Lucas: Exactly. And the YouTube video doubled down on that. It's not a polished production — but it's thorough. He walks through setting up the tool, importing a Postman collection, and running tests. At the 30-minute mark, he shows a real debugging session where he catches a bug that Postman had missed. That moment alone got clipped and shared on a few developer forums. Luna: What about the numbers? You mentioned $15K MRR. How long did that take? Lucas: He launched the product in January 2025 with a free tier and a single paid plan at $19 per month. In the first month, he signed up 150 free users and 12 paid users — about $228 MRR. His free-to-paid conversion rate was around 4.2 percent, which is actually above average for SaaS according to some benchmarks from ProfitWell. Luna: That's low absolute numbers, but a healthy conversion rate. How did growth accelerate? Lucas: The YouTube video started ranking for keywords like 'API testing tool' and 'Postman alternative.' By month three, organic traffic from Google was contributing about 5,000 visitors per month, growing 40 percent month-over-month for the first six months. By month eight, he had 400 paid users and crossed $7,600 MRR. After twelve months, he hit 790 paid users and about $15,000 MRR. Luna: So content created a compounding effect. The blog post and video kept working long after they were published. What about churn? Lucas: Monthly churn hovered around 3.5 percent. Not exceptional, but sustainable. His customer acquisition cost was effectively zero — just the time spent writing and recording. So even at that churn rate, the lifetime value to customer acquisition cost ratio was essentially infinite. Luna: That's the dream for bootstrappers. But I wonder — did he ever feel the need to add more marketing channels? Lucas: He experimented with a few things. He wrote a second blog post about scaling the tool for teams — that did okay but nowhere near the first. He also tried a Product Hunt launch in month four, which brought a spike of about 1,000 visitors but only converted to 15 paid users. So he quickly realized that the organic content channel was his strongest bet and doubled down there. Luna: What did 'doubling down' look like? More videos? More blog posts? Lucas: He published one new blog post every two weeks, always tied to a specific use case. For example, 'How to Test GraphQL APIs with ' and 'Automating API Tests in CI/CD Pipelines.' Each post was designed to rank for a long-tail keyword. He also started repurposing the blog posts into short Twitter threads. The threads didn't go viral but consistently brought in 50 to 100 new visitors per thread. Luna: So the strategy was sustainable because it didn't require constant bursts of attention. Just consistent, high-signal content. Lucas: Right. And the beauty is that he never hired anyone. He did all the writing, recording, and coding himself. His total monthly expenses were about $200 — hosting, domain, email service. So from month one, the business was profitable. He was able to quit his freelance gig by month eight. Luna: That's impressive. But I want to push back a little — this approach only works if you have the skill to produce content that actually ranks. Most developers aren't great writers or video creators. Lucas: That's true, and it's a real barrier. But Alex wasn't a professional writer either. His writing was clear but not fancy. The key was structure: he always started with a concrete problem, then showed how his tool solved it step by step, then ended with a clear call to action. That formula works regardless of writing flair. Luna: And the video was literally one take. So there's a lesson there about over-polishing. Sometimes raw and thorough beats slick and shallow. Lucas: Absolutely. He told me that the video's lack of editing actually built trust. Viewers could see he was using the tool in real time, making mistakes, correcting them. It felt authentic. One comment said, 'This is the first API tool demo I actually watched to the end because it didn't feel like a sales pitch.' Luna: That's gold. Let's talk about the product itself. How did he decide what features to build? With no user research budget, he must have relied heavily on feedback from those early users. Lucas: He did. In the first three months, he personally emailed every user who signed up for the free trial. He asked two questions: 'What almost stopped you from trying the tool?' and 'What feature would make you pay?' The responses shaped his roadmap. For instance, several users mentioned they needed team collaboration features, so he built a basic sharing mechanism — just shared workspaces — and that became a key reason free users upgraded. Luna: So product development was driven by direct user conversations, not guesswork. That's a classic lean approach. Lucas: Exactly. He maintained a public roadmap on a simple Notion page. Users could upvote features. He prioritized based on two criteria: how many users asked for it and whether it would increase conversion or reduce churn. He never built anything that didn't meet at least one of those. Luna: That discipline is rare. Most solo devs I see try to build everything at once and burn out. Did he ever get close to burnout? Lucas: He did around month seven. He was handling support tickets, writing content, developing features, and monitoring servers. He told me he worked 60-hour weeks for three straight weeks. That's when he decided to add a self-serve knowledge base and a community forum. Support tickets dropped by 40 percent after that. Luna: A smart investment. So what's next for him? Does he plan to keep it solo, or is he thinking about hiring? Lucas: As of last month, he's still solo. He's at $15,200 MRR and growing around 5 to 7 percent month-over-month. He says he'll consider hiring a part-time support person once he crosses $20K MRR, but he's in no rush. He enjoys the independence and the direct connection with users. Luna: I think that's a healthy perspective. A lot of founders feel pressured to scale fast, but if the business is profitable and you're happy, why change? Lucas: Exactly. And his story is a great reminder that you don't need a complex marketing machine. One piece of exceptional content can be the seed. But you have to be willing to put in the work to make that content genuinely useful. Luna: And then keep showing up. The compounding effect only works if you keep adding to it. Lucas: Right. Alex's approach wasn't a one-hit wonder. It was the first hit that gave him momentum, and the consistent output that sustained it. For any indie hacker listening, the takeaway isn't just 'write a blog post and hope.' It's 'write a blog post that solves a real problem, then write another, then another.' The medium is the marketing. Luna: Well said. That's a wrap for this episode. Thanks for joining us.