RevOps Metrics and KPIs: What to Track and How to Report Them

RevOps metrics are the measures that show how efficiently marketing, sales and customer success convert spend and effort into revenue. A mid-market B2B team needs 10 to 12 KPIs across five layers (pipeline, conversion, velocity, retention and efficiency), plus a health check, reported from one dashboard with one definition per metric.

Some of the longest ranking guides list 25 or more KPIs. Highspot covers 25 and Default covers 26. A list that long is a glossary, not a scorecard. Gartner's research summary on how revenue operations drives commercial execution (May 2025) ties misaligned commercial execution to missed opportunities, revenue churn and missed annual goals. Metrics are the instrument that exposes that misalignment, and only if every team reads the same number the same way.

This guide covers:

• The difference between a metric and a KPI, and a three-question test for promoting one to the other
• The 12 KPIs that carry a mid-market revenue engine, with formulas and worked examples in AUD
• The decision each KPI drives, so every number earns its place on the dashboard
• A reporting cadence by audience: weekly, monthly and quarterly
• The reporting mistakes that make dashboards ignored

What Are RevOps Metrics and KPIs?

RevOps metrics are quantified measures of how marketing, sales and customer success turn effort and spend into revenue. A KPI is a metric with a target, an owner and a decision attached to it. Every KPI is a metric; most metrics should never become KPIs.

Revenue operations (RevOps) is the function that unifies the systems, data and processes behind marketing, sales and customer success. For the full operating model, read What Is Revenue Operations (RevOps)?. Metrics are the measurement layer of that model. Without them, alignment is an opinion.

A metric describes. A KPI instructs. Email open rate is a metric. Pipeline created per rep per month, with a target of AUD 400,000 and a named owner, is a KPI. Apply this test before adding anything to the dashboard:

• Owner: one named person is accountable for the number, not a team.
• Target: a threshold exists that separates green from red.
• Decision: a specific action changes when the number turns red.

A number that fails any of the three stays a metric. Keep it in a drill-down report, not on the leadership dashboard.

How Many RevOps KPIs Should a Mid-Market Team Track?

A B2B mid-market team should track 10 to 12 RevOps KPIs. Beyond 12, reviews become data tours and no single number carries a decision. The set below covers five layers and a health check, which is the minimum needed to diagnose where revenue leaks.

Order matters. Fix the health KPIs first. A win rate calculated on incomplete close reasons and inconsistent deal stages produces confident, wrong answers.

Which Pipeline Metrics Show Whether Growth Is Funded?

Pipeline created and pipeline coverage show whether next quarter's revenue is already funded. Pipeline created measures the inflow of new opportunity value; coverage measures whether the open pipeline is large enough to hit quota at the current win rate.

Coverage is a derived target, not a fixed rule. The required coverage ratio equals 1 ÷ win rate. At a 25% win rate, the team needs 4x coverage. At 33%, it needs 3x. Teams that borrow a generic 3x benchmark without checking their own win rate either over-invest in demand generation or under-fund the quarter.

• Pipeline created by source: split inbound, outbound, partner and customer-referred. A blended number hides which channel is decaying.
• Coverage by close month: measure current quarter and next quarter separately. Next quarter coverage is the leading indicator.
• Pipeline created per rep: use it to expose capacity problems before they surface as missed quota.

Which Conversion and Velocity Metrics Expose Process Friction?

Stage-to-stage conversion, win rate, sales cycle length and sales velocity show where deals leak and how fast revenue moves. Sales velocity combines four inputs into one figure: (opportunities × win rate × average deal size) ÷ sales cycle length.

A worked example, using illustrative figures: 40 qualified opportunities, a 25% win rate, an average deal size of AUD 60,000 and a 90-day cycle. Velocity is (40 × 0.25 × 60,000) ÷ 90, which equals AUD 6,667 of revenue per day. Raise the win rate to 30% and velocity moves to AUD 8,000. Cut the cycle to 75 days and it also reaches AUD 8,000. The formula shows which lever is cheapest to move.

Check the table before acting on it. A 5-point win rate gain and a 15-day cycle cut each produce the same velocity here, but they need different work: the first is a qualification and enablement problem, the second is a procurement and champion-building problem.

Track stage-to-stage conversion for every stage, not only the final win rate. The stage with the steepest drop relative to your own history is the repair target.

Which Retention Metrics Matter Most for Revenue Quality?

Net revenue retention (NRR) and gross revenue retention (GRR) measure revenue quality after the sale. NRR includes expansion; GRR excludes it and shows churn and contraction alone. A business can post healthy NRR while GRR is eroding.

Worked example, using illustrative figures: starting MRR of AUD 200,000, expansion of AUD 18,000, contraction of AUD 4,000 and churn of AUD 10,000. NRR is (200,000 + 18,000 − 4,000 − 10,000) ÷ 200,000, which equals 102%. GRR is (200,000 − 4,000 − 10,000) ÷ 200,000, which equals 93%. The 102% looks safe. The 93% shows that 7% of the base leaked and expansion covered it.

