What does revenue operations do?

Owns the definitions, process, systems and measurement spanning marketing, sales and customer success. The distinguishing feature is decision rights over definitions — a team that only builds what it is asked to build is a service desk rather than a capability.

What is the difference between revenue operations and sales operations?

Scope. Sales operations serves the sales function; revenue operations spans the full customer lifecycle. The practical difference is authority at the boundaries between functions, which is where most operational failures occur.

Why do companies create a RevOps function?

Usually because reporting has stopped reconciling — two teams produce different numbers from the same systems and nobody can settle it. That symptom traces to definitions owned by nobody, which is the problem the function exists to hold.

Who should revenue operations report to?

Whoever makes it neutral across the functions it serves. Reporting into sales tends to make it a sales support team; the structural test is whether it can hold a definition against the largest function's preference.

Revenue Operations (RevOps)

The function that owns the systems, data and process connecting marketing, sales and customer success, so that revenue is produced by a designed system rather than by four teams improvising in parallel.

What the function is for

To make the organisation's revenue engine legible and operable: what the terms mean, how work moves between functions, which systems are authoritative, and whether the numbers describe reality. The output is the capacity to know what is true about revenue and act on it, rather than to argue about it.

Service desk or capability

Two teams of identical size and seniority can be doing very different work. One administers systems — builds fields on request, fixes broken automations, produces reports when asked. The other owns the definitions those systems encode.

The observable difference

Where the capability is absent, disagreements about performance are settled by seniority. Where it is present, they are settled by checking. That is the function's actual output, and it compounds.

What sits inside the remit

Definitions — what a qualified lead is, when a stage advances, which system is authoritative for a field. The definitional layer is the one that makes everything above it reconcilable.
Process — how work crosses function boundaries, who owns each step, what happens when a step fails.
Systems — configuration, integration and the governance of change, so that a change made in one place does not silently break another.
Measurement — the metric set, its construction, and the discipline of reviewing whether each measure still tracks what it was chosen to represent.
Planning — capacity, territory and quota design, which determine much of measured performance before any selling happens.

Where it goes wrong

Given responsibility without decision rights, the team executes other people's choices and inherits the consequences.
Positioned inside one function, it optimises that function's boundary at the expense of the others.
Measured on ticket throughput, it becomes efficient at request-taking, which is the activity that most reliably prevents structural work.
Staffed for tooling rather than for reasoning, it produces well-configured systems encoding definitions nobody agreed.

RELATED TERMS

Data Governance

The rules determining who may change what, how changes are reviewed, and how they are recorded. The control that stops a designed system from drifting back to whatever it was before.

Revenue Leakage

Revenue the business had already earned the right to collect but does not, through process gaps rather than lost deals — unbilled usage, missed renewals, unapplied price increases, discounts that outlive their approval.

Lifecycle Stages

The shared sequence describing a contact's relationship with the company over time — subscriber through customer — used to align marketing, sales and customer success on where someone is.

Single Source of Truth (SSOT)

The declared authority for a given piece of data — the system whose value wins when two systems disagree. Correctly applied it is decided per field, not per system.

COMMON QUESTIONS

What does revenue operations do?: Owns the definitions, process, systems and measurement spanning marketing, sales and customer success. The distinguishing feature is decision rights over definitions — a team that only builds what it is asked to build is a service desk rather than a capability.
What is the difference between revenue operations and sales operations?: Scope. Sales operations serves the sales function; revenue operations spans the full customer lifecycle. The practical difference is authority at the boundaries between functions, which is where most operational failures occur.
Why do companies create a RevOps function?: Usually because reporting has stopped reconciling — two teams produce different numbers from the same systems and nobody can settle it. That symptom traces to definitions owned by nobody, which is the problem the function exists to hold.
Who should revenue operations report to?: Whoever makes it neutral across the functions it serves. Reporting into sales tends to make it a sales support team; the structural test is whether it can hold a definition against the largest function's preference.