Latest / The Indie Hacker Podcast with Fexingo: Solo Developers, SaaS Side Projects, and Independent Tech / How a Solo Dev Built a SaaS With No Customer Support
Transcript
- Lucas: So there's this solo dev, goes by the handle CodeCactus on Indie Hackers. He built a SaaS product that processes sales tax filings for small e-commerce businesses — think Shopify sellers who dread filing multi-state returns. Luna: Right, because sales tax is a nightmare if you sell across state lines. What's the product called? Lucas: It's called TaxTally. And the wild part is, he designed it with literally zero customer support. No live chat, no email ticketing, no phone line. Just a knowledge base and a bug-report button. Luna: Zero support? For a product that handles people's tax filings? That sounds like a recipe for disaster. Lucas: That's exactly what I thought when I first saw it. But here's the thing — the product has been live for 18 months, has 2,400 paying customers, and averages less than five support tickets per month. Luna: Five tickets a month? That's insane. How did he pull that off? Lucas: The core strategy is what he calls 'proactive error messaging.' The software validates every input in real time before the user can submit anything wrong. If a field is missing or a number looks suspicious, a clear plain-English message pops up explaining exactly what needs to change and why. Luna: So it's like having a support agent baked into the UI before the user even knows they have a problem. Lucas: Exactly. And the messages are tested — he A/B tested different wording to see which ones reduced confusion. He also embedded a short explainer video next to every complex field. Not a full tutorial, just a thirty-second clip showing exactly what to enter. Luna: That's smart. But what about edge cases? Like a user whose situation doesn't match the standard flow? Lucas: That's where the knowledge base comes in. Every proactive error message includes a link to a specific knowledge base article. The articles are written in a very conversational tone — like 'Hey, we know this is confusing. Here's how other sellers handle it.' He tracks which articles get viewed most and improves them every week. Luna: And the bug-report button — is that separate from support? Lucas: Yeah, it's a one-click button that sends a technical log to a private Slack channel. It doesn't open a ticket. The user just gets an automated confirmation: 'We received the report. We'll fix it.' No back and forth. The dev fixes the issue and pushes an update, often within hours. Luna: So the users are basically debugging for him, but they don't have to talk to anyone. I can see how that would reduce frustration. Lucas: Right. And the interesting thing is, many customers actually prefer it. He surveyed users and found that over 60% said they chose TaxTally specifically because they didn't have to talk to a human. They wanted a self-serve experience. Luna: That makes sense. A lot of indie hackers are introverts themselves. But doesn't zero support lead to higher churn for people who do get stuck? Lucas: Surprisingly, no. His churn rate is under 3% monthly. He compares it to using a vending machine — if the machine works, you don't need a cashier. But if it breaks, you just want a refund button, not a conversation. So he also built an instant refund option: any customer can cancel and get a full refund for the current month with one click. No questions asked. Luna: That's a bold move. Doesn't that encourage people to churn just to get free months? Lucas: He thought it might, but the data shows only about 1% of refunds are what he calls 'exploitative.' Most people refund because they genuinely couldn't make the product work. And after refunding, about 20% actually come back later and resubscribe. Luna: So the refund becomes a trust signal. That's clever. But what about onboarding? I imagine that's where most support tickets would come from. Lucas: He spent four months perfecting the onboarding flow. It's a seven-step wizard that only lets you proceed if each step is completed correctly. There's no way to skip ahead. And each step has a progress indicator with estimated time left. He found that showing '2 minutes remaining' reduced drop-off by 40%. Luna: That's a great detail. So the whole product is designed to prevent questions before they happen. It reminds me of the concept of 'support as a feature' — where the absence of support is the feature. Lucas: Exactly. And the biggest trade-off is that he can't handle complex cases. If a user has a truly unique tax situation — like selling in all fifty states with weird exemptions — TaxTally just won't work for them. He's okay with that. He'd rather lose that customer than add a support team. Luna: That narrows his total addressable market, but it keeps his operational costs near zero. He's essentially selling to the 80% of e-commerce sellers who have straightforward needs. Lucas: Exactly. His monthly operating costs are just server hosting and a couple of API fees — under $200 a month. With 2,400 customers paying $19 a month, that's over $45,000 in monthly revenue. Almost all margin. Luna: And no support salaries. That's the dream for a solo dev. But I wonder — is this replicable for other types of SaaS? Lucas: I think it depends on the complexity of the domain. TaxTally works because sales tax filing is rule-based and predictable. Something like project management software, where user goals are varied and subjective, would be much harder to make support-free. Luna: Yeah, that makes sense. So the key is to pick a problem that can be fully automated and has clear right-or-wrong answers. Lucas: Right. And then invest heavily in the UX to prevent confusion. He actually says his development time was split roughly 40% on core logic and 60% on error handling and messaging. Luna: That's a huge upfront investment. But it pays off over time because he never has to scale a support team. Lucas: And it gives him true freedom. He can take a week off and the product just runs. No tickets piling up. No customers waiting for replies. Luna: That's the indie hacker dream, right? Passive income with minimal maintenance. Speaking of which, I know this show is ad-free by design. If you find value in these deep dives and want to support that choice, you can throw a coffee at the team at buy me a coffee dot com slash fexingo. Lucas: Yeah, we keep it ad-free exactly so we can talk about real strategies like this without selling anything. And listener support is what makes that possible. So thanks to anyone who contributes. Luna: Alright, back to TaxTally. One thing I'm curious about — how does he handle new feature requests without support channels? Lucas: He uses a public Trello board where users can vote on features. But he doesn't respond to comments. He just looks at the votes and builds what's most requested. There's no conversation. Luna: So it's a one-way feedback loop. That works if you trust your own judgment. Lucas: He's very data-driven. He also tracks feature usage with simple analytics. If a feature isn't used, he removes it. He's ruthless about keeping the product simple. Luna: I love that. So the takeaway for indie hackers is: if you can design your product to be self-explanatory, you can eliminate the biggest operational headache. But it only works for certain domains. Lucas: Exactly. TaxTally proves that for rule-based problems, zero support is not just possible — it's a competitive advantage. Customers value speed and autonomy over human interaction. Luna: And you get to keep your weekends. That's a pretty good trade-off.