Short answer
RevOps, short for revenue operations, is the function that runs the systems, data and processes behind marketing, sales and customer success as one system instead of three. A RevOps team owns the CRM and sales tools, lead routing, shared definitions of stages and metrics, reporting and the forecast. Its job is to stop revenue leaking at the handoffs between teams and to give leaders one set of numbers they trust.
- RevOps puts sales ops, marketing ops and customer success ops under one owner and one set of definitions.
- Its output is fewer leaks at the handoffs and a forecast leaders believe.
- Start with shared definitions of a lead, an opportunity and each stage; tools come second.
- Most companies need a RevOps owner once marketing, sales and success each run their own systems.
On this page
This page is for founders, sales and marketing leaders deciding whether they need revenue operations, and for people moving into a RevOps role. It defines the term, shows what the function owns, and works through the kind of problem it exists to find.
What revenue operations means
Revenue operations (RevOps, sometimes "revenue ops") is the operational function behind every team that brings in revenue: marketing, sales and customer success, and often finance for billing and forecasting. HubSpot's definition is a function that aligns sales, marketing and customer success around shared data, processes and goals, and it notes that RevOps usually reports to the chief revenue officer.
In practice RevOps owns four things:
- Systems: the CRM, marketing automation, sales engagement and billing tools, and how data moves between them.
- Data: account and contact records, duplicates, field definitions and data quality.
- Process: lead routing, stage definitions, handoffs between teams, territories and quotas.
- Insight: dashboards, funnel reporting and the forecast.
The point of putting these under one owner is that revenue rarely leaks inside a team. It leaks between them: a lead marketing counted that sales never saw, a deal sales closed that onboarding didn't hear about.
RevOps vs sales ops, marketing ops and business ops
| Function | Scope | Typical owner of |
|---|---|---|
| Sales operations | The sales team only | CRM for sales, territories, quotas, commission data, the sales forecast |
| Marketing operations | The marketing team only | Marketing automation, lead scoring, campaign tracking, attribution |
| Customer success operations | Post-sale teams only | Health scores, renewals data, onboarding workflows |
| Revenue operations | All three, end to end | Shared definitions, the full funnel, routing between teams, one forecast |
| Business operations | The whole company | Planning, budgeting and cross-company projects, often beyond revenue |
Many companies build RevOps by merging the first three. Others start with a single RevOps hire and never have separate ops teams at all.
What a RevOps team measures
Salesforce's guide lists the metrics RevOps typically tracks, including customer acquisition cost, annual recurring revenue, churn, renewal rate, customer lifetime value and days sales outstanding. The most useful ones cross a handoff, because no single team owns them:
| Metric | Handoff it checks |
|---|---|
| Lead to first contact time | Marketing to sales |
| Share of leads routed to an owner | Marketing to sales |
| Opportunity to closed won rate by source | Sales, by marketing channel |
| Time from signature to go-live | Sales to customer success |
| Net revenue retention | Customer success back to sales for expansion |
Worked example: finding the leak
Illustrative example. The company and numbers are invented to show the method.
Ridgeway Colo (ridgeway.example) is a data-center colocation provider. Marketing reports 360 quote requests in a quarter. Sales says it received 250. Both are right, and neither team can see why.
The new RevOps manager traces the path. The web form made "racks needed" optional, but the routing rule assigned leads by rack count. Leads without it sat in an unassigned queue: 110 of them.
| Step | Routed leads | Unrouted leads, if worked the same way |
|---|---|---|
| Leads | 250 | 110 |
| Qualified opportunities (40%) | 100 | 44 |
| Closed won (25%) | 25 | 11 |
| Annual contract value at $48,000 each | $1.2M | $528,000 |
The routing gap was costing about $528,000 in annual contract value a quarter, roughly 44% on top of what sales closed. The fix took a day: route leads without a rack count to a default owner, and add an alert when any lead waits more than an hour. No team was negligent. The problem sat between two systems, and nobody owned the space between them until RevOps did.
Start with shared definitions
Before tools, RevOps needs everyone to agree what the words mean. Write them down in one place:
Lead: [who counts, e.g. a person at a company in our ICP who has given contact details] Marketing qualified lead: [the exact criteria, e.g. fit score above X plus a high-intent action] Sales qualified lead: [the criteria sales accepts, and who decides] Opportunity: [created when, e.g. after a discovery call confirms problem, owner and timeline] Stages: [each stage name, with its exit criteria and required fields] Closed won: [signed contract, or signed and paid?] Churn: [contract ended, or usage stopped?] Owner of this sheet: [name, in RevOps] Last reviewed: [date]
The MQL vs SQL guide covers the most argued-over line on that sheet, and the sales pipeline page covers stage definitions and exit criteria.
When you need RevOps
| Your situation | What to do |
|---|---|
| Fewer than about ten people in sales and marketing, one CRM | A founder or an ops-minded rep owns the definitions part time |
| Marketing, sales and success each have their own tools, and numbers disagree | Hire one RevOps owner with authority over all three |
| Several products, segments or regions, with a forecast the board relies on | A RevOps team with systems, analytics and planning roles |
Common mistakes
- Treating RevOps as CRM admin. Field changes without authority over definitions don't fix disputes.
- Buying tools first. A new platform on top of conflicting definitions gives you the same argument with better charts.
- Reporting to one team. RevOps that reports to sales gets asked to grade marketing, and vice versa.
- Measuring inside teams only. The money is in the handoffs, so measure them.
- Dirty account data at the top. If marketing and sales disagree about which companies are targets, every downstream number inherits it. A written ICP fixes that at source, and Bebop can turn one into a list of matching companies with the reason each fits.
A 30-day RevOps audit
- Trace ten recent leads from form to outcome and note every place one stalled.
- Count leads with no owner, and how long the oldest has waited.
- Check that each pipeline stage has written exit criteria and required fields.
- Compare marketing's lead count, sales' lead count and finance's customer count for the same month.
- List every revenue tool, who owns it, and what data it sends where.
Next step: define the stages your pipeline runs on with the sales pipeline guide.
Sources
- What is RevOps? Revenue operations explained, HubSpot, accessed 26 October 2026
- What Is Revenue Operations (RevOps)?, Salesforce, accessed 26 October 2026
- Data Hub: data management software, HubSpot, accessed 26 October 2026
Written by the Bebop team at Blackpearl Group. Last updated .
Questions people ask
What does RevOps stand for?
RevOps stands for revenue operations. It's the function that runs the systems, data and processes behind the teams that bring in revenue, usually marketing, sales and customer success, and sometimes finance. A RevOps team owns the CRM and related tools, shared definitions of leads and stages, lead routing, reporting and the forecast, so every team works from the same numbers.
What is the difference between RevOps and sales ops?
Sales operations supports the sales team alone: its CRM setup, territories, quotas, commissions and forecast. Revenue operations covers the whole path from first marketing touch to renewal, so it also owns marketing and customer success systems and, most importantly, the handoffs between teams. Many companies create RevOps by merging sales ops, marketing ops and customer success ops under one leader.
What does a RevOps manager do?
A RevOps manager keeps the revenue engine's plumbing working. Day to day that means administering the CRM and connected tools, fixing lead routing, maintaining data quality, writing and enforcing stage definitions, building dashboards and supporting the forecast. The most valuable part of the job is finding where leads, deals or customers stall between teams and fixing the process behind it.
What is HubSpot revenue operations?
HubSpot defines revenue operations as a function that aligns sales, marketing and customer success around shared data, processes and goals. For companies running on HubSpot, RevOps work usually means owning the shared CRM: properties, lifecycle stages, workflows, lead routing and reporting across all three teams. HubSpot sells its data management tools as a separate product called Data Hub.
Who does RevOps report to?
Most often the chief revenue officer, which HubSpot describes as the usual reporting line, because the CRO owns marketing, sales and customer success together. Where there's no CRO, RevOps may report to the CEO, COO or CFO. What matters is that it sits above the individual revenue teams, so it can set definitions and fix handoffs without taking one team's side.