Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Built a SaaS That Replaced a Full-Time Employee
Transcript
- Lucas: So, Luna, I want to talk about a specific kind of SaaS that I think a lot of listeners have probably wished existed at some point — software that replaces a full-time employee. Luna: That sounds like the dream for a solo dev. Build something that does what a person does, but for a fraction of the cost. Lucas: Exactly. And there's a great example I came across recently. A developer named Sarah Chen, who was laid off from a mid-sized marketing agency about two years ago. She had a background in project management and a bit of coding. Luna: So she knew the pain point firsthand. Lucas: Right. She noticed that her team had a dedicated person — basically a project coordinator — whose entire job was scheduling meetings, chasing down updates, and compiling weekly status reports. That was their full role. And Sarah thought, 'I could automate 80 percent of this with a simple tool.' Luna: And she built it. Lucas: She did. She used her severance — about ten thousand dollars — to live on while she coded for three months. The result was a tool she called TaskButler. It's a SaaS that integrates with Slack and email, and it automates the scheduling, the reminders, and it generates a weekly report automatically. Luna: So instead of a human spending ten hours a week on that, the software does it in seconds. Lucas: Exactly. And the pricing was key. She set it at two hundred dollars per month per team. Compare that to a full-time project coordinator salary — say fifty thousand a year, plus benefits — and you're talking a fraction of the cost. For a small agency, that's a no-brainer. Luna: But how did she get her first customers? She didn't have a network in tech, I'm guessing. Lucas: She actually used LinkedIn groups for project managers. Not the big ones with thousands of members — she found smaller, niche groups for agency PMs. She joined, participated genuinely, and eventually offered a free version to a few people in exchange for feedback. Luna: That's grassroots, but it worked. Lucas: It did. Within six months, she had fifteen paying customers. Mostly small marketing and design agencies. Her MRR hit three thousand dollars around month seven. Luna: And then it scaled? Lucas: It did. By month twelve, she was at fifteen thousand MRR. That's fifty customers at two hundred dollars per month each. And she was still the only person working on the product. Luna: This is the kind of story that makes me think about the 'jobs to be done' framework. She didn't just build a tool — she replaced a job. Lucas: That's exactly right. She identified a job that people were hiring a human to do, and she offered a software alternative. It's a classic Christensen insight, but it's hard to execute. Luna: And what about the risks? I mean, what happens if a client's workflow changes? Or if the software has a bug that causes a missed deadline? Lucas: Great question. Sarah actually had that happen. One of her early customers had a critical meeting delayed because TaskButler's calendar integration glitched. She handled it by being incredibly responsive — fixed it within hours, and personally apologized. That turned the customer into a loyal advocate. Luna: So being a solo dev meant she could move fast. Lucas: Exactly. But also, there's a ceiling. As she grew, she started getting requests for custom features — like different report formats, or integrations with Asana and Trello. She had to decide: do I build those, or stay focused on the core? Luna: And what did she do? Lucas: She built the most requested ones — Trello and Asana integrations — which actually opened up a new market. Now her tool works with those platforms, so it's not just for teams using Slack and email. Luna: Smart. That probably increased her addressable market significantly. Lucas: It did. And the interesting thing is, she's now exploring AI features — like using natural language to generate the weekly report, or even suggesting next steps based on the project status. That's a natural evolution. Luna: So the next version of TaskButler might replace not just the coordinator, but also some of the thinking that goes into planning. Lucas: Exactly. And I think that's the direction a lot of these 'replacing a role' SaaS products will go. But the key is starting with one very specific, repetitive task that people are already paying a human to do. Luna: And speaking of value — you know, we talk about these tools on the show without any ads. That's a deliberate choice. Lucas: Yeah, we've always felt that if the content is useful, listeners will support it in their own way. And some of you do, which keeps it ad-free. Luna: If today's tech conversation gave you something usable, you can support that choice at buy me a coffee dot com slash fexingo. No pressure — just an option. Lucas: Right. And now back to Sarah's story — I think one of the most instructive parts is how she priced it. Luna: Two hundred dollars per month. That's not trivial for a small agency, but compared to a salary, it's nothing. Lucas: And she didn't underprice it. She could have charged fifty dollars, but she would have had to get four times as many customers to hit the same revenue. By pricing at the value of what she replaced, she made the math easy for buyers. Luna: That's a lesson a lot of indie hackers struggle with — they price based on their costs, not on the value to the customer. Lucas: Exactly. And she also offered a monthly plan, not annual. She wanted to keep the commitment low so people would try it. And that worked. Luna: What about churn? Did she have a lot of people cancelling after a month or two? Lucas: Surprisingly low — like five percent monthly churn in the early days. She attributes that to the fact that once you set up the automation, it becomes part of your workflow. Cancelling would mean going back to manual work. Luna: So the stickiness came from integration depth. Lucas: Exactly. And she made sure the setup was easy — literally a five-minute configuration. That lowered the barrier to entry. Luna: So for any solo dev listening, what's the takeaway? Find a repetitive task that people are paying a human to do, build a simple tool that automates 80 percent of it, price it at a fraction of that human's cost, and make it easy to try. Lucas: That's the formula. But I'd add one more thing: start with a very specific niche. Sarah didn't build for all project managers — she built for small marketing agencies using Slack. That focus made her product obvious to her first customers. Luna: And now she's expanding. I think that's the ideal path: narrow launch, then broaden. Lucas: Exactly. And she's still solo. She's thinking about hiring help for customer support, but she's not in a rush. At fifteen thousand MRR, she's earning a good living and has the freedom to choose what to build next. Luna: That's the indie hacker dream, isn't it? Lucas: It really is. And it's replicable if you find the right job to replace. Luna: Well, thanks for that story, Lucas. I'm going to look up Sarah's blog — I think she writes about her process. Lucas: She does. I'll put a link in the show notes. And if you want to support the show, you know where to find us. Luna: Yeah, buy me a coffee dot com slash fexingo. Thanks for listening.