heyarnoux.

Function

RevOps and sales ops differ by what they are allowed to decide

Every comparison of the two lists the same differences: scope, remit, which teams they cover. Those are descriptions of an org chart. The distinction that predicts whether the function works is narrower and easier to check: whether it can change a definition, or can only report against one somebody else owns.

Sales operations supports a sales team: territories, quotas, the CRM, forecasting, commissions. Revenue operations covers the same ground across marketing, sales and customer success, on the argument that a buyer does not experience those as three departments. That is the textbook answer and it is accurate as far as it goes.

It also does not explain why two companies with identical org charts get completely different results from the same rename. The thing that varies is authority, and it is almost never written down.

The question that separates them

Ask who can change the definition of a qualified lead without asking permission.

If the answer is a marketing leader, and the operations function implements whatever they decide and reports on the result, that is sales ops, whatever the business cards say. If the operations function can say that the current definition is producing bad routing and change it, that is revenue operations. The title is downstream of that answer.

The same test works on any of the handful of definitions a go-to-market system runs on:

  • What counts as a qualified lead, and therefore what marketing is measured on.
  • What a pipeline stage means, and therefore what the forecast is built from.
  • What counts as churn as against a downgrade, which decides whether retention looks fine.
  • Which account belongs to whom, which decides compensation and therefore behaviour.

Each of those definitions is owned by somebody whose number improves when it moves. That is the structural problem revenue operations exists to solve, and a function without the authority to overrule those owners cannot solve it.

What the rename moves, and what it usually does not

ThingUnder sales opsUnder revenue operations
Reporting lineTo the sales leader.To a revenue or operating leader above all three functions. This is the part that rarely changes.
DefinitionsReceived from whoever owns the number.Owned by operations and argued about in public.
Scope of toolingThe CRM and what feeds it.The whole path from first touch to renewal.
What it is measured onSales productivity.Conversion between functions, which is where the losses are and which nobody owned before.

Most renames move the third row and leave the first two alone. The team gets more systems to maintain, no more authority than before, and a title that promises coordination it cannot enforce. That is the common failure, and it looks like an operations problem rather than the governance problem it is.

The three jobs that only exist in revenue operations

If a function is doing none of these, the rename was cosmetic.

Reconciling definitions across functions. Marketing's qualified lead, sales' accepted lead and success' healthy account are usually defined independently, measured separately, and quietly inconsistent. Somebody has to hold the single version and say no.

Owning the handoffs rather than the stages. Each function optimises its own stage and the losses collect in the gaps between them. The gap is the only thing that belongs to nobody by default, which is why it is where revenue operations earns its cost.

Governing the write path end to end. A field written by four processes in three formats cannot be reported on consistently, and that problem is not solvable inside one function because the processes belong to different ones.

DefinitionsReconciled across functions, not per function
HandoffsOwned by name, because the gaps belong to nobody
Write pathsGoverned end to end, across department lines

Why the rename fails when it fails

It fails when the function is given responsibility for an outcome and authority over only part of its inputs. Conversion from marketing-qualified to sales-accepted is the standard example: operations gets measured on it, marketing owns the qualification rule, sales owns the acceptance rule, and operations owns a dashboard.

The fix is not more tooling. It is writing down which definitions operations owns outright, and accepting that this takes something away from whoever owned them before. Teams that skip that conversation have renamed a function rather than changed one.

When sales ops is the right answer

When there is one revenue motion and one team running it. Coordination between functions is not a problem you have yet, and a function built to solve it will spend its time on ceremony.

When the operations headcount is one person. One person cannot own the definitions of three functions and also keep the CRM working. Give them the CRM and the definitions that routing and scoring actually read, and leave the rest.

When the executives still disagree about the model. Revenue operations enforces a shared definition. If there is no agreement to enforce, the function becomes the venue for the argument rather than the resolution of it.

Questions people ask

What is the difference between RevOps and sales ops?

Sales ops supports one function; revenue operations spans marketing, sales and success. The difference that predicts results is narrower: whether the function can change a definition or only report against one.

Is RevOps just a rename of sales ops?

Frequently it is. If the reporting line and the ownership of definitions did not move, the team got more systems and no more authority.

Who should RevOps report to?

Somebody above all the functions it is meant to reconcile. Reporting into sales while being measured on marketing conversion is the structural version of the problem it exists to fix.

When do you need revenue operations rather than sales ops?

When losses are collecting in the handoffs between functions rather than inside any one of them. With a single motion and a single team, that problem does not exist yet.

What does a revenue operations team actually own?

At minimum: the reconciled definitions, the handoffs between functions, and the write paths that cross departmental lines. A team owning none of those has been renamed rather than rebuilt.

Or skip the search

Want the person who owns it after it ships?

If the work is a standing obligation rather than a bounded project, tell me which system you want built first. You get example profiles and a call with your pick before anything starts.

Placement runs through AYTalent. Engineers are employed and trained on the bench before they start with you.