Prioritize Features by What Ships First
Name your MVP's one core feature, sort the rest into Must, Should, Could and Won't (MoSCoW), and flag what a service already sells.
How It Works
Describe Your Idea
One sentence: who has the problem, and what you'd build.
List Your Features, or Leave It Empty
Up to 12, separated by commas. Leave it empty and the model proposes 6 to 10.
Get the Core and Four Slots
The core and why people pick it, then Must, Should, Could and Won't. Download the PDF or JSON.
Where Feature Priorities Sits in Discovery
What is the one core? Feature Priorities names it, sorts the rest by what ships first and flags generic plumbing.
Use this when: Your feature list is longer than your budget and everything feels like a must-have.
Who it's for: Founders with a software idea and a long feature list.
Feature Prioritization Starts With the Core
Core is the one reason people pick you over what they use today. What it can't work without ships with it. The rest waits.
Important Is Not the Same as Core
A feature can be expensive and load-bearing and still not be why anyone picks you. "We can't launch without it" is not "this is why we win."
Auth and Billing Are Not Your Moat
Sign-in, payments, email, file storage and search are solved problems a service already sells. The tool flags them as generic, so you see which features are plumbing and which is yours.
Frequently Asked Questions
A grid that sorts features by one rule, so you see what ships first when the list outgrows your budget. This one sorts everything around the core.
At most 3 Musts: the core plus up to 2 features it can't work without. Everything else waits in Should, Could or Won't.
Must have, Should have, Could have and Won't have, not now. Here the core sits on top, and features a service already sells get flagged as generic.
Then nothing is. The tool pushes back and holds the core to the one reason people pick you over what they use today.
A cut means later, not never. You keep the final call. Why cut fast: Scope Shaping. Why keep the core short: Find the Core.
Not by us. Your answers go to the AI for the run, then live only in this tab; a reload clears them. Download the PDF or JSON to keep the result.
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.