I wrote the book on developer marketing. Literally. Picks and Shovels hit #1 on Amazon.

Get your copy
Product management

RICE scoring

rys SKOR-ing

A prioritization framework that scores initiatives by Reach, Impact, Confidence, and Effort to produce a comparable priority score.

RICE is a prioritization framework developed at Intercom. It scores each initiative on four dimensions: Reach (how many users it affects in a given period), Impact (how much it improves the experience, scored 0.25 to 3), Confidence (how sure you are of the estimates, as a percentage), and Effort (person-months required).

The formula: (Reach x Impact x Confidence) / Effort = RICE score. Higher scores indicate higher priority. The formula naturally favors initiatives that affect many users, have high impact, and require low effort.

RICE's strength is forcing explicit assumptions. When a PM says 'we should build feature X,' RICE asks: how many users will it reach? How much will it move the needle? How confident are you? How much work is it? These questions surface assumptions that might otherwise go unchallenged. The output feeds directly into roadmap decisions and helps prioritize the backlog.

Examples

A PM scores two competing features.

Feature A: Reach 5,000/quarter, Impact 2, Confidence 80%, Effort 3 person-months. Score: (5000 x 2 x 0.8) / 3 = 2,667. Feature B: Reach 20,000/quarter, Impact 1, Confidence 60%, Effort 2 person-months. Score: (20000 x 1 x 0.6) / 2 = 6,000. Feature B scores higher despite lower per-user impact.

Low confidence reduces a feature's RICE score.

The team wants to build an AI feature. Impact could be huge. But confidence is 40% because they have not validated the use case. RICE score: mediocre. The PM proposes a one-week spike to validate the use case and increase confidence before committing to the full build.

A team calibrates RICE scoring together.

The PM, designer, and tech lead each score 10 features independently. They compare scores. Where they disagree, they discuss assumptions. The discussion surfaces information no individual had. Final scores reflect the team's collective understanding.

Frequently asked questions

How do you estimate Reach in RICE?

Use data when available: how many users perform the relevant action per quarter? When data is unavailable, estimate based on the target segment size. Be explicit about assumptions. The number does not need to be precise; it needs to be defensible.

What are the weaknesses of RICE scoring?

Subjective scoring (Impact and Confidence are judgment calls), does not account for strategic value or competitive necessity, and can bias toward incremental improvements over bold bets. Use RICE as one input, not the sole decision-maker.

Related terms

Picks and Shovels: Marketing to Developers During the AI Gold Rush

Want the complete playbook?

Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.