Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Used API Documentation to 10x MRR
Transcript
- Lucas: So there's this solo developer, Sarah Chen, who was working as a backend engineer at a mid-size fintech company last year. She was constantly frustrated by how terrible most API documentation is — incomplete endpoints, missing error codes, example code that doesn't actually run. Luna: Oh, the classic. Every developer I know has a horror story about some API that took them three days to integrate because the docs were misleading. Lucas: Exactly. And Sarah thought, 'Someone should fix this.' But instead of waiting, she built a tool in two weeks that auto-generates interactive documentation from API traffic — think of it like a Wireshark filter that produces readable docs. She called it DocBridge. Luna: Two weeks. That's impressively fast. What was the initial version like? Lucas: It was just a Node.js script that listened to HTTP requests on a proxy, parsed the JSON bodies, and output Markdown files. She put it on GitHub with a README that said, 'If you hate writing API docs, try this.' That was it. No landing page, no pricing, no marketing. Luna: And people actually found it? Just from GitHub? Lucas: Yeah, primarily through Hacker News and a few Reddit threads in r/webdev. Within a week, she had about 300 stars and a dozen people asking if they could pay her for a hosted version. That was her aha moment. Luna: So she had demand before she even thought about monetising. That's the dream scenario for any indie hacker. Lucas: Right. She spent another two weeks building a hosted SaaS version — same core functionality but with a web dashboard, team accounts, and a simple pricing tier: free for solo devs, $29 a month for teams, $99 for enterprise. She launched it on Product Hunt and hit $1,200 MRR in the first month. Luna: That's decent momentum. But how did she go from $1,200 to where she is now — I think you said $45K MRR? Lucas: Forty-five thousand as of last month, yes. About ten months after launch. And the key insight was that she didn't do any traditional marketing. Instead, she embedded herself in developer communities — answering questions on Stack Overflow about API documentation, contributing to open source projects, and writing detailed blog posts about the specific problems DocBridge solves. Luna: So content marketing, but very technical and genuine. Not the typical 'growth hacking' stuff. Lucas: Exactly. One post she wrote — 'How to Automate API Documentation for Your Microservices Architecture' — got picked up by the r/programming subreddit and drove over 500 sign-ups in a weekend. She didn't even mention DocBridge until the last paragraph. That's the difference between selling and educating. Luna: I love that approach. It's so much more sustainable than paid ads for developer tools. Developers can smell a sales pitch from a mile away. Lucas: Absolutely. And Sarah also did something smart with her pricing: she never changed the free tier. She kept it generous enough that solo devs could use DocBridge indefinitely for their personal projects. That created a massive word of mouth funnel inside companies — a developer would use it for free on their side project, then convince their team to buy the paid plan at work. Luna: That's the classic bottom-up adoption play that companies like Slack and Notion used. But for a solo dev, it's even more powerful because she doesn't need a sales team. Lucas: Exactly. She told me that about 60% of her enterprise customers came from a free-tier user who upgraded when they joined a larger team. And she never had to run a single ad or hire a salesperson. Luna: That's a great metric. What about churn? Did she have any issues with that? Lucas: Initially, yes. In months three and four, she saw churn around 8% on the team plan. She dug into the data and found that most cancellations happened after the first billing cycle — people signed up, used it for a month, then forgot about it. So she added a simple onboarding email sequence that showed users how to integrate DocBridge with their CI/CD pipeline, and churn dropped to under 3%. Luna: That's a huge improvement. And it's a classic example of how improving the product experience can have a bigger impact than any growth tactic. Lucas: Yeah. She also started doing customer interviews every week — just thirty-minute calls with anyone willing to talk. That's where she discovered that the biggest pain point wasn't just generating docs, but keeping them in sync with the actual API. So she built a feature that automatically updates the docs whenever the API changes, which became her strongest selling point. Luna: So she turned a common frustration into a core differentiator. That's product-market fit in action. Lucas: Right. And another thing she did was release her revenue numbers publicly every month on her blog. That built a lot of trust and also attracted other indie hackers who became evangelists for her product. Luna: I think that's something a lot of bootstrappers overlook. Transparency can be a really effective marketing tool, especially in the developer community. Lucas: Speaking of which — if today's tech conversation gave you something usable, a couple of dollars a month is genuinely what keeps shows like this going. You can find us at buy me a coffee dot com slash fexingo. No pressure, but every little bit helps us stay ad-free. Luna: Yeah, we really appreciate it. And it goes right back into bringing you more stories like Sarah's. Lucas: So back to DocBridge — one of the most interesting things Sarah did was she never raised any outside funding. She bootstrapped the entire thing from her savings and reached profitability within six months. Luna: That's remarkable. What was her burn rate during those early months? Lucas: She kept it incredibly lean. Her only costs were the server hosting — about $150 a month on DigitalOcean — and her own time. She was still working her full-time job for the first four months, building DocBridge in the evenings and weekends. Luna: So she was effectively running a profitable side project before she even quit her day job. That's the ideal ramp for any indie hacker. Lucas: Exactly. She told me that her goal was to get to $5K MRR before going full-time, which she hit in month five. That gave her enough cushion to take the leap. Luna: Smart. And now she's at $45K MRR with no employees. Is she planning to hire? Lucas: She recently brought on a part-time contractor for customer support, but she's deliberately staying small. She says she wants to keep the product focused and not lose the direct connection with users that helped her get this far. Luna: That's a trade-off that a lot of founders struggle with. But for a tool this specialised, it might be the right call. Lucas: I think so. And she's also started offering a free tier for open source projects, which has generated a ton of goodwill and even more inbound leads. Luna: That's a smart move. Open source projects are often the ones with the worst documentation because nobody has time to maintain it. Lucas: Right. And by providing value there, she's essentially training the next generation of developers to rely on DocBridge. When they go to work at a company that needs paid docs, they'll naturally suggest her tool. Luna: So it's a long-term play that also serves a genuine need. I think that's a great lesson for anyone building in the developer tools space. Lucas: Absolutely. And one more thing — she credits much of her success to being extremely responsive to feedback. In the early days, she would personally reply to every support email within an hour, even at 2 AM. Luna: That level of dedication is hard to sustain, but it clearly paid off. Lucas: It did. And now that she has a contractor handling support, she still reads every single ticket to stay close to the user's pain points. Luna: That's a good habit. So what's next for DocBridge? Any big features on the roadmap? Lucas: She's working on an ai powered feature that suggests improvements to existing documentation based on common user questions. So if multiple users ask the same question about an endpoint, DocBridge will automatically flag that part of the docs as unclear and suggest rewrites. Luna: That's brilliant. It turns customer support data into documentation improvements. I can see that being a huge differentiator. Lucas: Exactly. And it's something only a small team could build because you need that tight feedback loop between support and product. Larger companies often lose that connection. Luna: Yeah, that's the indie hacker advantage — you can move fast and stay close to the user. Lucas: So that's Sarah Chen and DocBridge: a solo developer who turned a personal frustration into a $45K MRR business by focusing on a specific pain point, building in public, and staying relentlessly user-focused. Luna: And proving that you don't need a big team or venture capital to build a successful SaaS product. Lucas: Right. If you're thinking of starting something, maybe the next big opportunity is hiding in your own daily frustrations.