I've been brainstorming on ways to help your users prioritize your features set.
There are a few non-starters I first had to solve:
Not all votes should be consider equal. Paying users should get higher priority. VERY satisfied users should get more priority others.
Votes should be garbage collected and they should lower in rank over time.
You can't show your entire feature list as there may be too many features.
You have to keep the form simple. Can't take more than 30-60 seconds.
I came on upon this solution.
After a week of usage you prompt for the NPS (net promoter score) question.
"On a scale of 1 to 10 how likely are you to recommend our product to another user?"
then after that you ask them ONE question.
"Which of the following two features do you think we should prioritize?"
Then you pull two random features from your roadmap.
Then you ask one more question:
"If you could have ONE feature in X what would it be?"
Here's the logic.
The NPS can be used along with their membership information (do they pay) to prioritize votes. If they knew about NPS prioritization they could game you but they can't game paying.
The pairwise comparison is used to rank features. Votes are calculated a rank based on their age, NPS score, and their membership level.
The final question is used by you to manually compute the roadmap.
You can add new features but they should be based on manually interpreting the final question.
I'd kill for something like this in Polar.
If you guys want to steal this and make a startup out of it feel free - just make me an advisor and give me stock :-P