In Brief
- Core Answer: Revenue operations is the function that unifies marketing, sales and customer success under a single data model, one set of definitions, and shared accountability for the revenue number.
- Why It Matters: When each team keeps its own definitions and systems, the same question gets three answers. RevOps exists so that the revenue number means one thing across the business.
- Best For: Leaders at $5M+ businesses deciding whether to build a RevOps function, hire a consultant, or restructure what they already have.
Revenue operations is the function that unifies marketing, sales and customer success under one data model, one set of definitions, and one accountable owner for how revenue is produced and measured.
It exists because of a specific failure. Marketing counts MQLs, sales counts opportunities, finance counts bookings, and none of the three reconcile. Everyone reports growth; nobody can explain the gap. RevOps is the answer to that.
What RevOps Actually Owns
The term is used loosely enough to be unhelpful, so here is the concrete scope.
Area | What RevOps owns | What it does not |
|---|---|---|
Data model | One definition of account, contact, opportunity, stage | The content of individual deals |
Systems | CRM architecture, integrations, data flow | Day-to-day selling in the CRM |
Process | Routing rules, stage criteria, handoffs | Individual rep coaching |
Reporting | Definitions, dashboards, forecast methodology | The forecast commit itself |
Enablement of the system | Making the process usable and adopted | Product or sales training content |
The unifying theme: RevOps owns the machinery, not the selling. When RevOps starts owning quota or deal strategy, it stops being able to referee definitions impartially — which was the reason to create it.
The definitions problem is the whole job
Most RevOps value comes from something unglamorous: making everyone agree what a qualified opportunity is, then enforcing it in the system. Loose stage criteria produce inflated pipeline, inaccurate forecasts and arguments about attribution that cannot be settled with data.
If your organisation cannot answer "what makes stage 3 different from stage 2" in one sentence, that is the first RevOps project, not a dashboard.
How to Structure the Function
Structure follows scale. The common mistake is hiring a senior RevOps leader before there is a system to run, or leaving RevOps inside sales long after it needed independence.
Company stage | Typical shape | Reports to |
|---|---|---|
Under $5M | Part of a sales or marketing ops role | Whoever owns the CRM |
$5M–$20M | First dedicated RevOps hire, generalist | CRO or COO |
$20M–$100M | Small team split by systems / analytics / process | CRO |
$100M+ | Full function, often under a Chief Revenue Officer | CRO or CFO |
Reporting line matters more than headcount. RevOps sitting under sales tends to optimise for sales convenience — looser stage criteria, favourable attribution. An independent line, or a dotted line to finance, keeps the definitions honest.
The accountability question is explored further in the Chief AI Revenue Officer role and revenue operations and growth strategy.
Build, hire, or bring in consulting?
- Build in-house when the process is stable and the problem is ongoing maintenance and reporting.
- Hire a consultant when you need a one-off rebuild — CRM migration, stage redefinition, attribution model — and lack the internal capacity to design it.
- Do both, in that order, if the consultant leaves behind documentation and an internal owner. A rebuild with no owner reverts within two quarters.
The failure pattern with revenue operations consulting is a beautiful new system that nobody maintains. Ask any prospective consultant who owns it on day 91.
The First 90 Days
- Audit the definitions. Write down what each stage means today, in practice, not in theory. The gap is your backlog.
- Fix the data model before the dashboards. Reporting on a broken model produces confident wrong answers.
- Instrument the handoffs. Marketing to sales, sales to customer success. Most leakage happens at boundaries.
- Build one forecast methodology. Not three. Document it.
- Establish attribution. Including channels that produce no click — increasingly a material share of B2B discovery.
Attribution deserves emphasis. If AI answer engines influence a deal and never produce a referral, a last-touch model credits branded search and you underinvest in the thing that actually worked. Tracking revenue impact from AI covers the infrastructure, and AI revenue attribution and ROI the reporting side.
Where Agentic AI Fits
RevOps is unusually well-suited to agentic systems, because much of the work is continuous, rule-bounded and currently done badly by humans out of tedium: data hygiene, routing, stage validation, anomaly detection in the funnel.
What agents should not own is the definitions themselves. An agent enforcing stage criteria is useful; an agent deciding what the criteria should be is a governance failure. The line is covered in human-in-the-loop AI decision governance.
For the operational side, AI lead response automation covers routing and speed-to-lead, and AI-native process redesign covers rebuilding a workflow from the outcome backward rather than automating the existing one.
The role that builds the systems RevOps governs is the GTM engineer; GTM engineering explains what the role builds and when to hire one.
Frequently Asked Questions
What is revenue operations?
The function that unifies marketing, sales and customer success under one data model, one set of definitions and shared accountability for the revenue number. It owns CRM architecture, routing, stage criteria, forecast methodology and attribution.
What does a revenue operations team do?
It owns the machinery of revenue rather than the selling: the data model, systems and integrations, routing rules and stage criteria, reporting definitions and forecast methodology. It does not own quota, deal strategy or rep coaching.
When should a company hire for revenue operations?
Usually between $5M and $20M in revenue, when marketing, sales and customer success have each built their own definitions and the numbers stop reconciling. Below that, it typically sits inside an existing sales or marketing operations role.
Should revenue operations report to sales?
Independence works better. RevOps sitting under sales tends to optimise for sales convenience — looser stage criteria, favourable attribution — which undermines the impartiality that justified creating the function. A CRO, COO or dotted line to finance keeps definitions honest.
Is revenue operations consulting worth it?
For a one-off rebuild — CRM migration, stage redefinition, attribution model — yes, provided the engagement leaves behind documentation and a named internal owner. A rebuilt system with no owner reverts within two quarters.