Your first Head of RevOps should be a builder if you cannot trust your CRM data today, and an analyst if the data is sound but nobody has time to turn it into decisions. Most Series A to C software companies need the builder first, and most hire the analyst because analysts interview better in front of a board.
This guide is for founders, CROs and CFOs hiring a first head of RevOps in the UK or US. It covers how to diagnose which profile you need, what each one costs you in year one if you get it wrong, how to structure the role, the scorecard and interview loop we recommend, and what the first 90 days should produce.
Why the first RevOps hire matters more than most
RevOps has moved from a nice-to-have to an expected function. Back in May 2021 Gartner predicted that by 2025, 75% of the highest growth companies in the world would deploy a RevOps model. In a July 2025 study of 400 US RevOps and executive decision-makers, commissioned by Salesloft from Wakefield Research, 98% said the function's scope had grown over the past year, and 89% said RevOps still lacked clearly defined strategic goals. That second number is the real story: companies know they need RevOps, but many have not decided what they want it to do.
The first hire sets the architecture everyone else inherits. The object model, the opportunity stages, the definition of a qualified opportunity, the way ARR is calculated, the forecast categories: these decisions are expensive to undo once three teams build reports on top of them. A weak first hire does not just underdeliver; they create two years of rework for the second hire.
Forecast credibility is usually what triggers the search. Gartner's State of Sales Operations research, published in February 2020, found that only 45% of sales leaders and sellers had high confidence in their organisation's forecasting accuracy. When the board stops trusting the number, the CEO starts looking for a Head of RevOps. The question is whether the forecast is wrong because nobody analyses the data, or because the data itself is wrong.
Builder or analyst: what is the difference?
Every RevOps leader does some of both. The distinction is where they are strongest and what they want to spend their days doing. Hire against the weakness you have, not the strength you admire.
| Builder (systems-first) | Analyst (insight-first) | |
|---|---|---|
| Core strength | CRM architecture, data model, routing, integrations, automation | Forecasting, capacity planning, cohort and funnel analysis, board reporting |
| Typical background | Salesforce or HubSpot admin to architect, marketing ops, GTM systems | Sales strategy, FP&A, consulting, business intelligence |
| What they fix first | Duplicate accounts, broken lead routing, stage definitions, field sprawl | Forecast method, pipeline coverage targets, quota and capacity models |
| Tools they reach for | Salesforce Flow, CPQ, LeanData, HubSpot workflows, integration platforms | Spreadsheets, SQL, Looker or Tableau, Clari, planning tools such as Pigment |
| Where they struggle | Presenting a defensible forecast to a CFO or board | Rebuilding a CRM they did not design and do not want to administer |
| Best fit when | The data is untrustworthy or the stack is held together by one admin | The data is clean but the CRO and CFO lack analysis and planning |
There is a third profile, the true hybrid, who can architect a Salesforce org on Monday and defend a capacity model to the CFO on Friday. They exist. They are usually on their second or third Head of RevOps role, they know their market value, and they move quickly. If you meet one, do not run a six-week process.
How do you know which one you need?
Run a short diagnostic before you write the job description. It takes an afternoon with your CRO, your CRM admin (if you have one) and whoever builds the board pack. Answer each question honestly.
The builder-or-analyst diagnostic:
- The board test. If the board asked tomorrow for pipeline by segment, by source and by quarter, could you produce it from the CRM without manual clean-up? If not, score one for builder.
- The duplicate test. Pick 20 of your largest customers. How many exist more than once as accounts, or have contacts scattered across duplicates? More than two or three, score one for builder.
- The routing test. When an inbound demo request arrives, how long until the right rep owns it, and is that automatic? If it relies on someone in Slack, score one for builder.
- The definition test. Ask your CRO, CFO and Head of Marketing separately how they define a qualified opportunity and how ARR is calculated. If you get three answers, score one for builder.
- The time test. How many hours a month does someone senior spend assembling the forecast and board pack by hand? If it is more than a couple of days, and the inputs are reliable, score one for analyst.
- The planning test. Did you set this year's quotas and hiring plan from a capacity model, or from a top-down number divided by headcount? If top-down, score one for analyst.
- The question test. List the three commercial questions you most want answered, such as why mid-market win rates fell or which segment has the best payback. If the data to answer them exists but nobody has time, score one for analyst.
Four or more builder points means you need a builder, even if the role is called Head of RevOps and even if the CFO wants an analyst. Four or more analyst points with few builder points means your systems are in better shape than most, and an analytical leader will create value quickly. A split usually means a builder with credible analytical skills, because analysis on bad data is wasted effort.
What goes wrong when you hire the wrong profile
The failure modes are predictable, and both are expensive.
An analyst hired into a broken CRM spends the first six months reconciling exports in spreadsheets, building workarounds rather than fixes. The reports look polished, but they rest on manual adjustments only that person understands. When they leave, the reporting leaves with them. They also tend to become frustrated: they joined to influence strategy and find themselves de-duplicating accounts.
A builder hired when the systems are already sound will improve them further, often impressively, but the CRO still has no capacity model and the CFO still builds the forecast. Leadership starts to ask what RevOps is for. The builder, meanwhile, wants a roadmap of projects and resents being pulled into ad hoc analysis.
Either way you are looking at a second search within 12 to 18 months, plus the cost of whatever was built on the wrong foundations.
When should you hire your first Head of RevOps?
There is no single ARR threshold, but there are reliable signals. Most companies hire too late, after the CRM has already become a liability. Look for these triggers:
- You have, or are about to have, more than one sales team (for example SMB and mid-market, or UK and US) with different stages, territories or comp plans
- Your CRM admin is a part-time duty for an SDR manager or a marketing ops specialist, and requests wait weeks
- Quota setting for next year has started and nobody can explain the capacity maths
- Marketing and sales disagree about pipeline numbers in most weekly meetings
- You are preparing for a fundraise and due diligence will ask for cohort, retention and funnel data
- Customer success is being given renewal or expansion targets with no shared data model
If only one or two apply, a strong RevOps manager or a senior Salesforce administrator may be the right hire, reporting to the CRO, with the Head of RevOps title saved for later. Over-titling a first hire creates problems when you later need someone above them.
Builder, analyst or both: how to write the role
Write the job description around outcomes for the first 12 months, not a list of every RevOps responsibility. Candidates read generic RevOps job descriptions as a warning: either the company does not know what it needs, or it expects one person to do the work of a team. Be specific about the state of the systems and the size of the problem.
What a strong first Head of RevOps brief includes:
- The current state. CRM platform and age, who administers it today, the main tools around it, and a frank sentence about data quality.
- Three to five 12-month outcomes. For example a rebuilt opportunity process with agreed stage definitions, automated lead routing, a weekly forecast the CFO signs off, and a capacity-based plan for next year.
- Scope boundaries. Say whether enablement, deal desk, comp administration and customer success operations are in or out of scope in year one.
- Team and budget. Whether they will hire, how many people and when, and whether they control the GTM tooling budget.
- Reporting line and access. Who they report to and whether they attend leadership meetings. Strong candidates will ask in the first call.
- Location and working pattern. Be honest about office days. In the UK and US alike, this is one of the first filters candidates apply.
Where should a first Head of RevOps report?
At most early-stage companies the first RevOps leader reports to the CRO or the CEO. In a survey of 180 RevOps professionals across 28 countries, run by the agency Revenue Wizards between September and November 2024, 38% of teams reported directly to the CRO, with many in smaller companies reporting to the CEO. The same survey found 23% of RevOps professionals worked alone, which is the reality of most first hires.
As companies scale, more RevOps leaders move under the CFO or COO so that the function stays neutral across marketing, sales and customer success. The Salesloft and Wakefield study found 79% of organisations still categorise RevOps as sales-adjacent, which candidates often read as a sign the function will be treated as sales support rather than a strategic partner.
| Reports to | Advantages | Risks | Best when |
|---|---|---|---|
| CRO | Close to the number; fast decisions on pipeline and process | Seen as sales ops; marketing and CS priorities lose out | One sales motion, CRO owns marketing and CS too |
| CEO | Neutral across functions; seat at leadership table | CEO bandwidth; can become a dumping ground for projects | Early stage, no CRO yet, or functions led separately |
| CFO or COO | Neutral; strong planning and data discipline; credible with the board | Further from sellers; risk of slower system changes | Later stage, multiple motions, heavy planning and comp complexity |
| CMO | Strong marketing ops foundation | Sales sees it as marketing's team; rarely survives scale | Rarely the right first choice |
Decide before you start the search. Changing the reporting line after the offer is a common reason first RevOps hires leave early.
What does a first Head of RevOps actually own?
Be explicit. These are the areas a first RevOps leader typically owns, and the questions each one has to answer:
- CRM and GTM systems: object model, stages, fields, permissions, integrations and the tooling roadmap
- Data quality: account hierarchy, de-duplication, enrichment and the definitions everyone uses
- Lead management: scoring, routing and service levels between marketing, SDRs and AEs
- Forecasting: forecast categories, cadence, inspection and the method for calling the number
- Planning: capacity model, ramp assumptions, quota setting, territory design and hiring plan
- Compensation: plan design input, crediting rules, commission calculation and dispute handling
- Deal desk: discount approvals, non-standard terms and quote-to-cash
- Reporting: the weekly operating metrics and the board pack
A builder will lead with the first four and grow into planning. An analyst will lead with forecasting and planning and need a strong systems admin alongside them, either hired or contracted. Budget for that admin from day one if you hire an analyst into a messy CRM.
The scorecard: how to assess RevOps candidates
Use a written scorecard with four or five competencies, each scored against evidence rather than impressions. RevOps candidates are often outstanding at describing frameworks; the scorecard forces the panel to ask what they actually built and what changed as a result.
| Competency | What good looks like | Evidence to ask for |
|---|---|---|
| Systems depth | Can design, not just administer, a CRM; understands trade-offs in object model and automation | Walk through an org they rebuilt: what they changed, why, and what broke |
| Analytical rigour | Builds capacity and forecast models from first principles; knows the assumptions that matter | A capacity model with ramp, attrition and attainment assumptions they can defend |
| Business partnering | Pushes back on senior leaders with data; earns trust across sales, marketing and CS | A time they told a CRO or CFO something unwelcome, and what happened |
| Prioritisation | Has a method for saying no; sequences foundations before features | How they ran the request queue and what they deliberately did not build |
| Scaling the function | Knows when to hire, contract or buy; has hired ops people before | Their first two hires, why those roles, and how they were assessed |
A four-stage interview loop for a first Head of RevOps
Recommended loop (three to four weeks end to end):
- Hiring manager screen (45 minutes). Context, motivation and the diagnostic question below. Share your honest view of the current state.
- Systems deep dive (60 minutes). With your CRM admin or a technical adviser. The candidate walks through an architecture they designed; for a builder, give them a read-only look at a sanitised part of your org.
- Planning exercise (90 minutes, prepared in advance). Give a simplified data set: current reps, ramp, historical attainment, attrition and next year's bookings target. Ask how many sellers you need, when to hire them, and what pipeline coverage that implies.
- Leadership panel (60 minutes). CRO, CFO and Head of Marketing or CS. Focus on partnering and conflict: how they would handle three competing priority lists in week one.
Keep the exercise realistic and short. A take-home that needs more than three hours of preparation will lose the best candidates, who are usually employed and fielding other approaches.
Worked example: the capacity exercise
This is an illustrative version of the planning exercise. A good candidate will challenge every assumption in it.
Suppose next year's new-business target is $6m in annual contract value. Each fully ramped AE carries a $750k quota, and historically 70% of plan is achieved per ramped seller on average. Ramp takes six months, during which a new AE delivers roughly half of a ramped seller's output. Annual attrition is 20%.
- Effective output per ramped AE: $750k quota × 70% attainment = $525k
- Sellers needed if all were ramped all year: $6m ÷ $525k ≈ 11.4
- Adjust for ramp: if four of those sellers are hired in Q1, each delivers about half output for six months, so you lose roughly one full seller-year of capacity
- Adjust for attrition: at 20%, expect two or three departures, each costing ramp time on their replacement
- Result: a plan of around 14 to 15 quota-carrying AEs, hired front-loaded, rather than the 8 you get by dividing $6m by $750k
What you are looking for is not the answer, but whether the candidate asks the right questions: is the attainment figure skewed by one star seller, does ramp differ by segment, is there enough pipeline to support 15 sellers, and what coverage ratio does history support? A builder may be less fluent here; an analyst should be fluent. A hybrid will also ask whether the CRM data behind those assumptions can be trusted.
Questions that separate strong RevOps candidates
- If I gave you our CRM tomorrow, what would you check in your first week? Strong candidates have a diagnostic routine: stage definitions, duplicate rates, field usage, automation conflicts, integration errors, report sprawl.
- How do you define a qualified opportunity, and who should own the definition? Look for an answer that involves sales, marketing and finance agreeing, then the system enforcing it.
- Tell me about a forecast you called that turned out wrong. Why? Good answers name the assumption that failed and what they changed in the method.
- What did you deliberately not build in your last role? This reveals prioritisation discipline.
- How should a deal desk balance speed against margin? Look for clear approval thresholds and service levels, not just a process diagram.
What to pay a first Head of RevOps
Pay varies widely with scope. A first Head of RevOps who will build the function and own planning, systems and comp is a different hire from a senior manager who will run Salesforce under a CRO. In both the UK and US the role is normally salaried with a bonus, rather than a sales-style OTE, and equity is common at venture-backed companies. Hybrid candidates with deep Salesforce architecture skills, CPQ experience and a credible board presence command a premium in both markets.
Two practical points. First, benchmark against your own GTM leadership: a Head of RevOps paid far below the Head of Sales they must challenge will struggle to do so. Second, if you hire an analyst into messy systems, budget for a Salesforce administrator or a systems partner as well; the total cost of the function is what matters. For current role-by-role ranges see /salary-guide and /specialisms/revenue-operations.
The first 90 days: what should a new Head of RevOps deliver?
A realistic first 90 days:
- Days 1–30, diagnose. Interview every GTM leader and a sample of reps and CSMs. Audit the CRM, integrations and reports. Publish a short current-state document with the top ten problems ranked by business impact.
- Days 31–60, agree definitions. Get sign-off on stage definitions, qualified opportunity criteria, ARR and pipeline definitions. Fix the most damaging data issues, usually routing and duplicates.
- Days 61–90, ship the operating rhythm. A weekly forecast process with clear categories and inspection, a single pipeline dashboard everyone uses, and a draft capacity model for next year's plan.
- Ongoing, publish the roadmap. A quarterly RevOps roadmap with what is in, what is out and why. This is how the function stops being a ticket queue.
If after 90 days you have a clear current-state view, agreed definitions and a forecast leadership trusts more than before, the hire is working, whichever profile you chose.
First Head of RevOps: common questions
Hire a builder if you cannot trust your CRM data, and an analyst if the data is sound but nobody has time to analyse it. Run a short diagnostic first: if leadership defines a qualified opportunity three different ways or the board pack needs manual clean-up, you need a builder.
Typically when you run more than one sales motion or region, quota setting needs a capacity model, marketing and sales disagree on pipeline numbers, or a fundraise needs cohort and funnel data. If only one of those applies, a RevOps manager or senior admin may be enough.
At early stage, usually the CRO or CEO. As companies scale and run several motions, many move RevOps under the CFO or COO to keep it neutral across sales, marketing and customer success. Decide before the search; candidates ask early.
Sales operations supports the sales team. Revenue operations covers the whole go-to-market: marketing, sales and customer success share one data model, one set of definitions and one planning process, so pipeline and retention are measured consistently.
A ranked current-state assessment, agreed definitions for stages, qualified opportunities and ARR, fixes to the worst data problems, and a weekly forecast process leadership trusts. A draft capacity model for next year should follow.
Use a scorecard covering systems depth, analytical rigour, business partnering, prioritisation and scaling the function. Include a systems walk-through and a short capacity planning exercise with real-looking numbers, then a panel with the CRO and CFO.
Some can. True hybrids are usually experienced Heads of RevOps who have built a function before. They are scarce and well paid, so if you find one, run a fast, well-organised process.