RevOps

WHAT IT IS RevOps is the discipline of operating revenue as one process rather than three. It owns the shared data model, the definitions of each stage from first touch to renewal, the handoffs between functions, the technology that supports them, and the forecast that the business actually plans against. **Not this:** RevOps is not SalesOps: it owns the end-to-end revenue process across marketing, sales and customer success, rather than the operations of the sales function within it. WHY IT EXISTS Marketing, sales and customer success each optimise their own stage, and the losses concentrate at the boundaries: a lead definition marketing and sales do not share, an opportunity handed over without the context that won it, a renewal risk visible in support data that never reaches the account team. Each function's dashboard can be green while the revenue process leaks. RevOps exists because those seams have owners on both sides and therefore no owner at all. WHEN TO USE IT Adopt it when marketing and sales dispute lead quality, when the forecast is routinely wrong in the same direction, or when churn is discovered at renewal rather than predicted. The structural trigger is having three separate operations functions with three separate systems of record. WHO OWNS IT A RevOps function owns the end-to-end process, the shared definitions and the systems that span functions. Functional leaders own performance within their stage. Finance owns the revenue recognition and must agree the definitions, or the company runs two sets of numbers. Critically, RevOps needs a mandate above any single function — a RevOps team reporting into sales will optimise for sales, which is how it ends up as /salesops with a broader title. WHAT GOOD LOOKS LIKE One data model spans the lifecycle, with stage definitions written down and agreed by every function they affect. Handoffs carry context, and both sides can see what happened after the handoff. The forecast has a documented methodology, its accuracy is measured against outcomes, and it improves. Customer health signals flow from support and product usage into the account teams before renewal. The technology stack is consolidated enough that the same customer is one record. HOW TO IMPLEMENT Agree the stage definitions first and get finance to sign them, because every subsequent measurement depends on them. Instrument the handoffs and measure what is lost — conversion by stage, time in stage, and how often a handed-over record is complete. Establish forecast methodology and start scoring its accuracy immediately, since an unscored forecast never improves. Consolidate systems only where the duplication is actually causing the loss; a large migration undertaken before the definitions are agreed moves the problem. The reporting consistency this depends on is /analyticsops work. HOW TO ASSESS YOURSELF Ask marketing and sales to define a qualified lead separately and compare. Score the last four forecasts against outcomes. Ask how a renewal risk becomes visible and how long before renewal. Take the scored self-assessment at /assess and sequence the gaps with /roadmaps.