Free product prioritization tool

Free RICE Score Calculator

The RICE score calculator ranks product features by Reach, Impact, Confidence, and Effort using the formula (Reach x Impact x Confidence) / Effort. Add your backlog, score each idea, and instantly see a prioritized roadmap you can export as CSV.

Want to turn customer signal into ranked priorities? Use FeatureVote to collect feature requests, capture votes, and feed real data into your RICE prioritization.

What is the RICE prioritization framework?

RICE was developed by Intercom to help product teams compare feature ideas with a single, transparent score. Each idea is rated on four variables and combined using the formula RICE = (Reach x Impact x Confidence) / Effort. The higher the score, the more it should rank in your roadmap.

Reach

Number of users or customers affected per time period, for example per quarter. Use real numbers from analytics or funnel data when possible.

Impact

Per-user impact on Intercom's standard scale: 3 massive, 2 high, 1 medium, 0.5 low, 0.25 minimal. Pick the closest tier rather than inventing new values.

Confidence

A percentage (100% high, 80% medium, 50% low) that penalizes guesses. If your reach or impact estimate is a guess, drop confidence accordingly.

Effort

Total work in person-months across product, design, and engineering. Any consistent unit works as long as you use the same one for every feature.

Score your features

Add a row per idea, set the four RICE variables, and the score updates instantly. Your data stays in this browser.

RICE score4,000.0
RICE score450.0
RICE score4,000.0

Prioritized roadmap

Features sorted by RICE score, highest first. Add a name and the four RICE values to include a row in the ranking.

  1. Onboarding checklist

    Reach 5,000 · Impact 2 · Confidence 80% · Effort 2 pm

    RICE

    4,000.0

  2. #2

    Dark mode

    Reach 8,000 · Impact 0.5 · Confidence 100% · Effort 1 pm

    RICE

    4,000.0

  3. #3

    Slack integration

    Reach 1,200 · Impact 3 · Confidence 50% · Effort 4 pm

    RICE

    450.0

Working tip

Keep your effort estimates in the same unit (person-months works well) and use the same time window for reach across every feature. RICE only ranks fairly when each variable is measured the same way for all candidates.

How to calculate a RICE score

  1. 1

    Define reach

    Estimate how many users or customers the feature will affect over a fixed time window such as a quarter.

  2. 2

    Estimate impact

    Choose 3, 2, 1, 0.5, or 0.25 to describe how much the feature will change behavior for each user it reaches.

  3. 3

    Set confidence

    Pick 100%, 80%, or 50% to discount estimates you are less sure about. Drop confidence on guess-heavy ideas.

  4. 4

    Estimate effort

    Total work in person-months across product, design, and engineering. Include review and testing time.

  5. 5

    Compute RICE

    Multiply Reach by Impact by Confidence and divide by Effort. Higher scores rank higher in your roadmap.

RICE score calculator FAQ

Common questions about the RICE prioritization framework and using a RICE score calculator on a real backlog.

What is the RICE scoring model?

RICE is a product prioritization framework created by Intercom. It scores each feature idea on four factors - Reach, Impact, Confidence, and Effort - and combines them into a single score: (Reach x Impact x Confidence) / Effort. The higher the RICE score, the higher the priority.

How do I calculate a RICE score?

Multiply Reach (users affected per time period) by Impact (per-user impact on a 0.25 to 3 scale) by Confidence (a percentage between 50% and 100%), then divide the result by Effort in person-months. The output is a single comparable number you can use to rank features against each other.

What are good Impact values to use?

Intercom's standard scale is 3 = massive impact, 2 = high, 1 = medium, 0.5 = low, and 0.25 = minimal. Pick the value that best describes how much the feature will change behavior for the users it reaches. Stick with these discrete values rather than inventing new numbers, since the scale is what makes scores comparable across features.

When should I use RICE vs other prioritization frameworks?

Use RICE when you have a backlog of feature ideas and want a transparent, repeatable way to compare them. It works best when you can estimate reach in real numbers and effort in person-months. For early-stage products with very little data, lighter frameworks like ICE or MoSCoW are easier to apply. For roadmaps with strong dependencies or strategic themes, pair RICE with a qualitative review.

Is RICE better than ICE scoring?

RICE adds Reach and Effort to the original ICE (Impact, Confidence, Ease) framework, which makes it more rigorous for product teams that need to compare features at scale. ICE is faster and works well for early ideation. RICE is better when you need to defend prioritization decisions with stakeholders, because it forces you to estimate audience size and engineering cost up front.

Score features your customers actually want

Reach and impact are easier to estimate when you have real customer signal. FeatureVote helps product teams collect feature requests, capture votes, and feed authentic data into your RICE prioritization.