Revenue operations: what RevOps does, how teams are structured, and what it measures
What a revenue operations function is for, how it differs from sales ops, the three ways teams are structured, and the metrics a RevOps lead is judged on.
, 5 min read, Go-to-market
Key takeaways
- Revenue operations exists because sales, marketing and customer success each optimised their own systems and nobody owned the handoffs between them.
- Sales ops serves the sales team. RevOps serves the whole revenue funnel, which is why it usually reports to a CRO or COO rather than to a VP of Sales.
- The first year of a RevOps function is almost always data plumbing: one definition of an account, one source of pipeline truth, one funnel that reconciles.
- Judge the function on forecast accuracy, pipeline conversion and time reps spend selling, not on the number of dashboards it produces.
Most companies arrive at revenue operations the same way. Marketing reports a number of qualified leads. Sales reports a different number for the same month. Customer success has a churn figure nobody can tie back to how those accounts were sold. Three teams, three systems, three definitions, and a leadership meeting spent arguing about whose spreadsheet is right instead of what to do next.
Revenue operations is the function created to end that argument permanently. It is less glamorous than it sounds and more consequential than it looks.
What the function actually owns
One set of definitions
The unglamorous core of the job. What counts as an opportunity. When a lead becomes qualified and by whose judgment. What "pipeline" means, and whether it includes deals with no next step booked. What an account is when a customer has four subsidiaries.
These sound like bookkeeping questions. They determine whether a forecast is meaningful, whether a marketing channel looks profitable, and whether a rep's quota is achievable. Until one person owns them, every number in the business is negotiable.
The systems and the data flowing between them
A typical go-to-market stack has a CRM, a marketing automation platform, an outbound sequencer, a conversation intelligence tool, a data enrichment provider, a CPQ or billing system, and a business intelligence layer on top. Each was bought by a different team for a good reason. RevOps owns how they connect, what happens when a field changes in one and not the others, and who has permission to change what.
The handoffs
Marketing to sales. SDR to account executive. Account executive to customer success. Each of these is a point where context is lost, timing slips and accountability blurs. RevOps designs the rules for each one, instruments them, and reports on where deals stall.
Planning
Territory design, quota setting, capacity modelling, compensation plan mechanics and the annual number. These decisions usually involve sales leadership and finance, but the modelling work and the historical data behind it sit with revenue operations.
RevOps compared with sales ops
| Sales operations | Revenue operations | |
|---|---|---|
| Scope | The sales organisation | Marketing, sales, customer success |
| Reports to | VP of Sales | CRO, COO or CFO |
| Owns | Quotas, territories, CRM hygiene, commissions | The above, plus lifecycle definitions, the full funnel and cross-team handoffs |
| Typical question | Why is this rep behind quota | Why does this segment convert at half the rate of that one |
| Appears at | Roughly 20 to 30 reps | Roughly 50 employees, or earlier in product-led companies |
The distinction is not seniority. A strong sales ops function inside a sales-led company can be more sophisticated than a thin RevOps function elsewhere. The difference is whether the mandate crosses team boundaries, because that is what determines whether anyone can fix a handoff.
How teams get structured
Centralised. One team serving all go-to-market functions, reporting to a single leader. Fastest to align on definitions, and the default below roughly 200 employees. Risk: the queue gets long and the team becomes a ticket desk.
Embedded. Analysts sit inside marketing, sales and customer success, with a shared systems and data team underneath. Each function gets responsive support. Risk: the definitions drift apart again, which is the exact problem the function was created to solve.
Hybrid. Strategy, systems and the data model stay central. Analysts are distributed into the functions but report on a dotted line to RevOps. This is where most companies past 300 employees end up, because it keeps one source of truth while staying responsive.
A practical rule: centralise anything that must have a single definition, distribute anything that is about speed of response to one team's questions.
What to measure the function on
RevOps teams are often judged on output volume, dashboards built, tickets closed, which rewards activity over effect. The metrics that reflect whether the function is working:
- Forecast accuracy. Variance between the forecast at the start of the quarter and the actual result. A function that reduces this from 30 percent to 8 percent has changed how the company can plan.
- Stage conversion rates by segment. Not just overall win rate, but where deals die, per segment. This is the diagnostic the rest of the go-to-market strategy depends on.
- Pipeline coverage and its reliability. Coverage ratio matters less than whether the pipeline in the CRM reflects reality.
- Selling time. Hours per week a rep spends in customer conversations rather than in administration. Every automation project should move this number.
- Speed to lead. Time from inbound signal to first human contact, which is usually the single most improvable conversion input.
- Data completeness on the fields that drive decisions. Not all fields, only the ones feeding routing, reporting and compensation.
Building the function from scratch
The order matters, and the temptation is always to start at the end.
- Audit the definitions. Write down what each team currently means by lead, opportunity, pipeline, account and churn. The gaps are the roadmap.
- Fix the CRM data model. Objects, required fields, validation rules. Nothing downstream works if this is wrong.
- Instrument the funnel end to end. One funnel, agreed by all three teams, that reconciles from first touch to renewal.
- Automate the handoffs. Routing, alerts, task creation, so transitions do not depend on someone remembering.
- Then build reporting. Dashboards built before the first four steps simply display disagreement more attractively.
Most teams get impatient somewhere around step two and jump to step five. The result is a beautiful dashboard that leadership stops trusting within a quarter, and the original argument resumes.
When you need one
The honest trigger is not headcount. It is the first time a leadership meeting is spent reconciling numbers instead of deciding something. If that has happened twice in a quarter, the cost of not having the function is already higher than the salary.
Frequently asked questions
- What does revenue operations do?
- Revenue operations owns the systems, data and processes that the whole revenue funnel runs on: the CRM and the tools around it, the definitions behind each metric, the handoffs between marketing, sales and customer success, territory and quota design, forecasting, and the reporting leadership makes decisions from. In practice the job is making one version of the numbers exist.
- What is the difference between revenue operations and sales operations?
- Scope and reporting line. Sales operations supports the sales organisation: quotas, territories, CRM hygiene, commissions, pipeline reporting. Revenue operations covers the same ground for marketing and customer success as well, and owns the transitions between them. Sales ops usually reports to a VP of Sales, RevOps to a CRO, COO or CFO.
- How is a revenue operations team structured?
- Three common models. Centralised, where one team serves every go-to-market function, which is the norm below about 200 employees. Embedded, where analysts sit inside sales, marketing and customer success with a shared systems team. And hybrid, where strategy and systems are central while analysts are distributed. Most companies start centralised and move to hybrid as they grow.