---
title: "What Companies Actually Spend on RevOps"
type: study
evidence_type: measurement
sample: "11 published sources"
methodology: "Reconciliation of 11 published benchmark sources against each other; resolves the widely-miscited '5–10%' figure to headcount rather than spend."
publisher: "LeanScale"
date_modified: 2026-08-04
word_count: 2398
topics: ["revenue-operations"]
canonical_url: https://knowledge.leanscale.team/research/revops-investment-study/
source: "LeanScale Knowledge Hub — https://knowledge.leanscale.team"
license: "Free to quote and cite with attribution to LeanScale."
---

# What Companies Actually Spend on RevOps

**Evidence type:** measurement (what we measured)

**Sample:** 11 published sources

**How it was measured:** Reconciliation of 11 published benchmark sources against each other; resolves the widely-miscited '5–10%' figure to headcount rather than spend.

What survives when you stop reading RevOps content marketing and go back to the primary documents — the survey PDFs, the press releases, the benchmark tables, and the footnotes underneath them. Finding 01 · The missing number

## Seven findings from the literature.

What survives when you stop reading RevOps content marketing and go back to the primary documents —
the survey PDFs, the press releases, the benchmark tables, and the footnotes underneath them.
Finding 01 · The missing number

### Nobody publishes the number everyone asks for.

There is no credible published benchmark for "RevOps as a percentage of revenue." Not from Gartner, not from Forrester, not from any of the SaaS benchmarking houses. Every authoritative source answers a different question — headcount share, staffing ratios, absolute FTE counts — and the percentage-of-revenue figure that circulates online is always someone's undisclosed arithmetic on top of one of those.
Finding 02 · The citable answer

### The defensible benchmark is 5–10% of GTM headcount.

ICONIQ Growth's January 2026 survey of GTM executives at 150+ B2B software companies puts RevOps at 5–10% of go-to-market headcount, median 7%. It is remarkably stable: 5–11% across seven revenue bands , 6–9% across customer segments, 7–10% across growth motions. When a ratio holds that flat across that many cuts, it is describing something structural.
Finding 03 · The planning proxy

### One RevOps head per ~$21M of ARR.

Derived from ICONIQ's absolute FTE counts, the ratio is tighter than any percentage: $21M–$29M of ARR per RevOps head from $25M all the way through $500M+. It is the single most useful planning number in the study — and it breaks in exactly one place. Below $25M ARR it compresses to ~$12M per head , because the first RevOps hire is indivisible.
Finding 04 · The denominator decides

### The same team is 7% or 0.9% depending on what you divide by.

One company, one RevOps team, one year — and five defensible answers ranging from 7% down to 0.9%. The popular "5–10% of sales and marketing spend" rule only survives if you count systems as well as people. On a people-only denominator it lands at 4% , and at a heavy-spending VC-backed company it lands at 3.6%. Anyone quoting the rule without stating the denominator is quoting noise.
Finding 05 · The datasets disagree

### The two largest samples are 2.7× apart.

ICONIQ's survey implies 4.3 sellers per RevOps head. PeerSignal's title scrape of ~2,500 B2B software companies observes 11.8:1. Neither is wrong. ICONIQ surveys VC-backed growth companies who self-report a RevOps function; PeerSignal counts LinkedIn titles across the whole market and deliberately excludes marketing ops. Cohort and counting method, not error — which is precisely why a single quoted ratio is worthless without both.
Finding 06 · The stats don't hold up

### The most-quoted RevOps ROI numbers have no evidence base.

BCG's famous figures — 10–20% sales productivity, 30% lower GTM expense, 100–200% marketing ROI — appear in a 2020 article with no sample size, no methodology, and no citation. The equally ubiquitous "36% more revenue growth, 28% more profitability" is an orphan: it is attributed to Forrester everywhere and traces to nothing. Forrester's actual published figure for aligned revenue teams is 19% and 15%.
Finding 07 · The 2026 freeze

### RevOps headcount goes flat this year. The work doesn't.

ICONIQ's median expected RevOps headcount change for 2026 is 0% — while Sales and Post-Sales grow 10–20%. RevOps is being asked to absorb a fifth more selling capacity with the same team, on a bet that AI and outside help close the gap. That is the most consequential number in the study, and it is not a benchmark. It's an arbitrage.
Methodology & Limits

## A reconciliation, not a survey.

