RevOps: what it is, why it's gaining ground, and how to get started tomorrow
In other blogs in this series, we explored why automation projects stall: processes that haven't been cleaned up, data that isn't usable, and teams that don't work together. But there's a deeper cause connecting all these problems: no one owns the whole.
Marketing optimises for leads. Sales optimises for deals. Service optimises for ticket resolution. Each team has its own tools, its own data, and its own KPIs. Customers don't experience a coherent journey, they experience a series of disconnected touchpoints. And when something goes wrong between two departments, everyone is passing the buck.
This ownership problem is exactly why more and more organisations are introducing a new function: RevOps. In this blog, we walk you through what it is and isn't, why it's becoming increasingly important, and how you can start applying it in your organisation tomorrow.
)
)
What is RevOps?
RevOps stands for Revenue Operations. It's a function or a team that owns the entire commercial engine: from first contact to returning customer. RevOps explicitly bridges the gap between commercial departments (marketing, sales, service) and technology. And in doing so, it addresses a gap that traditional organisational structures rarely fill naturally: no one owns the full customer journey.
What RevOps is not: it's not a new name for marketing operations, not an IT function managing tools, not a reporting role building dashboards, and not a project manager for automation programmes.
What RevOps actually is:
Owner of the entire customer journey, not just one phase
Responsible for alignment between teams on definitions, processes, and data
The person who makes the call when marketing and sales disagree on what a lead is
The guardian of a single customer profile shared across all teams, commonly known as the 'Golden Record'
)
From silos to one consistent experience for the customer
For a long time, automation was a single-department project in most organisations: marketing automation sat with marketing, sales automation sat with sales. Each with its own tools, its own priorities, and its own definition of success. That worked, up to a point.
Because customers have never thought in departments. They expect one experience, regardless of who they're speaking to. A customer who calls service expects to be recognised as the same person who received a marketing email last week and spoke to sales last month. That expectation demands a single source of truth about the customer. And a single source of truth demands a single owner.
Ownership is a recurring theme in successful business automation. In the blog 'The PPIT framework: the four factors that determine whether business automation succeeds or fails', we covered this under the P for People. It's not just about the people working with automation, it's about clear roles and responsibilities. One of the most important questions is: who owns the full customer journey? In most organisations, the honest answer is: no one.
That's precisely where RevOps comes in. RevOps takes ownership of the entire commercial chain, ensuring that marketing, sales, and service no longer optimise in isolation, but share responsibility for one customer journey.
What RevOps actually does
RevOps isn't an abstract function. Its responsibilities are concrete and directly tied to the bottlenecks where automation programmes tend to break down.
)
)
A real-world example: from black box to 23% conversion
At a 150-person SaaS organisation, the handover from marketing to sales was a black box. Marketing generated leads, sales was unhappy with the quality, and no one could see what happened in between.
After appointing a RevOps lead, three concrete changes were made:
One shared definition of a SQL
An automated handover with context (not just a name, but behavioural data and a scoring rationale)
A joint weekly pipeline review
The result after six months: lead-to-opportunity conversion rose from 12% to 23%. Not by generating more leads, but by improving alignment between the teams.
)
RevOps and the PPIT framework
RevOps doesn't stand apart from the PPIT framework. Where the framework identifies the four factors that determine whether business automation can succeed, RevOps ensures those factors stay connected in practice. Because RevOps works across departments, it keeps decisions about people, processes, data, and technology connected.
People: RevOps is the executive sponsor or works directly with one. RevOps resolves conflicts between teams.
Process: RevOps owns cross-functional processes such as lead handover and opportunity management.
Information: RevOps owns data governance and the 'Golden Record'.
Technology: RevOps decides on the tech stack in collaboration with IT and the business.
That makes RevOps more than just a new function. It's a way of keeping all four components of the PPIT framework in balance.
This also connects to the automation maturity model. At the highest maturity level, automation is fully integrated across all departments. Reaching that level requires cross-functional ownership, typically in the form of RevOps. Without that owner, level 4 stays out of reach, no matter how much you invest in technology.
How to get started tomorrow, even without a formal RevOps function
You don't need to wait for a formal RevOps function to start adopting a RevOps mindset. The five steps below are things you can act on tomorrow, with the people and resources you already have.
Step 1: Assign ownership explicitly.
Designate someone who is responsible for the full customer journey. Not as a side task, but as a core responsibility. This can be an existing role, such as a Head of Commercial or VP Growth, with an expanded mandate.
Step 2: Bring the three departments together.
Schedule a monthly 'revenue alignment' session with marketing, sales, and service. Discuss where the friction is in handovers, which leads do and don't convert, and what service is hearing from customers that marketing and sales should know.
)
Step 3: Document your definitions.
Write down what a lead is, what an MQL is, what an SQL is, and when an opportunity is created. Make sure all systems use the same definitions. It sounds straightforward, but it's the foundation everything else rests on.
Step 4: Measure end-to-end, not by phase.
Add a metric to your reporting that covers the full journey: for example, the time from first contact to closed deal, or conversion from lead to customer, rather than just lead to MQL.
Step 5: Identify the first bottleneck.
Where do leads disappear? Where does the pipeline stall? Where does sales blame marketing or the other way around? Start there. Not with a large programme, but with one concrete improvement.
)
RevOps isn't a hype: it's a structural fix
Automation programmes stall because no one owns the whole. Not because the technology falls short. Not because the intention isn't there. But because the organisational structure makes it impossible to decide, steer, and improve cross-functionally.
RevOps solves that. And you don't need to wait until you can build a full RevOps team. Start with RevOps thinking: cross-functional, data-driven, customer-first.
Want to explore what ownership and RevOps could look like in your organisation? Get in touch and we'll work through it together.
)
The four factors that determine whether business automation succeeds or fails
Want to know how to apply RevOps thinking in your organisation? Download our whitepaper CTRL+SHIFT: The four factors that determine whether business automation succeeds or fails.
Download the whitepaper