The RevOps metrics worth tracking

Most reporting disputes are definitional. Before building a dashboard, write down what each metric means, which records are included, and who owns the definition. That document prevents more arguments than any tool.

Sapwood is a revenue operations and GTM engineering shop in Denver. The diagnostic is free. Retainer $2,000 a month for up to 15 hours a week, Kaypo included. included in the retainer outside it.
See every price

The metrics that matter most are pipeline coverage, stage conversion, sales cycle length, speed to lead, net revenue retention, and forecast accuracy. Most reporting problems are definition problems rather than tooling problems: two teams calculate coverage differently, so the number becomes a debate instead of a decision.

Last updated September 2026

Published prices. The diagnostic is free. Retainer $2,000 a month for up to 15 hours a week, Kaypo included.

The core set

Dashboards built on agreed definitions, across pipeline coverage, stage conversion, retention, and campaign contribution. Retainer, two to three weeks.

Metrics that mislead

MQL volume

Trivially inflatable and frequently inflated. Track qualified conversion rate instead, which cannot be gamed by lowering the bar.

Activity counts

Calls and emails measure effort, not outcome. Useful for coaching a specific rep, misleading as a team metric.

Blended CAC

Averages across segments that behave nothing alike, producing a number that describes no actual customer.

Win rate without stage context

Win rate measured from first touch and win rate measured from qualified opportunity are different numbers, and people quote them interchangeably.

Define before you measure

A dashboard built on contested definitions gets ignored within a month, and rebuilding it does not help.

Common questions

Every price we charge is on the site.

No gated pricing and no call required to see a number. If you want to talk it through, the first one is free and takes thirty minutes.

See pricing More guides

Reporting and Business Intelligence

What it covers and what it costs

What we built and what it changed

The definitions everything inherits, where revenue leaks between teams, and one number with one source.

  • The RevOps tech stack What you need, and do not
  • Tools nobody uses Why it happens
  • Why the forecast is wrong The usual causes
MetricWhat it tells you
Pipeline coverageWhether the quarter is mathematically possible. Define it as open pipeline divided by remaining quota, and agree which stages count.
Stage conversionWhere deals actually die. Only meaningful once stages have exit criteria.
Sales cycle lengthBy segment, not in aggregate. Blended cycle length hides everything useful.
Speed to leadTime from record creation to first genuine contact attempt. One of the highest leverage numbers in the whole system.
Net revenue retentionThe number that determines whether growth compounds or leaks.
Forecast accuracyMeasured against commit, tracked over time. A forecast that is never scored is not a forecast.

Questions

What is a good pipeline coverage ratio?

Three to four times remaining quota is a common benchmark, though it depends heavily on your win rate. The ratio matters less than calculating it the same way every quarter.

What is a good speed to lead?

Under an hour is strong, under a day is acceptable, and multiple days means the signal is stale before anyone acts. Moving from five days to twelve hours is achievable inside one engagement.

How many metrics should we track?

Six to eight at the leadership level. Beyond that nobody reads them, and the dashboard becomes decoration.

What is net revenue retention and why does it matter?

Revenue from existing customers including expansion, minus churn and contraction. Above 100 percent means the base grows without new logos, which changes the economics of everything else.

How do we stop teams arguing about numbers?

Write the definitions down, name an owner for each, and put them where the dashboard lives. Almost every disagreement traces back to an unwritten definition.

Let us look under the hood.

Read-only access to your systems, and a written report you keep either way.

Start the free diagnostic

Let's chat.

Thirty minutes. Tell us what you are working on and we will tell you on the call whether we can help.

Add your name and a work email so we know who we are talking to.

Thank you!

We will reach out to you shortly. If you have not heard from us by tomorrow, email hello@sapwood.io.

While you wait, keep reading