This study is different from the rest of the series, and the difference matters. Read this section before
you quote anything from it.
What this is. A reconciliation of eleven published third-party sources
against each other and against a common arithmetic. Where a source published a headcount share, we
converted it to dollars; where it published absolute FTE counts, we derived ratios. Every conversion is
stated on the page so you can disagree with it. This is not a study of LeanScale's own customer data
— unlike the other studies in this series, no proprietary delivery data is used here.
The primary documents. ICONIQ Growth's Building the Modern GTM Org (January
2026 survey, 150+ B2B software companies, published May 2026) carries the load — it is the only source
that publishes RevOps headcount share and absolute FTE counts and per-chart sample sizes.
SaaS Capital's 2026 spending benchmarks (Q1 2026, 1,000+ private B2B SaaS) supply the spend denominators.
PeerSignal supplies the large-N observational check.
The conversion, stated plainly. To turn headcount into dollars we assume a
$200K fully-loaded cost per RevOps FTE (base plus bonus, benefits, and payroll burden,
blended across ICs and leadership — consistent with published 2026 RevOps compensation ranges of
$140–160K for ICs and $187–300K for leaders). Move that assumption and every dollar figure on this page
moves with it. The headcount findings do not.
The weakest leg. The systems half of "people plus systems" is the least well-sourced
number here. Published GTM tooling spend is fragmented and mostly vendor-authored; we model it as a range
of $4K–$10K per GTM seat per year and show the range rather than a point estimate. If you
only trust one thing on this page, trust the headcount ratio and treat the dollar cascade as an
illustration of why the denominator matters rather than as a precision instrument.
The bias to hold in mind. ICONIQ is a growth-equity firm surveying its own network and
portfolio. That cohort is better-capitalised and more operationally sophisticated than the median B2B
software company — which is very likely why its implied staffing ratio is nearly three times richer than
PeerSignal's market-wide scrape. Read ICONIQ as "what well-funded companies do," not
"what companies do."
Why it matters
Benchmarks in this category are unusually circular. A consultancy publishes a figure with no method, a
vendor blog repeats it, an SEO page cites the vendor blog, and within two years the number is "industry
standard." Four of the eleven sources here are ultimately quoting each other. The grading
table below exists so you can see which is which before you put a number in a board deck.
The Evidence Base

## What the sources actually measure.

Eleven sources, but only a handful measure the same thing. Here is how the literature distributes — by
what is being counted, and by who did the counting.
By what it measures
By evidence type
Read the zero
The most telling bar in the study is the empty one. Not one of the eleven sources publishes RevOps
spend as a percentage of revenue — the exact number every budget conversation opens with. Just over
half measure headcount share or a staffing ratio, and a quarter publish a claimed ROI uplift with no
staffing figure attached at all.
The Denominator Cascade

## The most important chart in the study.

One company. One RevOps team. One year. Five defensible answers to "what percentage are we spending on
RevOps?" — depending entirely on what sits underneath the division line. The lime band is the popular
5–10% rule of thumb.
The same team, five denominators
Median B2B software company · ICONIQ headcount shares converted at $200K loaded cost per FTE
Read top to bottom as the denominator widens. The 5–10% rule survives on GTM headcount
and on sales-and-marketing spend only when systems are counted alongside people . Strip the systems
out and it falls to 4%. Apply it at a heavily-funded company — where sales and marketing spend runs closer
to 42% of revenue than 23% — and it falls to 3.6%. All five numbers describe the identical team.
The practical consequence
If someone tells you to spend "5–10% on RevOps," the only correct response is "percent of
what?" On headcount it is a well-evidenced benchmark from a 150-company survey. On sales and
marketing dollars it is defensible only with tooling in the numerator. On total revenue the right
answer is closer to 1% , and a team asking for 5% of revenue is asking for five times the
market rate.
The Planning Ratio

## One head per $21M of ARR.

Percentages move when the denominator moves. Headcount ratios don't. This is the number to actually plan
against — derived from the absolute RevOps FTE counts ICONIQ published for each revenue band.
ARR supported per RevOps FTE
By 2025 revenue band · derived from published median FTE counts
Flat from $25M to $500M+ — between $21M and $29M of ARR per RevOps head, with no
trend. The outlier is the bottom band, and it is the most important cell in the table: below $25M ARR the
ratio compresses to roughly $12M per head , because you cannot hire two-thirds of a person.
Per-band sample sizes in the source range from 9 to 24 companies; the $500M+ band is the thinnest and should
be read as directional.
The indivisibility problem. Every percentage-based rule assumes you can buy a fraction
of a head. At $15M ARR, 7% of a 20-person GTM org is 1.4 people — so you hire one and run under-invested,
or hire two and run over. This is why the small-company band looks anomalously rich: it isn't generosity,
it is rounding up to one.
Where the ratio quietly changes meaning. ICONIQ's largest band shows RevOps rising to
11% of GTM headcount at $500M+. That is not more of the same work — at that scale the
function has absorbed deal desk, pricing, and a data-engineering interface. The ratio holds; the job
description doesn't.
What RevOps actually spends its time on. ICONIQ's respondents allocate roughly
22% to data and reporting, 22% to systems and tools, 13% to GTM planning, 10% to AI
experimentation , with deal desk and enablement each around 9%. At consumption-priced companies
data and reporting jumps to 30% — usage-based revenue demands a forecasting rigor that
seat-based revenue doesn't.
And where it reports. 76% of RevOps functions report into Sales. At
companies with consumption or outcome-based pricing that drops to 63%, with 32% reporting into
Finance instead — the clearest structural signal in the data that pricing model reshapes the
function.
The Conflict

