What is a feature request? Definition and examples
A suggestion from a user or customer for something new the product should do, or something it should do differently.
Feature request: A suggestion from a user or customer for something new the product should do, or something it should do differently.
Feature requests often describe a solution (“add a CSV export”) when the useful part is the need behind it (“I need to share bookings with my accountant”).
Grouping requests by need and counting who asks is how teams turn them into priorities.
Example
- “Could invoices show our company name?”
- “Dark mode for the docs would be lovely.”
- “Let me split the payment with friends.”
From request to decision
- 1
Capture it in their words
Keep the original request, with who asked and where they were in the product.
- 2
Find the need
Ask what they are trying to do. “Export to CSV” might really be “share with my accountant”.
- 3
Group similar requests
Requests for the same need, worded differently, belong together. The count is your demand signal.
- 4
Decide and tell them
Yes, not now, or no. Each answer is better than silence, and a reply builds trust.
What to record with each request
- Who asked, and what plan or segment they are in.
- The page or screen they were on.
- The problem behind it, in their words.
- How many others asked for the same thing.
Where Bopmigo fits
People send requests from the Feedback window, and Bopmigo groups requests about the same thing so you can see how many asked.
Questions
Should I build every requested feature?
No. Look for the need behind it, how many people share it, and whether it fits your product.
Where should feature requests go?
One place your whole team can see, grouped by need. Scattered across email and chat, they get lost.
How do I say no to a feature request?
Thank them, explain briefly why not now, and offer a workaround if there is one.