At a glance
Key takeaways
- Capture the outcome the customer wants, not only the feature name they suggested.
- Use votes as one signal beside customer impact, frequency, strategy, and effort.
- Keep the private inbox broader than the public roadmap.
Why feature requests get messy so quickly
The same idea arrives in five different forms: a support ticket, a sales note, an email, an in-app message, and a roadmap comment. If each channel becomes its own backlog, nobody knows whether demand is growing or simply being duplicated.
The other problem is language. Customers naturally suggest a solution. Your job is to understand the job they are trying to finish, who is affected, and what happens today when the capability is missing.
A simple feature request management workflow
- Capture every request in one inbox with the original customer wording and context.
- Clarify the problem, expected outcome, urgency, and current workaround.
- Group requests that describe the same underlying need.
- Evaluate demand alongside strategy, customer impact, retention risk, and effort.
- Publish only requests that are useful for wider validation or roadmap communication.
- Update the status when the idea is received, planned, in progress, shipped, or declined.
How to prioritize feature requests fairly
Fair does not mean “most votes wins.” It means using the same questions for every request. A feature with ten votes from casual users may matter less than a workflow blocker affecting three long-term customers. A popular idea may also pull the product away from its purpose.
Write down the criteria your team trusts and keep them simple enough to use. For a small SaaS, customer impact, frequency, strategic fit, confidence, and effort are usually enough to start.
| Signal | Question to ask |
|---|---|
| Customer impact | What becomes possible or less painful if we solve this? |
| Frequency | How often does the problem appear across customers and workflows? |
| Strategic fit | Does solving it strengthen the product we are trying to build? |
| Confidence | Do we understand the problem well enough to choose a solution? |
| Effort | What is the smallest useful version and its ongoing cost? |
How to manage feature requests in TellTide
Enable the Feature request category in the TellTide widget so users can describe ideas without mixing them with bug reports or reviews. New requests appear in the Features view of the inbox, where you can search, review context, and update status.
When a request is ready for wider visibility, show it on the public roadmap and place it in the appropriate roadmap stage. Customers can then vote and comment while your team keeps control of the decision.
Questions teams ask before choosing this workflow
What is feature request management?
Feature request management is the process of collecting customer ideas, clarifying the underlying need, grouping related requests, prioritizing them, and communicating decisions.
Should every feature request go on a public roadmap?
No. Keep the intake inbox broad and publish only requests that are clear, appropriate for public discussion, and useful for validation or communication.
How do I track feature requests without a spreadsheet?
Use a feature request tool with structured intake, searchable inbox states, voting, and a public roadmap so context and progress stay connected.
Abhijith
Founder of TellTide, writing practical guides about product feedback, feature requests, and public roadmap workflows for SaaS teams.