RevOps headcount scales roughly linearly with revenue. What changes qualitatively at each stage is the shape of the team — what specializes, what stays generalist, and who it reports to. A Series A company runs RevOps with one person. A Series D company runs it with 20 to 40. In between, the org goes through three or four structural rewrites, and each one tends to be painful because it usually happens 6-12 months later than it should.
I've spent years talking to RevOps leaders across Series A through Series D companies, and the pattern is consistent. The team you need at $10M ARR is not the team you need at $30M ARR, and the team at $30M is not the team at $80M. Below is what the structure actually looks like at each stage, what it costs, and where teams most commonly get it wrong.
Series A ($1-5M ARR): one person, player-coach
At Series A you have one RevOps person. Usually titled Sales Operations Manager, occasionally Head of Revenue Operations if the founder is ambitious about the title. They own everything that touches the revenue engine that isn't selling: CRM administration, forecast build, territory assignments, basic reporting to the board, tool selection, data hygiene.
This person is a player-coach. They run the weekly forecast call and they also fix broken Salesforce validation rules. They report to the CEO or the Head of Sales, depending on how technical the founder is. Base comp is $90-140K depending on geography and experience.
The common mistake at this stage is hiring a strategic RevOps leader too early. A $250K VP of RevOps at Series A does not have enough surface area to justify the cost. You want a senior IC who can build, not a leader who wants to hire a team.
Series B ($5-20M ARR): 3-5 people, functional splits emerge
Between Series A and Series B, one of two things happens. Either the single RevOps person becomes a bottleneck and revenue-critical work slips (bad forecast, missed territory calls, broken commissions), or they burn out and quit. Either outcome forces the same conclusion: RevOps needs functional splits.
At Series B, most teams look like this:
- Deal desk / order management — 1 person, owns pricing exceptions, quote approvals, closed-won data quality
- Analytics — 1-2 people, owns forecast, pipeline generation reporting, board metrics
- Systems / tech admin — 1 person, owns CRM configuration, tool integrations, data flow
- Enablement lite — sometimes rolled in, sometimes stood up separately
The Head of RevOps at this stage typically reports to the CFO or the COO. Base comp for the leader is $180-260K plus equity. The IC roles pay $110-160K depending on function.
The biggest structural decision at Series B is whether marketing ops rolls into RevOps or stays inside marketing. Data-forward teams roll it in. Teams that leave marketing ops outside RevOps tend to end up with a data silo and a two-source-of-truth problem within 18 months.
Series C ($20-60M ARR): 8-15 people, specialization deepens
Series C is where RevOps becomes a real function. Territory and quota planning gets its own owner. Comp administration becomes complex enough to need dedicated ownership. The forecast analyst is no longer wearing three other hats.
A typical Series C RevOps org:
- Sales strategy / planning — 2 people, owns territory design, quota setting, capacity models
- Comp administration — 1-2 people, plan design and execution
- Forecasting / analytics — 2-3 people, weekly forecast, pipeline analytics, executive reporting
- Enablement — 2-3 people, onboarding, training, playbooks
- Marketing ops — 2 people, campaign attribution, MQL flow, funnel analytics
- CS ops — 1-2 people, retention forecasting, renewal motion, health scoring
- Systems — 1-2 people, CRM, integrations, data infrastructure
The head of the function reports to the CFO or COO. Some teams put it under a Chief Revenue Officer at this stage — that is where the political trouble starts. More on that below.
VP RevOps at Series C-D pays $250-380K base plus equity. This is where the role starts commanding real leverage on revenue outcomes.
Series D+ ($60M+ ARR): 20-40+ people, regional and specialty splits
Past $60M ARR the shape changes again. Regional splits appear — Americas RevOps, EMEA RevOps, APAC RevOps — each with its own analytics and enablement embed. New specialty functions get carved out:
- Product ops — embedded with the PLG motion, owns self-serve funnel analytics
- Revenue accounting / revenue recognition — a real function at $80M+, closer to finance than sales
- Dedicated data engineering — RevOps data becomes complex enough that it needs its own eng team
- Strategy function — 2-4 people, works with the CRO on annual planning, M&A, market entry
At this stage, the leader is often a Chief Revenue Operations Officer or SVP RevOps, reporting to the CRO or COO with a dotted line to the CFO. Comp lands at $350-500K base plus meaningful equity.
The org gets political here. Regional GMs want their own RevOps embed and control. Corporate wants standardization. This is a normal tension, but it is worth building the operating model deliberately rather than letting it emerge.
Reporting lines: the actual debate
The most common question I hear is who RevOps should report to. There is no universally right answer, but here is the shape of the trade-off:
- Under the CFO. Finance discipline is high. Forecast accuracy tends to be better. The downside is that finance leaders are trained to be conservative, and RevOps under finance can end up over-indexing on cost control at the expense of speed.
- Under the CRO or Head of Sales. RevOps is close to reps, feedback loops are fast, and enablement tends to be sharper. The risk is politicization — RevOps ends up defending the CRO's forecast rather than reporting the truth. This is the most common source of forecast credibility problems at Series C+.
- Under the CEO or COO. Neutral. Best structure at Series B-C when the function is small enough to warrant executive attention. Harder to sustain at Series D+ because the CEO has too many direct reports.
The pattern I see working best: CFO or COO reporting line at Series B and C, transition to CRO reporting at Series D+ once the function is large enough to defend its own analytical independence.
RevOps vs BizOps: where they diverge
At small companies these two functions overlap. RevOps is the revenue engine specifically — marketing ops, sales ops, CS ops. BizOps is broader — strategic finance, corporate development, cross-functional operations, sometimes even people ops.
Below $20M ARR, these two functions can be one team. Above $60M ARR, they should be separate. In between, it depends on the shape of the business.
The failure mode is a "BizOps" team that quietly owns revenue reporting without accountability to sales leadership. When forecast credibility is low, this is often the reason: revenue data lives with people who do not sit close enough to the revenue engine.
Compensation ranges (US, 2026)
- Sales Ops Manager (Series A-B): $90-140K base
- Senior RevOps Analyst: $120-160K base
- Head of RevOps (Series B): $180-260K base
- VP RevOps (Series C-D): $250-380K base
- Chief RevOps Officer / SVP RevOps (Series D+): $350-500K base plus equity
These are US ranges. EMEA runs 25-35% lower. APAC varies widely. Add 15-25% for late-stage companies in competitive markets.
Common structuring mistakes
Under-investing. One RevOps person at $30M ARR is a revenue leak. The math is straightforward: if a two-person RevOps team can move forecast accuracy from 70% to 85%, or improve conversion by even one percentage point through better multithreading analytics on the buying committee, the ROI is 10-50x the incremental headcount cost.
Burying RevOps under the CRO too early. Below $30M ARR this is usually fine because the CRO is close enough to reality. Above $30M, it starts to erode forecast credibility because RevOps loses the ability to disagree with the CRO in public.
Marketing ops outside RevOps. A data silo is created within 12-18 months. Board reporting becomes inconsistent. Attribution debates become theological. The best time to consolidate is at Series B.
No CS ops until it is too late. Expansion revenue is 30-50% of total ARR at mature SaaS companies. Under-investing in CS ops is under-investing in the largest revenue lever most companies have. Winning by Design's 2024 benchmarks show retention economics move faster than acquisition economics, and CS ops is where that lever lives.
Building a team that cannot connect revenue to relationships. This one is subtle. Most RevOps teams track pipeline, conversion, and forecast. Very few track relationship intelligence — who on the team knows whom in a target account, and whether that mapping is being used. At Series C+ this becomes one of the highest-leverage things RevOps can own.
Frequently asked questions
When should we hire our first RevOps person? Usually at $2-5M ARR, once the founder or Head of Sales is spending more than 20% of their week on forecast, comp, and CRM cleanup. Hiring earlier is fine if the founding team is not technical enough to build the CRM well.
Should RevOps report to the CFO or the CRO? At Series B-C, CFO or COO. At Series D+ you can move it under the CRO once the function is large enough to defend its analytical independence. The failure mode to avoid is a small RevOps team reporting to a strong CRO — the forecast will drift optimistic.
What is the right ratio of RevOps headcount to revenue? Rough benchmark: 1 RevOps person per $3-5M ARR at Series B, 1 per $5-8M at Series C, 1 per $6-10M at Series D+. These are directional. Complex product lines and multi-motion companies (PLG plus enterprise) need more.
Should marketing ops report into RevOps? Yes, past $10M ARR. Keeping marketing ops inside marketing creates a data silo that is expensive to unwind later. The exception is companies where marketing runs a demand-gen motion that is deeply integrated with brand — in that case marketing ops can stay closer to the CMO, but revenue reporting still needs to consolidate under RevOps.
How do we measure whether RevOps is working? Forecast accuracy (target: 85%+ at Series C+), rep-facing NPS on RevOps support, time-to-close on deal desk requests, and the number of net-new revenue-critical dashboards shipped per quarter. Also worth tracking: how often the CRO overrides the RevOps forecast in the board meeting. If it is every quarter, something is broken.
What is the difference between RevOps and BizOps? RevOps owns the revenue engine specifically. BizOps owns broader operations, strategy, and cross-functional planning. Below $20M ARR they overlap. Above $60M they should be separate teams.
