Book a consultation
Resources

Sales Analytics & Revenue Operations

Revenue operations explained for B2B leaders: how RevOps works, the metrics that matter, and how to put it in place.

Read the guide
Lead to cash to renewal runs on one revenue data model, so every team trusts the same numbersLead-to-cash flow across marketing, sales, finance and customer success.MarketingLeadCaptured, scoredHandoff 1SalesClosed dealContract signedHandoff 2FinanceCashInvoiced, collectedHandoff 3Customer successRenewalRetained, expandedExpansionOne revenue data modelSame definitions for every teamTrusted revenue numbersLead to cash to renewal runs on one revenue data model, so every team trusts the same numbersLead, closed deal, cash and renewal stages, owned by marketing, sales, finance and customer success, share one revenue data model.MarketingLeadCaptured, scoredHandoff 1SalesClosed dealContract signedHandoff 2FinanceCashInvoiced, collectedHandoff 3Customer successRenewalRetained, expandedExpansionOne revenue data modelSame definitions for every teamTrusted revenue numbers

Revenue operations lines up sales, marketing, customer success and finance behind one revenue process and one set of data. This guide explains what revenue operations is, how it works, which metrics to track and how to calculate them, and the tools behind it. It is written for CROs, CFOs and RevOps leaders who want a revenue engine built on numbers everyone trusts.

What it is

What is revenue operations? One team owning the whole revenue process

Revenue operations, or RevOps, is the function that runs the processes, systems and data behind revenue across the whole customer lifecycle. Instead of sales ops, marketing ops and customer success ops working apart, RevOps joins them under shared definitions, shared tools and shared targets.

Revenue operations covers every stage; sales ops covers threeScope bars across seven lifecycle stages: three separate ops teams cover parts; revenue operations spans all seven.Revenue operations covers every stage; sales ops covers threeScope across the lifecycle: first touch, MQL, SQL, deal, won, onboarding, renewal and expansionFirsttouchMQLSQLDealWonOnboardingRenewalMarketing opsSales opsCustomer success opsRevenue operationsSeparate ops teams leave gaps at each handoff; revenue operations owns the whole process and shares it with finance.Revenue operations covers every stage; sales ops covers threeScope columns over seven lifecycle stages; RevOps spans all of them.Revenue operations covers everystage; sales ops covers threeScope across the lifecycle: first touch, MQL, SQL,deal, won, onboarding, renewal and expansionMktgopsSalesopsCSopsRevOpsFirst touchMQLSQLOpportunityClosed-wonOnboardingRenewal, expansionRevOps: one owner from first touch to renewal.

The difference from sales operations is scope. Sales operations supports the sales team. Revenue operations covers every stage, from first touch to renewal and expansion, and gives finance the same view of pipeline and revenue that sales sees. In short: one owner, one process and one set of numbers for revenue. That shared view is what makes the forecast credible.

Components

Revenue operations works when people, process and data line up

RevOps rests on three parts, people, process and data, with technology in support. If one is missing, the other two cannot hold the model together. A team with no agreed process argues about handoffs. A process with no clean data cannot be measured. Data with no owner decays.

RevOps problems often trace back to one weak part. Find it first, and fix it before adding tools or headcount.

Trusted revenue numbers rest on people, process and dataThree pillars, people, process and data, on a technology base, holding up one set of revenue numbers; each pillar shows what breaks without it.Trusted revenue numbers rest on people, process and dataThe three parts of RevOps, technology underneath, and what breaks when one is missingOne set of revenue numbers everyone trustsPeopleA RevOps lead who ownsthe revenue engineWithout it: data decaysProcessOne funnel with stageand handoff rulesWithout it: handoffs aredisputedDataOne metric dictionaryand clean CRM dataWithout it: nothing canbe measuredTechnologyA CRM and connected tools configured around the documented funnelTrusted revenue numbers rest on people, process and dataStacked: revenue numbers on top of people, process and data, on a technology base.Trusted revenue numbers rest onpeople, process and dataThe three parts of RevOps, technology underneath, andwhat breaks when one is missingOne set of revenue numbersPeopleA RevOps lead who owns the revenue engineWithout it: data decaysProcessOne funnel with stage and handoff rulesWithout it: handoffs are disputedDataOne metric dictionary and clean CRM dataWithout it: nothing can be measuredTechnologyCRM and connected tools
Component 1

Someone owns the revenue engine

People: a RevOps lead reporting to the CRO, COO or CEO, or a fractional team in smaller firms.

