Saying no to feature requests kindly.
Thank them specifically, say no clearly with a one-sentence reason, offer a workaround if one exists, and log their vote. A fast honest no keeps more customers than a slow fake maybe.
How do I decline a feature request without upsetting the customer?
Use the four-part reply: appreciate specifically, decline clearly, redirect usefully, leave the door open. It fits in four sentences.
Example: "Thanks, you're right that exporting to CSV would help with your quarterly reports. We're not building that this quarter; we're keeping the product focused on scheduling. In the meantime, the print view gets you most of the way there. I've logged your vote and I'll email you personally if this changes."
Why is a clear no better than 'maybe someday'?
"Great idea, adding it to the list!" feels kind and costs you later: the customer waits, checks back, and churns disappointed, now with a story about being ignored.
A clear no lets them decide with real information. Some leave, they needed a different product. Most stay, and trust you more because your yes now means something.
Which feature requests should I actually build?
- 1Count votes, but weight them: one request from five different customers beats five requests from one loud customer.
- 2Listen for the problem under the feature. "I want CSV export" often means "I need to show my accountant the numbers", which might be a share link, not an export.
- 3If it serves your core customer's core workflow, queue it. If it serves an edge case, decline it, every yes to the edge is a tax on the center.
Quick answers.
Should I have a public roadmap or feature-vote board?
Yes, once requests repeat, it converts complaint energy into participation. Ours is at /roadmap, and it's where every request lands.
What if a big customer threatens to leave over a feature?
Same rules. If it fits the core, their size moves it up the queue honestly. If it doesn't, a bespoke feature makes them your boss at one customer's salary.
Do I tell people when I build something they asked for?
Always, personally, by email. "You asked for this in March, it shipped today" is the single best retention message that exists.
Build the thing this guide is about.
Stencil turns your idea into working subscription software — no code required.