How to Hire a Head of RevOps: A Founder Guide

The first head of RevOps hire usually arrives at 2M to 8M ARR at venture-backed B2B SaaS companies. The hire moves the company from a founder-managed CRM with rough forecasting to a structured revenue function with clean pipeline data, working comp plans, and a forecast the CFO trusts.

This guide covers the timing, the scope, the comp benchmarks, the scorecard, and the most common hiring mistakes. The benchmarks come from Pavilion's State of RevOps surveys, RepVue, ICONIQ Growth, and the practitioner data at The RevOps Report.

When the hire makes sense

Three signals usually trigger the first RevOps hire. The first is that the founder or VP Sales has lost confidence in the forecast and is spending too many hours per week reconciling pipeline data. The second is that the comp plan has visible bugs that nobody on the team has the bandwidth to fix. The third is that the company is hitting a quota and territory design that is producing seller frustration.

Quick benchmarks

Bridge Group benchmarks place the median first RevOps hire at 2M to 5M ARR. Companies that wait past 8M ARR usually have a VP Sales who is operating as a part-time RevOps lead, which slows both functions.

What the role should own

In practice

The first head of RevOps should own:

1. CRM administration: clean pipeline data, accurate stage definitions, working reports.
2. Forecast: weekly pipeline review, monthly forecast call, quarterly review.
3. Comp plan: design, administration, dispute resolution.
4. Quota and territory: annual design, mid-year adjustments.
5. Reporting: leadership dashboards, board metrics, ad hoc analysis.
6. Cross-functional partnership: marketing on attribution, customer success on retention metrics.

What the role should not own initially is the marketing automation platform. That work belongs to marketing ops and should be a separate hire when the marketing org reaches the size that justifies it. The MOps vs RevOps guide walks through the split.

The candidate profile

The right first head of RevOps has four things on their resume. The first is operating experience as a senior RevOps manager or director at a similarly sized B2B SaaS company. The second is fluency with Salesforce or HubSpot administration plus at least one BI tool. The third is documented experience designing a comp plan and a quota model. The fourth is a strategic posture that lets them partner with the VP Sales and the CFO rather than just executing tickets.

What goes wrong

The most common candidate profile mismatch is hiring a senior Salesforce admin and calling them head of RevOps. The admin work is necessary, but the role also requires strategic planning, cross-functional partnership, and executive communication that pure admins do not have practice with.

Comp benchmarks

Quick benchmarks

Pavilion and RepVue data place senior RevOps manager OTE between 140K and 200K US dollars, director OTE between 170K and 240K, and VP RevOps OTE between 240K and 350K at venture-backed B2B SaaS companies. Equity is meaningful at growth-stage companies, with director-level grants in a 0.1 to 0.5 percent range and VP grants in a 0.3 to 1 percent range.

The variable component runs lower than in sales roles, typically 15 to 25 percent of OTE tied to operational metrics like forecast accuracy, CRM data quality, or revenue plan attainment. The RevOps Report tracks the benchmarks by stage and segment.

The scorecard

A working scorecard for a first head of RevOps covers:

1. CRM administration depth and data hygiene track record.
2. Forecast design and accuracy.
3. Comp plan and quota model experience.
4. BI tool fluency and reporting capability.
5. Cross-functional partnership with sales, marketing, and finance.
6. Executive communication and presentation skills.

The scorecard should be written before the search starts. Evaluations based on charisma or prior logos produce mismatched hires.

The interview loop

A five-stage loop runs well:

1. Hiring manager screen, 30 minutes.
2. Deep dive into prior operating work, 60 minutes with the VP Sales.
3. Practical exercise: candidate analyzes a fictitious pipeline data set and recommends three operational changes.
4. Cross-functional interview with marketing and finance leaders.
5. Reference calls with a peer, a direct report if applicable, and the prior manager.

The practical exercise is the highest-signal stage. A candidate who can read pipeline data, identify the operational issues, and recommend changes the VP Sales would implement is dramatically more likely to ramp quickly.

Onboarding plan

In practice

The first 90 days should produce three artifacts: a CRM cleanup plan with measurable outcomes, a forecast cadence the leadership team uses, and a comp plan audit identifying any issues. The plan should look like:

• Days 1 to 30: data audit, stakeholder interviews, current state assessment.
• Days 31 to 60: CRM cleanup, forecast cadence design, comp plan audit.
• Days 61 to 90: operating cadence rollout, first clean forecast call, board reporting starts.

Founders who skip the audit period and ask the new head of RevOps to ship changes in week two produce a leader who applies generic best practices rather than tailored solutions.

Reporting structure

Reporting patterns

The first head of RevOps should report to the VP Sales or to the CRO at companies with one in seat. Reporting to the CFO produces tighter financial discipline and slower operational change. Reporting to the COO is common at companies past 30M ARR and works well when the COO has revenue experience.

Reporting to the CEO directly is rare at the first RevOps hire stage and usually indicates that the company is missing a senior revenue leader. The pattern is sustainable for six to nine months but breaks if the CEO does not have the bandwidth to manage the function.

Tool stack decisions

Stack patterns

The first head of RevOps should own three tool stack decisions in the first six months: the CRM (usually inherited), the BI tool (often a new selection), and the forecast or pipeline management tool (often a new selection). The decisions should be made after the audit period, not in the first 30 days.

The RevOps directory and The RevOps Report track the active platforms. Common picks include Clari, Gong, BoostUp, and Outreach for forecast and pipeline management, with Tableau, Looker, or Mode for BI.

Common mistakes

Common pitfalls

Four patterns recur. The first is hiring a senior Salesforce admin and expecting them to also handle strategic planning, which produces strong admin work and weak strategic work. The second is hiring the head of RevOps before the company has a defined sales motion, which produces a leader designing operating cadence for a motion that does not yet exist.

The third is reporting the head of RevOps to the CFO without a strong VP Sales partnership, which produces a finance-aligned RevOps function that struggles to ship operational change. The fourth is failing to provide executive sponsorship, which produces a head of RevOps running tickets for whichever VP shouts loudest.

The fix to all four is to write the scope, the reporting line, and the executive sponsorship model before the hire starts. The path to VP RevOps guide covers the career path the new hire will eventually follow.

When to expand the team

In practice

The first head of RevOps typically asks for the first analyst or specialist hire within six to twelve months. The common first expansions are a senior RevOps analyst, a Salesforce administrator, or a dedicated forecast and pipeline operations lead. The expansion timing depends on the company's revenue scale and the complexity of the operating cadence.

By 20M to 50M ARR, the function typically grows to a team of four to eight, with sub-specialization into systems, analytics, and process design. At that scale, the head of RevOps title often expands to VP RevOps.

Frequently asked questions