Revenue Operations (RevOps)

Revenue Operations is the team that runs the plumbing under every dollar a B2B company books. RevOps owns the CRM, the comp plan logic, the territory map, the forecast model, the funnel stages, and the analytics that connect a marketing-sourced lead to a renewal three years later. The function emerged because sales ops, marketing ops, and customer success ops were each owning a slice of the same revenue motion and arguing about whose numbers were right. Putting one VP over all three ends the argument.

What RevOps Actually Does

A RevOps team owns four things: systems (CRM, marketing automation, CPQ, comp tools), data (the source of truth for pipeline, bookings, attribution), process (lead routing, opportunity stages, forecast cadence), and enablement of the leaders (deal desk, territory design, capacity planning). The work splits into strategic projects — designing the comp plan for FY27, building the new segmentation model — and operational reps — closing the books, scrubbing pipeline, running the Monday forecast call.

The team reports into the CRO or COO at most growth-stage companies. A 200-person sales org runs roughly 1 RevOps headcount per 25 quota-carrying reps. Under that ratio, you find the VP Sales rebuilding spreadsheets at 11pm instead of selling.

How to Identify a RevOps Function

You have RevOps if a single team owns:

If those live in five different teams, you have sales ops, marketing ops, and CS ops — not RevOps. The naming matters less than the consolidation.

Worked Example

A Series C SaaS company at $40M ARR has 32 AEs, 18 SDRs, 6 CSMs, and 1.5 RevOps headcount. The team is drowning. Forecast accuracy is ±18%. The board asks for net retention by cohort and nobody can produce it without a week of spreadsheet work.

The CRO hires a VP RevOps and three more analysts. Twelve months later: forecast accuracy is ±6%, the comp plan rebuild moved pay mix from 60/40 to 50/50 with accelerators above 110%, and the pipeline coverage target is now segmented by stage and segment instead of a single 3x rule. Net new ARR per rep ticks up 14%.

When Sales Orgs Build a RevOps Team

The trigger is pain. The CRO can't forecast within ten points. The CFO doesn't trust the bookings number. Reps are paid late or wrong. Marketing claims they sourced 60% of pipeline; sales says 20%. Each of those is a RevOps gap.

By company stage: under $5M ARR, the COO or a senior AE handles it. $5M–$20M ARR, one sales ops manager. $20M+ ARR, a dedicated VP RevOps with a team. Above $100M ARR, RevOps splits into deal desk, comp & territory, analytics, and systems sub-functions.

Common RevOps Misconceptions

Three things RevOps is not. It is not a glorified CRM admin role — admin is one slice of systems work, not the job. It is not a reporting function — building dashboards without owning the definitions underneath produces pretty charts that disagree with each other. It is not neutral — RevOps decides what gets measured, which means it decides what gets rewarded, which means it shapes rep behavior more than any sales manager.

The pattern to watch: a weak RevOps team lets sales leaders define their own stage criteria and forecast categories. The result is optimistic pipeline padding and a forecast that misses by twenty points two quarters in a row. The function exists to enforce the definitions, not negotiate them.