Skip to main content

RevOps: what revenue operations is, what it owns, and how to set it up

RevOps, short for revenue operations, is the function that owns the data, process, systems, and reporting behind every team that touches revenue: marketing, sales, and customer success. Instead of three ops teams with three versions of the pipeline, one team owns the CRM, the lead lifecycle, routing, forecasting, and the numbers the board sees.

This is a guide to the function itself. If you are looking for outside help, see RevOps consulting instead.

By Garrett Wolfe, founder of OneGTM. Updated .

Key takeaways

  • RevOps puts marketing ops, sales ops, and CS ops under one owner, so there is one definition of a lead, one pipeline, and one forecast.
  • It owns the CRM data model, lifecycle stages, routing, forecasting, reporting, and the revenue tech stack.
  • Sales ops is a slice of RevOps focused on the sales team: territories, quotas, comp, and deal desk.
  • A startup needs RevOps thinking from the first CRM, and usually a dedicated person somewhere between 10 and 30 reps.
  • The first three things to fix are almost always lifecycle definitions, inbound routing, and one pipeline report everyone trusts.

What RevOps is

Most companies start with ops spread across teams. Marketing ops owns the forms and the MAP, sales ops owns the CRM and the forecast, and CS ops owns renewals in a spreadsheet. Each team defines a lead, an opportunity, and a churned customer a little differently, and the board deck takes a week to reconcile.

Revenue operations fixes that by making one team responsible for the whole path from first touch to renewal. The work does not change much. What changes is that the definitions, systems, and reports are designed together, so a lead created by marketing arrives in sales with the fields sales needs, and a closed deal arrives in CS with the context CS needs.

What RevOps owns

AreaWhat it meansA typical deliverable
CRM and data modelObjects, fields, ownership rules, and data qualityA field dictionary and dedupe rules everyone follows
Lead lifecycleStage definitions from subscriber to customer, with entry and exit rulesOne written lifecycle that marketing and sales both sign off
Routing and speed to leadWho gets which lead, how fast, and what happens if they miss itInbound routed and booked in minutes, with a fallback owner
Pipeline and forecastingOpportunity stages, exit criteria, and the forecast cadenceA weekly forecast call run off the CRM, not a spreadsheet
Reporting and attributionThe numbers leadership and the board useA pipeline report by source and segment that matches finance
Revenue tech stackWhich tools exist, who owns them, and how they connectA stack map with owners, costs, and renewal dates
Territories, quotas, and compUsually shared with sales opsCapacity model and comp plan for next year

RevOps vs. sales ops vs. marketing ops vs. GTM engineering

ScopeMain question
RevOpsMarketing, sales, and CS operations togetherIs the revenue engine measured and run on one set of definitions?
Sales opsThe sales teamDo reps have the territories, quotas, tools, and process to hit the number?
Marketing opsThe marketing teamDo campaigns, forms, scoring, and attribution work?
GTM engineeringThe systems that create pipelineAre we finding, scoring, and reaching the right accounts automatically?

At a seed or Series A company, one person often does all four. The full breakdown of the sales side is in the sales operations guide.

Metrics RevOps tracks

MetricWhat it tells you
Speed to leadMinutes from form fill to first human touch. The cheapest pipeline win most companies have.
Stage conversion ratesWhere deals stall, by segment and source.
Pipeline coverageOpen pipeline divided by the remaining quota for the period.
Win rate and sales cycle lengthHow efficient the sales process is, by segment.
Forecast accuracyHow close the committed number lands to what actually closed.
CAC payback and net revenue retentionWhether growth is efficient, and whether customers expand after they buy.

The RevOps stack

The core is a CRM (Attio, HubSpot, or Salesforce). Around it: lead routing, enrichment, call recording, a BI tool for anything the CRM cannot report, and integrations that keep the sequencer, billing, and product data in sync. Choosing a CRM from scratch? Start with the best CRM for startups.

How to set up RevOps at a startup

  1. Pick one source of truth: One CRM, and a rule that a deal not in it does not exist.
  2. Write the lifecycle: Lead, qualified lead, opportunity, customer, churned. Define how a record enters and leaves each stage.
  3. Fix inbound routing: Enrich every form fill, assign an owner automatically, and let the buyer book a meeting on the spot. The full process is in B2B lead management.
  4. Define opportunity stages: Each stage gets exit criteria a manager can check, not a probability someone typed in.
  5. Build one pipeline report: By source and segment, reviewed weekly, and reconciled with finance monthly.
  6. Review the stack quarterly: Cut tools nobody uses, and check that every integration still writes the fields it should.

When to bring in RevOps help

Hire a full-time RevOps lead when the work is continuous and you can give them a seat at the leadership table. Before that, a part-time operator or a revenue operations agency covers the design and the build. Fractional firms that publish fees are compared in best fractional RevOps firms. I do this work hands-on at OneGTM: the person who scopes it builds it in your CRM, then documents it so your team can run it.

RevOps FAQ

What is RevOps?
RevOps, or revenue operations, is the function that owns the data, process, systems, and reporting behind marketing, sales, and customer success. It puts the three ops teams under one owner so the company runs on one definition of a lead, one pipeline, and one forecast.
What does a revenue operations team do?
It designs and runs the CRM data model, lead lifecycle stages, lead routing, opportunity stages, forecasting, reporting and attribution, and the revenue tech stack, and it usually shares territories, quotas, and comp planning with sales ops.
What is the difference between RevOps and sales ops?
Sales ops supports the sales team: territories, quotas, comp, deal desk, and rep tooling. RevOps covers marketing, sales, and customer success operations together, so sales ops is often a part of RevOps.
When should a startup hire RevOps?
Use RevOps thinking from the first CRM setup. A dedicated hire usually makes sense once there is a sales team of roughly 10 to 30 reps or several revenue teams that need shared definitions. Before that, a part-time operator or RevOps consultant can cover it.
What metrics does RevOps own?
Common ones are speed to lead, stage conversion rates, pipeline coverage, win rate, sales cycle length, forecast accuracy, CAC payback, and net revenue retention.
Is RevOps the same as GTM engineering?
No, though they overlap. RevOps governs the revenue engine: definitions, process, reporting. GTM engineering builds the systems that create pipeline, such as enrichment, scoring, signals, and outbound automation. At small companies one person often does both.

Want RevOps designed and built in your CRM?

Talk to OneGTM about RevOps

Tell me what you're building. I reply the same day.

Call with Garrett

Takes about 20 seconds. Times show up right here, and the call is with Garrett directly. See our privacy policy.

Systems we've built for

Rather do it the old way? team@getaob.com LinkedIn