What Sales Orgs Actually Spend on Enablement, and Why the Average Is a Useless Number
The 'enablement spend as a percentage of revenue' statistic gets cited constantly and means almost nothing, because it averages two totally different situations into one number nobody should benchmark against.
Somewhere in every enablement budget conversation, someone puts a slide up with a single number on it: enablement spend as a percentage of revenue. The figure that circulates in most state-of-the-industry decks sits somewhere between 1% and 2%. A CFO asks whether you're above or below it. You give an answer, the meeting moves on, and nobody asks the only question that actually matters, which is: above or below it compared to whom? Because that 1–2% isn't describing one kind of company. It's the blended average of two completely different exercises that both happen to get filed under "enablement," and averaging them together produces a number that's actively misleading for almost anyone who tries to use it.
Two populations, one blended number
Population one is the org building the function from zero. No certification programme, no dedicated headcount, content living in someone's Google Drive folder called "Sales Stuff FINAL v3." This org hires its first enablement lead, buys its first LMS licence, and pays an agency or a consultant to build a certification curriculum because nobody internal has done it before. Every pound of that spend is upfront and lumpy, landing against a revenue base that hasn't grown into it yet.
Population two is the org with a mature function. Certification exists, content gets refreshed rather than built from scratch, the platform is amortised, and the enablement team is a stable headcount line that grows roughly in step with the sales org. Spend here is smooth, mostly salary, sitting against a much bigger revenue denominator.
These are not two points on the same curve. They're two different cost structures that happen to share an account code.
The maths that makes the average lie
Take two shapes I've seen up close, made anonymous but not exaggerated.
| Org A (building from zero) | Org B (mature, steady-state) | |
|---|---|---|
| Revenue | £15m | £180m |
| Enablement headcount | 1 (new hire) | 7 |
| Platform/LMS spend | £40k (new licence) | £55k (existing, amortised) |
| Certification build | £90k (one-off, contracted) | £15k (annual refresh) |
| Total enablement spend | £450k in year one, loaded with build cost | £1.4m |
| Spend as % of revenue | ~3.0% | ~0.8% |
Blend a sample of orgs shaped like these across a typical industry survey and you land, unsurprisingly, right in that 1–2% band everyone quotes. But neither Org A nor Org B should benchmark against it. Org A isn't overspending at 3% — it's paying the fixed cost of building something that doesn't yet exist, and that cost doesn't scale down just because revenue is smaller. Org B isn't underspending at 0.8% — it has already paid the build cost and is now paying maintenance on an asset. Tell Org A's board to get to "industry average" and they'll gut the one-time investment that was supposed to make them look like Org B in eighteen months. Tell Org B's board they're "underinvesting" relative to the average and they'll add headcount the model doesn't need.
What actually drives the number, stage to stage
The honest way to think about enablement spend isn't a ratio to revenue at all — it's a ratio to what stage you're actually in, and what that stage structurally requires:
- Zero-to-one (0–18 months of the function existing). Spend is dominated by one-time build costs: platform selection, first certification curriculum, first content library. This is capital expenditure wearing an opex disguise, and it should be budgeted and reported as such rather than folded into a run-rate percentage.
- Standing up cadence (18–36 months). Spend shifts toward people — coaches, content owners — and away from tooling, because the tooling decision is already made. This is where the ratio to revenue starts dropping fast, which looks like "efficiency" on a chart but is really just the one-time cost rolling off.
- Steady-state (36+ months). Spend tracks headcount growth in the sales org, refresh cycles, and not much else. This is the only stage where a percentage-of-revenue comparison across companies is even close to apples-to-apples — and even then, only against other steady-state orgs of similar sales-org size.
The benchmark that isn't a percentage of revenue
If you want a number to actually manage against, stop dividing by revenue and start dividing by the thing enablement spend is meant to move. Two better denominators:
- Cost per rep supported. This normalises for company size without dragging revenue — a figure shaped by pricing, market, and product mix, none of which enablement controls — into the ratio.
- Cost per point of ramp-time reduction, or per point of win-rate movement. Harder to compute, but it's the only version of the metric that ties spend to the outcome you're actually buying it for.
Before you build either number, get honest about which of the three stages above you're actually in — not which one the org chart claims, the one your actual artifacts put you in. The RevOps Maturity Self-Assessment is a fast way to place yourself without the self-flattery that creeps into an internal audit. If your spend is still dominated by tooling decisions, the RevOps Tech Stack Audit Checklist will tell you whether that spend is one-time or recurring before you report it as a run rate. And if the real question underneath the budget conversation is headcount rather than percentage points, the Sales Capacity & Headcount Planner answers it directly instead of by proxy.
The next time someone puts that 1–2% slide in front of you, ask which population they sampled. If they don't know, the number was never a benchmark. It was a headline.