RevOps roles explained. Who actually does what.

Lauren Pearson here. I get some version of "who should we actually hire for this" almost every time a founder decides they need RevOps, and the honest answer depends far more on what stage the business is at than on the job title itself.

The short answer. Three roles, one shared remit.

A RevOps analyst is mostly reactive: building and maintaining dashboards, keeping CRM data clean, and answering the "why did the pipeline number move" questions that come up in every weekly review. A RevOps manager is mostly proactive: redesigning the sales process, choosing and configuring the tool stack, and setting the metric definitions the analyst then reports against. A head or VP of RevOps owns the strategic layer: the forecasting model, the cross-functional alignment between sales, marketing and customer success, and the final call on how the business defines "pipeline," "qualified" and "committed."

What ties all three together, whatever the title, is a remit that spans more than one department. The RevOps Co-op's 2025 State of RevOps Survey found 79 per cent of RevOps professionals now support sales, marketing and customer success simultaneously, rather than sitting inside a single department with a borrowed title. That cross-functional reach is the actual definition of the role. A sales ops hire with a RevOps job title but no authority over marketing's lead handoff or customer success's renewal data is sales ops with better branding, not RevOps.

How it works in practice. What each role is actually accountable for.

The clearest way to tell the three roles apart is by the question each one is expected to answer without escalating it. An analyst answers "what does the data say happened": which deals moved, which stalled, why a number looks different this week. A manager answers "why is the process producing that result", and is expected to redesign the workflow, tooling or definitions that caused it, not just report on them. A head or VP answers "are we going to hit the number and what needs to change to get there", which means owning the forecast itself and the authority to force alignment between sales, marketing and customer success when their versions of the truth disagree.

Skill requirements shift with each step up. An analyst needs to be fluent in the CRM's reporting layer and comfortable enough with spreadsheets or a BI tool to answer a question the same day it is asked. A manager needs process design skills on top of that, the ability to map a workflow, spot where it breaks, and configure the tooling to fix it, plus enough credibility with sales and marketing leads to get a changed process actually adopted. A head or VP needs commercial judgement above the technical skillset: reading a forecast, knowing which risk is real versus noise, and holding three department heads to one shared definition of the numbers.

How these three roles map onto headcount, and the order a founder-led business should hire them in as it grows, is a separate question from what each role does. Our guide to revenue operations team structure covers that scaling and hiring-order decision in full; this piece stays focused on the roles themselves.

A worked example makes the split concrete. A 60-person SaaS business noticed its weekly forecast kept moving between the Monday leadership meeting and the Wednesday board update, with no clear reason why. The RevOps analyst on the team could show, within the hour, exactly which deals had changed stage and by how much, that was the "what happened" question, answered well. What the analyst could not answer was why three different reps were logging the same stage differently, which needed a manager to sit with the sales team, tighten the stage definitions, and rebuild the pipeline report so the same deal could not be read two ways depending on who filled it in. Once that fix held for a full quarter, the remaining question, whether the business should tighten its forecast commitment to the board given the new, more reliable numbers, sat squarely with the head of RevOps, since it was a judgement call about risk and commitment, not a data or process fix. Three questions, three different owners, one shared set of numbers underneath all of them.

The title landscape has moved quickly regardless of team size. "Head of RevOps" and "VP of RevOps" are among the fastest-growing titles in the sector as investors and boards have started asking founders directly who owns the revenue number end to end, and a formal title answers that question cleanly on an org chart even before the process work behind it has caught up. See our full revenue operations approach for how we sequence that process work so a senior hire has solid ground to work from rather than a title with no foundation under it.

What good looks like. One person can explain the whole funnel without checking three spreadsheets.

A working RevOps structure shows up in a simple test: ask whoever owns the role to explain, from a single marketing lead through to renewal, exactly where a deal is and why, and they can do it without opening three separate tools or checking with three separate department heads first. If the honest answer is "let me check with sales and get back to you," the role exists on paper but the cross-functional authority behind it does not yet.

The other sign is fewer, not more, competing versions of the pipeline number. Before a proper RevOps role exists, sales, marketing and customer success often each keep their own definition of a qualified lead or an at-risk account, and reconciling the three takes a standing meeting nobody enjoys. Once the role is working, that reconciliation meeting quietly disappears, because there is only one definition to check against in the first place. For the practical work of consolidating those definitions, our revenue operations consulting service starts from exactly this audit.

A third, quieter sign is that escalations move up the chain for the right reason rather than the wrong one. A healthy structure sees questions land with the manager because a process genuinely needs redesigning, or with the head of RevOps because a real strategic trade-off is on the table, not because the analyst has been asked to make a call that was never theirs to make. When escalations start happening simply because nobody is sure who owns a decision, that is a sign the three roles have blurred rather than a sign the team needs another hire.

Pitfalls to avoid. Where the hire is set up to fail before day one.

The most common mistake is hiring the title without the authority. A business brings in a RevOps manager or lead and gives them a dashboard mandate but no say over how sales logs a deal or how marketing defines a qualified lead, which leaves them reporting on numbers they have no ability to actually fix. If the hire cannot change a process, only observe it, expect an analyst's results from a manager's salary.

The second is mismatching seniority to the actual problem. A business that hires a VP of RevOps to fix what is really an analyst-level reporting gap ends up with an expensive hire spending their first year doing dashboard work beneath their pay grade and mandate, while the strategic alignment problem they were meant to solve never had anyone junior enough to do the groundwork first. The reverse happens just as often: hiring an analyst and expecting them to redesign a lead-handoff process across three departments, which needs a manager's process authority, not an analyst's reporting remit. Match the hire to the actual gap, not to whichever job title sounded most senior in the budget conversation.

A job description is cheap to write and expensive to get wrong. Before drafting one, write down the specific question the business cannot currently answer, then match it to the role built to answer that type of question, rather than starting from a title and working backwards into a job description that tries to cover all three at once.

The third is letting the manager and VP roles blur once both exist. If a RevOps manager quietly starts making cross-functional calls that should sit with the VP, or a VP gets pulled into configuring tools that should sit with the manager, both roles end up half doing each other's job and neither does their own well. Write down, even briefly, which of the three questions, what happened, why did the process cause it, what do we do about it, each hire owns, and revisit that split whenever a new senior hire joins.

My own rule of thumb when a founder asks which role to hire first: if you cannot yet name, in one sentence, what "qualified" means across sales and marketing, you need a manager to fix that definition before you need a VP to align around it. Fix the definition with a fractional engagement or a short consulting sprint first, then hire permanently into whichever role the remaining gap actually calls for.