Feature Prioritization Matrix
Classify every feature as core (your competitive advantage), supporting (necessary but not unique), or generic (buy, don't build) — then phase everything into MVP, Growth, and Scale by business impact.
Free, no signup required. Results in 2-5 minutes.
How It Works
List Your Features
Paste a feature list or describe your product. The AI extracts features and classifies each as core, supporting, or generic.
AI Classifies and Scores Everything
The AI classifies each feature by domain (core, supporting, generic), scores business impact, and proposes phases — all at once. You review the full picture, not one feature at a time.
Refine and Confirm
Agree, push back, or ask questions. The AI challenges your assumptions but respects your final call. It flags risks when you override its recommendations.
Get Your Priority Matrix
Features classified by domain and phased into MVP, Growth, and Scale. Core domain features ship first, supporting features get deferred, generic features get bought off-the-shelf.
Core, Supporting, or Generic — Every Feature Has a Type
Your matching algorithm is core — it's your competitive advantage, build it custom. User management is supporting — necessary but not unique. Auth and payments are generic — solved problems, buy them. The AI classifies every feature so you know where to invest engineering time.
Everything Can't Be MVP
When all 15 features are 'must-have,' nothing gets shipped. The AI scores each feature by business impact and assigns phases — MVP, Growth, or Scale. Core features ship first. Supporting features get deferred. Generic features get bought.
The Priority Matrix Becomes the Project Scope
This isn't an academic exercise. The feature prioritization matrix maps directly to development phases. MVP gets built first. Growth features have clear triggers for when to add them. Scale features wait until you've validated the business.
Frequently Asked Questions
Core features are your competitive advantage — the reason someone picks you over alternatives. Supporting features enable core but aren't unique (user management, notifications). Generic features are solved problems (auth, payments, email). This distinction drives what you build custom, what you keep simple, and what you buy — and feeds directly into Tech Strategy.
Typical products have 1-3 core features. If you say 5+, you probably have 0. "Important" doesn't mean "core." Auth is important — it's not your competitive advantage. The test: "The reason someone picks us over the alternative is ___." That's core. The discipline behind keeping it short is the Find the Core principle.
It will challenge you. Auth and payments get flagged as "buy, don't build." Supporting features get deferred if they're not needed for MVP. You make the final call, but the AI flags scope risk when you keep everything. The principle behind cutting fast is Scope Shaping.
MVP includes all core features plus the supporting features they depend on. Growth adds retention and expansion features with clear triggers for when to build them. Scale adds optimization. Each phase has concrete entry criteria, not arbitrary timelines. The MVP phase maps directly to MVP in 6 Weeks.
8-15 is the sweet spot. Under 8 is fine — the AI may suggest features you're missing. Over 25, the tool will suggest grouping into capabilities first, then prioritizing the groups. Once the list is sized, Build Cost & Plan shows what fits in your budget.
Where To Next
Next discovery step:Tech Strategy
Principles behind it:Scope Shaping, Find the Core, Consolidation
When you're ready to build:MVP in 6 WeeksPoC in 2 Weeks
Built & Maintained by Varstatt
Varstatt is a one-person product studio run by Jurij Tokarski, product engineer since 2011. These tools are free and open — no signup, no catch.