Revenue operations (RevOps) is the function that aligns marketing, sales, and customer success around shared data, processes, and goals. RevOps metrics are the measurements that cut across all three teams to give a unified view of how the revenue engine is performing. Unlike siloed metrics that each team tracks independently (marketing tracks MQLs, sales tracks win rate, CS tracks NPS), RevOps metrics are designed to reveal how the handoffs between teams affect the final outcome: revenue retained and grown.
The value of RevOps metrics is accountability across the full funnel. When marketing, sales, and CS each track their own metrics in isolation, each team can “succeed” while overall revenue growth stagnates — because the gaps between teams are where value is lost. RevOps metrics make those gaps visible.
Funnel Conversion Metrics
The most foundational RevOps metrics track conversion at each stage transition across the full funnel: from lead to MQL, from MQL to opportunity, from opportunity to close, and from new customer to retained/expanded customer.
The key funnel conversion metrics:
- Lead-to-MQL rate: What percentage of raw leads meet qualification criteria? Low rate indicates poor top-of-funnel targeting; high rate with poor downstream conversion indicates weak MQL criteria.
- MQL-to-opportunity rate: What percentage of MQLs that sales receives are converted to active opportunities? This is the primary marketing-to-sales handoff metric.
- Opportunity-to-close rate (win rate): What percentage of qualified opportunities result in won deals? Measured overall and by lead source, segment, rep, and competitor.
- New customer-to-retained-customer rate (logo retention): What percentage of new customers are still customers 12 months later?
Tracking all four together reveals where the funnel is leaking. A RevOps team that can see that MQL-to-opportunity rate dropped from 28% to 19% in Q2 can investigate and determine whether the problem is lead quality (marketing issue), follow-up speed (sales operations issue), or qualification criteria (RevOps definition issue) — and route the fix to the right team.
Pipeline Metrics
Pipeline Coverage
Pipeline coverage ratio is total pipeline divided by revenue target. The standard benchmark is 3-4x: if you need $1M to close this quarter and have $3M in qualified pipeline, you are at 3x. Below 3x at the start of a quarter is a risk signal; above 5x often indicates pipeline hygiene problems (stale deals inflating the count).
RevOps manages pipeline coverage differently than sales managers do. Sales managers watch coverage at the team or rep level. RevOps watches it in aggregate and by segment, and uses coverage trends (three consecutive quarters of declining coverage) as a leading indicator of future revenue misses — allowing proactive intervention before the miss happens.
Pipeline Velocity
Pipeline velocity is revenue generated per time unit from the current pipeline: (Opportunities x Win Rate x ACV) / Sales Cycle Length. It is the single metric that most comprehensively represents GTM engine efficiency, because it incorporates all four drivers simultaneously.
RevOps uses pipeline velocity to model the effect of interventions. If win rate improves by 5 percentage points (from 25% to 30%), what is the velocity impact? If average deal size increases by $2,000 (from $10,000 to $12,000), what does that do to velocity? These calculations allow RevOps to prioritize improvement initiatives by expected revenue impact.
Average Sales Cycle Length
Average sales cycle length (the time from opportunity creation to close) is tracked as a RevOps metric because it affects both pipeline velocity and forecasting accuracy. Sales cycles that are lengthening over time signal either mix shift (more complex enterprise deals entering the pipeline), qualification problems (opportunities are being qualified too early and taking longer to close), or process friction (proposals, legal review, and procurement cycles are taking longer).
Sales cycle length by stage reveals where deals are spending time. A deal that takes an average of 45 days from discovery to proposal submission and another 60 days from proposal to close has a different process improvement opportunity than a deal where total cycle time is 90 days with 60 days in discovery. Stage-by-stage cycle time gives RevOps teams the specificity to target interventions.
Revenue Retention and Growth Metrics
Net Revenue Retention (NRR)
NRR is the most important RevOps metric for a subscription business at scale. It measures the percentage of ARR from a cohort of existing customers that is retained and grown over a period (typically 12 months), including expansion revenue from upsells and seat additions, and net of churn and contraction.
NRR above 100% means existing customers are growing faster than they are churning — the installed base compounds on its own. Best-in-class SaaS NRR is 120-140%+. NRR that falls below 100% means the installed base is shrinking, which requires ever-increasing new customer acquisition to maintain flat revenue — a deteriorating unit economic position.
Gross Revenue Retention (GRR) / Logo Retention
GRR measures the percentage of ARR retained from existing customers, excluding expansion. It is the floor on NRR — NRR can exceed 100% only if expansion revenue from remaining customers more than compensates for churned ARR. Tracking GRR separately from NRR makes churn visible even in companies with strong expansion economics.
Expansion Revenue Rate
Expansion revenue rate is the additional ARR generated from existing customers through upsells, cross-sells, and seat or usage growth as a percentage of opening ARR. For mature SaaS companies, expansion is often the primary growth driver because it requires no acquisition cost. RevOps tracks expansion rate to ensure the CS and expansion motion is performing and to identify accounts with unused expansion potential.
Unit Economics Metrics
Customer Acquisition Cost (CAC)
CAC is total sales and marketing spend divided by new customers acquired in a period. RevOps tracks CAC at the blended level and by channel, because blended CAC masks the significant variation in acquisition cost by source. Inbound organic leads typically have a far lower marginal CAC than enterprise outbound; understanding the mix and its trend allows better resource allocation.
CAC Payback Period
CAC payback period is the months required to recover CAC from customer revenue at current gross margins. It is calculated as CAC / (MRR per customer x gross margin %). Standard benchmark: 12-18 months for well-run B2B SaaS. A rising payback period signals either increasing acquisition cost or declining ACV/gross margin — both worth investigating.
Customer Lifetime Value (CLV) to CAC Ratio
CLV/CAC is a ratio that expresses how much revenue a customer generates over their lifetime relative to what it cost to acquire them. A ratio above 3:1 is typically considered healthy for SaaS; the higher the ratio, the better the unit economics of acquisition. CLV is calculated from average contract value, average retention period (1 / monthly churn rate), and gross margin.
Operational Efficiency Metrics
Lead Response Time
Lead response time is the median time between MQL creation and first sales contact. Research consistently shows that contact rates and qualification rates fall sharply with each hour of delay: a lead contacted within 5 minutes is 9x more likely to qualify than one contacted after 30 minutes. RevOps monitors response time to identify process gaps (no coverage during specific hours, leads sitting in queues, routing errors) and holds the standard against which sales operations improvements are measured.
Forecast Accuracy
Forecast accuracy is the percentage variance between committed forecast and actual closed revenue at the end of a period. RevOps owns the forecasting model and is responsible for its accuracy. Consistently over-forecasting means deals that were in the pipeline were not as qualified as they appeared; consistently under-forecasting means the company is leaving revenue on the table in resource planning. RevOps uses forecast accuracy trends to improve the model over time.
Data Quality Score
A composite measure of CRM data completeness (required fields populated), accuracy (correct information vs. verified sources), and freshness (how recently data was updated). Data quality is not a revenue metric in itself, but it is a prerequisite for accurate reporting on all of the above. A RevOps function that cannot produce reliable attribution, pipeline, and retention reports because CRM data is incomplete has a foundational problem that will undermine every other metric on this list.
Building a RevOps Metrics Dashboard
An effective RevOps metrics dashboard should be:
- Cross-functional. Include metrics that span marketing, sales, and CS rather than replicating each team’s existing dashboard. The value of RevOps is the connected view.
- Leading and lagging. Include both outcome metrics (revenue, NRR, win rate) that reflect historical performance and leading indicators (pipeline coverage, activation rate, MQL volume) that predict future performance.
- Actionable. Every metric on the dashboard should have an owner, a target, and a defined response if the metric falls below threshold. A dashboard that shows data without triggering action is a reporting tool, not a management tool.
The discipline of RevOps is not in the metrics themselves but in using them to drive the cross-functional conversations and interventions that would not happen if each team tracked only their own KPIs. The metrics are the vocabulary; the alignment is the value.