How the PM Org Benchmark works

It scores your product team against 8 metrics and rolls the results into a single 0-100 score with a letter grade.

The formula: Each metric has a bottom, median, and top benchmark value. Your input is linearly interpolated between those points into a percentile from roughly 10 to 95. The 8 percentiles are then combined into a weighted average (weights ranging from 0.05 to 0.2 depending on how much each metric drives outcomes), producing the overall score. Scores map to grades: A at 85+, B at 70-84, C at 50-69, D at 30-49, F below 30.

Worked example: A team reporting 90% monthly retention (bottom 85%, median 94%, top 98%, weight 0.20) lands at the 32nd percentile: 10 + ((90 - 85) / (94 - 85)) x 40 = 32. The calculator repeats this for PM-to-engineer ratio, sprint length, features shipped per quarter, NPS, revenue per PM, discovery hours, and planning horizon, then weights and averages all 8 into the final score.

When to use it: Run the benchmark quarterly to track whether structural changes (headcount, process, roadmap cadence) are moving the metrics that matter. Pair it with the NPS calculator and RICE calculator to act on the weakest scores, and the product metrics guide for definitions of each input.