Component 2

Handoffs stop being disputed

Process: one documented funnel with stage definitions, handoff rules and a regular forecast rhythm.

Component 3

Everyone sees the same numbers

Data: one metric dictionary, clean CRM and revenue data, and dashboards from lead to renewal.

Component 4

Systems that support the process

Technology: a CRM and connected tools configured around the documented funnel, not the other way round.

Data maturity self-check

Which part of your revenue engine is weakest?

7 questions on common data practices. The result is an illustrative level, not a benchmark score.

Illustrative
1. Who owns the revenue process end to end?
2. Is the funnel documented with stage definitions and handoff rules?
3. Do marketing, sales and finance report the same revenue numbers?
4. Do your core metrics have written formulas and owners?
5. How clean is the CRM?
6. Are billing and finance data linked to the CRM?
7. Is there a regular forecast and pipeline rhythm?
0 of 7 answered
Benefits

Without revenue operations, each team wins its own metric and the company loses

Without revenue operations, every team optimizes its own number.

Marketing reports leads. Sales reports bookings. Finance reports recognized revenue. The three rarely match, and leadership meetings become debates about data instead of decisions about growth.

One shared funnel shows leads stall at MQL to SQLFunnel bars: 2,400 leads, 720 MQL, 180 SQL, 126 opportunities, 32 won; MQL to SQL at 25% is highlighted.One shared funnel shows leads stall at MQL to SQLDemo dataLeads by stage in one quarter, with the conversion rate to the next stageLeads2,400MQL72030% from LeadsSQL18025% from MQLOpportunity12670% from SQLClosed-won3225% from OpportunityOnly 25% of marketing-qualified leads are accepted as sales-qualified: fix that handoff first.One shared funnel shows leads stall at MQL to SQLFunnel bars with conversion per stage; the MQL-to-SQL handoff at 25% is highlighted.One shared funnel shows leads stallat MQL to SQLLeads by stage in one quarter, with the conversionrate to the next stageDemo dataLeads: 2,400MQL: 72030% from LeadsSQL: 18025% from MQLOpportunity: 12670% from SQLClosed-won: 3225% from OpportunityOnly 25% of MQLs become SQLs:fix that handoff first.

RevOps fixes this by agreeing definitions once and reporting from one source. Handoffs between teams become measurable, so leaders can see where leads stall and deals slip. Forecasts improve because they rest on consistent stage definitions and clean pipeline data.

For the CFO, the payoff is forecast accuracy and a clear link from pipeline to bookings to recognized revenue. The decision it supports: how much to commit to the board. For the CRO, it is visibility into conversion and capacity. The decision: where to add reps or coaching next quarter. Over time, the biggest gain is speed: decisions that used to wait for reconciled numbers now happen in the weekly meeting.

Metrics

Revenue operations metrics only help when each one has a formula and an owner

A metric without a formula invites argument. Write down each revenue operations metric once, with how it is calculated, who owns it and which system it comes from. These six are a common core set to start with. Show them together on one demo-data dashboard before rolling them out.

A demo RevOps dashboard on six core metrics

Demo data
Pipeline coverage2.4x▼ -0.3x
Win rate21%▼ -5 pts
Sales cycle length64 days▲ +6 days
Acquisition cost$18.2K▲ +7%

Coverage is 2.4x, but win rate fell 5 points this quarter

Win rate by quarter, closed-won / all closed opportunities, %

20%22.5%25%27.5%30%Q4Q1Q2Q321% in Q3: down 5 pts20%22.5%25%27.5%30%Q4Q1Q2Q321% in Q3: down 5 pts

So what: Review lost deals by stage before adding more pipeline.

MetricFormulaOwnerSource
Pipeline coverageOpen qualified pipeline / remaining targetCROCRM
Win rateClosed-won / all closed opportunitiesSales leaderCRM
Sales cycle lengthAvg days from creation to closed-wonSales leaderCRM
Customer acquisition costSales and marketing cost / new customersCFOFinance system

Know if the target is reachable

Demo

Pipeline coverage = open qualified pipeline / remaining revenue target for the period.

Know how often you win

Demo

Win rate = closed-won opportunities / all closed opportunities in the period.

Know how long deals take

Demo

Sales cycle length = average days from opportunity creation to closed-won.

Know if customers grow with you

Demo

Net revenue retention = (starting recurring revenue + expansion - contraction - churn) / starting recurring revenue.

Know how far to trust the forecast

Demo

