Revenue operations
Also known as: RevOps
Revenue operations is the function that aligns marketing, sales and customer success on one set of data, one set of definitions and one process for moving a lead to a paying, renewing customer.
Before revenue operations exists as a named function, marketing, sales and customer success usually run their own tools, their own reports and their own definition of a lead. Revenue operations exists to close that gap: one pipeline definition, one source of truth for the numbers, and one team responsible for the handoffs between the three groups.
Example
Picture a company where marketing counts a lead the moment a form is submitted, sales counts it once a call is booked, and finance only sees a number once a contract is signed. Three monthly reports show three different totals for the same period, and every leadership meeting starts with an argument about whose number is right. A revenue operations lead sits down with all three teams, agrees on one definition for each stage, and rebuilds the reports from that single definition. The argument about whose number is right disappears within one reporting cycle, because there is only one number left to look at.
How to use it
Give revenue operations ownership of the CRM, the reporting layer and the service level agreements between teams, not just a dashboard to maintain. The function works best when it reports to a leader who can enforce a decision across marketing, sales and customer success, since without that authority, RevOps becomes a group that documents disagreements instead of resolving them.
Start with the handoffs, not the tools. Map where a lead or an account moves from one team to another, fix the definition at each handoff point, and only then decide which software should enforce it.
Common mistakes
A frequent mistake is treating revenue operations as a rebrand of the sales operations team, which leaves marketing and customer success data out of the picture entirely. Another is buying a new CRM before agreeing on shared definitions, which just moves the same disagreement into more expensive software. A third is measuring RevOps by activity, such as reports produced, instead of by outcomes like pipeline accuracy or the speed of handoffs between teams.
Revenue operations depends on a working marketing and sales SLA to keep the handoff between those two teams from drifting back into disagreement.