Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use the 80-20 Rule to Double Profit
Transcript
- Lucas: So here's a question that keeps bootstrapped founders up at night: How do I grow profit without adding more people or raising prices? Luna: That's the holy grail, isn't it? More output, same input. Lucas: Exactly. And the answer might be hiding in a principle you already know: the 80-20 rule. But applied in a way that feels almost counterintuitive. Luna: If today's episode helps you think differently about your own business, that's the whole point. The reason this show stays ad-free is listener support — buy me a coffee dot com slash fexingo. Seriously, it's how we keep doing this. Lucas: Yeah, that's the thing. We put everything into making each episode actionable, and it's listeners like you who make that possible. So if you find value here, that link is there. Now let's get into the meat. Lucas: I've been looking at a case study from a bootstrapped project management tool called Flowt. They do about two million dollars in annual recurring revenue. The founder, Maya Chen, runs a lean team of eight people. Luna: I know Flowt. They have that clean interface. I didn't know they were bootstrapped. Lucas: Completely. And last year, Maya hit a wall. Support tickets were eating the team alive. They had one full-time support person and tickets were piling up. So she did something that sounds crazy at first. She ran a correlation analysis between feature usage and support tickets. Luna: Like, which features are causing the most pain? Lucas: Right. She pulled a simple SQL report — every feature, how many users touched it, and how many tickets referenced it. What she found was textbook Pareto: 80 percent of support tickets came from 20 percent of features. Luna: That's not surprising in itself — the Pareto principle shows up everywhere. But what did she do with that information? Lucas: She deprecated those features. And not just the features — she effectively fired the customers who exclusively used those features. Luna: Wow. That's bold. How many customers are we talking about? Lucas: About 15 percent of their customer base. These were users who only used the Gantt chart view and the custom field builder — two features that were notoriously buggy and generated half the support tickets. Maya gave them a six-month migration path: switch to a simpler workflow or move to a different tool. Most of them left. Luna: And what happened to revenue? Lucas: Revenue dipped about 8 percent over the next quarter. But here's the kicker — the support load dropped by 60 percent. That freed up the support person to focus on customer success and upsells. Within two quarters, revenue recovered and profit margin went from 22 percent to 41 percent. Luna: So she doubled her profit margin by losing customers. That's the opposite of the growth-at-all-costs mantra. Lucas: Absolutely. And this is a pattern I see more and more among bootstrapped founders. They realize that not all revenue is good revenue. Some customers cost more to serve than they bring in, especially when you factor in support time and feature maintenance. Luna: That's a hard lesson for founders who are used to counting every dollar of MRR. How do you even identify which features are the culprits? Lucas: Maya's approach was pretty straightforward. She tagged every support ticket with the feature it related to — they used a simple tag system in Intercom. Then she ran a monthly report that showed the top ten features by ticket volume, normalized by usage. So a feature used by 100 customers that generated 50 tickets is way worse than one used by 1,000 customers that generates 50 tickets. Luna: So you're looking at tickets per active user per feature. That's a more honest metric than raw ticket count. Lucas: Exactly. And she found that the feature with the highest tickets per user was the custom field builder. It was used by only 8 percent of customers but accounted for 22 percent of tickets. And the Gantt chart was similar. Luna: Those are features that sound important. A project management tool without a Gantt chart? That feels like a gap. Lucas: That's the fear. But Maya asked her remaining customers — the ones who used the core features — and they said they didn't care. They wanted reliability and speed over a clunky Gantt chart. She also found that many of the Gantt chart users were actually using it to print timelines for clients, not to manage projects internally. That was a use case that a simple export to a spreadsheet could handle. Luna: So she offered an alternative. That's smart. You're not just cutting people off — you're giving them a bridge. Lucas: Right. She created a one-page PDF guide showing how to use the existing task list view with dates and dependencies to replicate 90 percent of what the Gantt chart did. Then she offered a three-month grace period where support would help them transition. After that, the feature was removed. Luna: And how did customers react? I imagine some were angry. Lucas: A vocal minority. About five percent of the affected customers wrote angry emails. But Maya handled it by being transparent: 'We're removing this feature because we can't maintain it at the quality you deserve. Here's a better way to achieve the same thing.' Most people appreciated the honesty. Luna: I think that's a key lesson. Bootstrapped founders often feel obligated to keep every feature because they don't want to disappoint. But that obligation can kill the business. Lucas: Exactly. The sunk cost fallacy is huge here. You built the feature, you have customers using it, so you feel you have to maintain it. But the real cost is the opportunity cost of not improving the core experience. Luna: So what's the takeaway for a founder listening right now? How do they start? Lucas: Step one: tag your support tickets by feature for at least one month. If you don't have a ticketing system, a simple spreadsheet works. Step two: calculate tickets per active user per feature. Step three: identify the features where that ratio is more than double the average. Those are your candidates for deprecation. Luna: And what about the customers who use those features? Do you always try to migrate them, or sometimes you just let them go? Lucas: Maya's rule of thumb: if the feature has an alternative in your product, migrate. If not, and the feature is core to their workflow, help them find another tool. It's painful in the short term, but in the long term, you're building a product that's simpler, faster, and more profitable. Luna: It's like pruning a tree. You cut off the dead branches so the healthy ones can grow stronger. Lucas: Exactly. And Flowt's story proves it. Eighteen months later, they're at two point four million ARR with a 45 percent margin. They never raised VC. They just had the courage to cut. Luna: I think that's a great note to end on. Thanks, Lucas. Lucas: Thanks, Luna. For everyone listening, we'll be back next week with another story from the bootstrapped trenches.