Contents
RevOps team structure is how a company arranges its revenue operations roles, reporting line and hiring order across sales, marketing and customer success. It follows stage: one senior generalist reporting to the CEO or CRO, then a systems owner and an analyst, then sales, marketing and CS ops pods on one shared data layer. Updated November 2026: new stage table with first hires, sample org chart, dated 2025 survey data on team size and pay, unsourced ratios removed.
The right structure depends on your stage more than your industry, your tech stack, or what the org chart looks like at a company ten times your size. Having a RevOps function and having the right one are different problems.
What does a RevOps team do?
A RevOps team runs the systems, data, reporting and planning that sales, marketing and customer success share. The work falls into three lanes, and the structure at every stage is a question of who covers which lane.| Lane | Typical work | Who covers it early | Who covers it at scale |
|---|---|---|---|
| Systems and data | CRM administration, integrations, data quality, lead routing, permissions | The first RevOps hire | Systems administrator, data steward |
| Analytics and forecast | Pipeline reporting, the forecast model, stage conversion rates, board metrics | The first RevOps hire, part time | RevOps analysts |
| Planning and process | Territory design, territory planning, quota and comp modeling, stage definitions, the operating calendar | The CRO or CEO, with RevOps support | Sales, marketing and CS ops leads |
The difference from sales ops is scope: RevOps covers all three revenue teams and the handoffs between them. For the full comparison, see sales ops vs revenue operations. For the function as a whole, see our revenue operations guide.
RevOps team structure by stage
At each stage, the structure answers four questions: what the team looks like, who it reports to, who to hire next, and which sign says you have outgrown it. The ARR bands below are ORM's working guidance from B2B SaaS companies, not survey results. Real companies sit between bands, and a multi-product or usage-priced business needs more operations support at the same revenue than a single-product, seat-priced one.| Stage | Company size (illustrative bands) | Team shape | Reports to | First or next hire | Sign you have outgrown it |
|---|---|---|---|---|---|
| 0. Before RevOps | Under $5M ARR, founder-led sales | A sales leader or founder owns the CRM; outside help for setup | CEO | None yet; a fractional operator for CRM setup | Nobody can say which pipeline number is right |
| 1. First hire | $5M to $20M ARR | One senior generalist | CEO or CRO | Revenue operations manager who can configure the CRM and build reports | The generalist spends the week on tickets and never on the forecast |
| 2. Core team | $20M to $50M ARR | Leader plus a systems owner and an analyst | CRO | Systems administrator first, then an analyst | Marketing and CS still run their own ops with their own definitions |
| 3. Pods | $50M to $150M ARR | Head of RevOps with sales, marketing and CS ops leads, plus shared analytics | CRO | Marketing ops and CS ops leads; deal desk if pricing is complex | Each pod builds its own dashboards and the numbers drift |
| 4. Full function | $150M+ ARR, multiple segments or regions | VP of Revenue Operations over pods, a data and systems team, planning and comp | CRO or CEO | Data engineer, comp analyst, enablement | Regions or business units start hiring their own ops people |
Stage 1: First RevOps hire ($5M to $20M ARR)
At this stage, you need one senior generalist. One person who can handle CRM administration, basic reporting, pipeline hygiene, and process documentation. They will not be great at all of these. That is fine. The goal is coverage. Title: RevOps Manager or Revenue Operations Manager Reports to: CEO or CRO (never a VP of Sales or VP of Marketing) Core responsibilities:- CRM administration and data quality enforcement - Weekly pipeline reporting for leadership - Basic forecast roll-up and forecast variance tracking - Sales process documentation and stage definitions - Tool evaluation and vendor management
What this person should not be doing: Building machine learning models, designing compensation plans from scratch, or running marketing automation. Those require specialists. Asking a generalist to do specialist work guarantees mediocre results on everything. How big: One person, plus outside help where depth is needed. Revenue Wizards, a RevOps consultancy, puts the first in-house hire at about 26 to 50 employees and two or three RevOps people at 51 to 100, based on its own client work (Revenue Wizards, updated October 15, 2026). Fractional RevOps can cover the gap before that.The biggest risk at this stage is hiring too junior. A RevOps manager at a $15M company needs enough seniority to push back on the VP of Sales when pipeline hygiene slips. If they cannot have that conversation, the function will not work. A junior hire also tends to drift into pure CRM admin work, which leaves nobody on the forecast.
Stage 2: Building the core team ($20M to $50M ARR)
This is where RevOps starts to specialize. One generalist cannot cover CRM operations, analytics, tool administration, and cross-functional process design. The work splits into two lanes: systems and analytics. Typical roles:- Director of RevOps: strategy, cross-functional alignment, board reporting. - CRM or systems administrator: data quality, workflow automation, integration management. - RevOps analyst: pipeline reporting, forecast modeling, conversion analysis.
For dated salary figures by source for sales ops and RevOps managers, see the sales operations manager salary guide.
Reports to: CRO. At this stage, the CEO usually hands revenue accountability to a CRO, and RevOps needs to report to whoever owns the number.The Director role is the critical hire. This person translates between sales, marketing, customer success, and finance, and needs credibility with all four. Hire someone who has run pipeline reviews before. Someone who knows that B2B contact data decays at about 25 to 30% a year (ZoomInfo) and can build processes that fix it.
Hire the systems administrator before the analyst. 76% of CRM users say less than half of their CRM data is accurate (Validity, 2025), and a model built on that data starts from a weak base. The administrator also gives reps time back: reps spend just 28% of their week actually selling (Salesforce, 2022), and every hour of data entry the admin automates is an hour a rep can spend selling.
The analyst is where forecasting starts to get real. This person builds the models that replace gut-feel forecasting. They track stage conversion rates, pipeline velocity, and weighted pipeline coverage. They are the reason the board stops getting surprised. For how this role differs from a sales analyst, see RevOps analyst vs sales analyst.
Stage 3 and 4: Pods and the full function ($50M ARR and up)
From here, RevOps is a function with its own leaders. The work splits into pods for each revenue team, with a shared analytics and data layer so the pods do not build conflicting numbers. Typical structure:| Role | Pod | Focus |
|---|---|---|
| VP or Head of Revenue Operations | Leadership | Cross-functional strategy, board-level forecasting, exec alignment |
| Manager, Sales Operations | Sales ops | Territory design, quota modeling, comp plan administration, deal desk |
| Manager, Marketing Operations | Marketing ops | Campaign attribution, lead routing, funnel reporting |
| CS Operations lead | CS ops | Renewal forecast, health scoring, onboarding workflows |
| Senior RevOps Analyst | Shared analytics | Forecast modeling, pipeline analytics, scenario planning |
| RevOps Analyst | Shared analytics | Weekly reporting, data validation, dashboard maintenance |
| CRM Administrator | Shared systems | System configuration, integration management, data governance |
The VP role is a different job from the Director role. The VP of Revenue Operations sits in board meetings, explains forecast methodology to investors, and owns the revenue model and the forecast accuracy that comes out of it.
This is also where marketing operations formally joins the RevOps function. Before this stage, marketing usually runs its own operations. Once the data model needs to be unified, separate marketing and sales operations mean separate pipeline definitions, separate attribution models, and separate versions of the truth. That is exactly what RevOps exists to prevent.
At this size, the main structural choice is whether operators sit centrally or inside each function. We cover the trade-offs in centralized vs embedded RevOps and the short version in centralized vs decentralized RevOps. Most teams land on a hybrid: one leader, one backlog, one data model, with named operators assigned to each revenue team.
Illustrative RevOps org chart
Here is one way to lay out a Stage 3 team, for an illustrative company around $60M ARR with sales, marketing and customer success teams. Treat it as a template to adapt, not a target headcount.``` CEO | +-- CRO (owns the company forecast) | +-- VP Sales, VP Marketing, VP Customer Success | (internal customers of RevOps, not its managers) | +-- Head of Revenue Operations (owns forecast process, data model, planning calendar) | +-- Sales ops manager: territories, quota, comp admin, deal desk +-- Marketing ops manager: routing, attribution, campaign ops +-- CS ops lead: renewal forecast, health scores +-- Systems administrator: CRM config, integrations, permissions +-- RevOps analyst: forecast model, pipeline reports, board pack ```
Three things in this layout matter more than the box count. RevOps reports to the CRO, beside the functional VPs and not under any of them. Systems and analytics are shared, so every pod reads the same pipeline definitions. And requests come in through one queue: a RevOps intake process keeps the team from becoming a service desk. For more variations, see the RevOps org chart glossary entry.
Who should RevOps report to?
RevOps should report to whoever owns the whole revenue number: the CRO, or the CEO when there is no CRO. Reporting into sales or marketing gives one function control of the data every function depends on.Many teams still sit under sales. In the BoostUp.ai and RevOps Co-op 2025 survey, 35% of respondents reported into RevOps, 29% into sales, 14% into business ops, 8% into finance and 7% into marketing (2025 RevOps Comp & Impact Report). Those figures describe individual respondents, many of whom report to a RevOps leader, so they show where people sit, not where the function should sit.
The reporting line also shapes how the forecast is governed. As Pete Furseth, ORM's COO, puts it, forecasting is a joint exercise, but every week each level needs a clear owner: reps own their deals, managers own the roll-up, regional leaders own their number, and the CRO owns the company forecast. RevOps owns the process: the same definitions, the same cadence, and the same rules for what gets included, every week. When RevOps reports to the CRO, it can enforce that process across sales, marketing and customer success without taking a side. For the full argument, see who should RevOps report to.
The relationship matters as much as the box. Pete notes that a CRO often has a trusted relationship with the RevOps leader, sometimes from a previous company where they worked together. That trust is what lets RevOps say no.
How many people should be on a RevOps team?
There is no single right ratio, but survey data gives a range: in a 2025 survey, average RevOps team size ran from about 4 people at small companies to about 14 to 15 at companies above 1,000 employees. Size from the work first, then sanity-check against the numbers below.| Company size (employees) | Average RevOps team size |
|---|---|
| 0 to 50 | 4.4 |
| 51 to 200 | 3.7 |
| 201 to 1,000 | 7.8 |
| 1,001+ | 15.4 in the chart, 13.9 in the report text |
Two cautions. The survey reached people who work in RevOps, so companies with no RevOps team are underrepresented, and the 0 to 50 average sits above the 51 to 200 average, which tells you the small-company sample is noisy. The same report includes an expert note suggesting a ratio of 12 to 15 revenue-facing staff (AEs, CSMs and SDRs) per RevOps person, agreed upfront with finance. That is one practitioner's guidance printed in the report, not a survey result.
The better method is to list the recurring work (weekly forecast roll-up, monthly board reporting, annual territory and comp cycles, continuous system changes), estimate the hours, and add room for ad hoc requests. We walk through that method in how many RevOps people do you need.
Where the forecast sits in the team
The person in RevOps who is accountable for the forecast should talk to sales leaders every day, and always before the weekly forecast call. That is Pete's one habit for every RevOps team. "The science and math of a forecast are important, but so is the rhythm and vibe of the team," he says. The model has to be challenged by what the people closest to the deals are saying. It cannot be done in a vacuum.That has a structural consequence. If the analyst who owns the model sits three layers away from the sales leaders, or spends the week on system tickets, the daily conversation does not happen. Put the forecast owner close to the CRO and protect their time.
The opposite pattern is an ops team so buried in spreadsheets that it ends up running the forecast call itself. That warning sign, and when it means a sales ops team should become RevOps, is covered in sales ops vs revenue operations.
Two more points from Pete bear on structure:
- Tools depend on the operators. Sales teams enter the data, but RevOps or sales ops runs the forecasting process. If the operations team is not comfortable learning a new platform, it will not get adopted, however good the software is. Staff for the tools you buy. - The work is shifting toward decisions. Pete expects AI-native revenue teams to move from reporting, to prediction, to action, with people spending less time gathering data and reconciling reports and more time on judgment. That shifts future hires toward analysts and planners and away from report builders. It does not remove the need for an owner.
The three mistakes that break RevOps team structure
Mistake 1: Burying RevOps under Sales. RevOps reports to the revenue owner. When RevOps reports to the VP of Sales, it becomes Sales Ops with a new name. Marketing stops trusting the numbers. Customer success ignores the processes. The "single source of truth" becomes one department's version of the truth. Mistake 2: Hiring analysts before fixing the data. RevOps analysts build models on CRM data, and with most CRM users rating their own data as mostly inaccurate (the Validity figure above), a model starts from a weak base. Hire the CRM administrator first, set the entry standards, then hire the analyst. Mistake 3: Copying the enterprise model too early. A $30M ARR company does not need a VP of Revenue Operations, a Director of Sales Ops, a Director of Marketing Ops, and a team of analysts. That structure costs a lot and creates more internal politics than it solves. Build the team to match the stage. Add roles when the bottleneck demands it, not when the org chart looks incomplete.What does a RevOps team cost?
Base salary is most of the cost, and a three-person core team runs roughly $350,000 to $510,000 in base pay at 2025 US ranges. The table uses Captivate Talent's State of RevOps in 2025 ranges, which the recruiting firm describes as what it observes in the US market.| Role | Base salary range (US, 2025) | OTE range |
|---|---|---|
| RevOps Director | $180,000 to $250,000 | $250,000 to $350,000 |
| RevOps Manager | $130,000 to $180,000 | $180,000 to $250,000 |
| Sales Operations Manager | $120,000 to $170,000 | $160,000 to $230,000 |
| Marketing Operations Manager | $110,000 to $160,000 | $140,000 to $200,000 |
| Customer Success Operations Manager | $100,000 to $150,000 | $130,000 to $180,000 |
| RevOps Systems Administrator | $90,000 to $140,000 | $110,000 to $170,000 |
| RevOps Analyst | $80,000 to $120,000 | $100,000 to $150,000 |
- Stage 2 core team (director, systems administrator, analyst): $180,000 + $90,000 + $80,000 = $350,000 at the low end; $250,000 + $140,000 + $120,000 = $510,000 at the high end. Base only. - Stage 3 org chart above (director, sales ops, marketing ops and CS ops managers, systems administrator, analyst): $680,000 to $990,000 in base salary.
Add bonus, benefits, payroll tax and tools on top. For a cross-check, the BoostUp.ai and RevOps Co-op survey put median total OTE for its respondents at $129,155 in 2025. Salary aggregators disagree with each other, so compare several before you set a band; the sales operations manager salary guide lays them side by side with dates.
The comparison that matters is cost against the work. Pete's point about forecasting software applies to headcount too: the real cost includes the internal time, expertise and maintenance needed to make a model useful, on top of the license. If a forecasting partner carries the modeling, the team can stay smaller and spend its time on process and planning.
What the best RevOps teams have in common
The RevOps teams that drive real impact share five traits.
They own the forecast process and model. The CRO owns the number. RevOps builds and maintains the model and the cadence, and every other function feeds it.
They have direct access to the CEO or board. RevOps insights that get filtered through two management layers lose their edge. The best teams present directly to leadership.
They measure a short list of things, rigorously. The payoff from doing operations well is real: top B2B tech companies, led by SaaS providers, report 10% to 20% gains in sales productivity from stronger go-to-market operations (BCG, 2020).
They enforce data quality through process, not audits. Quarterly data cleanup projects mean the data was bad for the previous 89 days. Process-level enforcement means bad data never enters the system.
They resist becoming a service desk. RevOps is strategic. The moment it becomes the team that pulls reports on demand, it stops being able to do the work that moves the revenue number.
Alignment pays when it is designed in. Emerging companies preparing for exit that align the people, process, and technology involved in their demand engine will experience 36% more revenue growth and up to 28% more profitability (Forrester, 2021). When those gains do not show up, the cause is usually unclear ownership, which is a structure problem.
How to know when your RevOps structure needs to change
The signals are usually obvious in hindsight. Pipeline reviews run long because nobody trusts the numbers. Forecast accuracy has not improved in two quarters. The RevOps team spends most of its time on ad hoc report requests.
Each of those signals points to a structural gap. Long pipeline reviews mean the data model is fragmented. Flat forecast accuracy means the analytics capability is missing. Excessive report requests mean the team is understaffed or has no intake process.
When you see those signals, start with the structure before adding people. A single senior hire who fixes the reporting architecture will do more for forecast accuracy than three junior analysts pulling data from spreadsheets.
RevOps evolves with the business. The structure that works at $20M will not work at $80M. Plan for that. Revisit the org design whenever you cross a revenue threshold, add a product line, or enter a new region. For the toolset that supports each stage, see our roundup of the best RevOps tools.
Frequently Asked Questions
What is a RevOps team structure?
It is the way a company arranges revenue operations roles, the reporting line and the order of hires across sales, marketing and customer success. Early on it is one senior generalist. Later it splits into systems, analytics and planning work, then into sales, marketing and CS ops pods that share one data layer and one leader who reports to the CRO or CEO.
How many people should be on a RevOps team?
Survey averages give a starting point. In the 2025 RevOps Comp & Impact Report from BoostUp.ai and RevOps Co-op, average RevOps team size was 4.4 at companies with 0 to 50 employees, 3.7 at 51 to 200, 7.8 at 201 to 1,000 and 15.4 above 1,000 in its chart, though its text gives 13.9 for that top band. Size your own team from the recurring work it must deliver, then compare.
When should a company hire its first RevOps person?
Hire when nobody owns the CRM, leadership argues about which pipeline number is right, and revenue comes from more than one motion, such as new business plus renewals. Revenue Wizards, a RevOps consultancy, puts that first in-house hire at about 26 to 50 employees in its client work. Make it a senior generalist, since a junior hire tends to become a CRM admin.
Who should RevOps report to?
RevOps should report to the executive who owns the whole revenue number, usually the CRO, or the CEO when there is no CRO. Under the VP of Sales it turns into sales ops with a new name and marketing and customer success stop trusting its numbers. In the BoostUp.ai and RevOps Co-op 2025 survey, 29% of respondents still reported into sales.
What roles are on a RevOps team?
A full team has a RevOps leader, a systems administrator who owns the CRM and integrations, one or more analysts who own reporting and the forecast model, and operations leads for sales, marketing and customer success. Larger teams add deal desk, compensation and enablement roles. Small teams cover the same work with fewer people wearing more hats.
How much does a RevOps team cost?
Base pay drives most of it. Captivate Talent's 2025 ranges for the US are $180,000 to $250,000 for a RevOps director, $90,000 to $140,000 for a systems administrator and $80,000 to $120,000 for an analyst. That puts a three-person core team at about $350,000 to $510,000 in base salary before bonus, benefits and tools.
---
ORM Technologies builds and maintains custom revenue forecast models for B2B SaaS companies. Unlike dashboards or platforms, ORM works as a dedicated forecasting partner directly on your CRM data. Learn more at orm-tech.com.Frequently Asked Questions
What is a RevOps team structure?
It is the way a company arranges revenue operations roles, the reporting line and the order of hires across sales, marketing and customer success. Early on it is one senior generalist. Later it splits into systems, analytics and planning work, then into sales, marketing and CS ops pods that share one data layer and one leader who reports to the CRO or CEO.
How many people should be on a RevOps team?
Survey averages give a starting point. In the 2025 RevOps Comp & Impact Report from BoostUp.ai and RevOps Co-op, average RevOps team size was 4.4 at companies with 0 to 50 employees, 3.7 at 51 to 200, 7.8 at 201 to 1,000 and 15.4 above 1,000 in its chart, though its text gives 13.9 for that top band. Size your own team from the recurring work it must deliver, then compare.
When should a company hire its first RevOps person?
Hire when nobody owns the CRM, leadership argues about which pipeline number is right, and revenue comes from more than one motion, such as new business plus renewals. Revenue Wizards, a RevOps consultancy, puts that first in-house hire at about 26 to 50 employees in its client work. Make it a senior generalist, since a junior hire tends to become a CRM admin.
Who should RevOps report to?
RevOps should report to the executive who owns the whole revenue number, usually the CRO, or the CEO when there is no CRO. Under the VP of Sales it turns into sales ops with a new name and marketing and customer success stop trusting its numbers. In the BoostUp.ai and RevOps Co-op 2025 survey, 29% of respondents still reported into sales.
What roles are on a RevOps team?
A full team has a RevOps leader, a systems administrator who owns the CRM and integrations, one or more analysts who own reporting and the forecast model, and operations leads for sales, marketing and customer success. Larger teams add deal desk, compensation and enablement roles. Small teams cover the same work with fewer people wearing more hats.
How much does a RevOps team cost?
Base pay drives most of it. Captivate Talent's 2025 ranges for the US are $180,000 to $250,000 for a RevOps director, $90,000 to $140,000 for a systems administrator and $80,000 to $120,000 for an analyst. That puts a three-person core team at about $350,000 to $510,000 in base salary before bonus, benefits and tools.
Five free days of implementation
Start with ORM and your first five days of implementation are free. We build your forecast model on your live pipeline, then you decide.
Claim your five days