A feature request is feedback from a user asking for a new capability, improvement, or change to a product. Feature requests are a primary source of product intelligence. The challenge is not collecting them — it's prioritizing which ones to build based on frequency, impact, and strategic alignment.
A feature request is any user-submitted suggestion to add, change, or improve a product's functionality. Feature requests come through support tickets, in-app feedback widgets, user interviews, NPS follow-ups, and community channels. They represent the clearest possible signal of unmet user needs — but raw feature requests need to be interpreted carefully, since users often describe solutions rather than the underlying problems.
The most effective frameworks for feature request prioritization are RICE (Reach × Impact × Confidence ÷ Effort), ICE (Impact × Confidence × Effort), and the Kano model. The key insight is that volume of requests is not the same as priority — a single feature request from your largest enterprise customer may outweigh 100 requests from free-tier users. Always weight requests by user segment, revenue impact, and strategic fit.
Every feature request deserves a response — even a 'no.' Users who receive thoughtful responses, even rejections, are significantly more loyal than users who are ignored. The most important responses are: (1) accepting the request and giving a timeline, (2) declining with a clear reason, or (3) asking follow-up questions to understand the underlying problem. Acknowledging requests closes the feedback loop and signals that user input matters.
FeedbackJar captures user feedback directly in your product. Improve Feature by acting on what users actually tell you.
Start Free Trial