Prioritize your product roadmap with customer rankings
Too many feature requests and limited time to build? Ask customers to rank the features they want. See what matters across the group—and where paying customers and prospects want different things.
Go beyond feature upvotes
Upvotes show interest in an idea, but not which feature someone would put ahead of another. A ranked poll asks customers to compare the options, so second and third choices contribute too.
- Collect the ideas you missed. Let customers propose missing features or suggest removing options that no longer belong. Enable additions, removals or both; review proposals and apply approved changes in a new round. Process comments can be enabled separately for voting, observation and results.
- Understand whose priorities differ. Ask about plan, company size or customer stage, then filter results by the answers. Check whether a popular request matters across your audience or mainly to one segment.
- Include customers in different languages. Offer translated versions of the same poll, with everyone contributing to the same result.
What a ranked result can reveal
Imagine eight features competing for the next release. In this fictional example, Mobile app gets the most first choices. SSO and access controls leads when every ranking position earns points, because it appears consistently near the top.
Illustrative comparison: 60 synthetic complete ballots, scored from 8 points for first place to 1 for last. All ballots have equal weight. This is not the live poll result.
| Feature | First choices | Ranked points |
|---|---|---|
| SSO & access | 12 | 377 |
| API & webhooks | 11 | 350 |
| Mobile app | 17 | 307 |
| Custom reporting | 4 | 284 |
| Slack integration | 8 | 274 |
| Roles & permissions | 0 | 222 |
| Audit log | 8 | 210 |
| Bulk import | 0 | 136 |
Split the same sample by customer type: SSO leads among enterprise teams; Mobile app leads among smaller teams. That gives you a useful planning question: whose needs should this release serve?
This comparison stays fixed. The live poll below uses its configured voting method and includes visitor ballots.
Run your own feature prioritization poll
-
Prepare the features to compare.
Choose features competing for the same planning cycle. Merge duplicates and describe the problem each one solves; add images or links where useful. A shortlist is optional; candidate limits depend on your plan and counting method.
-
Invite the customers you need to hear from.
Adapt the preset’s questions to your audience and share the poll. Enable partial rankings when people cannot assess every feature.
-
Bring the result into planning.
Compare the overall ranking and relevant segments, then weigh effort, dependencies and strategy. Customer preference is useful input—not proof of willingness to pay or a delivery commitment.
Try the live roadmap poll
What should a B2B workspace build next? Rank the eight example features and submit your ballot. Your vote counts in this demo.
Before you start
Does Rezon replace our roadmap tool?
No. Use Rezon to collect and compare customer priorities, then take that input into your existing roadmap and delivery workflow. It does not manage your backlog or schedule releases.
Can separate groups contribute to one planning poll?
Yes. In a separate invited-panel poll, you can include results from teams or regions ranking the same features against the same question. Each source poll contributes one collective ballot with a weight you set, so group size does not automatically determine influence. Finalize the options and disable candidate-change suggestions in the source polls before linking. This changes influence; filtering customer segments only compares their preferences.
What if only a few customers respond?
Treat the result as feedback from those participants, not a verdict from your whole market. Check who is missing before acting, and avoid drawing firm conclusions from very small segments.