RICE Score Calculator

What is the RICE prioritization framework?

RICE is a scoring model that helps product managers decide which initiatives to build first. It was popularized by Intercom as a way to bring objectivity to roadmap decisions and to stop the loudest voice in the room from dictating priorities. Instead of arguing about gut feel, every idea is scored on four factors — Reach, Impact, Confidence, and Effort — and the resulting number gives you a defensible, comparable ranking.

The formula is deliberately simple: RICE = (Reach × Impact × Confidence) ÷ Effort. Three factors push the score up (more reach, more impact, more confidence) and one pushes it down (more effort). The output is a single number that approximates “total impact per unit of work” — exactly the thing a resource-constrained team wants to maximize.

How to score each RICE factor

Reach

Reach is how many people or events your initiative will affect within a defined time period — usually a quarter. Use real numbers from your analytics where you can: monthly active users who will see a feature, checkout sessions per quarter, support tickets avoided per month. Keep the time window consistent across every item so the comparison stays fair.

Impact

Impact captures how much the initiative moves your goal for each person reached. Because precise impact is impossible to measure in advance, RICE uses a fixed five-point scale: 3 for massive, 2 for high, 1 for medium, 0.5 for low, and 0.25 for minimal. This constraint is a feature, not a limitation — it keeps everyone honest and avoids fake precision.

Confidence

Confidence is the percentage that reflects how much you trust your Reach and Impact estimates. Use 100% when you have strong data, 80% when you have some evidence, and 50% when it is largely a hunch. Confidence is the antidote to wishful thinking: it automatically discounts exciting-but-unproven bets so they do not leapfrog validated work.

Effort

Effort is the total amount of work required, measured in person-months across product, design, and engineering. One person working for one month equals 1. Effort is the denominator, so a small, cheap win can outrank a high-impact feature that takes a year to build — which is usually the right call for a team that wants momentum.

A worked example

Say you are weighing a single sign-on (SSO) feature against a dark mode. SSO reaches 1,200 enterprise users a quarter, has massive impact (3), 100% confidence, and costs 6 person-months: (1,200 × 3 × 1.0) ÷ 6 = 600. Dark mode reaches 15,000 users but has minimal impact (0.5), 100% confidence, and 2 person-months: (15,000 × 0.5 × 1.0) ÷ 2 = 3,750. Dark mode scores higher here — a useful reminder that broad, cheap improvements often beat narrow, expensive ones, even when the expensive one “feels” more important. The calculator above does this math for you and re-sorts the list as you type.

When to use (and not use) RICE

RICE shines when you are comparing a backlog of similar, incremental features and you have at least rough usage data. It is less useful for non-negotiable work like security and compliance, for large strategic bets whose payoff is non-linear, and for brand-new products with no users to estimate reach from. Treat the score as an input to the conversation, not the final word — the best PMs use RICE to surface surprises and pressure-test intuition, then apply judgment.

Want the deeper theory, scoring rubrics, and common pitfalls? Read our full RICE framework guide, or compare it with other models on the prioritization template page.