## Two large datasets, 2.7× apart.

Both are credible. Both are recent. They are measuring the same ratio and they do not agree — and
understanding why is more useful than picking one.
Sellers per RevOps head
Account executives and SDRs per RevOps FTE
The ICONIQ figure is implied rather than published: it combines the reported RevOps
share of GTM headcount (7%) with the reported sales-team composition (AEs and SDRs ≈ 60% of a sales org
that is ≈ 50% of GTM). Across ICONIQ's own published spread the implied ratio ranges from 2.4:1 to 7.0:1 —
so even the richer figure is a range, not a point.
How to use the conflict
Treat the two as a floor and a ceiling on the same question . If you are a well-funded
growth company benchmarking against your peer set, ICONIQ's richer staffing is the relevant comparison. If
you are arguing to a CFO who will Google the market rate, the 12:1 figure is what they will find. Quote
both, or you will get ambushed by the one you left out.
The CFO Frame

## RevOps costs about what finance costs.

The most useful comparison in this entire study isn't to another GTM benchmark. It's to the back-office
function every CFO already knows the cost of.
Function cost as a percentage of revenue
RevOps derived from ICONIQ FTE counts · finance benchmarks from APQC process data
RevOps at 0.93% of revenue sits between APQC's top-performing finance
function (0.7%) and the median one (1.2%). The comparison is deliberately imperfect — finance is a mature,
heavily-benchmarked function and RevOps is not — but it is the frame that makes the number legible to the
person approving it.
The argument this unlocks
"We are asking for roughly what the finance function costs, to do for revenue what finance does for cash:
own the system of record, close the period, and make the forecast trustworthy." That sentence survives a
budget review. "Industry standard is 5–10%" does not — because the first question back is
percent of what , and most teams don't have an answer.
Source Grading

## Which numbers survive a skeptical CFO.

Every source we found that publishes a quantitative claim about RevOps investment, graded on sample size,
transparency of method, recency, and whether the primary document actually says what it is quoted as
saying. Grades are ours, and we state the reason for each.
The orphan statistic
"Companies with a RevOps function see 36% more revenue growth and 28% more profitability" appears in
hundreds of RevOps articles, attributed to Forrester. We could not find a Forrester document that says it.
Forrester's published figure for aligned revenue teams is 19% faster growth and 15% higher
profitability . Somewhere between the report and the tenth blog post, the numbers grew by roughly
90%. Do not put this stat in a deck.
The Playbook

## How to actually answer the question.

Three moves, in order. They work whether you are setting the budget or defending it.
01

### Pick the denominator before you pick the number.

Headcount is the defensible one — 5–10% of GTM headcount, median 7% , from a
150-company survey with published per-chart sample sizes. If you need a dollar figure, say which
denominator you used and whether systems are in the numerator. The single most common failure in RevOps
budget conversations is quoting a percentage whose denominator nobody agreed on.
02

### Sanity-check against the FTE ratio.

Percentages drift; the ratio doesn't. One RevOps head per ~$21M of ARR holds from $25M
through $500M+. Under $25M ARR, stop using percentages entirely — the answer is one or two people, and
the honest framing is that the first hire is indivisible. If your percentage-derived number and your
ratio-derived number disagree by more than one head, your denominator is wrong.
03

### Price the gap, not the headcount.

The live number for 2026 is not a benchmark — it's that RevOps headcount is flat while sales
grows 10–20%. Somebody has to absorb a fifth more selling capacity on the same team. The
budget question worth arguing isn't "are we at 7%," it's "what happens to the work we just decided not
to hire for." That gap gets closed by automation, by scope cuts, or by outside capacity — and choosing
deliberately beats discovering it in Q4.
Where this came from
LeanScale is a revenue-operations firm. We build and run the GTM systems inside high-growth B2B software
companies — which is why we spend our time on questions like this one. Talk to us
if you're sizing a RevOps function, or defending the one you have.
LeanScale
A LeanScale Field Study · August 2026. A reconciliation of published third-party research; no proprietary
customer data is used in this study. Sources: ICONIQ Growth, Building the Modern GTM Org (May 2026)
and The State of GTM in 2026 ; SaaS Capital, 2026 Spending Benchmarks for Private B2B SaaS
Companies ; PeerSignal RevOps benchmarks; APQC finance-function process benchmarks; Forrester; Gartner;
Boston Consulting Group; Winning by Design; SellingBrew; RevOps Co-op; Revenue Operations Alliance. Dollar
conversions are ours and are stated in the methodology. Grades are editorial.
leanscale.team

## Canonical

https://knowledge.leanscale.team/research/revops-investment-study/