Feature Request Survey Questions
22 Feature Request Survey Questions to Prioritize Your Roadmap
Collect feature ideas and find the ones worth building
Feature request surveys help you systematically collect user ideas, understand the problem behind each request, and prioritize by impact. Use these feature request survey questions to build a roadmap driven by real user needs.
No credit card required
When to send
Run feature request surveys quarterly as a standing roadmap input, after releasing a major feature (to capture what is still missing), or when you notice a cluster of similar support requests that might signal a gap.
19 Feature Request survey questions
Organized by purpose - use the ones that fit your goal, or use them all.
Feature discovery
What is the one feature you wish [Product] had that it currently does not?
Open Text
What problem would this feature solve for you?
Open Text
How are you currently working around the absence of this feature?
Open Text
How often would you use this feature if it existed?
Single Choice
- • Multiple times a day
- • Daily
- • A few times a week
- • Weekly
- • Monthly or less
Prioritization and impact
How important is this feature to your workflow?
Single Choice
- • Critical - blocking me right now
- • Important - would use regularly
- • Nice to have
- • Minor improvement
Would the absence of this feature cause you to switch to another tool?
Single Choice
- • Yes, actively looking at alternatives
- • Possibly
- • No
If you had to rank your top 3 requested features, what would they be?
Open Text
Which of these potential features is most valuable to you?
Single Choice
- • [Feature A]
- • [Feature B]
- • [Feature C]
- • [Feature D]
- • None of these
Use case and context
What is the specific situation where you would use this feature?
Open Text
Who else on your team would benefit from this feature?
Open Text
Have you seen this feature done well in another tool? Which one?
Open Text
What would a good implementation of this feature look like?
Open Text
Willingness to pay
Would you pay more for [Product] if this feature was included?
Single Choice
- • Yes, significantly more
- • Yes, a bit more
- • No - it should be included in the current price
- • No - not worth paying for
Would this feature justify upgrading to a higher plan?
Single Choice
- • Yes, definitely
- • Possibly
- • No
Existing features feedback
Are there any existing features in [Product] you feel are underbuilt or half-finished?
Open Text
Which feature do you find least useful and could be removed or simplified?
Open Text
What integrations would save you the most time?
Open Text
Is there anything you expected [Product] to do that it currently cannot?
Open Text
Any other feedback for our product team?
Open Text
Tips for running Feature Request surveys
Always ask "what problem does this solve" - the feature request is the solution, the problem is what you need.
Segment requests by plan tier - power users and free users often want very different things.
Track request frequency over time to spot trends, not just one-off ideas.
Share a summarized roadmap back with requesters - it closes the loop and builds trust.
The most-requested feature is not always the most impactful - use the impact/urgency questions to prioritize.
Run your first Feature Request survey in minutes
Mapster lets you send in-product surveys, link every response to a real user, and segment results by plan, role, or cohort. Free to start.
Try Mapster FreeNo credit card required
Frequently asked questions
How do I collect feature requests systematically?
Use a recurring quarterly survey plus in-product prompts after key actions. Store responses in a tagged database so you can cluster by theme and see which requests are growing over time.
What is the most important question in a feature request survey?
"What problem would this solve?" - most feature requests are solutions in disguise. Understanding the underlying problem lets you find a better or faster implementation than the one the user suggested.
How do I prioritize feature requests from surveys?
Score each request by: frequency (how many users ask for it), urgency (is it blocking them?), segment fit (does it come from ICP users?), and strategic alignment. High scores on all four = build it next.
Should I share my roadmap with users who submit feature requests?
Yes - even a brief "we have logged this" reply increases trust significantly. Users who feel heard are more likely to respond to future surveys and less likely to churn while waiting for a feature.
More survey question libraries
NPS
NPS Survey Questions
Ready-to-use NPS survey questions to measure Net Promoter Score, uncover why users give each rating, and segment promoters from detractors.
CSAT
CSAT Survey Questions
Ready-to-use CSAT survey questions to measure satisfaction after support interactions, onboarding, or product experiences.
CES
CES Survey Questions
Ready-to-use CES (Customer Effort Score) survey questions to measure how easy it is for users to get things done in your product.
PMF
PMF Survey Questions
Ready-to-use PMF survey questions using Sean Ellis and Superhuman methods to measure product-market fit for SaaS products.
Exit
Exit Survey Questions
Ready-to-use exit survey questions for cancellations, churned users, and free-to-paid drop-offs. Find out why users leave before it is too late.
Onboarding
Onboarding Survey Questions
Ready-to-use onboarding survey questions to understand new user goals, identify friction, and improve time-to-value for SaaS products.
Start collecting Feature Request feedback today
Mapster connects every survey response to a real user. See results segmented by plan, role, and cohort - not just a spreadsheet of answers.
Get Started FreeNo credit card required