Free tool
RICE score calculator
Score feature requests by reach, impact, confidence and effort, see them ranked as you type, and export the list. The example below is the worked example from our RICE guide.
Your ideas
- 1RICE score · rank #1
- 2RICE score · rank #2
- 3RICE score · rank #3
- 4RICE score · rank #4
Ranking
- #1Snooze a reminder3,200
- #2Shared habits with friends833
- #3Export streak history as CSV800
- #4Smartwatch app375
Saved in this browser. The share link carries the whole table in the URL; nothing is stored on our side.
How it works
RICE gives every idea one number so a two-day tweak and a two-month project can sit in the same list. The score is (Reach × Impact × Confidence) ÷ Effort: higher means more value per unit of work.
- Pick the time period for Reach (month, quarter or year) and use it for every idea.
- For each idea, enter how many people it reaches in that period, its impact on your goal, how confident you are, and the effort in person-months.
- Read the ranking. Ideas with close scores are effectively tied; use judgment, such as which one fits this quarter’s goal.
- Export the CSV or copy a share link so your team can challenge the inputs.
The score ranks options; it doesn’t make the decision. Security fixes, legal requirements and severe bugs get done regardless of score. The RICE framework guide covers how to get inputs you can defend and the common mistakes.
FAQ
How do you calculate a RICE score?
Multiply Reach by Impact by Confidence, then divide by Effort. For example, 4,000 users a quarter × 1 (medium impact) × 80% confidence ÷ 1 person-month = 3,200.
What is a good RICE score?
There's no absolute good score. RICE only works for ranking ideas against each other when they were scored with the same scales and the same time period for Reach.
Should Effort include design and QA time?
Yes. Effort is total time from everyone involved, in person-months. Counting only engineering time makes design-heavy projects look cheaper than they are.
Where do I get Reach numbers?
From analytics for the screen or plan the idea touches. Vote counts on a feedback board are a floor, not the reach, because many affected users never vote. Merge duplicate requests first so you aren't undercounting.
Is my data saved?
The table is saved in this browser so it's there when you come back. The share link puts the whole table in the URL itself; nothing is sent to or stored on a server.
Related guides
- GuideThe RICE prioritization framework, with worked examplesHow to score Reach, Impact, Confidence and Effort, with a worked example table.
- GuideHow to prioritize feature requests: votes, RICE and revenueWhat each signal tells you, and how to combine them into a decision.
- GuideHow to handle duplicate feature requestsSpot duplicates across channels, decide when two asks are the same, and merge them without losing voters.
Other free tools
- Free toolDuplicate request finderPaste requests or upload a CSV. See which ones are the same ask, grouped, in your browser.
- Free toolRelease notes writerTurn PR titles and commit messages into release notes users can read.
- Free toolFeedback tool cost calculatorSee what Canny, Featurebase, Frill, Nolt, Upvoty, UserJot and Sikia cost for your team.
Want this done for you?
Sikia captures requests from Slack, Discord and an in-app widget, merges duplicates into votes, and emails the people who asked when you ship.