Revenue Operations (RevOps) is the discipline that designs and maintains how a B2B company generates, qualifies and closes business: the processes, criteria, roles, tools and data that connect marketing, sales and client relationships. It isn't a tool or a renamed department: it's the set of shared rules that makes those teams work as a single chain.
This guide explains what RevOps does, how it differs from Sales Ops and Marketing Ops, three ways to have it, and when it's too early to hire someone to do it full time.
In short
- RevOps governs what no single team governs alone: the definitions, the data and the hand-offs between marketing, sales and client relationships.
- Sales Ops optimises one team; RevOps designs the rules between all of them.
- You can have it as an in-house role, an external service or a designed system. Each model assumes something different.
- The threshold for needing it isn't revenue, it's structure.
What is Revenue Operations?
Revenue Operations is the function that brings together the processes, data, tools and teams involved in generating revenue (marketing, sales and client relationships) under one set of rules.
The reference definitions agree on the essentials:
- Gartner defines it as "a business function that aligns sales, marketing and customer success teams to drive revenue growth" (Gartner, Revenue Operations (RevOps), accessed 12/10/2026).
- Forrester says it "unifies and optimizes data, processes, technology, and talent to better serve the customer lifecycle" (Forrester, The WIIFM of Revenue Operations, accessed 12/10/2026).
What both say without saying it: RevOps isn't a tool. It's a discipline applied to a business so that the tools make sense.
Where does it come from, and why is everyone talking about it?
According to Forrester, the idea began to circulate in the early 2000s, as the way companies buy changed: a B2B buyer reaches sales with much of the decision already made, and the purchase jumps between marketing, sales and service with no regard for the org chart.
What has changed in recent years is that the idea has been formalised. In June 2023 Forrester launched a research service dedicated to RevOps, with its own official definition. Gartner predicted that by 2026, 75% of the highest-growth companies would adopt a RevOps model, up from less than 30% at the time of the forecast.
The underlying reason is simple: when marketing, sales and service measure different things, each team can hit its targets while the company doesn't grow. Someone has to own the rules between them.
What does a RevOps team do?
It works across four areas:
| Area | What it decides |
|---|---|
| Process | What a qualified lead is, how it moves from marketing to sales, what counts as a won or lost opportunity |
| Data and measurement | What is measured at each stage, from which source, who looks at it and what decision it informs |
| Tools | Which CRM, which automations and which integrations, always after the process |
| Team alignment | Roles, owners and shared definitions across marketing, sales and service |
In one line: RevOps owns the shared layer. It doesn't run campaigns or sell; it decides the definitions, the data and the hand-off rules everyone works with.
How is a RevOps team structured?
The four areas above are also the natural way to structure it. In a smaller company, one person covers all four, often alongside another role. As the company grows, each area gets its own owner, and process and data are usually the first to need one, because they're where the arguments between teams start.
What matters more than the shape is where it sits, which the FAQ below covers.
RevOps vs Sales Ops vs Marketing Ops: what's the difference?
Scope. Sales Ops and Marketing Ops optimise how one team executes. RevOps designs and governs what connects them.
| RevOps | Sales Ops | Marketing Ops | |
|---|---|---|---|
| Scope | The whole commercial organisation: marketing, sales and client relationships | The sales team's execution | Campaigns, attribution, marketing technology and inbound lead management |
| Measures | Lifecycle performance, revenue retention, commercial efficiency | Win rate, pipeline velocity, forecast accuracy, quota attainment | Campaign performance and lead contribution |
| Role | Designs and governs processes across teams | Optimises one team | Optimises the marketing engine |
Source for the comparison: HubSpot, RevOps vs. Sales Ops: What's the difference? (updated 2026, accessed 12/10/2026). The Marketing Ops "Measures" row is our own summary.
What is a revenue system, and what is a revenue operating system?
They're what RevOps works on. Three terms worth keeping apart:
- Revenue system: the documented architecture that connects demand generation to closing. It has six components: positioning, demand engine, marketing-to-sales conversion, sales process, measurement and roadmap.
- Revenue operating system: that system put to work, with named owners, a stated review rhythm and metrics tied to decisions. RevOps is the practice; the revenue operating system is what it acts on.
- Revenue blueprint: the document that defines how business is generated, qualified and closed: who does what, in what order, with which tool and with what success criterion at each stage. It's the deliverable, not the result.
A useful rule: buying the platform doesn't create the system. A CRM reflects the process you already have, tidy or not.
What RevOps is not
- It isn't a CRM. The CRM is a tool; RevOps decides which process it supports. Do you need RevOps, or just a better CRM? →
- It isn't an agency. An agency executes; RevOps designs the system in which that execution makes sense.
- It isn't a sales director. Whoever leads the team works within the rules; they can't also design the system they work in without marking their own homework.
- It isn't a tools project. If the process is clear and what fails is the set-up, you need an implementation partner, not RevOps.
Three models: in-house role, external service or designed system
There are three ways to have RevOps, and each one assumes something different about where your problem lies:
| Model | What it is | When it fits | What it assumes | Where it goes wrong |
|---|---|---|---|---|
| In-house role | A person or team on the payroll | There's a defined system to maintain, volume and several commercial teams | That it's already known what needs running | Someone is hired to design and run it at the same time |
| External operations service | A provider runs your CRM, reporting and automations on an ongoing basis | The process is decided and you lack technical capacity | That the rules already exist | It runs a process nobody has decided, quickly |
| Designed system | Where the chain breaks is diagnosed, the system is designed and it's left running in your tools, with your team | You don't know where it breaks, or the problem crosses departments | A team able to execute, and management backing the changes | It's designed without data, which is why it starts with a diagnostic |
They aren't mutually exclusive. Many companies end up combining two: a designed system later maintained by someone in-house, or an external service running on rules that have already been decided. What usually goes wrong is hiring one while expecting what another provides.
At RevOps Studio we work in the third: diagnosis and design of B2B revenue systems. Process first, then the tool that supports it.
When is it too early to hire someone for RevOps full time?
When there's no system to maintain yet. A full-time RevOps person performs by running and improving rules that exist. If the rules don't exist, they spend their first months designing them, without a clear mandate to change how marketing and sales work, and at risk of designing the system they'll later be held to account against.
It isn't the moment either if the company is still looking for product-market fit: at that stage you need to experiment, not document.
The threshold isn't revenue, it's structure. These four signals point to it:
- Nobody can explain with data why you win or lose.
- Selling depends on specific people, and their absence shows in the pipeline.
- Marketing produces activity that sales doesn't recognise as opportunities.
- Improvements get explained again every time, because they were never written into a rule.
With three out of four, before hiring anyone, it's worth knowing where the chain breaks.
A named example: when we ran our own diagnostic at RevOps Studio, opportunities lived in a notes tool and invoicing in another, with no pipeline connecting them. Four pricing structures coexisted, and none was public. Neither was fixed by hiring: both needed rules to be decided.
What people search for, in the UK and Spain
In the UK, "revops" is searched around 720 times a month, "what is revops" around 210 and "revops meaning" around 140. In Spain, "revops" reaches around 260 (Ubersuggest, 12/10/2026). The UK search results for "what is revops" are dominated by software vendors, so most definitions you'll find come with a platform attached.
Two things to keep in mind as you read them. Most RevOps frameworks come from the US market, with large teams and buying cycles that differ from European ones. And a good part of what's offered as RevOps is the implementation of a specific platform. Both can be useful, but neither is the same as deciding the process.
Where should you start?
By finding out where your revenue chain breaks, with your own data. Before hiring anyone, switching CRM or commissioning a project, a figure per stage tells you whether the problem is process, tools or people, and what it costs.
The next guide explains how that's done, stage by stage.
Frequently asked questions
What is RevOps, in one sentence? The discipline that designs and maintains how a company generates, qualifies and closes business: processes, criteria, roles, tools and data.
What's the difference between RevOps and Sales Ops? Sales Ops optimises how the sales team executes. RevOps designs and governs the shared rules between marketing, sales and client relationships.
Who should RevOps report to? Someone above any single team; HubSpot names the CRO, COO or CEO as the usual options. Its job is the rules between teams, so if it reports into one of them, it ends up optimising for that team.
Do I need a CRM to do RevOps? You need a record, but the CRM comes after the process. With a clear process, a well-designed spreadsheet can do to start with.
Is RevOps only for large companies? Large companies tend to have in-house teams. Those that don't yet still need the same thing, shared rules, even if they don't need a full-time person to maintain them.
How long before it shows? It depends on where the bottleneck is. Some rules, like recording lead source and loss reason, take effect within days. Others, like visibility or the offer, mature over quarters.
Before you choose a model, see where your revenue breaks.
Carlos Estrada Fonseca is behind RevOps Studio. He has spent 15 years in B2B business development and revenue across EMEA and Latin America, most recently as SVP Business Development and General Manager at NP Digital Spain, and teaches at ISDI, The Valley and LaLiga Business School. LinkedIn profile