The 12 RevOps Metrics That Matter
The RevOps metrics worth reporting are the ones with a decision attached: pipeline coverage, stage conversion, sales velocity, CAC payback, net revenue retention, lead response time, win rate by source, forecast accuracy, cycle length, average deal size, qualified pipeline created, and cost per qualified opportunity.
- If no decision changes when a number moves, stop reporting it.
- Twelve is the ceiling. A dashboard with forty metrics is reporting none of them.
- Segment everything. An aggregate win rate conceals both your best and worst segments.
- Forecast accuracy is the metric that measures the RevOps function itself.
- MQL count, activity volume, and lead count are diagnostics. Making them targets corrupts behaviour.
The test for whether a metric belongs
One question: what decision changes when this number moves? If nobody can answer, the metric is being reported because it is available rather than because it is useful, and it is costing attention that a real metric needs.
Applying that test honestly usually cuts a reporting layer by half. The twelve below survive it in almost every B2B business — though a trusted metric set is necessary rather than sufficient, as building a data-driven revenue team covers.
The pipeline metrics
| Metric | Decision it drives | Benchmark |
|---|---|---|
| Pipeline coverage | Open the demand tap, or fix conversion | 3–4× the quarter's target |
| Qualified pipeline created | Whether demand generation is working now | Against plan, by source |
| Stage conversion | Which stage gets the process or enablement fix | Per stage, versus your own trailing 6 months |
| Cycle length | Whether the motion matches the deal size | Segment-specific; watch the trend |
Coverage is the single most useful number in a weekly review, and the most commonly miscalculated. Coverage means qualified pipeline against target at your historical win rate — not total open pipeline, which includes deals that will never close and flatters the figure precisely when you most need honesty.
The efficiency metrics
| Metric | Decision it drives | Benchmark |
|---|---|---|
| Sales velocity | Which of the four inputs to attack | Trend matters more than the absolute |
| CAC payback | Channel and headcount investment | Under 12 months healthy; over 24 concerning |
| Cost per qualified opportunity | Where to move budget | Fully loaded, by source |
| Average deal size | Segment focus and packaging | Watch the distribution, not the mean |
Sales velocity is worth computing because it decomposes cleanly: opportunities × win rate × deal size ÷ cycle length. When it drops, exactly one of those four inputs moved, and the decomposition tells you which — which is far more actionable than the headline figure.
The system metrics
| Metric | Decision it drives | Benchmark |
|---|---|---|
| Lead response time | Routing and SLA enforcement | Median under 1 hour for high intent |
| Win rate by source | Which channels bring good-fit buyers | Compare sources, not to an external number |
| Net revenue retention | Fund expansion or acquisition | 105–120% mid-market SaaS |
| Forecast accuracy | Whether the system can be trusted at all | Within 10% at start of quarter |
Forecast accuracy deserves special attention because it is the metric that measures the RevOps function itself. Every other number on this page can look reasonable while the forecast still misses by 30%, and when that happens the problem is definitional rather than commercial — stages that mean different things to different people produce a forecast that means nothing to anyone.
Segment everything
Every metric above is close to useless in aggregate. An overall win rate of 22% might be 40% in your core segment and 8% in an adjacent one you should stop selling to — and the aggregate actively conceals the decision.
- By source, always. This is where the largest variance lives and where budget decisions get made.
- By segment, meaning company size or vertical — whichever your motion actually differs across.
- By rep, for coaching only. Never publish rep-level conversion as a leaderboard; it produces stage-skipping rather than improvement.
- By cohort, for anything retention-related. Aggregate retention hides churn behind unrelated expansion.
The metrics to demote
Four numbers that are useful as diagnostics and corrupting as targets.
| Metric | Why it corrupts | Use instead |
|---|---|---|
| MQL count | Hit by loosening qualification, which is the failure it should prevent | Qualified pipeline created |
| Activity volume | Rewards calls made rather than conversations had | Meetings held per rep |
| Raw lead count | Rewards cheap volume regardless of fit | Cost per qualified opportunity |
| Pipeline value, unqualified | Inflated by deals nobody believes in | Coverage on qualified pipeline only |
Each of these is worth watching. None should appear in a compensation plan or a board target, because in every case the easiest way to move the number is the behaviour you were trying to prevent — the argument set out in cross-functional alignment.
How to report them
- 01One owner per metric
A named person who is expected to explain movement. Unowned metrics get reported and never interrogated.
- 02Trend, not snapshot
Every number against its trailing six months. A single period tells you almost nothing and invites over-reaction to noise.
- 03One anomaly investigated per review
Not a list of anomalies noted — one, chased to a conclusion. A review that surfaces twelve oddities and resolves none produces awareness without decisions.
- 04Read them in the cadence
Coverage and response time weekly; efficiency and retention monthly; the full set quarterly. The rhythm is in the RevOps operating cadence.
Want this diagnosed on your own numbers?
The RADAR™ Scan scores your revenue engine in 2 minutes — 12 questions, a 0–100 score, and your gate verdict. No email required.
Run your RADAR™ Scan→Questions this raises.
What are the most important RevOps metrics?
What is a good pipeline coverage ratio?
How do you measure whether RevOps is working?
Why is MQL count a bad target?
How many metrics should a RevOps dashboard have?
Related guides.
The function, the stack, the metrics, and the operating cadence — what revenue operations actually is once you strip out the vendor marketing.
RevOpsFour reviews, fixed agendas, named owners — the rhythm that stops a revenue system decaying back to entropy within two quarters.
RevOpsEach metric, how to calculate it without the usual errors, realistic benchmarks, and which two a board actually asks about.
RevOpsFirst we build your pipeline. Then we build the machine that scales it.
Every engagement starts with the RADAR™ Reveal — a 2-week audit with a scored report, gate verdict, and roadmap. Yours to keep, whatever you do next.