Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / Building a SaaS Product That Competes With Free Alternatives
Transcript
- Lucas: So Luna, there's this question I keep seeing in indie hacker forums that feels almost unfair at first glance. Someone says, 'I want to build a to-do list app,' and the top comment is always, 'But there are a hundred free ones already.' Luna: Right, and it's a fair point. Google Keep, Microsoft To Do, TickTick's free tier... why would anyone pay for something they can get for zero dollars? Lucas: Exactly. And yet, Todoist charges five bucks a month and has over 30 million users. So the question isn't really whether you can compete with free. It's how. And that's what I want to drill into today — the specific strategies that let paid products not just survive against free alternatives, but thrive. Luna: I'm actually a good case study for this. I use Todoist, and I pay for it. And I couldn't tell you exactly why I started paying, but I know I never considered going back to something free once I got hooked on certain features. Lucas: That's exactly the kind of user we need to understand. So let's start with the first strategy, which is basically: don't try to win on the basic use case. The free tools cover that. You win on the power user use case. Luna: Meaning, the person who just wants to jot down a grocery list will never pay you. So you don't build for them. Lucas: Right. You build for the person who organizes projects with subtasks, labels, filters, recurring due dates, shared lists with their partner, integrations with their calendar. The free tools can do the first layer of that, but they break down once you have more than, say, fifty active tasks across multiple projects. Luna: That's exactly where I hit the wall with Google Keep. I had notes everywhere, no structure, and it just became noise. Lucas: And that's the moment a user becomes willing to pay. They hit a pain point that the free tool can't solve elegantly. The paid product doesn't need to be better at the basic thing. It needs to be dramatically better at the next level. Luna: So the second strategy — I'm guessing this is about integrations? Lucas: Bingo. Free tools are often walled gardens. They don't talk to Slack, or Notion, or your calendar, or your CRM. A paid SaaS can offer Zapier integrations, API access, or native connections that make it indispensable inside a workflow. The user isn't paying for the app itself. They're paying for how it fits into their existing system. Luna: That makes a lot of sense. I use Todoist with my Google Calendar and Slack, and once you have that loop, switching costs are real. Lucas: And that leads to the third strategy, which I think is the most underestimated: brand voice and intentionality. A free tool often feels generic. It's designed to offend no one. But a paid product can take a stance. Todoist has this very specific philosophy of 'clear mind, organized life.' They emphasize rapid capture and the Inbox zero approach. That identity creates a micro-community. Luna: So you're paying to be part of a tribe, almost. Lucas: Exactly. And this works for any category where the free alternatives are undifferentiated. Think about note-taking. Notion charges, but it's not just a note app — it's a 'workspace.' Roam Research charges for a very specific way of thinking called bi-directional linking. They're not competing with Apple Notes. They're offering a different philosophy. Luna: What about habit trackers? I've seen a ton of free ones, but then there's Streaks, which costs money and has a very loyal following. Lucas: Streaks is a perfect example. It's not a generic habit tracker. It focuses on a specific insight — that you should track no more than twelve habits at a time, and that streaks are the primary motivational mechanism. Everything in the product reinforces that one idea. The free alternatives usually let you add unlimited habits and then overwhelm you. Streaks says 'no, that's not how this works.' Luna: So the constraint itself becomes the value. Lucas: Right. And that's a design choice a free tool usually can't afford to make, because they want to appeal to everyone. As a solo developer, you have the luxury of being opinionated. In fact, you have to be. Luna: Let's bring this back to practical advice. Say someone listening wants to build a SaaS product that competes with a free alternative. What's the first thing they should do? Lucas: I think the first thing is to identify a user segment that is already paying for something related. If you're building a password manager, there are free ones, but people already pay for 1Password and Bitwarden. So you know willingness to pay exists. Then you find the pain point those paid tools don't solve. Maybe it's for families, maybe it's for freelancers who need to share passwords with clients temporarily. Luna: So don't compete with the free tier of your competitor. Compete with their paid tier by being better at one specific thing. Lucas: Exactly. And you can start small. Like, there's a solo dev I came across who built a simple app that just syncs bookmarks across browsers. There are free bookmark managers, but none of them handled a specific edge case — like bookmarking a whole folder of tabs at once. He built that one feature, charged $2 a month, and got a few hundred users. That's a viable micro-SaaS. Luna: I love that. It's the classic indie hacker move: find the corner case, own it, and don't worry about the mass market. Lucas: And that brings us to the last point I want to make. You don't need to outspend free. You need to out-care. Free tools are often maintained by a small team or neglected. A solo developer who responds to support emails within an hour, sends a personal onboarding note, and adds features users actually request — that's a differentiator that no free tool can match. Luna: And that's something anyone can do, regardless of budget. Lucas: Yeah. So if you're thinking about building a product in a space with free competitors, don't be discouraged. The free option is often just good enough for the casual user. Find the power user who's outgrown it. Give them a focused, opinionated, well-supported tool. And charge a fair price. Luna: Before we wrap, Lucas, I think a lot of this — the focus on power users, the intentionality — it reminds me of why listeners support shows like this. It's not just about information; it's about a community that cares about the details. And that's exactly the kind of thing that keeps us going without ads. Lucas: That's a really good point. If today's conversation gave you something useful, and you want to help us keep the podcast independent and ad-free, we do have a small way you can chip in. It's at buy me a coffee dot com slash fexingo. No pressure at all, but it helps us keep doing deep dives like this. Luna: Absolutely. And honestly, even just a coffee's worth of support goes a long way for a small show like ours. Lucas: Alright, so to wrap up today's angle: competing with free is less about price and more about depth. Pick a specific user, solve their specific pain, and charge for the value you create. That's the indie hacker way. Luna: And if you've got a story about paying for something you could get for free, we'd love to hear it. Drop us a note. Lucas: Until next time, keep building.