What is revenue operations?
Revenue operations (RevOps) is the function responsible for the systems, data, processes and definitions that the entire revenue team relies on. It spans marketing, sales and customer success. Its job is to make sure every team is working from the same data model, the same lifecycle definitions, the same tooling and the same set of reports, so leadership can make decisions on a single source of truth.
The simplest test for whether a company needs RevOps: if marketing, sales and customer success each present a different revenue number in the same meeting, the function is overdue.
Why does revenue operations exist?
RevOps exists because the cost of misaligned definitions, fragmented tooling and inconsistent reporting compounds as a business grows. What works at ten people becomes chaos at fifty. RevOps centralises the rules so growth doesn’t destroy the system, and so that automation and AI have clean data to work with.
What does a revenue operations team own?
A revenue operations team owns the revenue tech stack, the data model that connects marketing, sales and customer success, lifecycle and stage definitions, lead and account routing, forecasting infrastructure, end-to-end reporting and the change-management process for any of the above.
| Domain | RevOps owns | Other teams own |
|---|---|---|
| Tech stack | Selection, integration, governance | Day-to-day use |
| Data model | Definitions, properties, integrity | Data entry |
| Lifecycle | Stage definitions and transitions | Stage management on records |
| Forecasting | Methodology and inputs | Forecast calls |
| Reporting | Dashboards and dataset governance | Interpreting reports |
| Process change | Change-management workflow | Initiating change requests |
How to build a revenue operations function step by step
Building RevOps starts with definitions, not tools. The fastest way to make progress is to align the team on lifecycle stages, then audit the systems against those definitions, then close the gaps.
- Agree shared definitions for lead, MQL, SQL, opportunity, customer and churn. Write them in one document.
- Map current systems and data flows against the definitions. Highlight every place the definitions break.
- Choose a single source of truth per data point. For most growth-stage businesses on HubSpot, that’s the CRM.
- Rebuild lifecycle stage automation in HubSpot so transitions follow the agreed definitions, not opinion.
- Stand up unified reporting tied to those stages so marketing, sales and customer success see the same numbers.
- Operate a single intake process for all change requests so the data model doesn’t drift.
RevOps vs sales operations vs marketing operations
Sales operations and marketing operations are functional. They support one team each. Revenue operations is structural. It owns the shared layer underneath both, plus customer success. In practice, MOps and SalesOps execute inside their teams; RevOps governs the definitions, data and tooling that connect them.
When does a business need revenue operations?
Most B2B businesses need a RevOps function between £3m and £20m in revenue, or once they pass roughly 50 employees with a dedicated sales and marketing team. The trigger is rarely headcount alone; it’s the moment leadership stops trusting the reports. Below that scale a HubSpot partner subscription typically delivers RevOps outcomes faster than an in-house hire.
Project36 delivers RevOps as a managed subscription through Flow™. You get strategy, HubSpot engineering and analytics under one accountable team.
Keep reading