Progression from Stage 1 to Stage 2 is gated principally by three capabilities: data architecture, process standardisation, and cross-functional credibility. None is easy; all three are necessary. The transition typically takes 18–24 months of deliberate investment from a competent Stage 1 starting point.

Data architecture

The first gate is data architecture. Stage 1 implementations operate with fragmented data in functional systems — sales uses one set of definitions, marketing another, customer success a third. Reporting becomes politically contested because each function reports from its own system using its own definitions.

Stage 2 requires moving from fragmented data to a centralised revenue data layer. This means a data warehouse architecture, identity resolution across systems, standardised entity definitions, and documented data contracts. The technical work is meaningful but the harder work is the cross-functional negotiation over definitions.

Process standardisation

The second gate is process standardisation. Stage 1 work is ad-hoc and request-driven — every report is built fresh, every cadence is negotiated, every handoff is informal. Stage 2 requires moving to documented, repeatable cadences: standardised forecasting cycle, defined lifecycle handoff processes, formal compensation administration, documented deal desk procedures.

The standardisation work meets predictable resistance. Each function prefers its own way of doing things and treats standardisation as an imposition. The credible argument is that standardisation reduces system-wide friction more than it costs in individual function flexibility — a system-level argument that requires system-level accountability to land.

Cross-functional credibility

The third gate is cross-functional credibility. The RevOps leader and team need to be peer-level partners with the heads of sales, marketing, and customer success — not subordinate service providers or imposed process police.

Credibility is earned through demonstrated competence on problems each function actually cares about, not through declaration. The RevOps team that helps the head of marketing solve attribution problems will have credibility on marketing-sales handoff redesign. The team that helps the head of customer success build NRR forecasting will have credibility on lifecycle programme governance.

Read the full pillar guide
The RevOps Maturity Model →
Related
ArticleStage 1 RevOps: Getting Started
ArticleStage 2 RevOps: Building the Operating System
ArticleWhy RevOps Implementations Stall
DefinitionRevOps Maturity Model
DefinitionRevOps Resources
DefinitionService Provider Deployment Model