Sales operations vs revenue operations: when to merge them
Sales operations vs revenue operations — what is the actual difference?
Short answer: Sales Operations supports the sales team. Revenue Operations supports the whole revenue motion — marketing, sales, and customer success — as a single system. Sales Ops is tactical; RevOps is strategic. Sales Ops reports into a VP of Sales; RevOps reports into a CRO or COO.
If you have ever sat in a meeting where the marketing leader and the sales leader were both confident the pipeline number was correct but disagreed by 40%, you have lived through the problem RevOps was invented to solve.
TL;DR — Sales Ops vs RevOps at a glance
| Dimension | Sales Ops | RevOps |
|---|---|---|
| Scope | Sales team only | Marketing + sales + CS |
| Reports to | VP of Sales | CRO or COO |
| Primary KPI | Sales productivity | Revenue efficiency (CAC, NRR, LTV) |
| Owns CRM | Yes | Yes — plus marketing automation + CS platform |
| Forecasting | Sales pipeline | Full revenue forecast |
| Tooling decisions | Sales stack | Full GTM stack |
| Team size at £10M ARR | 1–2 | 2–4 |
| Typical first hire | Sales Ops analyst | RevOps generalist |
The fastest mental model: Sales Ops makes the sales team run. RevOps makes the company run from a customer-acquisition standpoint.
What Sales Operations actually does
Sales Operations is the older of the two functions. It has existed since enterprise software companies in the 1990s realised that AEs were spending 40% of their week on admin and the CFO wanted to know why.
A Sales Ops team owns:
- CRM administration. Stages, fields, permissions, validation rules, data quality.
- Sales reporting. Pipeline dashboards, activity reports, rep scorecards.
- Forecasting cadence. Building and running the weekly forecast meeting.
- Quota and territory planning. How quotas are set, how territories are carved.
- Comp plan administration. Calculating commissions, handling disputes.
- Sales tooling. Choosing, configuring, and supporting the sales stack.
- Sales process documentation. Maintaining the playbook.
- Onboarding ops. Getting new reps set up with tools, access, and training schedules.
In a 20-person sales team, Sales Ops is typically 1–2 people. In a 100-person sales team, it can be 5–8.
What Sales Ops does not own (in a clean org): marketing automation, lead routing logic above the SDR layer, customer success platform, churn forecasting, board-level revenue reporting. Those are RevOps territory.
What Revenue Operations actually does
RevOps emerged around 2018–2020 as a response to a structural problem: every modern B2B company has marketing, sales, and customer success as three separate functions, each with their own tools, their own data, and their own definition of "a qualified opportunity." When those definitions disagree, the company cannot forecast, cannot diagnose leaks, and cannot optimise spend.
RevOps owns:
- The full GTM tech stack. CRM + marketing automation + CS platform + data warehouse, integrated.
- Lead-to-revenue data model. A single definition of "lead", "MQL", "SQL", "opportunity", "customer", "churned" — used identically across marketing, sales, and CS.
- End-to-end funnel reporting. From first touch to renewal, the same numbers everywhere.
- Revenue forecasting. Pipeline + retention + expansion + churn, modelled together.
- Attribution. Which channels actually produced revenue, not just leads.
- GTM strategy support. Pricing analysis, segment-level profitability, win/loss synthesis.
- Cross-functional process design. Lead handoff, expansion handoff, renewal motion.
At £10M ARR with a healthy GTM motion, a RevOps team is typically 2–4 people: one leader, one analyst, one ops generalist, sometimes one specialist (often around data engineering or systems integration).
The decision matrix — Sales Ops, RevOps, or both?
| Stage | Revenue | Recommendation |
|---|---|---|
| Pre-product-market-fit | <£500K ARR | Neither. Founder runs ops. |
| Early scale | £500K – £2M ARR | Part-time Sales Ops (10–15 hrs/week, often fractional) |
| Sales-led growth | £2M – £10M ARR | 1–2 Sales Ops in-house. RevOps emerging. |
| Multi-channel growth | £10M – £30M ARR | RevOps as the umbrella, Sales Ops as a sub-function. |
| Scale | £30M+ ARR | Full RevOps team, with embedded Sales Ops, Marketing Ops, CS Ops |
This is the modal path. There are sensible exceptions — a product-led company at £5M ARR might need RevOps before Sales Ops because the volume of self-serve data dwarfs the sales-led pipeline. A pure outbound consultancy at £5M ARR might never need RevOps at all because there is no marketing motion to integrate.
When (and how) to merge the two
Most companies arrive at this question between £8M and £15M ARR. The pattern that works:
Trigger signals that it is time to merge into RevOps:
- Marketing and sales disagree on pipeline numbers more than once a quarter.
- Customer success has its own renewal forecast that does not reconcile with the sales forecast.
- The data warehouse is being built but no single team owns the GTM data model.
- The founder is asked for a unified revenue forecast and has to assemble it manually from three spreadsheets.
- Win/loss insights are not flowing back into marketing campaign decisions.
When you see three or more of these, it is time.
How the merge usually works:
- Promote or hire the RevOps leader first. This is typically a Director or VP RevOps. They report to the CRO or COO (not the VP of Sales).
- Sales Ops becomes a sub-team under RevOps. Same people, same scope, different reporting line. This frequently causes friction with the VP of Sales — be ready for it.
- Marketing Ops and CS Ops absorb into RevOps over the next 6–12 months. Usually with the existing people in those roles, not new hires.
- The GTM data model gets defined as the first RevOps deliverable. Until this exists, nothing else works.
- A single revenue dashboard replaces three separate ones. The new dashboard becomes the source of truth in every leadership meeting.
The mistake to avoid: do not rename Sales Ops to "RevOps" and call it done. The scope has to genuinely expand. If the function still only services the sales team, it is still Sales Ops with a new title.
The org chart implications
The reporting line is the part that causes the most political tension, so it deserves its own section.
| Org pattern | Sales leader reaction | When it works |
|---|---|---|
| Sales Ops reports to VP Sales | Happy | Pre-RevOps |
| RevOps reports to VP Sales | Frustrated marketing + CS | Rarely works long-term |
| RevOps reports to CRO | Generally accepted | Most common modern pattern |
| RevOps reports to COO / CFO | Sales sometimes feels under-served | Works when CRO is weak or absent |
| RevOps reports to CEO | Strategic but expensive politically | Only at early stage |
The "RevOps reports to CRO" pattern is the default for a reason — it puts revenue accountability and revenue operations under the same person, while still giving RevOps reach into marketing and CS through cross-functional authority.
If your company does not have a CRO yet (most companies under £15M ARR do not), the next-best home is the COO or the founder/CEO directly.
The hiring sequence
If you are building from zero, the order matters:
| Hire # | Role | When |
|---|---|---|
| 1 | Sales Ops generalist | £1–2M ARR, when CRM hygiene becomes painful |
| 2 | Marketing Ops specialist | When MAP (HubSpot/Marketo) configuration outgrows the marketing manager |
| 3 | RevOps leader | £8–12M ARR, when you need cross-functional reporting |
| 4 | RevOps analyst | When the leader spends >30% of their time on reporting work |
| 5 | CS Ops | When CS hits 5+ CSMs and renewal forecasting becomes its own job |
| 6 | Data engineer (RevOps-aligned) | When the warehouse becomes the source of truth |
Compressing this sequence — for example, hiring a £150K RevOps Director at £3M ARR — usually backfires. The role is over-spec'd for the work available, the person gets bored, and the team loses them within a year.
The skill differences
This matters when you are interviewing.
A great Sales Ops hire looks like:
- Strong CRM admin (Salesforce Admin certified, or HubSpot Ops Hub certified).
- Excel/Sheets fluency for ad-hoc analysis.
- Patient with reps; understands sales motion from the inside.
- Often a former SDR or junior AE.
- Detail-orientated, process-oriented.
A great RevOps hire looks like:
- Strategic — can model a business case, not just clean data.
- SQL-fluent. Probably built a dashboard in Looker, Hex, or Metabase.
- Has worked across marketing, sales, and CS in some capacity.
- Often a former consultant (MBB, Big 4), a former founder, or someone who graduated from Sales Ops by demonstrably operating cross-functionally.
- Strong written communication — RevOps produces a lot of memos.
If you hire a great Sales Ops person and ask them to do RevOps work, they often struggle with the strategic and cross-functional dimensions. If you hire a great RevOps person and ask them to do Sales Ops work, they often get frustrated by the tactical depth. Both can be developed in either direction, but the starting skill set matters.
The data model is the actual deliverable
Behind all the org design discussion, the substance of the work is this: every modern B2B company runs on a data model that connects marketing, sales, and CS. That model has roughly the following shape:
| Entity | Owned by | Key fields |
|---|---|---|
| Account | Sales | Industry, employee count, revenue, ICP fit score |
| Contact | Marketing + Sales | Role, decision-making power, engagement history |
| Lead | Marketing | Source, campaign, qualification status |
| Opportunity | Sales | Stage, amount, close date, primary contact |
| Customer | CS | Health score, ARR, contract end date |
| Renewal opportunity | Sales + CS | Up-for-renewal date, expansion potential |
In a Sales-Ops-only world, only Account, Contact, and Opportunity live in the CRM cleanly. Lead is fuzzy, Customer is somewhere else (often a CS platform like Gainsight or Vitally), Renewal is in a spreadsheet.
In a RevOps world, all six entities live in a shared model, with a single ID that links them across systems. That is what enables end-to-end reporting — and that data work is the bulk of what a RevOps team actually produces in its first year.
For UAE & KSA teams
Most B2B service firms in the Gulf running £500K–£5M ARR (our exact ICP) are at the Sales Ops stage, not the RevOps stage. A few region-specific notes:
Hiring market for Sales Ops vs RevOps. Dubai and Riyadh both have a healthy junior Sales Ops talent pool, drawn largely from former SDRs and BDRs at regional SaaS companies (Property Finder, Bayut, Foodics, Tabby). RevOps-grade talent is much rarer locally and frequently means hiring remote (often from the UK, Egypt, or India) or upskilling a strong Sales Ops person over 12–18 months.
Government and enterprise procurement data. A Saudi or UAE company selling into government has a parallel data layer that does not exist in a standard CRM — vendor registration, tender tracking, technical evaluation status. Local Sales Ops people understand this intuitively; remote-hired RevOps generalists often do not. If you hire RevOps remotely, give them a procurement orientation in the first month.
Arabic-language reporting. Most CRM dashboards default to English. For executive consumption in Saudi family offices and Emirati government adjacent businesses, an Arabic-language summary alongside the English dashboard goes a long way. This is a small Sales Ops task that disproportionately affects perceived professionalism.
Friday-Sunday weeks. The reporting week ends Thursday in KSA and Friday or Saturday in UAE depending on the company. Default CRM dashboards built on a Monday-Sunday week miscount everything. Configure week boundaries explicitly — a 30-minute fix that nobody outside the region thinks about.
Cross-border deal complexity. A B2B firm with offices in both Riyadh and Dubai often has deals that touch both legal entities, both VAT regimes, and both banking systems. The CRM data model needs to handle this — a single "Account" with two "Sub-Accounts" or "Legal Entity" picklists is the usual shape. This is genuinely Ops work, not strategy work.
What MAVEN does about it
For the £500K–£5M ARR firms we work with, the answer is almost always "you do not need RevOps yet — you need a working sales process with light Sales Ops support." Our Sales Process Program bundles the 1-FTE-equivalent of Sales Ops work into the 90-day install and the Fractional VP Retainer afterwards.
When a client outgrows that — usually around £6–8M ARR — we help them hire their first RevOps leader and structure the function. The Sales OS Blueprint covers the architecture transition in detail.
If you are not sure where you are on this curve, a virtual coffee is the cheapest diagnostic — 30 minutes, we ask about your current state and tell you whether the right next hire is a Sales Ops generalist, a RevOps leader, or neither.
Frequently asked
Can one person do both Sales Ops and RevOps?
Up to about £5M ARR, yes — and it is usually called "Head of RevOps" with Sales-Ops-shaped work. Above that, the two functions diverge enough that one person cannot keep up.
Should RevOps own the data warehouse?
Sort of. RevOps should own the GTM data inside the warehouse. The warehouse itself usually sits under engineering or data. The cleanest pattern is shared ownership: data engineering owns the pipes; RevOps owns the GTM tables.
Does RevOps own pricing?
Usually no. Pricing sits in product or finance, with RevOps providing the data and the modelling support. RevOps owning pricing is a sign of a weak finance function or a very strategic RevOps leader.
What does a fractional RevOps engagement look like?
For companies in the £2–10M ARR band, fractional RevOps (1–2 days/week) is a real option. The fractional operator builds the data model, sets up the reporting, hires the first in-house Sales Ops, and exits in 9–12 months. MAVEN does the equivalent on the Sales side; for pure RevOps fractional work, we refer to a few trusted partners.
Is "GTM Ops" a third thing now?
Some companies use GTM Ops as a synonym for RevOps. Others use it as an umbrella above RevOps. There is no industry consensus. Pick the term that suits your company and be consistent.
Where does sales enablement fit?
Sales Enablement is its own function, typically a peer of Sales Ops, both reporting into the VP of Sales (or both into RevOps in a mature org). Enablement owns content, training, and certification; Ops owns systems, data, and process.
Post 5 of 10 in our outbound + sales OS series.
Related reading
Level Up Your Sales Career
Join The Sales Development Society — weekly live coaching, proven templates, and a community of ambitious B2B salespeople going from entry-level to enterprise.
Join the CommunityReady to install your sales engine?
Book a 30-minute Virtual Coffee. No deck, no pitch — just an honest read of where you are.
Book a Virtual Coffee