Free tool
RICE prioritization calculator
Score any feature by Reach × Impact × Confidence ÷ Effort. Get a clear number to rank your backlog by value per unit of effort.
427
High priority
RICE is blind to revenue. A request from one paying enterprise account can beat a high-reach ask from free users. Feed it real reach and the revenue behind each request and the ranking changes.
Beyond the number
A score is only as good as its inputs.
Reach is usually a guess. When product behavior is on the spine, reach is measured — how many accounts actually touch this surface — not estimated.
Confidence comes from evidence. Tie each item to the feedback and the accounts that asked, and confidence stops being a vibe.
Add the missing variable: revenue. RICE ranks effort efficiency; the spine adds the money at stake, so the top of the list reflects what paying customers need.
FAQ
RICE scoring questions
What is the RICE prioritization score?
RICE scores a feature by Reach × Impact × Confidence ÷ Effort. Reach is how many people it affects per period; Impact is a multiplier (3 massive → 0.25 minimal); Confidence is a percentage; Effort is person-months. Higher score = more value per unit of effort.
How do I calculate a RICE score?
Multiply reach by impact by confidence, then divide by effort. For example, 800 reach × 2 impact × 80% confidence ÷ 3 person-months ≈ 427.
What is a good RICE score?
RICE scores are only meaningful relative to each other — score your whole backlog and rank. As a rough read, this tool bands a single score as low, medium, or high so you can sanity-check it, but the real value is comparing items on one consistent scale.
What is RICE missing?
RICE weighs reach and effort but is blind to revenue — a request from one paying enterprise account can outweigh a high-reach request from free users. The fix is to feed RICE real reach and the revenue behind each request, instead of guessing both.
More free tools: MRR & ARR · churn calculator · Rule of 40 · stack cost.