Forecast accuracy = 1 - (absolute difference between forecast and actual / actual).

Know what a customer costs to win

Demo

Customer acquisition cost = sales and marketing cost / new customers in the period.

Step by step

How to implement revenue operations in 5 steps, starting with the process map

Start by mapping the revenue process from first touch to renewal. Name the owner of each stage and the handoff between teams. Note where data is entered, where it is missing and where teams use different words for the same thing.

Implement revenue operations in 5 steps

Select a stage, use Next or the arrow keys

Map the process. Map first touch to renewal, name the owner of each stage and handoff, and note where data breaks.

Step 1 of 5

Next, agree a metric dictionary. Define stages, statuses and core metrics once, with formulas and owners, and get sign-off from sales, marketing, customer success and finance.

Third, clean and connect the data. Remove CRM duplicates, enforce required fields and link marketing, billing and finance data so reports cover the full lifecycle.

Fourth, build shared dashboards. Report pipeline, conversion, forecast and retention from one source, with a view for each leader on the same definitions.

Finally, set the operating rhythm: weekly pipeline reviews, monthly forecast reviews and quarterly process reviews. Measure every improvement against the starting point, so the value of revenue operations is visible to the board.

The first two steps need no new software. They are about agreement, not tools, and everything that follows depends on them. The outcome is a revenue process every leader can see, measure and improve. A practical next step is a short review of your CRM data and definitions.

Tools

A revenue operations stack has four layers, and each depends on the one below

Buying more tools rarely fixes a RevOps problem. The stack works when each layer is clean before the next is added. The CRM comes first because every other layer reads from it. Analytics comes last because it can only report what the layers below capture.

Each layer reads from the one below, so the CRM comes firstFour stacked layers: CRM at the base, then marketing automation, integration and automation, and analytics and BI on top.Each layer reads from the one below, so the CRM comes firstA revenue operations stack, built from the bottom up4Analytics and BIDashboards and the forecast on a governed model3Integration and automationBilling, finance and product data linked to the CRM2Marketing automationCampaigns, forms, scoring and sequences1CRMOne record of every account and deal: HubSpot or SalesforceBuild and clean layer 1 first; analytics can only report what the layers below capture.Each layer reads from the one below, so the CRM comes firstFour stacked layers with the CRM as the base layer.Each layer reads from the one below,so the CRM comes firstA revenue operations stack, built from the bottom up4Analytics and BIDashboards and the forecast on a governedmodel3Integration and automationBilling, finance and product data linked tothe CRM2Marketing automationCampaigns, forms, scoring and sequences1CRMOne record of every account and deal:HubSpot or SalesforceBuild layer 1 first: analytics onlyreports what the layers below capture.
One record of every account and dealCRM: HubSpot or Salesforce are common choices for B2B teams.
Leads captured and nurturedMarketing automation and engagement: campaigns, forms, scoring and sequences.
Billing and product data in syncIntegration and automation: workflows linking finance and product data to the CRM.
Pipeline and retention you can trustAnalytics and BI: dashboards on a governed data model.
Forecasts built on the same dataForecasting, part of the analytics layer: pipeline and history from the CRM feed a forecast that finance and sales both review.

A simple rule helps when evaluating tools: if a new tool cannot read clean data from the CRM, it will only add another version of the truth.

HubSpotSalesforce
Frequently asked questions

Revenue operations: questions leaders ask before they build a RevOps team

What is the difference between revenue operations and sales operations?

Sales operations supports the sales team with territories, quotas, tools and reporting. Revenue operations covers the whole revenue lifecycle across marketing, sales, customer success and finance, with shared definitions and data. As a company grows, sales operations often becomes one part of a wider RevOps function.

Where should revenue operations report in the organization?

RevOps usually reports to the CRO, COO or CEO rather than to one department, so it stays neutral across marketing, sales and customer success. The reporting line matters less than a clear mandate to own revenue processes, systems and metric definitions across all of those teams.

When is a company ready for a RevOps model?

Consider revenue operations when teams report conflicting numbers, marketing and sales dispute handoffs, or forecasts keep missing. Companies without a dedicated team can start with a fractional RevOps and data function that sets definitions, cleans the CRM and builds shared dashboards.

Get a RevOps data review and see where your revenue numbers disagree

Want revenue operations metrics your whole leadership team trusts? Start with a consultation to review your CRM, definitions and forecasting process, before any build is proposed.

Explore sales and revenue analyticsSales forecasting
See how we work