Every solo founder reaches the point where customer demands are driving their roadmap in the wrong direction. Here is how to take back control — without losing your best customers.
The feature request problem is one of the most common traps for solo SaaS founders. You build something people want, they start paying, and then each customer has a slightly different vision for what the product should become. If you say yes to everything, you end up with a product that does everything for no one. If you say no to everything, you lose customers who had genuinely good ideas.
The fundamental issue is that customers optimise for their own use case. A feature that would be transformative for one customer might confuse every other customer, increase your support burden, and take two weeks to build. The customer who requested it won't understand why you hesitate — from their perspective, it's obvious.
Solo founders are especially vulnerable to this trap because there is no product team to absorb the social pressure. Every feature request is a direct conversation with a paying customer. Saying no feels personal — and sometimes, customers make it personal.
The response that works: acknowledge the request genuinely, explain your current focus, and leave the door open without a commitment. Do not apologise for not building it. Do not say "that's a great idea" if you have no intention of building it.
Template: "Thanks for this — I understand why [feature] would be useful for your workflow. Right now, we're focused on [specific priority] for the next [timeframe]. [Feature] isn't on our immediate roadmap, but I've noted the request. If this is a blocker for you, [alternative — manual workaround, integration, competitor who does this]. Happy to help you find the best path." End there. Do not promise to "consider it" unless you mean it.
The phrase "I've noted the request" is honest and non-committal. It doesn't say no permanently. It doesn't create an expectation. It acknowledges the feedback without promising action.
Build what your best customers need, not what your loudest customers want. Your best customers are the ones with the lowest churn, the highest plan, the most referrals, and the most specific problem that your product uniquely solves. When their requests overlap with the requests from other similar customers, that is a signal worth acting on.
The framework: for every feature request, ask three questions. How many customers have asked for this? Would building it help the customers most likely to pay the most and stay the longest? Does it align with the core problem the product solves, or does it expand scope in a direction that adds complexity without adding focus?
A demanding customer — one who sends multiple feature requests, escalates support tickets quickly, or threatens to cancel if specific features aren't built — is not automatically a problem. Sometimes they are your most engaged and valuable user. The question is whether their demands are pulling the product in a direction that serves the broader customer base or away from it.
The response that de-escalates most situations: acknowledge their frustration, explain the constraint honestly (you're one person, this takes longer than they'd like), and offer a realistic timeline if you intend to build it or a clear no if you don't. Ambiguity is what makes demanding customers more demanding — they keep asking because they don't have a clear answer.
Firing a customer is the right move when: their demands consume a disproportionate amount of your time relative to their plan value, they are consistently abusive to you in communication, their use case is fundamentally misaligned with your product's direction and no amount of feature development will fix that, or they have threatened to chargeback or harm your reputation as a negotiating tactic.
How to do it: issue a full refund for the current period. Send a calm, professional email explaining that the product isn't the right fit for their use case and offering to help them find an alternative. Do not engage with arguments or escalation. The refund closes the transaction cleanly.
The counterintuitive result: most founders who fire a customer for the first time report feeling relieved within 24 hours and find that the customer's departure frees up significant time and energy. The customers who make you dread opening your email are almost never your best customers.
Tell Marcus your current feature request situation and what's taking up your time. You'll get a specific recommendation in session one.
Try GhostCoach free →14-day free trial · cancel anytime