Feature Value Scorer
Prioritize your roadmap and pricing tiers. Map features based on Customer Value vs. Implementation Cost to find 'Quick Wins' and 'Margin Drivers'.
Value (X) vs Cost (Y)
Matrix Analysis
Bubble size = Willingness to Pay
Bottom Right (Quick Wins)
High Value, Low Cost. These are gold. Include in Pro plans to drive upgrades, or Enterprise to boost margin.
Top Right (Strategic)
High Value, High Cost. These define your product but are expensive. Ensure they are priced high enough to cover costs.
Top Left (Money Pits)
Low Value, High Cost. Why are you building these? Kill them or find a cheaper way.
Execution Steps
List your potential product features.
Rate 'Customer Value' (1-10) based on how much users want it.
Rate 'Cost' (1-10) based on complexity/effort to build and maintain.
Tag Willingness-to-Pay (WTP) impact (Bubble Size). High WTP means users will pay extra for it.
Use the matrix to assign features to Basic (Low Cost/Low WTP), Pro (Quick Wins), and Enterprise (High WTP).
Pro Strategy
- Move 'High WTP / Low Cost' features to your highest tier. This maximizes margin.
- Use 'High Value / High Cost' features as your core differentiators (Pro Plan) but price accordingly.
- Kill or depreciate 'Low Value / High Cost' features. They consume resources without adding revenue.
Core Concepts
The Value/Cost Matrix
A strategic framework to visualize ROI. High Value / Low Cost items are your profit engines.
Margin Drivers
Features that cost little to deliver but command High Willingness to Pay (e.g., SSO, Priority Support). These belong in your top tier.
Money Pits
High Cost / Low Value features. Avoid building these unless absolutely necessary for parity.
What is Feature Value Scorer?
This tool adapts the RICE scoring model (Reach, Impact, Confidence, Effort) specifically for pricing strategy. By correlating development effort with willingness-to-pay, it helps Product Managers structure tiers that align cost-to-serve with revenue capture.
Best For
- • Designing SaaS pricing tiers.
- • Pruning product roadmaps.
- • Identifying upsell opportunities.
Limitations
- • Subjective inputs.
- • Does not account for feature dependencies.
Alternative Methods
Kano Model
Classifies features by satisfaction (Delighters vs Basics).
Industry Applications
See how this methodology generates real revenue uplift in different sectors.
SaaS Start-up
High churn on Basic plan.
Identified 'Custom Domain' was Low Cost (1) but High WTP. Moved it to Pro.
Agency Retainers
Low margins.
Scored 'Weekly Reporting' as High Cost / Low Value. Replaced with automated monthly dashboard (Low Cost).
Hardware Manufacturer
Feature creep.
Mapped 'Voice Control' as High Cost / Low Value. Cut it.