Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use Customer-Sourced Feature Requests
Transcript
- Lucas: There's this moment every bootstrapped founder knows. You open your inbox and there it is — a carefully written email from a paying customer, describing the one feature that would make your software perfect for them. And your gut says 'yes, we should build that.' But the data says something else. Luna: Right, because every feature request sounds urgent when it comes from someone who's already paying you. Lucas: Exactly. And that's the trap. The most dangerous thing a bootstrapped company can do is build everything customers ask for. You end up with a bloated product, a confused user base, and a development team that never ships anything meaningful. Luna: So how do you separate the signal from the noise? I mean, you can't just ignore your customers. Lucas: You can't. But you can build a system that turns feature requests into strategic data. And the companies that do it well treat requests almost like votes in an election — they're weighted, they're transparent, and they're tied to real outcomes. Luna: Give me an example. Who's doing this well? Lucas: Let's start with Basecamp. For years, they've had a famously strict policy — they say no to roughly 90 percent of feature requests. Jason Fried wrote about this back in 2016. Their reasoning is that every new feature adds complexity, and complexity is the enemy of clarity. Instead, they use a system where they ask customers three questions: What problem are you trying to solve? How often does it come up? What's the workaround you're using now? Luna: That workaround question is key. If there's a decent workaround, the feature might not be that critical. Lucas: Exactly. Basecamp found that most requests had a workaround that took less than five minutes. So the real need wasn't a new feature — it was often better documentation or a small tweak. By saying no, they kept their product focused. And their churn rate? It's been below 2 percent for years. Luna: But saying no that often — doesn't that frustrate customers? Lucas: It can, if you don't explain your reasoning. But Basecamp is transparent. They publish a public roadmap and they reply to every request with a thoughtful explanation. Customers actually respect that. There's research from the Harvard Business Review showing that customers who feel heard are more loyal, even if their specific request isn't granted. Luna: So the transparency itself becomes a retention tool. I like that. Lucas: Now let's look at a smaller bootstrapped company: MailerLite. They're an email marketing platform, competing with the likes of Mailchimp. They built a public feature request board where customers can submit ideas and vote on others. But here's the clever part — they weight the votes based on customer tier. A paying customer's vote counts more than someone on the free plan. Luna: So it's not just a popularity contest. It's aligned with revenue. Lucas: Exactly. And they also tag requests with the number of customers who would benefit, plus the estimated development effort. They built a simple scorecard: impact times urgency divided by effort. That formula tells them which features to build first. And they publish the scores publicly. Luna: That's pretty transparent. Does it work? Lucas: It does. Within six months of launching that board, they saw a 30 percent increase in paid upgrades. Customers who engaged with the board were more likely to convert and less likely to churn. The board became a community hub — customers would discuss workarounds and even help each other without MailerLite having to build anything. Luna: So the board itself became a feature. That's smart. Lucas: And it's a pattern we see in other bootstrapped companies too. There's a tool called Canny that helps companies run these boards — ironically, Canny itself is bootstrapped. Their CEO, Andrew, says the biggest mistake founders make is treating feature requests as isolated data points rather than as signals about what customers value. Luna: So how do you operationalize that? What's the framework? Lucas: I'd say there are four steps. First, collect all requests in a single, public place. Second, tag each request with customer tier, frequency, and workaround existence. Third, score them using a simple formula — something like 'value to customers' times 'strategic fit' divided by 'development hours'. Fourth, publish the roadmap and update it monthly. Luna: And then you have to actually build the top-scoring features. Otherwise the whole exercise is performative. Lucas: Right. But here's the counterintuitive part — sometimes the best thing you can build is nothing. One bootstrapped founder I know runs a project management tool for small agencies. He gets hundreds of feature requests each year. He builds maybe ten. But he responds to every single one with a personal video message explaining why he's not building it. His NPS score is 72. Luna: That's insanely high. What's his secret? Lucas: He says the secret is honesty. He tells customers: 'I could build this feature, but it would make the product harder for your colleagues to use. I'm trying to keep it simple.' Customers appreciate that he's thinking about the whole user base, not just them. And they stay. Luna: So it's about managing expectations, not just fulfilling requests. Lucas: Exactly. And that's where a lot of founders trip up. They think they have to say yes to keep customers happy. But saying yes to everything is a guarantee that you'll end up with a product that's mediocre for everyone. The most valuable feature is often the one you don't build. Luna: I want to dig into the scoring formula a bit more. You mentioned value, strategic fit, and effort. How do you measure strategic fit for a bootstrapped company? Lucas: Strategic fit is about whether the feature aligns with your core value proposition. If you're a simple invoicing tool and someone asks for a full CRM, that's low strategic fit. You'd be moving into a crowded space where you can't compete. Instead, you integrate with a CRM and let the customer choose. MailerLite does this — they don't build landing page builders, they integrate with tools that do. Luna: So the scoring system forces you to be honest about what you're trying to be. Lucas: Yes. And it also helps you say no gracefully. When a customer sees that their request scored low on strategic fit, they understand the reasoning. It's not arbitrary. And you can point them to an integration or a workaround. Luna: But what about the features that customers don't ask for but desperately need? Like, how do you balance customer-driven development with innovation? Lucas: That's the classic Henry Ford quote — if I asked people what they wanted, they'd have said faster horses. Bootstrapped founders need to reserve maybe 20 percent of their development time for unrequested features that they believe will move the needle. Basecamp does this. They call it 'slow burn' projects. Things like their Hill Charts feature — no one asked for it, but it became a differentiator. Luna: So it's a mix. Eighty percent customer-driven, twenty percent visionary. Lucas: Roughly. And the visionary features should be tested with a small group before full rollout. That minimizes risk. One of the best examples I've seen is from a bootstrapped company called Baremetrics. They built a feature called 'Forecast' that used machine learning to predict future revenue. No one asked for it. But they tested it with ten customers, got great feedback, and now it's one of their top selling points. Luna: So the key is having a system that lets you manage both the pull and the push. Lucas: Exactly. And that system starts with how you listen. If you're just reacting to emails, you'll drown. But if you create a structured, transparent process, you turn feature requests from a distraction into a strategic asset. Luna: I think a lot of our listeners could use that framework. And if you're finding these conversations useful for what you're building or running, a couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo, if you've gotten something out of them. Lucas: Yeah, and it makes a real difference. Keeps the whole thing ad-free and independent. Luna: So, circling back — what's the one thing you'd tell a founder who's drowning in feature requests? Lucas: Don't build anything until you've asked the customer three things: their problem, the frequency, and their workaround. If the workaround is good enough, you've just saved yourself weeks of development. And the customer feels heard. That's the paradox — sometimes the best way to serve your customers is to not build what they ask for. Luna: But to build something they might value even more: focus. Lucas: Exactly. Focus is the feature that never gets requested but always pays off.