Enablement Should Report to Finance, Not to Sales
Where enablement sits on the org chart predicts its survival better than the quality of its programs does — and reporting through Sales is usually the wrong answer.
Ask ten sales leaders who enablement should report to and nine will say some version of "me" — or "my head of sales ops," which amounts to the same answer wearing a different badge. It sounds obvious. Enablement makes reps better at selling; sales leaders own selling; keep it close. I've now watched three enablement functions get gutted in three separate downturns, at three different companies, and in every post-mortem the quality of the training wasn't the issue. The org chart was. When the CFO went looking for the number that made the board's cost target work, enablement was sitting in a place where nobody had ever translated what it did into cash.
The reporting line decides the currency you're measured in
This isn't a metaphor. Where a function sits determines which numbers get attached to it, because it determines who signs off on its budget and what that person already tracks. Report through the VP of Sales and you get measured in sales' native currency: reps trained, NPS off the last kickoff, adoption rate of the new methodology, maybe a soft correlation with quota attainment that nobody can quite prove causation on. Report through Finance, RevOps, or a COO who already speaks in unit economics, and you get measured in cash: cost of ramp, cost of vacancy, payback period on a coaching investment. Only one of those two vocabularies survives being read aloud in a board deck about where next year's opex comes from.
I'm not being cute about "speaking the language of the business." I mean literally: a CFO doing a synergy review works down a spreadsheet looking for line items with no attached economic consequence, because those are the ones you can zero out without anyone downstream noticing for two quarters. "Training and Enablement — £190k" reads exactly like a line with no consequence, because whoever built the budget never connected it to one.
What actually gets cut first, and why
Here's roughly how a revenue-org budget review triages itself under pressure, ranked from hardest-to-touch to first-against-the-wall:
- Commission and OTE payouts. Contractually obligated and tied directly to bookings the company has already recognised. Nobody touches this first; it's the closest thing revenue has to a fixed cost that's also clearly variable-and-earned.
- CRM, forecasting, and pipeline tooling. Cutting it blinds leadership to the pipeline itself during the exact quarter they need visibility most. Survives almost every review.
- Marketing-sourced pipeline spend. Ugly, but it has a CAC and an LTV that finance has already blessed somewhere in a deck. A number with provenance is hard to argue with, even a mediocre one.
- Sales headcount. Painful and slow to cut because it's backed by a capacity model — quota per rep, ramped reps versus total reps — that everyone in the room already trusts and uses for forecasting.
- RevOps and sales analytics headcount. Protected mostly by association: they produce numbers finance uses in the same meeting where the cuts are being decided. Hard to fire the people holding the flashlight.
- Enablement, reporting through Sales. No line connects it to cash. It's read as the training-and-morale budget, and it is, without exception, the first thing zeroed when the CRO needs a fast 8% out of opex by Friday.
Notice the pattern: every survivor on that list is measured in a currency finance already trades in. Enablement, reporting through Sales, is the only line still being measured in the currency of "did people like it."
The finance-speaking alternative, with real numbers
Now run the same function through Finance or RevOps, with a dotted line into FP&A, and watch what changes. The conversation stops being "did reps enjoy the workshop" and starts being "what's the ramp-time trend line, and what's it costing us."
Take a mid-market AE on £70k OTE, target ramp to full quota in 90 days, actually ramping in 150. That's a 60-day gap. If the role carries roughly £40k of quarterly quota value per month and a rep sells at about half capacity while ramping, that gap costs you in the region of £40k of unrealised pipeline capacity per hire. Hire fifteen AEs a year and you're looking at £600k of ramp drag before you've spent a penny fixing it. A CAC & LTV Calculator run against your onboarding cohort will tell you within an afternoon whether your ramp curve is bleeding more than your enablement budget costs — most leaders have never actually run that comparison, because nobody asked them to.
Same function, two reporting lines
| Reports through Sales | Reports through Finance/RevOps | |
|---|---|---|
| Budget defended in | activity language — sessions run, content shipped | unit-economics language — ramp cost, vacancy cost |
| First question each quarter | "did reps like the training?" | "is the ramp-time trend line moving?" |
| Survives a hiring freeze | rarely | usually — it's the freeze mitigation |
| Primary artefact it owns | content calendar | ramp-cost model, quota-readiness gate |
| Sits next to | sales ops generalists | FP&A, revenue operations |
What to do before the reorg happens
You don't need to wait for a formal reporting change to start protecting the function, and you shouldn't, because the reorg conversation only happens after someone's already been cut. Start building the cash-denominated case now, regardless of who you report to today. Track ramp-to-productivity by cohort. Track the cost of an open or under-firing seat. Put both in front of whoever owns the board deck, even informally, using something closer to a Board-Ready Sales Metrics Dashboard Template than a training recap. If half your leadership team still can't tell you what CAC payback period means for their own patch, a Sales Metrics Literacy Quiz circulated before that conversation will save you from explaining unit economics from scratch in the meeting where your budget actually gets decided.
Enablement rarely dies because it stopped working. It dies because nobody translated what it does into a number the CFO would recognise before the meeting where the decision got made without anyone from enablement in the room.