You have headcount approved for “someone to own RevOps,” and a hiring manager who has never hired one. The first question everyone asks is comp. The better first question is level — because a RevOps manager and a RevOps director are not the same job at two price points. One keeps the machine running. The other decides what machine you build. Hire the wrong one and you either overpay for someone who will be bored inside a quarter, or underpay for someone who can’t defend the forecast when your CFO starts asking.
Below is what each tier actually does, how their week splits between strategy and execution, the projects you should hand them in the first 90 days, and what the market is paying in 2026.
A manager makes the number trustworthy. A director makes it defensible.
The five RevOps levels at a glance
Posted base salary comes from RevOps Careers’ analysis of 485 US ops postings with disclosed pay in Q1 2026, covering revenue, sales, marketing and customer success operations. Share of postings comes from the same study’s 1,890-posting dataset.
| Level | Common titles | Median posted base | Share of postings | Strategy / execution |
|---|---|---|---|---|
| Analyst | RevOps Analyst, Sales Ops Analyst, CRM Analyst | $95,000 | 27% | 10 / 90 |
| Manager | RevOps Manager, Sales Ops Manager, Systems Manager | $143,000 | 31% | 25 / 75 |
| Senior Manager | Sr. Manager, RevOps; Sr. Manager, GTM Systems | $151,000 | 3% | 40 / 60 |
| Director | Director of RevOps, Head of Revenue Operations | $202,000 | 11% | 65 / 35 |
| VP | VP Revenue Operations, VP GTM Operations | $186,000* | 1% | 85 / 15 |
*The VP median sits below the director median because, as RevOps Careers notes, only eight VP-level postings in the set included salary. The RevOps Report’s RevOps-only data puts the VP median at $250K across 10 postings — treat both as directional.
The strategy/execution split is our working rule of thumb from scoping these searches, not a survey figure. Use it to calibrate your interview loop: if you plan to test a director on building dashboards, you’ve written a manager req.
Analyst: the builder you point at a backlog
An analyst executes against a list someone else wrote. That is the value, not a limitation — a good one clears a year of deferred CRM cleanup in a quarter.
What to expect: field and validation-rule changes, report and dashboard builds, list pulls, lead routing fixes, data hygiene, and answering “can you pull me…” requests from sales and marketing. Strong analysts can write SQL and are fluent in Salesforce or HubSpot.
First 90-day projects: dedupe accounts and contacts, rebuild the core pipeline dashboard, document the lead-to-opportunity process as it actually runs today.
Don’t hire one if nobody on your team can tell them what to build. An analyst without a manager or a clear owner becomes an expensive ticket queue. At a $95,000 median, it’s the cheapest seat in ops — and the one most often hired too early.
Manager: the default first hire
Manager is where the market lives: 31% of all ops postings sit at this level, more than any other. For most companies making a first RevOps hire, it’s the right answer.
What to expect: ownership of the CRM and the tools bolted onto it, the weekly pipeline and forecast cadence, the reporting that leadership reads on Monday, and the deal-desk and quote processes. A manager is cross-functional by default — the RevOps Co-op’s 2025 report, as cited by RevOps Careers, found 79% of RevOps professionals support sales, marketing and customer success at the same time. Usually an individual contributor, sometimes with one analyst.
First 90-day projects: a single source of truth for pipeline, stage definitions and exit criteria sales will actually follow, a clean handoff from marketing to sales to CS, and a tool audit that cuts at least one redundant license.
Comp: a $143,000 median posted base. The same study notes that analysts with 2–3 years of experience are realistic manager candidates — so a strong manager hire may be a stretch promotion for them, which is good for retention.
Where managers struggle: being asked to set the forecast methodology, own territory design, or present to the board. That’s director scope. If those sit in your job description, price accordingly.
Senior Manager: the bridge nobody posts
Senior manager is the rarest title in the market — just 3% of ops postings. That scarcity is useful information: most companies either don’t need the level yet or promote into it.
What to expect: a manager with a defined domain and real ownership inside it. Typical scopes are “owns the forecast process end to end,” “owns the full GTM systems roadmap,” or “runs sales ops while a peer runs marketing ops.” Often one or two direct reports. They recommend strategy and are trusted to execute it; they don’t yet set it for the whole revenue org.
First 90-day projects: redesign the forecast call and roll-up, stand up capacity planning for next year’s hiring, lead a CRM migration or major platform consolidation.
Comp: a $151,000 median — only about $8,000 above manager. That thin gap is why candidates often read a senior manager req as “a manager job with more work.” If you open this level externally, sell the scope and the path to director, not the title.
Director: the one who owns the number
The jump from senior manager to director is the biggest in the ladder — $151,000 to $202,000 at the median. That $51,000 isn’t paying for the same work done better. It’s paying for different work.
What to expect: ownership of forecast methodology and accuracy, annual planning (territories, quotas, capacity), compensation plan design with finance, the ops roadmap and budget, and a team — typically two or more people across sales, marketing and CS ops. A director sits in the CRO’s staff meeting and can defend the forecast in front of the CFO without a manager in the room. At smaller companies the title is often “Head of Revenue Operations,” and it’s still a builder role: expect them to execute alongside the team for the first year.
First 90-day projects: a forecast methodology leadership signs off on, the next fiscal year’s territory and quota plan, a written ops roadmap with a hiring plan, and a clear intake process so ops stops being run from Slack DMs.
Comp: $202,000 median posted base across all ops functions. The RevOps Report’s RevOps-only data lands in the same place — a $200K median and a $206K average across 37 postings, with ranges from $107K to $343K. That spread is the stage and scope talking: a Head of RevOps at a Series A and a director running a 10-person team at a public company share a title and little else.
Where directors struggle: in companies that really wanted a manager. A director hired into a one-person team with no planning mandate will spend their time building dashboards and start interviewing within a year.
VP: when ops needs a seat at the exec table
VP roles are thin — 1% of ops postings. You need one when revenue operations spans multiple directors or functions, and the leader has to shape pricing, packaging, go-to-market model and board reporting rather than just support them.
What to expect: exec-team planning, GTM strategy alongside the CRO and CFO, ownership of the full revenue tech budget, and leadership of several ops leaders. Very little hands-on execution.
Comp: hard to benchmark from postings alone. The RevOps Report shows a $250K median and $270K average across 10 VP postings, ranging $185K–$429K. With samples that small, calibrate against live market conversations — and expect meaningful equity and bonus on top of base. Many VP searches look more like sales leadership recruiting than an ops search.
How to pick the right level
Four questions settle it.
Who defends the forecast? If your CRO does and just needs clean data, hire a manager. If you need someone else to own the methodology and answer for it, hire a director.
Is this a seat or a function? One person keeping systems healthy is a manager. A team you’ll grow to three or more in the next 18 months needs a director to design it — see our five steps to building a RevOps team.
Is annual planning in scope? Territories, quotas, capacity models and comp plans are director work. Put them in a manager req and you’ll either get no qualified applicants or a manager who is underwater by Q3.
Is the real need building, not operating? If the backlog is enrichment, routing automation and outbound infrastructure, you may want a GTM engineer instead of either level. We break that fork down in GTM engineer or RevOps? Which req to open, and our GTM engineer recruiting team runs those searches.
Then post the band that matches the level you picked. Candidates read level from the comp range before they read the title — a “Director” req at $150K pulls managers, and a “Manager” req at $200K pulls directors who’ll expect a team. Our salary benchmarks keep current bands for both, and if you want a second opinion on scope before the req goes live, that’s the first call our revenue and marketing operations recruiting team makes. Get the level right and you’ll hire top-tier talent in days, not weeks. Get it wrong and you’ll be re-opening the req in two quarters.
