Three terms. Endless confusion. And if you’re a B2B founder at £1M–£5M ARR trying to figure out what you actually need, the academic debate doesn’t help you much.
So let’s cut through it.
What Sales Ops actually owns
Sales Operations is the function that supports the sales team in doing its job. It’s operational in the truest sense — removing friction from the selling motion.
In practice, that means: territory and quota management, CRM hygiene and administration, sales reporting and dashboards, commission calculation and compensation plan management, tooling (your CRM, your sequencing tool, your diallers), and onboarding and enablement for new sales hires.
The key thing about Sales Ops is that it sits inside the sales org. It reports to the VP Sales or CRO. Its job is to make sellers more effective and give leadership accurate data to manage the team.
At most companies that have a dedicated Sales Ops person, you’re typically looking at 20+ salespeople before it becomes a full-time role. Below that, it gets absorbed into whoever manages the CRM, which is often someone in RevOps, or — let’s be honest — a founder who hates doing it.
What Marketing Ops actually owns
Marketing Operations is the same concept applied to the marketing function. It owns the marketing technology stack (your MAP — marketing automation platform), lead management and scoring, campaign operations, database hygiene, attribution modelling, and reporting on marketing’s contribution to pipeline.
Where Sales Ops is focused on deals and revenue, Marketing Ops is focused on pipeline generation — the machinery that turns awareness into qualified demand. It manages the plumbing between your marketing tools and your CRM: making sure form submissions land in the right place, lead scores trigger the right actions, and the SDR team actually gets the leads marketing is generating.
Good Marketing Ops is invisible. Bad Marketing Ops is why you have 4,000 contacts in HubSpot with no idea where they came from or whether any of them are worth calling.
What RevOps actually owns
Revenue Operations is the unified version of both. It owns the entire revenue-generating process — from the first time a prospect encounters your brand through to renewal and expansion — and it treats that process as a single system rather than a collection of departmental functions.
RevOps looks at pipeline conversion rates across every stage. It manages the handoffs between marketing, sales, and customer success. It owns the tech stack holistically — not just the CRM for sales or the MAP for marketing, but how everything connects and what data flows where. It builds the reporting infrastructure that lets leadership make decisions based on what’s actually happening rather than what people think is happening.
The philosophical shift in RevOps is that it breaks down the traditional handoff model — where marketing throws leads over a wall to sales, who throw customers over a wall to CS — and replaces it with shared accountability for revenue across the whole journey.
Where they overlap (and why it gets confusing)
The confusion between these three terms comes from the fact that at most B2B companies, the functions overlap significantly and the same person often does all three.
If you have a “Sales Ops Manager” at a £3M ARR SaaS company, there’s a reasonable chance they’re also doing the work of Marketing Ops (because nobody else is) and some RevOps-style cross-functional analysis (because someone has to). Their job title just reflects where they sit in the org chart, not the full scope of what they do.
Equally, large enterprises that can afford dedicated Sales Ops and Marketing Ops teams sometimes appoint a RevOps leader above them to drive alignment — in which case RevOps becomes a strategic layer rather than a hands-on function.
The distinctions get academic fast. What matters is less the label and more the answer to a specific question: who in your business owns each of the following?
- CRM structure and data quality
- Lead-to-opportunity conversion and handoff rules
- Sales process definition and stage criteria
- Pipeline reporting and forecast accuracy
- Tech stack decisions and integrations
- Commission and quota administration
- Marketing campaign execution and attribution
If the answer to most of those is “nobody really”, you have an ops problem. If the answer is “three different people who don’t talk to each other”, you have a RevOps problem.
What most B2B businesses at £1M–£5M ARR actually need
At this stage, you almost certainly don’t have the headcount to justify separate Sales Ops, Marketing Ops, and RevOps functions. Nor should you.
What you need is one person or function that owns the revenue system end-to-end — someone who understands how marketing feeds sales, how sales data should be structured, what the CRM should actually contain, and how to build reporting that tells you whether the business is on track or not.
That’s RevOps as a unified function. It’s not three jobs rolled into one person. It’s a different way of thinking about operations — holistically, across the full revenue journey, rather than in departmental silos.
For most founders I work with, the first sign they need this isn’t headcount pressure — it’s when they realise they can’t answer basic questions about their own pipeline. What’s the conversion rate from demo to proposal? How long does the average deal take to close? Which marketing channel generates the best-fit customers, not just the most leads? If you’re guessing, you don’t have a RevOps function — you have a collection of tools and a prayer.
The practical question to ask
Don’t start with the org chart. Start with the gaps.
Ask yourself: where does revenue get lost in my business because nobody owns the process? Is it in lead quality and handoff? Is it in pipeline visibility and forecasting? Is it in post-sale handoff and expansion? Is it in the data — your CRM has records, but you don’t trust what they say?
Those gaps tell you what you actually need. Whether you call it Sales Ops, RevOps, or something else entirely is secondary.
The goal is a revenue system that works — one where you can see what’s happening, trust the data, and make decisions from it. At most B2B businesses at this stage, that starts with getting the foundations right: a properly structured CRM, clean stage definitions, and clear ownership of who does what and when.
If you want to understand what this looks like in practice, my post on what RevOps actually means goes deeper on the function itself. And if you’re trying to figure out whether you need a fractional operator or something more hands-on, the RevOps Consultant page explains how I work with businesses at this stage. For founders who want to explore what’s actually going on in their revenue system, a Discovery Week is usually the right starting point.