RevOps is not sales ops with a bigger remit

Three teams close the same quarter and report three different numbers. Marketing counts 340 leads and £1.2m of influenced pipeline. Sales counts 210 qualified opportunities and £780k closed-won. Finance invoices £712k. Nobody has miscounted, and no single system is broken.

What is missing is an owner for the definitions in between. Marketing decides what counts as a lead. Sales decides when a lead becomes an opportunity. Finance decides when revenue is recognised. Each definition is reasonable on its own, each was set by a different team for a different purpose, and no one is accountable for the fact that they do not compose.

That gap is the thing revenue operations exists to close, and it is why RevOps is not sales ops with a wider job title.

What sales ops actually owns

Sales ops serves the sales organisation. The remit is real and demanding: territory and quota design, pipeline hygiene, forecast submission, CRM configuration for the way reps work, commission calculation, and the weekly discipline of making sure the pipeline review is looking at something true.

The defining characteristic is not the size of the job. It is the boundary. Sales ops optimises one function's process, reports into that function's leadership, and is measured on that function's outcomes. When a sales ops lead finds that the marketing team's lead definition is inflating the top of the funnel, they can raise it. They cannot settle it.

Marketing ops has the mirror-image scope on the other side: campaign infrastructure, the automation platform, list hygiene, form and landing-page plumbing, and the lead lifecycle up to the point of handover.

Both functions do necessary work. Both stop at the same place — the seam.

Where RevOps starts

RevOps takes the seams as its subject. Not the CRM, not the automation platform, not the dashboard — the joins between them, and the definitions that have to hold steady across all three.

That is why the reporting line matters more than it looks. A revenue operations function that reports into sales is sales ops with a broader title, because when marketing's definition and sales' definition conflict it will resolve in sales' favour every time. The authority to settle a cross-functional argument has to come from somewhere above the functions in dispute.

The definitions problem is most of the job

It is tempting to describe RevOps as tooling and integration work. In practice the tooling is downstream of a smaller and much harder problem: agreeing what the words mean and then enforcing it in the systems.

A short and entirely ordinary list of questions that most organisations have never formally answered:

• What is a lead? Anyone who filled in a form, or anyone who filled in a form and matches the target profile? If a single company submits four forms, is that one lead or four?
• When is an opportunity created? When a rep books a call, when a discovery call happens, or when a budget is confirmed? Move that boundary by one step and every conversion rate in the business changes.
• What is the deal value? First-year contract value, total contract value, or annualised recurring revenue? A three-year deal at £30k a year is £30k, £90k or £30k depending on which system you ask.
• When does a deal close? On verbal agreement, on signature, or on first invoice? The gap between signature and invoice is where the CRM and the finance system stop agreeing.
• What is churn? Logo churn, revenue churn, or net revenue after expansion? These can point in opposite directions in the same quarter.

None of these has a universally right answer. Every one of them needs a decided answer, written down, and implemented identically everywhere it appears. That is the work. The integration project that follows is comparatively mechanical.

What a definition costs once it has drifted

The reason this is worth paying someone to fix is that undefined terms do not stay a reporting inconvenience. They become decisions.

A marketing team judged on lead volume against a loose lead definition will optimise for the loose definition, because that is what the dashboard rewards. Spend moves toward the channels that produce the most form fills. If those form fills convert at a fraction of the rate of a channel that produces fewer, better-qualified enquiries, the budget has been reallocated toward the worse channel by a measurement artefact — and everyone involved was doing their job correctly against the numbers they were given.

The cost is not the wrong dashboard. It is the quarter of spend that followed it.

When consulting is the right shape, and when it is not

RevOps consulting suits a specific situation: the definitional and structural work is substantial, largely one-off, and needs authority that cuts across functions — but the ongoing administration afterwards does not justify a permanent senior salary.

The honest signals that you want a permanent hire instead:

• The volume of daily operational work is already a full job — routing exceptions, access requests, forecast chasing, enablement.
• The work is inseparable from internal relationships that take months to build.
• You need someone in the room for decisions that happen continuously rather than in a defined project.

The honest signals that consulting fits:

• The systems disagree and nobody can say authoritatively why.
• You are integrating stacks after an acquisition, a replatform or a merge of two teams.
• You need a decision recorded and implemented, not a person to attend standups.
• You have tried to fix it internally twice and it has stalled both times on cross-functional disagreement rather than on capability.

The middle case — you need the seniority continuously but not full time — is what fractional RevOps describes. It is a commercial shape rather than a different discipline.

What to ask before you buy

Four questions that separate a scoped engagement from an open-ended one:

1. 01What is the first deliverable, and when? A written definitions document naming who signed off each term is a good first artefact. "A discovery phase" is not.
2. 02What changes in the systems, and what changes in the process? An engagement that only produces a slide deck has moved nothing.
3. 03Who has to agree, and have they agreed to agree? If marketing and sales leadership have not accepted in advance that a decision will be made and enforced, the project will produce a document nobody implements.
4. 04How will we know it worked? The testable outcome is usually that two named systems report the same figure for the same period, or that a metric everyone already watches becomes reproducible from source. Anyone quoting you a multiple of return on the engagement is guessing.

The short version

Sales ops makes the sales team effective. Marketing ops makes the marketing team effective. RevOps makes the handoffs between them survive contact with a board pack.

If your systems disagree about the same quarter and every attempt to fix it stalls on which team's definition is correct, the problem is not tooling and it is not seniority within a function. It is that nobody has been given the authority to decide.

That is the job. Everything else is implementation.

If this is the argument you keep having, revenue operations consulting is the page that describes how the work is scoped, and what RevOps is covers the discipline itself in more detail.