Skip to content

Free tools

RICE scoring calculator

Score each feature by Reach, Impact, Confidence and Effort. The calculator works out every RICE score and ranks your backlog, so you can see what to build first. Free, with no sign-up.

Your backlog

Feature 1
RICE score—
Feature 2
RICE score—
Feature 3
RICE score—

Do first

—

Fill in a row to score it. Every complete row ranks here, highest first.

Ranking

Nothing scored yet.

Score a feature to export your ranking as a CSV you can import into Quackback.

What is the RICE framework?

RICE is a prioritization framework created by Intercom. It weighs how much good an idea does against how much work it takes, so very different ideas can be compared on one number. The glossary covers the RICE framework in more depth.

Reach

People or events per period

How many people it affects in a set time, such as customers per quarter. Use real numbers wherever you can.

Impact

3 · 2 · 1 · 0.5 · 0.25

How much it helps each person reached, from massive (3) to minimal (0.25). Most work is a 1 or a 2.

Confidence

100% · 80% · 50%

How much evidence backs your Reach and Impact. It discounts ideas built on hunches. Below 50% is a moonshot.

Effort

Person-months

Total team time to ship: design, engineering, testing. The only factor that lowers the score.

How to calculate a RICE score

Multiply the three things that make an idea worth doing, then divide by the work it takes.

RICE = Reach × Impact × Confidence ÷ Effort

Use Confidence as a decimal, so 80% is 0.8. The score is the value you get for each person-month of work.
  1. Estimate Reach

    How many customers will it affect each quarter? Use analytics, or the number of customers who asked.

  2. Score Impact and Confidence

    Pick an Impact from 0.25 to 3, then a Confidence that matches your evidence: 100%, 80% or 50%.

  3. Estimate Effort

    Count the person-months to ship. Use 0.5 for anything well under a month.

  4. Rank by score

    Work out each score and sort the list, highest first.

Example: Bulk CSV export
Reach
500 customers a quarter
Impact
2 (high)
Confidence
100% → 1.0
Effort
2 person-months
500 × 2 × 1.0 ÷ 2
500
RICE score
500

The calculator's example, ranked

The example backlog scored with RICE
FeatureReachImpactConfidenceEffortRICE score
Slack alerts2,000180%11,600
Bulk CSV export5002100%2500
SSO with Okta120380%396

Slack alerts wins with only medium impact, because it reaches four times as many customers for half the work. SSO scores lowest, but if those 120 accounts are your largest customers, the score alone won't show it. Treat RICE as the start of the conversation, not the verdict.

How to score RICE well

The formula is simple. Consistent inputs are the hard part.

Use one period for ReachPer quarter is common. Mixing months and quarters skews every score.
Base Reach on dataProduct analytics, sign-up numbers or votes on the request, not a hunch.
Be strict with ImpactMost work is a 1 or a 2. If everything is a 3, the scale stops working.
Let Confidence do its jobDrop to 50% when Reach or Impact is a guess. Research can earn it back.
Count all the EffortDesign, engineering, testing and launch, not just the coding.
Score again each quarterNew feedback and new data change the inputs. Revisit the list regularly.

RICE and other prioritization frameworks

RICE suits a backlog where reach varies a lot. Other frameworks answer different questions.

Prioritization frameworks compared
FrameworkHow it scoresBest for
RICEReach × Impact × Confidence ÷ EffortProduct backlogs where you can estimate how many people each item reaches.
ICEImpact, Confidence and Ease from 1 to 10, averagedA fast first ranking of experiments and early ideas.
MoSCoWMust, Should, Could or Won't haveAgreeing the scope of a release with stakeholders.
KanoBasic, performance or delight featuresUnderstanding what customers expect and what delights them.
Value vs effortA two-by-two grid of value and effortA quick visual sort in a planning session.

Put real demand behind Reach

Reach is the number teams guess most often. A feedback board gives you a count instead.

Votes show how many customers want it

Customers post requests and vote on each other's. Duplicates merge, so votes add up in one place, and every request shows who asked. Sort by votes, then score the top requests with RICE.

  • Sort requests by votes to see demand
  • Add a vote for a customer who asked on a call
  • Turn a support conversation into a request
  • Filter by segment, such as plan or company, on Business
See how voting works

Example data. What follows is an interactive demo of a made-up workspace called Acme. Its customers, posts, votes and changelog entries are examples, not Quackback's own.

Acme Corp
PN
Boards
Powered by Quackback

Common questions

What is the RICE scoring model?

RICE is a prioritization framework created by Intercom. It scores each idea on four factors: Reach (how many people it affects in a period), Impact (how much it helps each of them), Confidence (how sure you are of those estimates) and Effort (how much work it takes). The score lets you compare very different ideas on one number.

How do you calculate a RICE score?

Multiply Reach by Impact and by Confidence, then divide by Effort: RICE = Reach × Impact × Confidence ÷ Effort. Use Confidence as a decimal, so 80% is 0.8. A feature reaching 500 customers a quarter, with high impact (2), 100% confidence and 2 person-months of effort, scores 500 × 2 × 1 ÷ 2 = 500.

What is a good RICE score?

There isn't one. Scores depend on how you measure Reach, so a score of 500 can be high for one team and low for another. RICE is for ranking items against each other within one backlog, scored the same way, not for setting thresholds.

What Impact values should I use in RICE?

The standard scale is 3 for massive, 2 for high, 1 for medium, 0.5 for low and 0.25 for minimal impact on each person reached. Most work is a 1 or a 2. Keep 3 for changes that transform the product for the people who use them.

How do I estimate Reach?

Count the people or events the item will affect in a fixed period, usually a quarter: customers who use the feature, sign-ups who see a change, or customers who asked for it. Use real numbers from analytics or your feedback board where you can, and use the same period for every item.

How should I estimate Effort?

Estimate the total person-months to ship, across design, engineering, testing and launch. Whole numbers are fine for most work; use 0.5 for anything well under a month. Effort is the only factor that divides, so bigger work needs a bigger payoff to rank well.

When should I use RICE instead of ICE?

Use RICE when ideas affect very different numbers of people and you can estimate how many, which is typical of a product backlog. Use ICE for a quick first pass over experiments or early ideas, where Reach is roughly the same or hard to know. Many teams screen with ICE and decide with RICE.

Who created the RICE framework?

RICE was created by Intercom's product team, who published it to help product managers compare ideas consistently. It has since become one of the most widely used prioritization frameworks.

Have another question? Talk to the team.

Run support and feedback in one place