What does a RevOps manager do?

A revenue operations manager owns the process that runs between marketing, sales and customer success — the definitions of each lifecycle stage, the rules that route work between teams, the service levels those teams owe each other, and the data the forecast is assembled from. The distinguishing feature against an analyst role is ownership: an analyst reports on how the process performed, a manager decides how it works.

What skills does a RevOps manager need?

Three, in rough order of how often they are the binding constraint. Process reasoning — being able to model how work actually flows and find where it stalls. Measurement literacy — knowing what a metric includes, excludes and distorts. And negotiation, because almost every RevOps decision takes something away from one function to give it to another, and the job is done through influence far more often than through authority.

Is RevOps manager a senior role?

It varies enough that the title alone is not informative. At a company under a hundred people it is frequently the most senior operations role and reports to a CRO or founder. At a larger company it sits under a Director or VP of Revenue Operations and owns one surface of the funnel. The reliable markers of seniority are whether the forecast is yours and whether anyone reports to you, not the word on the contract.

What is the difference between a RevOps manager and a sales ops manager?

Scope. Sales operations serves the sales function: pipeline, quota, territory, sales tooling. Revenue operations spans marketing, sales and customer success, which means owning the handoffs between them — the places where most revenue is actually lost. In practice many RevOps manager roles are sales ops roles with a broader title, and the way to tell is whether marketing and customer success process decisions genuinely run through the role.

THE ROLE

RevOps manager: what the role owns, and how it fails

The job is not administering a CRM. It is owning the process that runs between three functions that each believe they own it already — which is why the role succeeds or fails on authority far more than on tooling.

The clearest way to describe a revenue operations manager is by what breaks when the role is absent. Marketing declares a lead qualified; sales disagrees and works none of them. An opportunity sits in a stage nobody has defined an exit criterion for. Two systems hold a different value for the same customer and the forecast is assembled from whichever one the report happened to query. None of these is a tooling problem, and none of them belongs to any single function — which is exactly why they persist.

A RevOps manager owns them. Concretely, that means owning the lifecycle stage definitions, the routing rules, the service-level agreement between marketing and sales, the data quality standard, and the measurement everyone argues about at the quarterly review.

The authority problem, which is the whole job

Nearly every RevOps decision is a transfer. Tightening the definition of a qualified lead takes credit away from marketing and gives cleaner pipeline to sales. Enforcing stage exit criteria takes flexibility away from account executives and gives accuracy to the forecast. Standardising a field takes local convenience away from one team and gives reporting integrity to everyone.

This means the role is accountable for outcomes it usually cannot mandate. The functions that have to change behaviour do not report to it. That gap — accountability without authority — is the single most common reason capable people leave these jobs, and it is visible in the job posting before you take it if you read the verbs (see how to read a RevOps posting).

The managers who succeed close the gap with evidence rather than with escalation. A proposal that says “routing is broken” is an opinion and will be argued with. One that says “forty-one percent of inbound leads waited more than a day, and those converted at a third the rate of the ones that did not” is a measurement, and it changes the conversation from preference to arithmetic. That is the practical reason the measurement skill matters more than it looks like it should.

The first ninety days in a RevOps manager role

1
Inventory what exists before changing any of it
Every lifecycle stage and its definition, every routing rule, every required field, every report leadership actually looks at. Most organisations cannot produce this list, and producing it is the first thing that makes the role credible.
2
Find the definitions that two functions disagree about
Ask marketing and sales separately what a qualified lead is. Ask sales and customer success separately when an account is 'onboarded'. Where the answers differ you have found the handoff that is leaking, without needing any data at all.
3
Measure one leak properly
Pick the disagreement with the most revenue behind it and quantify it end to end. One well-measured finding buys more authority than five accurate opinions, because it cannot be argued with on preference.
4
Fix it with the smallest possible change
Resist the urge to redesign the funnel. A single enforced exit criterion, or one routing rule with an owner attached, delivers a visible result inside a quarter — and a visible result is what buys permission for the larger change.
5
Write the definition down where the argument happens
An agreement that lives in someone's memory is relitigated every quarter. Put it in the system, in the field help text, and in the report — not in a document nobody opens.

Three failure modes that come with the title

Becoming the report desk. The fastest way to lose the strategic half of the job is to be excellent at the tactical half. Ad-hoc report requests expand to fill whatever capacity exists, and a manager who answers all of them has no time left to change anything. The defence is a standing reporting layer plus a genuine refusal, not faster turnaround.

Owning the tool instead of the process. Administering the CRM is adjacent to the job and is not the job. It is also infinitely expandable, and it is the work that is most visibly urgent, which is why roles drift into it. A manager whose quarter is measured in configuration changes has been reclassified without anyone saying so.

Optimising a metric that hides the problem. Improving a conversion rate by tightening what counts as a conversion is not an improvement, and it is remarkably easy to do accidentally. Any measurement the role owns is a measurement the role can distort — which is the reason measurement literacy is a governance skill here and not an analytical nicety.

WHERE THIS FAILS

At companies under about fifty people this role is not really a process role. There is not enough process yet. It is a build role: standing up the systems and the definitions for the first time, which is different work with a different skill profile.

Where sales operations already exists and is strong, a new RevOps manager role is frequently scoped as marketing and customer success operations with a broader title. That can be a good job. It is not the job described above, and the difference is worth establishing before you accept it.

Learn the audit that makes the case

The ninety-day protocol above is a compressed version of a RevOps audit. The long version — what an audit is, the five domains it covers, and how to scope one — is written up in what is a RevOps audit. The course runs it properly: inventory, measure, prioritise, and export the whole thing as a workbook you can put in front of a leadership team.

See the training Job description template

COMMON QUESTIONS

What does a RevOps manager do?: A revenue operations manager owns the process that runs between marketing, sales and customer success — the definitions of each lifecycle stage, the rules that route work between teams, the service levels those teams owe each other, and the data the forecast is assembled from. The distinguishing feature against an analyst role is ownership: an analyst reports on how the process performed, a manager decides how it works.
What skills does a RevOps manager need?: Three, in rough order of how often they are the binding constraint. Process reasoning — being able to model how work actually flows and find where it stalls. Measurement literacy — knowing what a metric includes, excludes and distorts. And negotiation, because almost every RevOps decision takes something away from one function to give it to another, and the job is done through influence far more often than through authority.
Is RevOps manager a senior role?: It varies enough that the title alone is not informative. At a company under a hundred people it is frequently the most senior operations role and reports to a CRO or founder. At a larger company it sits under a Director or VP of Revenue Operations and owns one surface of the funnel. The reliable markers of seniority are whether the forecast is yours and whether anyone reports to you, not the word on the contract.
What is the difference between a RevOps manager and a sales ops manager?: Scope. Sales operations serves the sales function: pipeline, quota, territory, sales tooling. Revenue operations spans marketing, sales and customer success, which means owning the handoffs between them — the places where most revenue is actually lost. In practice many RevOps manager roles are sales ops roles with a broader title, and the way to tell is whether marketing and customer success process decisions genuinely run through the role.