RICE Scoring Calculator
Score features by Reach, Impact, Confidence, and Effort — then rank them. Free, no signup required.
Background
RICE is a feature prioritization framework created by Intercom. It helps product teams make objective, data-driven decisions about what to build next by scoring each idea across four dimensions.
The four factors
How many users will this affect in a given time period? Use real data from analytics — not guesses. Example: "500 users per quarter will encounter this feature."
How much will this affect each user? Scored on a scale: 3 (massive), 2 (high), 1 (medium), 0.5 (low), 0.25 (minimal). Be conservative — most features are a 1.
How confident are you in your Reach and Impact estimates? 100% = backed by data. 80% = educated guess. 50% = a hunch. This keeps speculation in check.
How many person-months will this take to ship? Include design, engineering, QA, and documentation. This is the only factor that lowers the score.
FAQ
RICE is a prioritization framework developed by Intercom. It scores ideas by four factors: Reach (how many users will this affect in a given period), Impact (how much will it affect each user), Confidence (how sure are you about your estimates), and Effort (how many person-months will it take). The RICE score is calculated as (Reach × Impact × Confidence%) / Effort.
The RICE score formula is: (Reach × Impact × Confidence) / Effort. Reach is the number of users affected per quarter. Impact is scored from 0.25 (minimal) to 3 (massive). Confidence is a percentage from 0 to 100. Effort is measured in person-months. A higher RICE score means a higher priority.
There is no universal "good" RICE score — it depends on your product and team. The value of RICE is in relative comparison: features with higher scores should generally be prioritized over those with lower scores. Most teams use RICE to rank their backlog, not to set absolute thresholds.
Use RICE when you have quantitative data about user reach and need to balance impact against effort. Use ICE (Impact, Confidence, Ease) for quicker, rougher estimates. Use MoSCoW for stakeholder-driven prioritization. Use the Kano model when you need to understand which features delight vs satisfy customers. RICE works best for product teams with usage analytics.
The standard Impact scale is: 3 = Massive (a transformative improvement), 2 = High (a significant improvement), 1 = Medium (a noticeable improvement), 0.5 = Low (a minor improvement), 0.25 = Minimal (barely noticeable). Be honest — most features are a 1 or 2. Reserve 3 for truly game-changing work.
Quackback is the open-source feedback platform. Collect requests, share roadmaps, and publish changelogs in one place.
Get started