Sales enablement and revenue operations function as one system: the rep-development data enablement generates and the pipeline and forecast data ops generates are inputs to the same decisions, and separating them under different leaders, different budgets, and different reporting lines breaks that loop. The evidence is concrete. Enablement and ops vendors have spent the past two years merging into single platforms, most visibly Highspot’s merger with Seismic in February 2026, because the product categories no longer describe separate jobs. Most of the B2B companies buying from those vendors haven’t made the same move internally. Enablement in a typical org reports to one of seven different homes depending on the company, with no consensus on where it belongs, and the fragmentation shows up in a comp gap, an untracked spend pool, and programs that look complete in a slide deck and don’t move a number anywhere else in the business.
Sales enablement and revenue operations are functionally one system, not two adjacent ones, because the rep-development work enablement runs and the pipeline, forecast, and dashboard work ops runs feed the same decisions about what a rep should do differently and what the business should expect next quarter. When those two halves report to different leaders with different budgets, the loop breaks in both directions: training gets built without the data that would target it, and dashboards get built without the training that would act on what they show.
The Vendor Market Already Merged These Categories
In February 2026, Highspot and Seismic announced a merger, combining two of the largest platforms in the enablement category into one company. Other consolidations preceded and followed it in quick succession. MediaFly had acquired Appinium roughly six months earlier. Clari had absorbed SalesLoft into a single revenue platform. Bigtincan and Showpad had been in acquisition talks for a year. Gong had been extending its product into territory that used to sit with ops. SalesLoft had been extending into territory that used to sit with enablement.
The pattern is consistent across every deal: platforms built to sell training content and platforms built to sell pipeline and forecast visibility stopped describing themselves as separate markets and started building toward the same product. The vendors serving B2B revenue teams concluded, with their own capital, that enablement and ops are one category. Most of the companies buying from them still run the two functions as if they were unrelated.
Where Enablement Actually Reports
The Sales Enablement Collective’s 2025 Landscape Report surveyed reporting lines across hundreds of B2B companies and found no consensus. Seven different departments claim the function, and no single one holds a majority.
| Reports Into | Share of Companies |
|---|---|
| Revenue Operations | 39.4% |
| Sales | 25.4% |
| C-Suite (direct) | 16.6% |
| Marketing | 5.2% |
| Product Marketing | 3.5% |
| Human Resources | 2.6% |
| Other | 7.3% |
A separate 2023 study from Mindtickle cut the same question a different way and landed on a different distribution: CRO at 29%, RevOps at 18%, CFO at 17%. Different survey, different methodology, same conclusion. Nobody has settled where this function belongs, and the two most-cited studies on the question produce different answers from each other.
The Skill-Plumbing Mismatch
Underneath the reporting confusion sits a structural mismatch. A majority of enablement leaders, 66% by industry estimates, came up through a sales background: they carried a quota, made rep of the year, and got promoted into a systems role. They think and operate like sales leaders.
The budget, procurement process, and reporting line they inherit typically run through L&D instead. The training line item sits where it always sat. Vendor contracts route through HR because HR held those relationships before the function had a name. The result is a sales-minded leader running a function measured on completion rates and certification percentages, the metrics L&D was built to track, rather than on pipeline or win-rate movement, the metrics the leader was hired to move.
What the Split Costs
The org chart problem shows up directly in compensation. VP of Sales and VP of Revenue Operations both compensate at roughly $333,000 in total annual compensation across a representative sample of US B2B SaaS companies. VP of Enablement, inside the same organizations, compensates at $190,000 to $267,000, a 30 to 40 percent gap at the same level of seniority, frequently reporting to the same executive.
Forrester’s research on hidden sales-support costs found the real number even more striking: enablement-related spend across a typical B2B organization runs approximately $135,000 per quota-carrying rep per year once every line item is accounted for, and that spend sits scattered across L&D budgets, sales tool budgets, marketing collateral budgets, and ops tool budgets rather than under one line a single leader can see. A company spending that much per rep with nobody positioned to add up the total has an accounting problem wearing the disguise of an org chart.
How the Split Happened
The separation traces to 1972, when Xerox hired Pat Kelly to build compensation analysis, territory design, and pipeline reporting into a formal discipline. That work became sales operations. In the same building, a training department reporting through HR ran new-hire onboarding and methodology certification, with no connection to what Kelly was building. Ops grew up alongside the rise of the CRM. Training grew up inside Learning and Development. The two functions worked on the same sales force for decades without ever sharing a reporting line.
The word “enablement” started appearing in job titles around 2010, and by 2020 most B2B companies with more than 200 reps had a team carrying it. The function that got the new name kept the same shape it always had: the LMS, the workshop calendar, and the completion tracking, while the data, the dashboards, the comp plans, and the authority over how reps get measured all stayed in ops. The title changed while the reporting line, budget, and data access stayed exactly where they were before the rename.
Why the Split Persists
Four forces keep the two functions apart even after most executives privately agree the current structure produces poor results.
Money and power. Whoever controls the enablement budget today, typically the CHRO through L&D, loses headcount and vendor leverage if the function moves. The same dynamic applies to every executive whose territory a consolidation would cross.
Career risk. Consolidating the two functions pays off over eighteen to thirty-six months, longer than the tenure most CROs can count on. Spending political capital on a restructure that a successor might get credit for is a rational reason to leave the org chart alone.
Professional identity. Most enablement leaders built their careers, networks, and certifications inside the training and L&D community. Reassigning the function to RevOps and measuring it on revenue metrics instead of completion rates asks that community to redefine its own professional identity, which is a slower and more personal change than an org chart edit.
The right time that never arrives. There is always a board meeting, a budget cycle, or a reorg competing for the same attention, and without a CEO or COO deciding a given year is the year, the default wins by inertia.
| Dimension | Split Model (Two Leaders) | Unified Model (One Leader, One System) |
|---|---|---|
| Spend visibility | Scattered across L&D, marketing, and ops budgets; no single total | Tracked under one owner who can see and optimize the full spend |
| Reporting line | One of seven inconsistent homes, varies by company | One line connecting training design to pipeline and forecast data |
| Compensation | 30-40% gap between VP Enablement and VP RevOps at the same level | Comp parity reflecting equal ownership of revenue outcomes |
| Training-to-data loop | Training built without deal data; dashboards built without training context | Training targeted by deal data; dashboards informed by what training changed |
| Vendor market alignment | Two budgets buying from two categories of vendor | One buyer aligned with a vendor market that has already merged the categories |
This argument concerns where the function reports and who owns the data loop connecting training to pipeline results, a separate question from whether sales training and sales enablement describe the same discipline day to day. The reporting-structure problem exists regardless of how a company defines that second distinction.
What a Unified Function Requires
Merging the two functions under one leader is an organizational decision, not a tooling purchase. It requires moving budget lines, changing who owns vendor contracts, and giving one person authority over both the training a rep receives and the data that shows whether it worked. This structural shift, laid out in full in Gap Revenue Performance, is what connects a three-layer performance system, the Skills, Opportunity, and Forecast Layers, into a system a single leader can run end to end.
Building that unified structure inside an existing organization is specific, hands-on work — not a slide deck.
Frequently Asked Questions
What is the difference between sales enablement and revenue operations?
In most B2B companies, sales enablement owns rep training, methodology certification, and content, while revenue operations owns pipeline data, forecasting, and dashboards. Functionally, both feed the same set of decisions about what a rep should do differently and what the business should expect, which is why the vendor market serving both categories has spent the past two years merging into single platforms.
Where does sales enablement typically report in a B2B organization?
There is no consensus. The Sales Enablement Collective’s 2025 Landscape Report found 39.4% reporting into Revenue Operations, 25.4% into Sales, 16.6% directly to the C-suite, 5.2% into Marketing, 3.5% into Product Marketing, 2.6% into HR, and 7.3% into other structures, with no single reporting line used by a majority of companies.
Why did Highspot and Seismic merge?
Highspot and Seismic announced their merger in February 2026, combining two of the largest sales enablement platforms into a single company. The deal followed a broader wave of consolidation between enablement and revenue operations vendors, including MediaFly’s acquisition of Appinium and Clari’s absorption of SalesLoft, as the vendor market concluded that enablement and ops products serve one underlying job rather than two separate ones.
How much does sales enablement spending typically cost per rep?
Forrester’s research on hidden sales-support costs puts the figure at approximately $135,000 per quota-carrying rep per year once every related budget line is counted, spread across L&D, marketing, sales tools, and ops budgets rather than tracked under a single owner.
Is there a pay gap between VP of Sales Enablement and VP of Revenue Operations roles?
Yes. VP of Sales and VP of Revenue Operations both compensate at roughly $333,000 in total annual compensation across a representative sample of US B2B SaaS companies, while VP of Enablement compensates at $190,000 to $267,000 in the same organizations, a 30 to 40 percent gap at comparable seniority.
Should sales enablement report to the CRO or to revenue operations?
The specific title matters less than whether one leader owns both the training a rep receives and the data showing whether that training changed pipeline or win-rate outcomes. Splitting those two halves under separate leaders, regardless of which department each one sits in, is what produces the disconnect between training spend and measurable performance.
0 Comments