The History of Revenue Operations

By Victor Hoang · Updated Oct 24, 2026

Picture a software company around 2012, where marketing runs its own system and reports leads. Sales runs the customer relationship management system, or CRM, and reports pipeline. Customer success keeps a spreadsheet of renewals. Each team has an operations person, and each has a different count of "customers."

Revenue operations, or RevOps, is a young name for an old problem. The label was in use in a few places by 2015. A cross-functional version of it shows up in March 2017. The research firm SiriusDecisions turned it into a codified model in 2019. The throughline: every time a company split its revenue work into specialist departments, someone had to build a back office to keep them in step, and RevOps is the latest attempt to make that back office one team.

Ask that company's CEO a simple question about revenue, and it takes three people a week to answer. That scene, repeated in thousands of companies, is what RevOps was invented to end.

Timeline at a Glance

The Ledger Years (c. 1900 BCE-1920s)

Merchants and managers learn to run revenue at a distance

The scene is a trading quarter in central Anatolia, almost four thousand years ago. Merchants from the city of Ashur work from a karum at Kanesh, buying and selling tin and textiles. Livius reports that more than 23,000 clay tablets from some seventy archives have been excavated there, mostly dated about 1950 to 1840 BCE. They cover loans, the costs of a caravan, wills and divorce acts. A firm in one city was tracking money and promises in another, and it did it with written records.

Skip ahead to medieval Italy. Francesco Datini, born around 1335, returned to Prato in 1382 and built a holding company of limited companies in Avignon, Florence, Pisa, Genoa, Barcelona, Valencia and Palma de Mallorca. His archive holds about 150,000 letters, dated from 1361 to 1411. The pattern is already familiar to anyone in operations: separate offices, one owner, and a lot of effort spent making sure everyone describes the same business the same way.

Keep precursor and concept apart. Neither the Ashur merchants nor Datini had a revenue operations team. They had record-keeping, and they had the problem every later firm inherited: you cannot manage what you cannot see. The word "revenue operations" is not part of this story. The function, as a coordination problem, is.

The modern managerial version arrived with the railroads and the large firms that followed them. Alfred Chandler's The Visible Hand (Harvard University Press, 1977) is the standard account of how salaried managers, not just markets, came to coordinate big American enterprises in the late 1800s and early 1900s. Selling and distribution were part of that story. In 1912, A. W. Shaw published "Some Problems in Market Distribution" in the Quarterly Journal of Economics (volume 26, pages 703-765), one of the early academic efforts to treat distribution as a set of business functions you could analyze. For the field side of that world, see the history of traveling salesmen and the history of sales quotas and territories.

What this era left unsolved was the middle: managers could see their own function, but nobody owned the seam between functions.

For teams today: RevOps is not a new idea about money. It is a very old idea about keeping records that every department agrees on.

The Back-Office Years (1970s-1990s)

Sales ops grows up inside the sales department, and the phrase appears elsewhere

By the late twentieth century, a sales force needed more than good reps. It needed territories, quotas, forecasts and reports. Practitioner writing often traces the first dedicated sales operations department to Xerox in the 1970s, built to take administrative work off sales managers. No dated primary record of that department is cited in those accounts, so treat the Xerox story as industry lore and not as established history. What is documented is the logic: someone has to design territories and count the numbers, and that someone should not be a person with a quota. How that work became a function of its own is told in the history of sales operations. The roots of that logic are in the history of sales quotas and territories and the history of sales commission.

Here is where a careful reading of the record helps. The Journal of Revenue Operations, in its history of the term, catalogs early uses of the exact words "revenue operations" and finds that they meant something else. A 1970 Nebraska state job classification used "Revenue Operations Supervisor" for government revenue administration, and a 1971 US transportation report used the phrase for fare-paying transit service. Same words, different job. It is a good reminder not to date a function by the first time its name appears.

The rest of the picture was marketing. Marketing ran on campaigns, agencies and trade shows, and its reporting stopped at the lead. Sales ran on pipeline. The two groups used different vocabularies and different systems, and neither owned the handoff. That gap is the one the funnel model tried to close, a story told in the history of the sales funnel.

What the back-office era created was a quiet divide: sales operations on one side, marketing on the other, finance and customer service on a third.

For teams today: a function that serves one team will optimize for that team. If your operations people sit inside departments, their incentives point inward.

The Software Funnel (1999-2012)

Cloud tools give each department its own system and its own numbers

The turning point is a browser. Salesforce was incorporated in Delaware in February 1999 to deliver customer relationship management as a service. Its June 22, 2004 prospectus shows how fast the shift happened: about 9,800 customers and more than 147,000 paying subscriptions in about 65 countries as of April 30, 2004. Sales teams now had a shared system of record, and sales operations had a platform to administer. The earlier technology story is in the history of CRM.

Marketing followed with its own stack. Marketo was incorporated in California in January 2006, and its 2013 prospectus is explicit about the ambition. It says marketers are becoming "central catalysts for revenue growth," and it describes analytics that measure the revenue impact of marketing activities. It also lists integrations with Salesforce and Microsoft Dynamics so that marketing, sales and service people can work together. Each department now had a tool, and someone to run the tool. Marketing operations became a job, next to sales operations.

The most influential attempt to connect the departments before RevOps was a model, not a role. SiriusDecisions' Demand Waterfall, which Forrester describes as a family of models that was updated in 2017 with a new "Demand Unit Waterfall" unveiled by Kerry Cunningham and Terry Flaherty, was built to foster alignment between marketing and sales over the stages between a name and a deal. The date of the original waterfall varies from one account to another, so this article does not assign one. For the mechanics, see the demand waterfall.

