Up to 70% off kits30% off services
MoSCoW Prioritization Tool
List your features, mark each one must, should, could or won't have, and give it a size and a value. See the board, how many weeks the MVP really takes, and where the list breaks the 60% rule. Download it as a CSV template for Excel or Sheets.
Features
| Feature | Priority | Effort | Value | Remove |
|---|---|---|---|---|
Your team
Must have
11 days- Sign-up, login and company accountsS · 5/5
- Quote request formM · 5/5
- Load tracking with status historyM · 5/5
- Staff quote deskM · 4/5
- Document downloadsS · 4/5
Should have
4 days- Card payments for invoicesM · 4/5
- Email and SMS status updatesS · 3/5
Could have
13 days- Saved addresses and repeat loadsS · 2/5
- Carrier mobile appXL · 3/5
Won't have (this time)
6 days- AI rate predictionL · 2/5
Want the estimate checked and priced?30% OFF
Our $349$499 Product Scope checks every size, adds acceptance criteria and gives you one fixed build price in about 5 business days. MVP Builds from $2,099$2,999.
The MoSCoW method, in practice
The four groups are easy. Holding the line is the hard part. These rules keep a MoSCoW list honest when we scope a product with a founder:
- Must means launch is pointless without it. Not "we really want it". If you would launch without it, even grudgingly, it is a should.
- Keep musts to about 60% of the effort. The shoulds and coulds are your buffer. When something takes longer, a could drops out instead of the date moving.
- Write a reason next to every won't. "Not now: needs months of data first" ends the debate. A bare "won't" restarts it every week.
- Look at value and effort together. A small, high-value could is often worth promoting; a large, low-value must is often a wish.
- Re-sort after every demo. Priorities change once people click through working software. That is the point of showing it early.
Ready to write the rest down? The free PRD template has a field for each group and the acceptance criteria that go with them.
Frequently asked questions
What MoSCoW is, the 60% rule, using it for an MVP and how the estimate works.
A way to sort requirements into four groups: Must have, Should have, Could have and Won't have (this time). It comes from the DSDM agile method. Must haves are the features the release is pointless or unsafe without; shoulds are important but can wait a little; coulds are nice extras; won'ts are agreed to be out of this release, which is as useful as deciding what is in.
DSDM guidance is no more than about 60% of the effort, so the shoulds and coulds leave room for surprises. If your musts are above that, the tool flags it: either some musts are really shoulds, or the timeline needs to grow.
Write every feature down, then ask of each one: would we launch without it? If yes, it is not a must. The must haves are your MVP. Shoulds go into the weeks right after launch, coulds into the backlog, and won'ts get a reason written next to them so the conversation does not restart every week.
Each effort size stands for a number of working days (S is 1, M is 3, L is 6 and XL is 12 by default; change them to match your team). The days are added per group and divided by how many developer days your team has each week. It is a planning estimate, not a quote.
Close. A value versus effort matrix sorts features by how much they matter against how much they cost. This tool records both for every feature, so you can spot high-value coulds worth promoting and low-value musts worth questioning, and the CSV keeps both columns for a spreadsheet chart.
No. The tool runs in your browser and nothing is stored or sent. Download the CSV or copy the summary before closing the tab.
Put it into a PRD with the free PRD template, then get it priced. Our $499 Product Scope checks every estimate, adds acceptance criteria and gives you one fixed price. MVP Builds start at $2,999.