Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Turn User Feedback into Product Roadmaps
Transcript
- Lucas: So Luna, we talk a lot about building software without outside money, and there's this recurring tension I see in every bootstrapped founder I know: you need user feedback to improve your product, but if you just build whatever your users ask for, you end up with a bloated mess and a roadmap that's basically a wish list from your most vocal customers. Luna: Right, and I've definitely been there. You get a support email that says, 'Can you add this one little thing?' and it seems so reasonable in isolation. But then you add it, and suddenly you've got ninety features that maybe three people wanted. Lucas: Exactly. And the tricky part is that listeners keep this show going, and they're often in that exact position. If these conversations are 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. Luna: Yeah, and it's ad-free because of that, which I appreciate. But back to the feature request problem — how do you actually turn feedback into a roadmap that doesn't just serve the loudest voice? Lucas: So the first step is to separate listening from obeying. You absolutely have to listen to every piece of feedback, but obeying is a whole different thing. A lot of founders conflate the two, and that's where the trouble starts. Luna: Yeah. So what's the practical difference? Lucas: Well, listening means you capture it, you acknowledge it, you thank the person. Obeying means you add it to the roadmap just because it was asked. A better approach is to run every request through a kind of feedback funnel — you collect everything, but then you categorize and score it before it ever touches your product plan. Luna: I like that. So you're not saying no to feedback, you're just filtering it. How do you score it? Lucas: There are a few dimensions that matter. First is frequency — how many different users have asked for this same thing? If it's one person, it's probably not a priority. Second is impact — would this feature unlock a whole new segment of customers, or is it just a nice to have for existing ones? And third is alignment with your core vision — does this fit the problem you're actually trying to solve? Luna: That makes sense. But even with scoring, don't you still end up with a list of everything ever requested? How do you keep it manageable? Lucas: You need a structured roadmap that's public. I know a solo developer who runs a CMS — a content management system — and he got so many feature requests that he was drowning. So he put up a public roadmap on his site, basically a Trello board, with three columns: under review, planned, and launched. Every request goes into under review, and then he moves things to planned only if they score high enough. Luna: And did that actually help? Or did it just give people more to complain about? Lucas: He said his churn rate dropped by eighteen percent within three months. Because even if he didn't build what they asked for, users could see that he was paying attention. They could see their request sitting in the under review column, and that transparency built a lot of trust. Luna: Eighteen percent is huge. So transparency itself is the feature, almost. Lucas: Exactly. It's not about giving everyone what they want. It's about making them feel heard. And that public roadmap does double duty — it also keeps him honest, because he can't quietly ignore a request once it's public. Luna: But what about the requests that never make it to planned? How do you tell a user no without losing them? Lucas: That's the art. The trick is to explain why you're not building it, but in a way that shows you understood their underlying problem. For example, someone asked this CMS developer to add a native commenting system. He didn't want to build it because it would add a lot of moderation burden. But instead of just saying no, he responded with, 'We don't have comment moderation capacity, but we do support Disqus and we have a guide to set it up.' He solved their problem without adding a feature. Luna: So you're redirecting them to an existing solution or a workaround. That's clever. Lucas: Yeah. And sometimes you can even turn a request into a plugin or an integration that someone else can build. That's how a lot of healthy ecosystems grow. Luna: I've also heard of founders using something called the one-in, one-out rule. For every new feature you add, you have to remove or simplify something else. Does that work? Lucas: It's a great constraint, especially for a bootstrapped team. It forces you to think about the trade-off of every addition. If you add a new settings panel, maybe you can consolidate three old settings into one. It keeps the product lean, and it also signals to users that you're serious about maintaining quality over quantity. Luna: But what about the feedback that's not a feature request at all — like bug reports or usability complaints? How do you handle those differently? Lucas: Bugs and usability issues should go straight to a separate track. They're not roadmap items in the same way — they're part of your baseline quality. If a feature is broken, you fix it before you build anything new. That's non-negotiable. But even there, you can apply the same funnel: is this affecting one user or a hundred? Is it blocking a key workflow or just cosmetic? Luna: So prioritization is really about impact and frequency, but also about your own time and energy. As a bootstrapped founder, you can't do everything. Lucas: Right. And that's where the scoring becomes really useful. You can use a simple formula: frequency times impact, divided by effort. It's not perfect, but it helps you say no to things that are low value, even if they're easy. Luna: I like that. But I also wonder, what about the request that comes in from a big customer who's paying you a lot of money? Do they get priority over the hundred small customers? Lucas: That's a classic dilemma. And the honest answer is, sometimes you have to say yes to a big customer to keep them. But you should do it consciously, not automatically. You can say, 'We'll build this because it's important to you, but we also need to make sure it doesn't break anything for our other users.' And then you add it to the roadmap with a clear label, like 'enterprise request'. Luna: So you're not just blindly following the money, but you're being transparent about your decisions. Lucas: Exactly. And that transparency extends to your whole process. A lot of the most successful bootstrapped founders I've seen share their roadmap publicly, and they even share the scoring criteria. It makes the whole thing feel fair, even when you have to say no. Luna: That makes me think of a founder I heard about who actually created a public vote where users could upvote features. Did that work? Lucas: It can work, but you have to be careful. Public voting can turn into a popularity contest, and the squeaky wheel gets the grease. But if you combine it with your own scoring — like letting users vote but then weighting it with your own strategic priorities — it can be a great signal. There's a forum hosting tool I know that does that, and it works well for them. Luna: So what's the biggest mistake you see bootstrapped founders make with feedback? Lucas: I think it's being too reactive. They get a feature request, they build it, and they never step back to see if it actually moved the needle. You need to close the loop: measure the impact of every feature you ship. Did it increase engagement? Did it reduce churn? Did it bring in new customers? If not, maybe you shouldn't have built it. Luna: So it's not just about choosing what to build, but also about measuring what you've built. Lucas: Right. And that measurement is what turns feedback into a real growth engine. Because once you see that a particular feature had a big impact, you know to double down on that kind of request in the future. Luna: That's a good place to wrap up. I think the takeaway is: listen to everything, but filter through a clear process, and be transparent about your decisions. Lucas: Yeah. And remember, your roadmap is not a promise — it's a conversation. Keep it open, keep it honest, and you'll build software that people actually want to pay for. Luna: And if you're nodding along, that coffee link is still in the description. We'll be back with more practical advice next week. Lucas: Until then, keep building.