feature-prioritization-matrix
Transform overwhelming client feature wish lists into structured MVP/Phase 2/Phase 3 plans with time estimates, preventing scope creep and creating profitable upsell opportunities.
When & Why to Use This Skill
The Feature Prioritization Matrix skill is designed to streamline software project planning by transforming chaotic client wish lists into structured, phased delivery roadmaps. It helps developers and project managers define MVP requirements, provide realistic time estimates, and prevent scope creep by categorizing features into logical development phases (MVP, Phase 2, and Phase 3).
Use Cases
- MVP Scoping: Efficiently filter core functionalities from a long list of requirements to launch a Minimum Viable Product faster and within budget.
- Scope Creep Management: Use the prioritization framework to handle mid-project feature requests by offering clear trade-offs or deferring them to later phases.
- Strategic Upselling: Create professional product roadmaps that demonstrate long-term value, encouraging clients to commit to future development phases.
- Project Estimation & Pricing: Generate data-backed time estimates and phased pricing structures to set realistic client expectations and improve project profitability.
| name | feature-prioritization-matrix |
|---|---|
| description | Transform overwhelming client feature wish lists into structured MVP/Phase 2/Phase 3 plans with time estimates, preventing scope creep and creating profitable upsell opportunities. |
Feature Prioritization Matrix
Turn feature chaos into structured, profitable delivery phases.
What This Skill Does
You list all features a client wants, and this skill outputs:
✅ MVP Features - Must-have for launch (what to build first) ✅ Phase 2 Features - Enhanced functionality (post-launch additions) ✅ Phase 3+ Features - Nice-to-haves (future roadmap) ✅ Estimated Build Time - Realistic hours per phase ✅ Pricing Structure - How to charge for phased delivery ✅ Priority Reasoning - Why each feature belongs in its phase
Who This Is For
Software Tailors need to prevent scope creep, keep projects manageable, create upsell opportunities, set realistic expectations, and deliver value quickly.
Prioritization Framework
MVP (Phase 1) - Must-Have
- Solves core problem
- Blocking other features
- Can't launch without it
- Simple to build
Phase 2 - Should-Have
- Significantly improves UX
- Automates manual processes
- Clear ROI
- Client proven they use MVP
Phase 3 - Nice-to-Have
- Competitive differentiator
- Efficiency optimization
- Not urgent
Future - Maybe Someday
- Expensive to build
- Adds recurring costs
- Unclear ROI
Presenting Phased Delivery
"I organized features into phases so you see working software in 6 weeks, not 6 months. Phase 1 ($18K) solves your core problem. Phase 2 ($7K) adds automation after you've proven you love it. Phase 3 ($10K) gives you competitive edge. You only commit to $18K today - if Phase 1 doesn't work, you stop. If it's amazing, you invest more."
Preventing Scope Creep
When client says "Can we just add...?":
"Great idea! [Feature X] takes [Y] hours. Three options:
- Add to Phase 2 for $[Z]
- Swap for something in MVP
- Expand MVP: add $[Z] and push timeline [W] weeks
Which makes sense?"
Never "just add" features for free.