Scope
What a head of revenue operations actually owns
The question this role exists to answer: Do the numbers the board sees hold up, and does the process behind them work the same way every time.
Owns
- CRM architecture and data governance
- Process definition across marketing, sales and customer success
- Forecast model and board reporting
- Revenue technology stack selection and integration
- Territory, quota and capacity modeling support
Shares
Does not own
- Sales strategy and quota setting decisions
- Marketing campaign strategy
- Individual deal ownership
Timing
When to hire a head of revenue operations
Too early
Below roughly five million in ARR informal coordination between functions usually still works, and a full RevOps hire is early.
The right window
Five million to one hundred million in ARR, which is where the function is most commonly built out.
Outgrown
Becomes a team with specialists by function at scale.
How much work this actually is
At Series B, with none of it covered today, the functions in this role's scope represent roughly 2.1 full time equivalents. The scope represents roughly 3 people of work at this stage. A leader can carry that only with a team underneath them. If the plan is a solo hire, the description needs to shrink.
| Function in scope | Group | Full time equivalents |
|---|---|---|
| RevOps, CRM and forecasting CRM architecture, data hygiene, process definition, forecast models, board reporting. |
Systems and infrastructure | 0.85 |
| Marketing operations Marketing automation platform, campaign infrastructure, lead flow, attribution reporting. |
Systems and infrastructure | 0.85 |
| Competitive intelligence Win and loss patterns, battlecards, displacement plays, pricing pressure tracking. |
Strategy and positioning | 0.43 |
Run your own coverage grid to see what this number looks like at your stage, with your team and your existing coverage.
Compensation
What a head of revenue operations costs
Structure matters as much as the number
A modest bonus tied to company or function performance. The role is not commission driven.
Equity: Commonly 0.08 to 0.25 percent at Series B.
Bands are directional, for scoping a description or a target range rather than making or accepting an offer. Benchmark figures are triangulated from the sources listed and refreshed with the data file. Live posted ranges come from GTM Radar and are only shown once enough matched postings exist to be meaningful.
Title confusion
Titles a head of revenue operations gets confused with
Most mis hires in go to market are not bad candidates. They are the right candidate for a different job than the one the company actually needed.
Head of Revenue Operations versus GTM Engineer
Scope and altitude. RevOps owns process, systems architecture and reporting integrity at the company level, unifying the CRM and stack, enforcing data hygiene, and building the forecast models leadership relies on. A GTM Engineer owns the specific automations and AI driven workflows that execute inside the process RevOps defines. RevOps sets the rules of the system. A GTM Engineer builds the machinery that runs inside those rules.
Head of Revenue Operations versus Marketing Operations Manager
RevOps is company wide across all revenue functions. Marketing Ops stays inside marketing's own systems. At smaller companies one person often covers both, and the split usually happens somewhere between ten million and thirty million in ARR.
Requirements
What to actually require
Non negotiable
- Deep CRM administration and architecture experience
- Built a forecast model leadership actually used
- Defined process across at least two revenue functions
- Comfortable saying a number is wrong to an executive
Genuinely optional
- SQL and data warehouse experience
- Compensation plan design
- Systems migration experience
Everything in this column belongs under a preferred heading, or out of the description entirely. Requirements lists that mix these two columns filter out strong candidates who self select away.
Tools this role works in
- CRM
- Forecasting and revenue intelligence
- Analytics and BI
- Data warehouse and pipelines
- CPQ and billing
- Marketing automation
Name the specific platforms in the description. Platform experience is not fully transferable in operations and automation roles, and candidates screen themselves in or out on exactly this detail.
Before you post
Red flags in a head of revenue operations job description
Screening
Interview questions that reveal fit
| Area | Question |
|---|---|
| Architecture | Describe the worst CRM you inherited. What did you fix first and why that. |
| Forecast | How would you build a forecast model here, and how would you know it was accurate. |
| Influence | Tell me about a time you told a leader their number was wrong. What happened. |
| Scope boundary | Where do you draw the line between what RevOps owns and what a GTM engineer or marketing ops person owns. |
Measure the role on
- Forecast accuracy
- CRM data completeness and hygiene
- Reporting reconciliation across systems
- Process cycle time on key handoffs
- Stack cost per revenue dollar
First 90 days
First 30 days
- Audit CRM data quality and current process definitions
- Reconcile reported numbers against source systems
By day 60
- Publish standardized stage and lifecycle definitions
- Deliver a rebuilt forecast model
By day 90
- Board reporting running from one trusted source
- Stack roadmap and process improvement plan published
Questions
Head of Revenue Operations hiring questions
What is the difference between RevOps and a GTM engineer?
RevOps owns process, systems architecture and reporting integrity at the company level: unifying the CRM and technology stack, enforcing data hygiene, and building the forecast models leadership relies on. A GTM engineer owns the specific automations and AI driven workflows that execute inside the process RevOps defines. RevOps sets the rules of the system and a GTM engineer builds the machinery that runs inside them.
When should a company build a RevOps function?
Most commonly between five million and one hundred million in ARR, past the point where informal coordination between marketing, sales and customer success still works. Gartner has projected that roughly seventy five percent of the highest growth companies will run on a formal RevOps model by the end of 2026, up from under thirty percent a few years earlier.
Does RevOps report to sales, finance or the CEO?
All three structures exist. Reporting into a CRO, the CEO or finance gives the function the cross functional neutrality it needs, because RevOps has to be able to tell sales that the forecast is wrong. Reporting into sales specifically tends to bias process and reporting toward sales priorities, which undercuts exactly the neutrality that makes the function valuable.
Next step
Turn this into a job description scoped to your company
The reference above describes the role in general. The builder takes your stage, your team, your existing coverage, your territory and your stack, and produces a description scoped to the gap you actually have, with a scope load check before you post it.
Related roles