Feature Request Template
A structured feature request template with problem statement, proposed solution, user impact, priority scoring, and acceptance criteria — designed for product teams and stakeholders.
Feature Request
Requested by: [Name / Customer]
Date: [Date]
Product Area: [Area]
Priority: [High / Medium / Low]
Problem Statement
As a [user type], I struggle with [specific problem] because [root cause]. This happens [frequency] and affects [number of users / revenue impact].
Proposed Solution
[Describe the feature or change that would solve the problem. Be specific about what it should do, not how it should be built.]
Alternatives Considered
1. [Alternative approach and why it was rejected]
2. [Current workaround and its limitations]
Impact & Priority
Reach: [How many users affected per quarter]
Impact: [Minimal / Low / Medium / High / Massive]
Confidence: [Low / Medium / High]
Effort: [Person-weeks to implement]
Acceptance Criteria
• Given [context], when [action], then [expected result]
• Given [context], when [action], then [expected result]
How to Use This Template
Start with the problem
Describe the pain point, not the feature. "I need an export button" is a solution. "I cannot share reports with my team" is the problem. Problems open up better solutions.
Quantify the impact
How many users are affected? How often does the problem occur? What is the revenue impact? Numbers make prioritization objective instead of political.
Include alternatives
Show what you considered and why you rejected it. This demonstrates thorough thinking and helps the product team understand constraints.
Write acceptance criteria
Define what "done" looks like with Given/When/Then statements. This bridges the gap between the request and development and prevents scope creep.
Customize in Dewx
Inside Dewx, tell Dew: "Create a feature request for [description]." Dew structures the request with problem statement, impact scoring, and acceptance criteria. All requests feed into your product roadmap in the CX Hub with automatic deduplication.
Related Templates
Frequently Asked Questions
What should a feature request include?
A good feature request includes the problem being solved (not just the feature wanted), who it affects, how often the problem occurs, the proposed solution, alternative solutions considered, expected impact, and acceptance criteria. This template walks you through all of these sections.
How do I prioritize feature requests?
Use a framework like RICE (Reach, Impact, Confidence, Effort) or ICE (Impact, Confidence, Ease). Score each request and rank them. Also consider: how many users requested it, does it align with the product roadmap, and what is the revenue impact. Dewx can score and rank requests automatically.
Should feature requests come from customers or internal teams?
Both. Customer requests tell you what the market needs. Internal requests (from sales, support, engineering) tell you what would reduce friction and improve efficiency. The best product teams synthesize both inputs and identify patterns rather than building features one-off.
How does Dewx help with feature request management?
Dewx captures feature requests from customers, support tickets, and internal teams in one place. Dew auto-categorizes requests, identifies duplicates, scores them using your prioritization framework, and links them to your product roadmap in the CX Hub.
Product Feedback, Organized
Simple, Transparent Pricing
Starting at $29/mo for solopreneurs. $79/mo for teams. All features included.
View pricingBuild What Users Actually Want
Dew captures requests from every channel, scores them objectively, and connects them to your roadmap — so you build the right features.
Try Dewx FreeStop Losing Feature Requests in Email Threads
Dewx captures, scores, and organizes every feature request from customers and teams. Build what matters most with data, not gut feeling.