Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Achieved Product-Market Fit Through User Research
Transcript
- Lucas: So there's this idea that keeps floating around indie hacker circles — that product-market fit is this magical moment where everything just clicks. You wake up one day and users are flooding in, revenue is climbing, and you've somehow made it. Luna: Right, like a switch flips. And I think a lot of people chase that, but the reality is usually much more gradual. Lucas: Exactly. And today I want to talk about a solo developer who approached it differently — not by building fast and hoping, but by doing something almost boring in its simplicity: systematic user research before writing a single line of code. Luna: Boring but effective. Who are we talking about? Lucas: A developer named Mark — I won't use his last name since he's not a public figure, but he's been documenting his journey on a private blog. He built a SaaS for small law firms — document automation, contract review — a pretty crowded space. But he reached twelve thousand dollars in monthly recurring revenue within eight months, and he credits it almost entirely to the research he did upfront. Luna: Fifty interviews, right? I read about this. He did fifty customer interviews before building anything. Lucas: That's the number. Fifty interviews with lawyers at small firms — partners, solo practitioners, even a few paralegals. His goal wasn't to sell them anything; it was to understand their workflow. Where do they waste time? What tools do they currently use? What's the one task they dread every week? Luna: And I'm guessing a lot of them said document review or contract clauses. Lucas: Exactly. But here's the thing — the most common answer wasn't 'we need better software.' It was 'we need to stop doing this manually, but we don't trust the existing tools.' They'd tried big enterprise solutions and found them too complex, or they'd tried simple tools that couldn't handle the nuance of legal language. Luna: So he found a gap — not in features, but in trust and simplicity. That's a much more interesting insight than just 'build a cheaper version.' Lucas: Right. And he validated it with something called a fake door test. He created a landing page that looked like a fully functional product — sample screenshots, a demo video, a sign-up button. But behind that button was just a waitlist and a message saying 'we're launching soon.' He drove a small amount of targeted ads — maybe two hundred dollars total — to see if people would actually click and enter their email. Luna: And what was the conversion rate? Lucas: Around twelve percent of visitors who clicked the sign-up button actually entered their email. That's not huge, but it was enough to tell him the problem was real. More importantly, when he followed up with those people, many of them agreed to a paid pilot — not free, paid — at a discounted rate. Luna: That's a big signal. People paying before the product even exists. Lucas: Exactly. So he built a minimum viable product — just the core feature: automated contract clause extraction. He focused on one use case, one type of document. And he gave it to those pilot users, then watched how they used it. He recorded sessions, took notes, asked them to think aloud. Luna: That's heavy. Some developers would rather just ship and iterate. But he was going deep on a small group. Lucas: And it paid off. One insight from those sessions: users kept trying to edit the extracted clauses directly in the tool, but his MVP only let them copy and paste elsewhere. So he added inline editing — a small change, but it doubled the time users spent in the app. Another: users wanted to save templates for frequently used clauses. That became his second feature. Within three months, he had a product that those five pilot users were using daily. Luna: So at that point, he had product-market fit for those five users. But scaling it — that's the hard part. Lucas: Right. He then used those five as case studies. He asked for testimonials, referrals, even permission to record a short video of one user explaining how the tool saved them two hours a week. That video became his primary marketing asset — not ads, not SEO, just that one video on his landing page. Luna: And that resonated because it was real. It wasn't a polished demo; it was a busy lawyer saying 'this actually works.' Lucas: Exactly. He grew to fifty users in the next three months, mostly through word of mouth in legal forums and LinkedIn groups. By month eight, he hit twelve thousand MRR. And here's the key metric he tracks: net promoter score. His NPS is consistently above sixty, which is exceptional for a B2B SaaS. Luna: So he's not just acquiring users; he's making them happy enough to stay and refer. Lucas: That's the definition of product-market fit, in my opinion. Not just growth, but retention and advocacy. And it all started with those fifty interviews. Luna: I think a lot of indie hackers skip that part because it's scary. Cold emailing strangers, asking for their time, handling rejection — it's emotionally draining. Lucas: It is. And Mark admitted that he got rejected by about seventy percent of the people he reached out to. But the ones who said yes gave him gold. He also offered a small incentive — a twenty-dollar Amazon gift card — which helped. And he made sure the interviews were structured but conversational, not like a survey. Luna: What kind of questions did he ask? I think that's the practical takeaway here. Lucas: He shared his framework. First, he asked about their role and daily routine — just to get them talking. Then he asked about the specific problem area: 'Walk me through the last time you had to review a contract. What did you do step by step?' Then he'd ask about the emotional side: 'What frustrates you most about that process?' And finally, he'd ask about past solutions: 'Have you tried any tools? What didn't work?' Luna: That last question is crucial. It reveals why competitors fail, not just what the user wants. Lucas: Exactly. He learned that most lawyers had tried either super basic tools that couldn't handle legal jargon, or enterprise tools that required IT setup. Neither worked. So his product had to be both simple and smart — and he prioritized that from day one. Luna: It's interesting that he didn't try to build a feature list that beat the competition. He just focused on one core thing and did it really well. Lucas: That's the indie hacker advantage. You can't out-feature a team of twenty engineers, but you can out-focus them. And focus comes from knowing exactly what your users care about. Luna: Speaking of focus — this kind of deep research takes time and sometimes a bit of support. If you're finding value in these conversations, consider supporting the show. It keeps us ad-free and allows us to dive into these detailed case studies. You can buy us a coffee at buymeacoffee.com/fexingo. Lucas: Yeah, honestly, listener support is what lets us spend time on episodes like this — talking about real numbers and real methods rather than surface-level advice. So thank you to anyone who contributes. Luna: Alright, back to Mark's story. Once he had those initial fifty users, he started seeing a pattern in feature requests. Almost everyone wanted integration with their existing document management systems. Lucas: Right. And that's a classic trap — you can start building integrations for every platform under the sun. But he resisted. He picked the one platform his users most commonly used — Google Drive — and built a deep integration there. Not just file sync, but actually pulling documents directly into his editor and saving changes back. Luna: That single integration probably made his product feel native to their workflow. Lucas: It did. And he measured the impact: users who connected Google Drive had a thirty percent higher retention rate after thirty days. That's a clear signal that he made the right call. Luna: So the lesson isn't just 'do user research' — it's 'do user research, then make hard prioritization decisions based on that research.' Lucas: Bingo. And I think that's where a lot of solo developers stumble. They do the interviews, they get great insights, but then they try to build everything at once. Mark's discipline was to build one thing at a time and validate each feature with a subset of users before rolling it out broadly. Luna: He also used a public roadmap, right? I know we've talked about that before on this show, but it's worth mentioning because it ties into the research loop. Lucas: Yes — he shared a simple Trello board with his users, showing what he was working on now, next, and later. Users could vote on items. That gave him a constant stream of prioritized feedback. But he didn't just build whatever got the most votes — he cross-referenced votes with his interview notes to make sure the loudest voices weren't leading him astray. Luna: That's smart. The squeaky wheel can be misleading if it's not representative. Lucas: Exactly. For example, a few power users kept asking for a mobile app. But during interviews, most users said they only worked on desktop. So he deprioritized mobile and instead improved the desktop experience. If he'd listened only to the vocal minority, he'd have wasted months on a mobile app that few people actually needed. Luna: So the combination — broad interviews to understand the market, then targeted feedback loops to refine — that's the recipe. Lucas: I think so. And the results speak for themselves. Twelve thousand MRR in eight months, with a solo founder working part-time alongside a consulting gig. He's since gone full-time on the product. Luna: What's next for him? Is he planning to raise money or stay bootstrapped? Lucas: He's staying bootstrapped for now. He's profitable, with low overhead — just hosting costs and a few freelance designers. He's considering hiring a part-time support person, but he's in no rush. His focus is on deepening the product for his existing niche rather than expanding to new markets. Luna: That's a good reminder that product-market fit isn't a finish line. It's something you maintain by continuing to listen and adapt. Lucas: Exactly. And I think that's the most important takeaway from Mark's story: the research never stops. Even now, he still does two or three user interviews every month. He calls it 'customer maintenance' — just checking in to see if anything has changed. Luna: I love that. It's like tending a garden, not just planting seeds. Lucas: Perfect analogy. So for any indie hacker listening — before you write that next line of code, before you buy that domain, talk to ten people. Not your friends, not other developers — actual potential users. You might be surprised what you learn. Luna: And if you do, let us know. We'd love to hear your stories. Lucas: Absolutely. That's it for today. Thanks for listening.