Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / Firing Bad Customers as a Bootstrapped Founder
Transcript
- Lucas: So there's this uncomfortable truth in bootstrapped software that almost nobody talks about until they've been burned by it: not every customer is worth keeping. Luna: That feels almost heretical in a world where we obsess over acquisition and top-line growth. Lucas: Exactly. But look at any bootstrapped founder who's been at it for more than a few years and they'll likely tell you about a customer they should have fired sooner. Josh Pigford, the founder of Baremetrics, wrote a really candid post about this back in 2016 — he cut $50,000 in annual recurring revenue by letting go of customers that were costing him more than they were worth. Luna: Wait — $50,000 in ARR? That's real money. What made those customers so toxic? Lucas: A few things. Some were constant support drains — they'd file ticket after ticket for features that weren't on the roadmap, or they'd demand custom integrations that only served them. Others were churn risks themselves, often late on payments or constantly negotiating discounts. Pigford realized that the time and emotional energy spent on those customers was pulling him away from building for the customers who actually loved the product. Luna: So the math was: ten percent of customers causing fifty percent of the headaches. I've heard that before in other contexts. Lucas: Right. And the thing is, for a venture-backed startup, you might just throw more bodies at the problem. But when you're bootstrapped, your support team is maybe one or two people, including the founder. Every hour you spend on a difficult customer is an hour you're not improving the product for the majority. Luna: What did Pigford actually do? Did he just cancel their accounts? Lucas: He did. But thoughtfully. He emailed each customer personally, explained that Baremetrics wasn't the right fit for their needs, and offered to help them transition to a competitor. Some were angry, but most appreciated the honesty. And within a few months, his net revenue actually increased — because the product got better for the customers who stayed, and those customers stuck around longer and referred more. Luna: So the short-term revenue hit was more than offset by improved retention and word of mouth. That's a powerful case study. Lucas: It is. And it's not just Baremetrics. I've talked to other bootstrapped founders who've done similar things. One founder I know in the project management space had a customer that represented about fifteen percent of his revenue, but they were constantly requesting custom features that would have broken the product for everyone else. He fired them, and within six months his NPS score jumped by twenty points. Luna: Wow. So firing customers can actually be a product strategy. It forces you to focus on a core audience. Lucas: Exactly. The key is identifying which customers are genuinely misaligned versus which ones you're just frustrated with. A good rule of thumb: if a customer's requests consistently pull your product away from its core value proposition, or if their usage pattern generates more support tickets than revenue, it's worth considering a conversation. Luna: How do you have that conversation gracefully? I imagine most founders are terrified of bad reviews or social media backlash. Lucas: You lead with empathy. Acknowledge that your product isn't meeting their needs, and that you want them to find something that works better. Offer a prorated refund or help setting up with an alternative. Most people respond well to honesty. And yes, you might get a negative review, but in my experience, the positive signal you send to your ideal customers — that you're serious about the product — outweighs that risk. Luna: It's like a weed in a garden. If you don't pull it, it chokes the flowers. Lucas: That's the metaphor exactly. And here's another angle: firing customers also changes your own psychology. When you know every customer chose to be there and is aligned with your vision, you build with more confidence. You're not second-guessing your roadmap for that one demanding client. Luna: I can imagine that also helps with pricing. When you're not afraid to lose customers, you're more likely to charge what you're worth. Lucas: Hundred percent. That's actually a side benefit. Okay, if today was useful to you in thinking about who you serve, know that the way we keep this show ad-free is through listener support. It's buy me a coffee dot com slash fexingo — all lowercase. That's what keeps these conversations going for the people who are building real products. Luna: Yeah, it's a small gesture that makes a big difference. We really appreciate it. Lucas: Back to the practical side — let's talk about how to actually decide which customers to fire. There's a framework I like called the 'support to revenue ratio.' You calculate the number of support tickets per dollar of revenue for each customer. If a customer's ratio is more than double your median, they're likely a candidate for a conversation. Luna: That's a clean metric. Do you also look at feature requests? Because some customers ask for things that would benefit everyone. Lucas: Great point. You differentiate between 'the product should do this' requests and 'I need this custom thing just for me' requests. The former are signals; the latter are distractions. If a customer's requests are mostly one-offs, that's a red flag. Luna: So it's not just about support cost, but about strategic alignment. Lucas: Right. And timing matters. If you're in early stages, you might need to tolerate more difficult customers because you're still figuring out product-market fit. But once you've got a solid core, you can start pruning. Pigford did it after he had about $400K in ARR, so he had enough revenue to absorb the hit. Luna: What about customers who are actually profitable but just annoying? Is that enough reason to fire them? Lucas: That's a harder call. If they're profitable and their requests are reasonable, you keep them. But if they're constantly negative or demanding your personal attention in ways that drain you, it might still be worth it. Founders' mental health matters. I've seen founders burn out because of one or two toxic customers. Luna: I think a key takeaway is that firing a customer shouldn't be a rash decision. It's a strategic move that requires data and self-awareness. Lucas: Absolutely. And if you do it right, you'll often find that the customers you fire end up thanking you — and your remaining customers get a better product. That's the paradox: subtraction leads to multiplication. Luna: I love that. So for anyone listening who's got that one customer they dread seeing in their inbox, maybe it's time to have an honest conversation. Lucas: Exactly. Thanks for being here, and we'll talk again soon.