The four specialisations
Strategy and analytics: forecasting, planning, segmentation, territory design, pricing analytics, revenue intelligence. Backgrounds: consulting, FP&A, business intelligence, strategy. The function that turns data into decisions.
Systems and data: CRM administration, marketing automation, customer success platform, data warehouse and ETL, system integrations, data quality. Backgrounds: revenue tech engineering, business systems, data engineering. The function that runs the infrastructure.
Process and programme management: cadence ownership, deal desk, compensation administration, lifecycle programme management, operational support. Backgrounds: operations, programme management, consulting. The function that runs the operating system.
Enablement and capability building: training curricula, onboarding, documentation, certification programmes, field readiness. Backgrounds: learning and development, sales enablement, customer education. The function that builds human capability.
The common imbalance
Most RevOps implementations over-invest in systems-and-data and strategy-and-analytics and under-invest in process-and-programmes and especially enablement. The empirical enablement deficit traces directly to this hiring imbalance.
The imbalance is structural rather than incidental. Analytical and technical talent is easier to hire (well-defined skill sets, larger talent pools, clearer interview signals). Enablement talent is harder to hire (less defined skill sets, smaller talent pools, harder to evaluate for impact). And enablement impact is harder to measure than systems impact, which depresses internal investment.
Closing the imbalance
Three actions help close the imbalance. First, set explicit headcount targets for each specialisation rather than letting team composition drift toward what's easy to hire. Second, evaluate enablement candidates by demonstrated impact (time-to-productivity for past hires, certification programme outcomes) rather than by activity. Third, tie compensation and performance review for the RevOps leader to balanced team composition, not just operational delivery.
The C-Suite playbook covers the executive-level governance design that supports this.