What the software era created was a data problem. Two systems, two definitions of a lead, and two teams that could each be right and still disagree.

For teams today: a shared tool is not a shared definition. Agree on the stages before you agree on the software.

The Naming (2013-2018)

Ops people notice they are solving the same problem, and a label appears

By the mid-2010s, the operations staff in each department were the ones feeling the pain. The Journal of Revenue Operations reports that "Rev Ops" shows up in a 2015 SEC exhibit from Viggle, where it described advertising campaign management and reporting, and in a 2014 Pandora offer letter for an executive of revenue operations in an advertising setting. The abbreviation existed. The cross-functional meaning had not yet arrived.

The same history locates the first secure public statement of the modern idea in 2017. It reports a March 2, 2017 Radius article, "The Rise of Revenue Ops," preserved in a web archive on March 23, and a Radius white paper, listed on MarTech on April 11, 2017, argues that operations professionals are central to scalable growth and presents Revenue Ops as a model for that. The Journal also reports that Scott Vaughan argued for merging sales and marketing operations in March 2017 without using the label, that LeanData published "Sales Ops + Marketing Ops = Revenue Ops" on May 2, 2017, citing Radius, and that Marko Savic and FunnelCake published "The RevOps Framework" in May 2017, adding customer success to the triad.

Who coined it? The record does not give one answer. Some guides credit an individual in 2016, but the careful histories decline to name a single inventor, and the dated artifacts point to several companies using the phrase at nearly the same time. The honest statement is that RevOps was named by practitioners in several places between 2015 and 2017 and spread through vendor and community content.

Spread was quick. The Journal reports a March 2018 SendGrid incentive plan in which RevOps co-administers payouts with financial operations, and a July 2018 LeanData survey in which 21 percent of respondents already had a RevOps team and 15 percent were building one. That survey is a vendor poll with sampling limits, not an estimate of all companies. Meanwhile, SiriusDecisions, described by Forrester as a leading B2B research and advisory firm, was agreed to be acquired for $245 million in cash on November 27, 2018.

What this era created was a label with no standard. Every company that said "RevOps" meant something slightly different.

For teams today: a name starts a conversation, not a structure. If your RevOps team has no charter, it is a rebrand.

The Charter and the Mainstream (2019-present)

Research firms codify it, job boards count it, scholars catch up

The turning point is an acquisition and a document. Forrester completed its purchase of SiriusDecisions on January 3, 2019. On April 17, 2019, Kate Pierpont wrote on Forrester's blog that revenue operations "integrates the operational work of sales, marketing and customer success", previewing a Summit 2019 keynote, "Revenue Operations: Now Is the Time," by Dana Therrien and Kerry Cunningham. The post describes a revenue operations charter: a shared set of operating principles that aligns planning, processes, systems, data and measurement across sales operations, marketing operations, sales enablement and customer success. It also warns that companies that reorganize without fixing the root causes of misalignment are likely to fail.

On November 4, 2019, a Forrester post co-authored by Scott McLeod announced three RevOps roadshow events, in Palo Alto, Atlanta and Boston, and said revenue operations was "increasingly being established and defined." For what a charter contains in practice, read the RevOps charter.

The job market caught up next. Fortune reported on January 23, 2023 that, in LinkedIn's list built from job titles posted from 2018 to 2022, Head of Revenue Operations ranked first among fast-growing roles, a mid-level job needing a median of five to six years of experience. Academics came last. The Journal of Revenue Operations reports that the earliest dedicated academic treatment it located is a 2021 master's thesis, followed by practice papers and interview studies from 2022 onward. In other words, the practice ran years ahead of the research.

What it left open is the old problem in a new form: a RevOps team can become one more silo. The structure question is covered in centralized vs embedded RevOps.

For teams today: the question is not whether to have RevOps. It is what the team owns, who it reports to, and which numbers it is allowed to settle.

Key People

Key Facts

• Merchants from Ashur left more than 23,000 tablets at Kanesh, mostly dated about 1950 to 1840 BCE.
• Salesforce's June 22, 2004 prospectus reports about 9,800 customers as of April 30, 2004.
• Marketo was incorporated in California in January 2006.
• Forrester agreed to buy SiriusDecisions for $245 million in cash on November 27, 2018 and completed the deal on January 3, 2019.
• Forrester defined revenue operations on April 17, 2019 as integrating the operational work of sales, marketing and customer success.
• Fortune reported in January 2023 that Head of Revenue Operations topped LinkedIn's list of fast-growing roles built from 2018 to 2022 postings.

The Pattern Behind the History

Our synthesis, not published research. Call it Split, Bridge, Charter:

• Specialize. Each time revenue work grew, firms split it into functions with their own staff, from Datini's offices to the sales and marketing departments of the cloud era.
• Count separately. Each function builds its own records and definitions, and the same customer is counted several ways.
• Bridge with a model. A shared model, such as the Demand Waterfall, comes before a shared team.
• Name the bridge. Practitioners across several companies reach for a label, and RevOps appears between 2015 and 2017.
• Write a charter or fade. The label sticks only where the team has agreed principles, owned systems and settled numbers.

What It Teaches Teams Today

• Own the seams. The value of RevOps is at the handoffs between marketing, sales and customer success, not inside any one of them.
• Fix definitions before tools. Agree what a lead, an opportunity and a customer are.
• Write the charter first. A team without agreed principles is a department with a new title.
• Be wary of origin stories. Dated records beat lore, so treat the Xerox legend and single-inventor claims as unproven.
• Keep it close to the buyer. The test of any ops team is whether the customer sees one company.

To see where RevOps sits in the larger story, read the history of sales. For the concept itself, read what is revenue operations, RevOps as alignment glue and the sales operations model.