Free tool
Feature prioritiser with RICE scoring
Score each feature by reach, impact, confidence and effort. See them ranked, fit them to the weeks you can afford, and send the ones that make the cut to the scope of your MVP brief. Free, no sign-up, saved in this browser.
Your features
One row per feature. Reach is how many users it affects in the first three months; impact is how much it helps each of them; confidence is how sure you are of both; effort is the person-weeks to build it. Scales from Intercom’s RICE method (opens in a new tab).
| Feature | Reach (users in 3 months) | Impact | Confidence | Effort (person-weeks) | Remove |
|---|---|---|---|---|---|
| Nothing added yet. | |||||
Person-weeks for the first version. Leave at 0 to rank without a limit.
Ranked
Add features with a reach and an effort to see them ranked.
The formula
RICE score = (reach × impact × confidence) ÷ effort
A higher score means more value for each week of work. Scores only compare features scored the same way, so use the same period for reach and the same unit for effort throughout. Treat the ranking as a starting point for a decision, not the decision itself.
Method: RICE: Simple prioritization for product managers (opens in a new tab), Intercom.
Prioritisation questions
What is RICE?
A scoring method published by Intercom for deciding what to build first. Each feature gets a score: reach times impact times confidence, divided by effort. Features that help many people a lot, that you are sure about and that are quick to build rise to the top.
What do I put for reach?
How many users the feature will affect in a set period. For an MVP, use the number of users you expect in the first three months, and the share of them who would use this feature. A sign-up form reaches everyone; an export to a spreadsheet may reach a few.
How do the suggested priorities work?
Features are ranked by score. If you enter the weeks of work you can afford, the calculator fills them in order of score until the weeks run out, skipping any that do not fit. The first 8 that fit are suggested as Must haves, the rest that fit as Should haves, and the ones that do not fit as Could haves. Your judgement comes first: a low-scoring feature can still be essential, such as payments or data protection.
Why no more than eight Must haves?
An MVP tests one idea with the smallest product that can test it. A long Must list usually means the first version is trying to do too much, costs more and takes longer to learn from. The MVP builder warns you when the Must list grows past eight.
Is my list saved?
Yes, in this browser on this device. Nothing is sent to us. “Send to my scope” adds the features to the scope of your MVP brief, with the suggested priority.