TemplateFREE⏱️ 30-45 minutes per request
Enterprise Feature Request Template
Free enterprise feature request intake template for evaluating and prioritizing customer requests. Includes request scoring, business case validation,...
Updated 2026-03-04
Enterprise Feature Request
| # | Item | Value (1-10) | Effort (1-10) | Score | Priority | Owner | |
|---|---|---|---|---|---|---|---|
| 1 | 3.0 | ||||||
| 2 | 2.5 | ||||||
| 3 | 1.8 | ||||||
| 4 | 1.2 | ||||||
| 5 | 1.1 |
#1
3.0
#2
2.5
#3
1.8
#4
1.2
#5
1.1
Edit the values above to try it with your own data. Your changes are saved locally.
Get this template
Choose your preferred format. Google Sheets and Notion are free, no account needed.
Frequently Asked Questions
How do I handle feature requests that come directly from executives?+
Treat executive requests the same as any other request: capture the intake, validate the business case, and score it. The difference is communication. Acknowledge the request quickly (within 24 hours) and share the evaluation timeline. If you decline an executive-escalated request, provide the reasoning directly to the executive rather than relaying through the sales rep.
What if a customer requests something we are already building?+
This is the best-case scenario. Respond immediately with: "Great news, this is on our roadmap for [quarter]. I would love to include you in the beta program." Use the request as a signal to confirm your prioritization was correct, and consider the customer as a design partner for validation. The [product strategy handbook](/strategy-guide) covers how to align customer input with your roadmap.
How do I decline a request from our largest customer without damaging the relationship?+
Be direct and honest. "We evaluated this carefully. Here is why it is not on our near-term roadmap: [reasoning]. Here is what we are building instead that addresses a related need: [alternative]. We will revisit this in [timeframe]." Customers respect transparent prioritization more than vague promises. The [stakeholder management guide](/stakeholder-guide) has detailed frameworks for these conversations.
Should I share the evaluation scoring with the customer?+
No. The internal scoring is a decision-making tool, not a customer communication artifact. Share the decision and the reasoning, not the process. Telling a customer they scored a 14/30 is not helpful. Telling them "we have prioritized security infrastructure this quarter, and your request is queued for Q3 review" is actionable information.
How many feature requests should a PM expect to process per quarter?+
For enterprise B2B products, 15-30 unique feature requests per quarter is typical. Many will be duplicates or variations on the same theme. The goal is not to process more requests faster; it is to identify the 3-5 patterns that represent real product opportunities. Batch similar requests together and evaluate the pattern, not each individual request. ---
Related Tools
RICE Score Calculator
Score features using Reach, Impact, Confidence, and Effort.
ICE Score Calculator
Prioritize with Impact, Confidence, and Ease — fast and lightweight.
WSJF Calculator
Weighted Shortest Job First scoring for SAFe and Lean teams.
MoSCoW Prioritizer
Categorize features into Must, Should, Could, and Won't have.
Explore More Templates
Browse our full library of PM templates, or generate a custom version with AI.