Role · RevOps Manager
RevOps Manager: what the role does and what it pays
What a RevOps manager is actually accountable for, how the role differs from sales ops, what it pays in the US, and what separates a strong one.
- Salary
- from $100,000
- Where the band goes
- Set by the rung, not the title. The ladder below says which is which, and the benchmarks post shows how each band was built.
Tools you will see on every CV
- Salesforce, or HubSpot in smaller companies
- Looker, Tableau or Power BI
- SQL
- Outreach, Salesloft or a comparable sequencer
- Gong or another conversation tool
- ZoomInfo, Clearbit or similar enrichment
- dbt, where the warehouse is the source of truth
Which is why the tool list is the least useful part of a CV for this role. Everyone has the same one.
What the role is accountable for
A RevOps manager owns the system that turns activity into revenue, and the reporting that says whether it is working. That means the CRM, the process built into it, the definitions everyone argues about, and the handoffs between marketing, sales and customer success.
The reason the role is hard to hire for is that almost all of the value is in judgement. Configuring a field is trivial. Knowing which field should not exist, and being willing to say so to the person who asked for it, is the job.
Where it goes wrong
The most common failure is not incompetence. It is an ops function that says yes to everything, accretes complexity for two years, and ends up as the reason nothing can change. The second most common is a strong analyst who cannot hold a conversation with a VP, and whose correct answers therefore never land.
Good and bad
What separates the two, in this role specifically.
These are the distinctions the rubric is built around. All of them are behavioural, so a CV cannot show them and a recorded session can.
- 01 Strong
Starts from the number that is wrong and works backwards to the system. Treats the CRM as a model of the business that has drifted from reality, and looks for the drift.
WeakStarts from the tool. Answers "the pipeline is wrong" with a list of fields to add, before establishing what the pipeline is supposed to represent.
- 02 Strong
Says no to requests, in writing, with a reason. Understands that an ops function that ships every request becomes the bottleneck it was hired to remove.
WeakShips everything asked for. Twelve months later the CRM has 400 fields, nine required at close, and reps are entering fiction to get past validation.
- 03 Strong
Designs for the person who inherits it. Documents the why, not the what, and can explain a two-year-old decision without reconstructing it from memory.
WeakBuilds something clever that only they can maintain, then becomes a single point of failure that the company mistakes for indispensability.
- 04 Strong
Is comfortable telling a VP the number they like is wrong, and has the working to back it.
WeakReports what was asked for. Knows the number is soft and lets it stand because correcting it is an uncomfortable conversation.
What it is advertised as
The same job, at four rungs, under whatever title the advert reached for.
Titles for this work are not standardised, and the rung matters more than the wording. These are the variants currently live in the UK market, so you can search for the right one and recognise the wrong one.
- 01
Analyst
Builds the reporting and keeps the data honest, working to definitions somebody else set. The rung where you find out whether someone asks what a field is supposed to mean before they chart it.
- Revenue Operations Analyst
- RevOps Analyst
- Revenue Operations Associate
- RevOps Planning Analyst
- 02
Manager
Owns the process and the systems under it, and is expected to say no to some of what is asked for. This is the rung most companies mean when they say they need RevOps.
- Revenue Operations Manager
- RevOps Manager
- Revenue Operations Specialist
- Revenue Operations Lead
- 03
Senior manager or systems lead
Owns the stack rather than a corner of it, usually with one or two people under them, and is judged on whether the architecture survives the next two years of change.
- Senior Revenue Operations Manager
- Revenue Operations Systems Lead
- RevOps Systems & Integration Lead
- RevOps Architect
- 04
Head of or Director
Carries the number with the CRO and owns planning, capacity and the operating rhythm. A different hire from the three above, and a common mistake is to advertise this and interview for the manager rung.
- Head of Revenue Operations
- Director of Revenue Operations
- Head of RevOps & Enablement
- VP Revenue Operations
Questions
Hiring a revops manager.
- What is the difference between RevOps and sales ops?
- Sales ops owns the sales function: territories, quota, forecast, CRM hygiene for reps. RevOps owns the whole revenue system across marketing, sales and customer success, including the handoffs where most value leaks. In practice many companies rename sales ops to RevOps without changing the scope, which is worth checking before you hire.
- Does a RevOps manager need to code?
- Not in the software engineering sense. They do need SQL, and increasingly comfort with a transformation layer like dbt, because the source of truth has moved from the CRM to the warehouse. Someone who can only work through report builders has a ceiling.
- What does a RevOps manager pay?
- Broadly $100,000 to $175,000 base for a manager-level individual contributor in venture-backed B2B software, with the top-quartile metros and regulated sectors at the top of the band. Heads of RevOps and directors run well above this.
- How do you test for the role rather than the tools?
- The assessment puts candidates in a broken instance and asks them to find out why a number is wrong, narrating as they go. Tool familiarity shows up incidentally. What is being marked is the order they do things in.
Hiring a revops manager? You will see the work before the interview.
Nothing owed until someone starts.
Book a call