For context, the 2026 SaaS Benchmarks Report from SaaS Rise (June 2026) puts median annual NRR for private B2B SaaS at 101%, citing SaaS Capital, Benchmarkit, KeyBanc and ChurnZero data from 2025. Treat benchmarks as a sanity check, not a target. Your own cohort trend is the stronger signal. Non-subscription B2B firms, such as managed services and retainer agencies, apply the same formulas to monthly recurring revenue.

Which Efficiency Metrics Show Whether Growth Is Affordable?

CAC payback and blended customer acquisition cost (CAC) show whether growth is affordable. CAC payback is the number of months of gross margin needed to recover the cost of acquiring a customer: CAC ÷ (new MRR × gross margin).

Worked example, using illustrative figures: CAC of AUD 24,000, new MRR per customer of AUD 2,500 and a gross margin of 75%. Payback is 24,000 ÷ (2,500 × 0.75), which equals 12.8 months. The SaaS Rise report's founder scorecard treats under 12 months as a target and over 18 months as a red flag. Use those as reference points, then set your own threshold from your cash position.

• Calculate CAC fully loaded: include salaries, commissions, tooling, agency fees and a share of RevOps cost.
• Segment by channel and by deal size: a blended CAC hides the channel that is subsidising the rest.
• Pair payback with GRR: a 10-month payback on customers who churn at month 9 is a loss.

How Do You Measure RevOps Health?

RevOps health is measured by forecast accuracy and CRM data completeness. Forecast accuracy shows whether leadership can trust the pipeline number. Data completeness shows whether every other KPI is calculated on reliable records.

Forecast accuracy is 1 − (|forecast − actual| ÷ actual). A forecast of AUD 1,000,000 against actual closed-won of AUD 850,000 scores 1 − (150,000 ÷ 850,000), or 82.4%. Track it at the start of the quarter and again at the midpoint. A consistent over-forecast points to inflated stage definitions. A consistent under-forecast points to deals being created late.

Data completeness is the share of records with every required field populated: deal stage, amount, close date, source, owner and close reason. Set a floor of 95% for active deals and enforce it through required properties and stage gates in the CRM. A HubSpot optimisation audit is the fastest way to find which required fields are missing and which properties duplicate each other.

How Should You Report RevOps Metrics?

Report RevOps metrics on three cadences: weekly operational, monthly leadership and quarterly board. Run all three from one shared dashboard with one definition per metric. The audience changes which KPIs appear, never the numbers.

Build the reporting layer in this order:

1. Write a metric dictionary. One page per KPI: formula, data source, owner, target and refresh cadence. Define lifecycle stages and deal stages in the same document.
2. Repair the properties behind the KPIs. Required fields, picklists instead of free text, and one source-of-truth property per concept.
3. Build one dashboard per audience in the CRM. In HubSpot, use deal, contact and company properties with dashboards filtered by team and owner.
4. Set red, amber and green thresholds. Base them on your own trailing four-quarter average, not generic benchmarks.
5. Hold one review ritual. The same people, the same dashboard and the same agenda every week. Decisions get logged next to the number that triggered them.

For the wider operating model that these reports plug into, see RevOps Framework: A Practical Guide for Australian Mid-Market Companies. If you lack the internal capacity to run it, Fractional RevOps vs Full-Time Hire compares the cost of each route in AUD.

Want a second opinion on your HubSpot setup? We can review your deal stages, required properties and dashboards against these KPIs and tell you what to fix first.

What Reporting Mistakes Make RevOps Dashboards Useless?

The five most common reporting mistakes are tracking too many KPIs, leaving definitions unwritten, mixing lagging and leading indicators, reporting averages without distributions, and building dashboards before fixing data. Each one produces numbers that leadership learns to ignore.

• Too many KPIs. Past 12, nobody can name the three that matter this quarter.
• Unwritten definitions. When marketing and sales define "qualified" differently, the conversion rate between them is fiction.
• Lagging indicators only. Revenue and NRR report what already happened. Pair them with pipeline created, coverage and stage conversion, which move first.
• Averages without spread. A 90-day average cycle can hide a 30-day segment and a 200-day segment that need different treatment. Report median and the slowest quartile.
• Dashboards before data. Visualising incomplete records makes the error look authoritative.

AI-assisted forecasting and scoring raise the stakes on data quality. Models trained on inconsistent stages scale the inconsistency. The measurement foundation in this guide is the prerequisite for the AI GTM strategy most teams are now planning.

TL;DR

Track 10 to 12 RevOps KPIs across pipeline, conversion, velocity, retention and efficiency, plus forecast accuracy and data completeness as health checks. Give every KPI an owner, a target and a decision. Report weekly, monthly and quarterly from one dashboard with one written definition per metric. A short list on clean data surfaces problems while they are still fixable; 25 numbers nobody trusts hide them.