RevOps (revenue operations) is the function that runs marketing, sales and customer success as one system instead of three. It owns the parts they share: one CRM and one set of data, one definition of a lead and of each deal stage, one process from first contact to renewal, and one set of revenue numbers everyone reports from. A business needs it when those teams argue about whose numbers are right instead of what to do next.

What does RevOps cover?

Definitions vary in wording, but they agree on four areas:

  • Data. The CRM, the fields in it, who may change them, and how records are cleaned, merged and kept current.
  • Process. The lifecycle stages, the handovers from marketing to sales and from sales to customer success, and what has to be true before a deal moves to the next stage.
  • Tools. Which systems each team uses and how they connect, so nobody types the same fact into three places.
  • Reporting. One pipeline, one forecast and targets that add up across teams.

Gartner put a date on the idea in May 2021. It described organisations starting to align the technology, data and KPIs of sales, marketing and customer success into one view of how revenue is made, and predicted that by 2025, 75% of the highest growth companies in the world would deploy a RevOps model (Gartner press release, 17 May 2021).

How is RevOps different from sales operations?

Sales operations serves the sales team: territories, quotas, the sales pipeline and commission. Marketing operations serves marketing: the automation platform, lead scoring and attribution. Each can do its job well and still optimise for its own team.

The trouble sits between them. A lead that marketing counts as qualified and sales never calls. A renewal date nobody owns. A revenue figure that differs between the board pack and the CRM. RevOps does not replace sales or marketing operations; it owns those joins. Its question is not how sales hits quota, but where revenue leaks between the first touch and the renewal, and who fixes it.

What are the signs a business needs RevOps?

  • Marketing and sales report different numbers for the same month, and meetings open with reconciling them.
  • Nobody can say how many leads became customers last quarter without an export and a spreadsheet.
  • Salespeople keep their real pipeline in a private sheet, because the CRM does not match how they sell.
  • Handovers lose context: the account manager asks the client again what the salesperson already knew.
  • Each team has bought its own tools, and they do not share data.

The last sign is common, and it costs selling time. In Salesforce's State of Sales survey of more than 7,700 sales professionals in 38 countries, published in December 2022, sales teams used an average of 10 tools to close deals, nearly 70% of reps said they were overwhelmed by the number of tools, and reps spent just 28% of their week actually selling (Salesforce, State of Sales, fifth edition). The 2024 edition found non-selling work, such as admin and meeting preparation, still took 70% of reps' time (Salesforce, sales AI statistics 2024). Salesforce sells CRM software, so read its figures as a vendor's survey, but the pattern matches what most sales leaders describe.

When does a business not need RevOps yet?

A founder who sells to a handful of clients, with one person doing both marketing and sales, does not need a RevOps function. One head holds the whole picture. The need appears when that picture splits across people: the first separate marketing hire, a sales team of more than two or three, or a customer success team that owns renewals. That is the moment to write down shared definitions, before each team builds its own.

RevOps does not have to be a department either. In a smaller business it is often one person, or part of one person's role, plus a named owner for the CRM. What matters is that someone is responsible for the joins between teams, and has the authority to change them.

Where should a business start with RevOps?

  1. Agree the definitions. What counts as a lead, a qualified lead, an opportunity and a customer, and what moves a record from one stage to the next. Write them down. Lifecycle logic covers how to set the stages.
  2. Pick one place for the truth. One CRM with an owner, and the other tools feeding it instead of competing with it. That is what data integration does: the inbox, calendar and calls write to the same record.
  3. Clean what is there. Merge duplicates, and fill or retire the fields nobody uses, so the reports mean something.
  4. Build one report everyone uses. Pipeline and revenue from first touch to renewal, from the same data. Data consolidation brings every revenue activity into one model for this.
  5. Then automate. Routing, handovers and reminders, and now AI agents that update records and prepare calls.

The order matters. Automation and AI agents act on whatever data they are given. On top of agreed definitions and one clean record, they give people hours back each week. On top of three systems that disagree, they produce wrong answers faster. Research agents covers what that layer looks like once the foundations are in place.

To see which of these steps your business would start with, the three questions on Build your revenue system point to it.