MoSCoW Prioritization Tool and MVP Planner
Drop in your feature list or start from a template, sort it with MoSCoW, RICE or a value/effort matrix, and see the cost and timeline of the MVP against building everything at once.
Paste a list
One feature per line, from a doc, spreadsheet or Jira.
MVP estimate
Add features or pick a template to see the MVP scope and cost.
Indicative figures, not a quote. How it’s calculated: A medium (M) feature costs : the median feature price in our project cost calculator. S = ×0.5, L = ×2, XL = ×4. Design, QA and project management add 35 %. Timeline assumes a team of two developers (80 hours a week).
The list stays in your browser. Nothing is sent until you submit the form below.
Have an MVP scope? Get an estimate in one business day
Send the feature list and the estimate from the planner. We will reply with a detailed estimate, timeline and team within one business day.
Thank you! We will send the estimate within one business day.
TL;DR: list every feature idea, put only what solves the main job into Must, and build that first. In a typical template, the Must column is 40–50 % of the features and about half the cost of building everything.
What is the MoSCoW method?
MoSCoW sorts requirements into four groups: Must have, Should have, Could have and Won’t have this time. Must is the smallest set without which the product does not do its job. Everything else waits for the next release.
How to define the MVP scope
- Write down every feature, even the ones you doubt.
- Move into Must only what the first users can’t do without.
- Check Must with RICE or the value/effort matrix: low-value, high-effort items go down.
- Look at the MVP cost and timeline and cut again if needed.
MoSCoW, RICE or value/effort: which to use?
MoSCoW is quick and easy to agree on with stakeholders. RICE adds numbers when opinions differ. The value/effort matrix shows quick wins at a glance. The planner keeps one list, so you can switch between methods.
FAQ
What is the MoSCoW prioritization method?
It splits features into Must have, Should have, Could have and Won’t have (this time). The MVP is usually the Must group.
How is the RICE score calculated?
RICE = Reach × Impact × Confidence ÷ Effort. Reach is users per quarter, impact is 0.25–3, confidence is a percentage, effort is in person-weeks.
How is the MVP cost estimated?
Each feature has a size: S, M, L or XL. A medium feature costs the median feature price from our project cost calculator; design, QA and project management are added on top. It is an indicative range, not a quote.
Can I import the result into Jira?
Yes. The CSV uses Summary, Description, Priority and Labels columns, which Jira’s CSV importer maps directly. Labels contain the MoSCoW group and MVP or Later.
Is my feature list sent anywhere?
No. The plan stays in your browser. Data is sent only if you submit the form to get an estimate.
How do I share the plan with the team?
Click “Share link”: the whole plan is encoded in the link after the # sign, so it is not sent to the server.