The complete guide to revenue operations (RevOps)

This guide is for founders, CROs and finance leaders at B2B SaaS companies who are deciding whether to build a revenue operations (RevOps) function, and for the first RevOps hire who has to make the job real. It covers the function and the team: what RevOps owns, when to hire for it, where it reports, which numbers it is accountable for and how it runs week to week.

After reading, you should be able to decide when to make your first RevOps hire, what to put in that person’s charter, which metric definitions to write down first, and how the team should grow with the company. We also cover pay, sourced from public salary data, and a first 90 days plan.

It is not a guide to software, and it is not for self-serve companies with no sales team, whose “RevOps” is usually product analytics and billing.

Summary

• RevOps is one owner for the plans, processes, data, systems and definitions that sit across marketing, sales and customer success.
• It differs from sales ops, marketing ops and CS ops in scope, not in skill: the same work, done once for the whole funnel instead of three times.
• Hire the first RevOps person when nobody can explain why two reports show different pipeline numbers. That usually happens around the first sales manager.
• Write definitions before dashboards: lifecycle stages, opportunity stages, forecast categories and how you calculate retention.
• Retention and payback metrics have no single standard. Public companies define them in their own words, so you must too.
• Run a fixed cadence: weekly pipeline review, monthly business review, quarterly planning.
• Pay is closer to sales leadership than to analytics at the senior end. Budget accordingly.

1. What RevOps is, and how it differs from sales, marketing and CS ops

Revenue operations is the function that owns the operating system of a company’s revenue teams: the plans, processes, data, systems and rules that marketing, sales and customer success use to find, win and keep customers.

The idea is older than the job title. In 2019 Forrester described a “revenue operations charter,” a set of shared operating principles across sales operations, marketing operations, sales enablement and customer success, meant to align planning, processes, systems, data and measurement.¹1 Source: Forrester, “Change Is Coming: The Revenue Operations Charter Is Born”, accessed Oct 2026. Published April 17, 2019. By 2023 its analysts were describing RevOps as something that unifies plans, processes, data, technology and talent across the revenue ecosystem, and were pushing back on the idea that it requires every ops person to report into one boss.²2 Source: Forrester, “Revenue Operations: Nine Myths And Two Realities”, accessed Oct 2026. Published September 15, 2023.

How it differs from the older ops roles

Most B2B companies start with ops embedded in each team: marketing ops runs automation and lead scoring, sales ops runs the CRM and forecast, CS ops runs renewal reporting. Each defines its own version of a customer, a qualified lead and a renewal. The result is three funnels that do not add up, and a pipeline finance cannot reconcile to bookings.

Function	Primary customer	Typical systems	Main question it answers
Marketing ops	Marketing team	Marketing automation, forms, ads data	Which programs create qualified demand?
Sales ops	Sales team	CRM, territories, forecast	Will we hit the number this quarter?
CS ops	Success and support	CS platform, ticketing, renewals	Who is at risk, who can expand?
RevOps	CRO, CFO, CEO	All of the above, plus billing data	Does the whole funnel add up, and where does it leak?

The table is our general guidance. In practice, RevOps often absorbs the older roles as specialist lanes, with one leader owning the shared definitions, data model and planning process.

That lemma shapes the rest of this guide. If you cannot centralize headcount for political reasons, you can still centralize definitions, systems ownership and planning. Those are the parts that fix reporting.

2. When to hire the first RevOps person, and where they report

There is no headcount threshold that triggers the hire, and we have not found a credible study that sets one. These are the signals we would use instead, as general guidance.

Signals that you need the hire

• Two numbers for one question. The CRO and CFO bring different pipeline or bookings figures to the same meeting, and nobody can explain the gap within an hour.
• The first sales manager arrives. Once someone manages reps, they need a forecast process, territories and quota, and a founder can no longer hold all of it.
• Compensation disputes. Reps contest commission statements, and finance rebuilds the calculation in a spreadsheet every month.
• A second go-to-market motion. You add a sales-assisted tier to a self-serve product, a partner channel, or a new segment, and stage definitions start to fork.

If none of these are true, a strong sales ops or marketing ops generalist is usually the better first hire.

Who should be first

The first hire is a builder. Look for someone who has administered a CRM at a company your size, has written stage definitions and a forecast process from scratch, and can talk to finance in finance’s terms. Evidence of reconciling numbers across teams matters more than depth in one tool.

Where RevOps reports

There are three common options, each with a real trade-off.

Reports to	Strength	Risk	Fits when
CRO or head of sales	Close to the forecast and the reps	Becomes sales ops with a new name	One sales-led motion, CRO owns marketing and CS
CFO	Neutral referee, strong on planning and comp	Distant from daily pipeline work	Several revenue leaders, heavy board reporting
CEO or COO	Seen as cross-functional by all teams	CEO bandwidth is thin	Early stage, or a COO who runs go-to-market

Our general guidance: report to whoever owns the funnel from first touch to renewal. If marketing, sales and CS each have their own leader, a CFO or COO line keeps RevOps neutral. Whatever the line, write a one-page charter, signed by the leaders of marketing, sales, CS and finance, saying what RevOps owns, advises on and does not touch.

3. The core responsibilities

The job has five parts. Sequence matters.

Systems and data ownership

RevOps owns the CRM as the system of record and the integrations that feed it. That means the data model (what an account, contact, lead and opportunity are), field ownership, permissions, and the approval process for new tools. It also means a weekly data quality routine with a named person: duplicates, records with no owner, open opportunities with close dates in the past.

Funnel definitions and lifecycle stages

Every revenue report rests on stage definitions. Write them down, with entry and exit criteria, before you build a dashboard.

HubSpot’s default lifecycle stages are a reasonable starting vocabulary: subscriber, lead, marketing qualified lead (MQL), sales qualified lead (SQL), opportunity, customer and evangelist, plus “other” for records that fit none of them.³3 Source: HubSpot Knowledge Base, “Use lifecycle stages”, accessed Oct 2026. An MQL is a contact marketing has deemed ready for sales; an SQL is one sales has identified as a potential customer.³ By default, HubSpot’s automatic updates only move the lifecycle stage forward, and integrations, imports and workflows cannot set an earlier stage until the current value is cleared.³

That design is worth copying in any system: stages should move backward only on purpose, because silent regressions break conversion reporting.

Opportunity stages need the same treatment. For each stage, write what must be true to enter it (a verified pain, a named economic buyer, a mutual plan) and what evidence a manager can check in the record.

Forecasting

RevOps owns the forecast process, not the forecast number. Sales leaders own the call; RevOps owns the method, the categories, the data and the history that lets you measure accuracy.

Salesforce’s forecasting module is typical of how CRMs structure this. Its forecast grid groups opportunities into categories (pipeline, best case, commit and closed) based on the stage an opportunity is in, and lets reps and managers make adjustments that change a rollup total without modifying the underlying opportunities.⁴4 Source: Salesforce Trailhead, “Review Your Collaborative Forecasts Setup”, accessed Oct 2026. That separation lets you compare the system’s number with the rep’s and manager’s calls over time.

As general guidance, map every stage to exactly one forecast category, freeze a weekly snapshot, and track accuracy by manager and segment.

Territory and quota planning

Territories decide who works which accounts; quotas decide what each rep must close. Both are annual exercises where sales and finance often disagree.

Salesforce, for example, tells admins to design a territory model as a hierarchy that represents the company’s sales structure, then apply assignment rules that populate owner fields on records.⁵5 Source: Salesforce Trailhead, “Design and Manage Territories”, accessed Oct 2026. The hard part is the logic: how to segment, how to balance accounts by potential, and what happens when an account changes segment mid-year.

Quotas should start from the company plan, then be checked bottom-up against each territory’s potential and each rep’s ramp. RevOps builds the model; the CRO and CFO agree the numbers.

Compensation operations

Compensation operations means correct, on-time commission statements, plus disputes, clawbacks and plan changes. It also has an accounting side. Under US GAAP, sales commissions that are incremental costs of obtaining a contract are generally capitalized and amortized. Workday, for example, says in its fiscal 2026 annual report that it treats commissions as “incremental and recoverable costs of obtaining a contract,” capitalizes them, and amortizes them over a period of benefit it has determined to be five years.⁶6 Source: Workday, Inc., “Form 10-K for the fiscal year ended January 31, 2026”, accessed Oct 2026. See the notes on deferred costs. This is an example, not accounting advice; confirm treatment with your auditor. Your plan design changes your financial statements, so finance must sign off on plan mechanics before they go to reps.

For the automation layer that moves records and approvals between these systems, see the complete guide to workflow automation tools.

4. The metrics RevOps owns

RevOps owns the definition and data quality of a short list of metrics. Other teams own the results.

Metric	What it answers	General formula
Pipeline coverage	Is there enough pipeline to hit target?	Open pipeline in period ÷ remaining target
Win rate	How often do qualified deals close?	Won ÷ (won + lost), by count or value
Sales cycle	How long does a deal take?	Average days from opportunity created to closed won
Net revenue retention (NRR)	Do existing customers grow?	Current ARR from a prior cohort ÷ that cohort’s prior ARR
Gross revenue retention (GRR)	How much do we keep, ignoring expansion?	As NRR, but expansion excluded and capped at 100%
CAC payback	How fast do we earn back acquisition cost?	Sales and marketing cost ÷ new gross-margin ARR, in months

The formulas above are general guidance. Each has choices you need to make and write down.

Pipeline coverage and win rate

Coverage targets should come from your own win rate, not from a rule of thumb. If you win one in four qualified opportunities by value, you need roughly four times the remaining target in qualified pipeline, before accounting for slippage. Measure win rate by segment and source; an outbound deal and an inbound deal rarely close at the same rate.

Sales cycle

Report the median as well as the average, since a few long enterprise deals distort the mean. If reps create opportunities at different points, the metric means nothing until entry criteria are fixed.

NRR and GRR

ARR, annual recurring revenue, is the annualized value of active subscription contracts. Net revenue retention compares current ARR from customers who existed a year ago with what those same customers paid a year ago. Expansion pushes it up; churn and downgrades pull it down.

Public companies show how much room there is for interpretation. Workday defines gross revenue retention as ARR from a prior-period set of customers compared with ARR from that same set at period end, counting losses from churn but not additional revenue from add-ons or expansion, and reported it at about 97% as of January 31, 2026.⁷7 Source: Workday, Inc., “Form 10-K for the fiscal year ended January 31, 2026”, accessed Oct 2026. Gross revenue retention definition and value in the key metrics discussion. Intapp reports a trailing twelve months “Cloud NRR” of 123% as of June 30, 2026, calculated by dividing current-period Cloud ARR by prior-period Cloud ARR for its SaaS contracts.⁸8 Source: Intapp, Inc., “Form 10-K for the fiscal year ended June 30, 2026”, accessed Oct 2026. Those are different scopes (all recurring revenue versus cloud contracts only) and should not be compared directly.

CAC payback

Customer acquisition cost (CAC) payback is how long a customer takes to repay what it cost to acquire. Bessemer Venture Partners defines it as the rate at which acquisition costs are repaid, usually including sales, marketing and customer success expenses, measured against gross-margin-adjusted ARR.⁹9 Source: Bessemer Venture Partners, “Scaling to $100 Million”, accessed Oct 2026. Published September 21, 2021. The same analysis put gross retention at a relatively consistent 85% to 90% across ARR ranges. In its 2021 “Scaling to $100 Million” analysis it suggested targets of under 12 months for SMB-focused companies, under 18 months for mid-market and under 24 months for enterprise.⁹

Treat those as one investor’s 2021 view. What matters for RevOps is consistency: decide which costs go into CAC and keep the definition stable so the trend means something.

For how pipeline gets created in the first place, see the complete guide to outbound in 2026. For how to call the quarter once it exists, see the complete guide to B2B sales forecasting, and for crediting the marketing that sourced it, the complete guide to B2B marketing attribution.

5. The operating cadence

A RevOps function is mostly a calendar. Without fixed meetings fed by fixed reports, every leader brings their own numbers.

Weekly: pipeline and forecast

One meeting per sales team, same day each week, same report. Review new pipeline created against target, deals that moved stage, deals that slipped close date, and changes in commit since last week. RevOps prepares the data and flags exceptions, such as deals in late stages with no recent activity or close dates in the past. The sales manager runs the meeting.

Keep it about deals. If the meeting turns into an argument about whether a number is right, the definition or the data is broken, and fixing that is RevOps’s job afterward.

Monthly: business review

A monthly business review (MBR) looks across the funnel, from sourced pipeline and conversion to bookings, churn and expansion. Finance attends. The output is a short list of actions with owners.

Quarterly: business review and planning

The quarterly business review (QBR) compares the quarter to plan, tests the assumptions behind next quarter (ramp, win rates, coverage), and adjusts territories, hiring or targets if needed. Once a year, the Q4 cycle becomes annual planning: capacity model, territories, quotas and comp plans, finished before the new year starts so reps begin with signed plans.

This cadence is our general guidance. Smaller companies can merge the monthly and quarterly reviews; larger ones add segment-level versions.

6. Team structure as you scale, and what RevOps people earn

How the team grows

The pattern below is our general guidance, not survey data. Stages are rough.

First hire (one person). A RevOps generalist or manager who owns the CRM, the definitions and the weekly reporting. Comp administration may still sit in finance.

Small team (two to four). Add a systems administrator for the CRM and integrations, and an analyst for reporting and forecasting. The lead starts running planning.

Department (five or more). Lanes form: systems, analytics and insights, planning (territories, quota, capacity), deal desk (pricing and contract approvals), and compensation operations. Marketing ops and CS ops either move in or align through a shared charter, per the hybrid model Forrester describes.² A director or VP leads, often with a seat in the executive planning process.

At every size, each system has one named admin and each metric one definition owner.

Salaries

There is no government salary series for RevOps as an occupation, so use proxies and job-specific data together. The figures below measure different things and should not be averaged.

10 Source: US Bureau of Labor Statistics, “Sales Managers,” Occupational Outlook Handbook, accessed Oct 2026. 11 Source: US Bureau of Labor Statistics, “Management Analysts,” Occupational Outlook Handbook, accessed Oct 2026. 12 Source: Levels.fyi, “General Revenue Operations Salary”, accessed Oct 2026. The 90th percentile was $340,000. Self-reported data; sample size not shown on the page.

Source	What it measures	Figure	Basis
US BLS	Sales managers	$148,270 median annual wage	May 2025, all industries10
US BLS	Management analysts	$101,860 median annual wage	May 2025, all industries11
Levels.fyi	General RevOps roles, US	$200,000 median total comp	Self-reported, updated Oct 29, 202612
Levels.fyi	Same, 25th to 75th percentile	$138,000 to $241,000	Self-reported12

The US Bureau of Labor Statistics (BLS) does not track RevOps separately. Its sales managers category, which counted about 650,100 jobs in 2025 and is projected to grow 4% from 2025 to 2035, is a reasonable proxy for senior RevOps leaders who own planning and the forecast.¹⁰ Management analysts, projected to grow 10% over the same period, are a closer proxy for analyst-level roles that improve processes and recommend changes.¹¹

Levels.fyi data is self-reported total compensation (base, bonus and equity) and skews toward larger technology employers, so expect early-stage startups to pay less cash.¹² Separately, a 2026 compensation report from Everstage with RevOps Co-op, built from more than 1,350 professionals, says RevOps pay nearly doubles within the first ten years of experience and that equity has become a standard part of RevOps compensation.¹³13 Source: Everstage, “State of RevOps Compensation Report 2026”, accessed Oct 2026. Everstage sells commission software; the page summarizes findings without full figures.

7. Tooling categories and the first 90 days

Tooling, at a high level

RevOps uses five broad categories of software. Vendors and pricing are in the stack guide.

• System of record. The CRM, plus the billing system for contract and invoice data.
• Data quality and enrichment. Deduplication, enrichment and routing so records arrive complete and owned.
• Forecasting and pipeline inspection. Native CRM forecasting or a specialist layer that snapshots pipeline and tracks accuracy.
• Planning and compensation. Territory and quota modeling, and commission calculation with statements reps can check.
• Reporting and analytics. CRM dashboards for daily work; a warehouse and BI tool once data from billing, product and support needs joining.

The rule for the function: no tool without an owner, a written reason and a defined write-back to the CRM.

A first 90 days plan

This plan is general guidance for a first RevOps hire at a company with a working CRM and a small sales team.

Days 1 to 30: listen and inventory.

• Meet every revenue leader and finance. Ask each for the three numbers they trust least.
• Inventory systems, integrations, owners and contract dates.
• Pull the last four quarters of pipeline, bookings and churn. Reconcile bookings to finance’s figures and document every gap.

Days 31 to 60: define and fix.

• Write one-page definitions for lifecycle stages, opportunity stages and exit criteria, forecast categories, NRR, GRR and CAC. Get sign-off from sales, marketing, CS and finance.
• Fix the top data problems you found: duplicates, ownerless accounts, stale close dates.
• Stand up the weekly pipeline report and start snapshotting the forecast.

Days 61 to 90: run the cadence.

• Run the first monthly business review on the agreed definitions.
• Draft the RevOps charter and a 12-month roadmap (planning cycle, comp automation, tooling changes).
• Agree the first two hires, if any, based on where the work actually piled up.

Avoid buying software in the first 90 days. Early problems are mostly definitions and data, and new tools copy them faster.

For the software side of the function, see the complete guide to building a B2B revenue stack, and for cutting what you already pay for, the complete guide to auditing your SaaS stack.

8. Mistakes we see most often

These come from general practice, not a survey.

• Renaming sales ops. The title changes, the scope does not, and marketing and CS keep their own numbers. Forrester warns that combining ops functions without creating new capabilities misses the point.²
• Hiring a VP before there is anything to unify. With one sales team and one CRM, a senior leader tends to over-build process.
• Letting RevOps own the number. RevOps owns the method and the data. The CRO owns the forecast call. Blur that and RevOps gets blamed for a missed quarter it could not influence.
• Comp plans without finance. Plan mechanics affect commission capitalization and the income statement.⁶ Plans designed without finance get redesigned mid-year.
• No snapshot history. Without weekly forecast snapshots you cannot measure accuracy, and without accuracy data the forecast process cannot improve.

9. The verdict

RevOps is worth building once your revenue numbers disagree with each other. Its value is one set of definitions, one system of record with named owners, and a fixed cadence. Hire a builder first, report to whoever owns the whole funnel, and write the charter and metric definitions before buying anything.

Frequently asked questions

What is the difference between RevOps and sales ops?

Sales ops supports the sales team: CRM, territories, forecast. RevOps covers the same work across marketing, sales and customer success, with one set of definitions and one data model. Many RevOps teams start as a sales ops team whose scope was widened on purpose.

When should a startup hire its first RevOps person?

When leaders bring conflicting numbers to the same meeting, when the first sales manager arrives, or when commission statements are rebuilt by hand every month. Before that, a strong sales ops or marketing ops generalist usually serves the company better.

Who should RevOps report to?

To whoever owns the funnel from first touch to renewal. That is often the CRO; if marketing, sales and CS have separate leaders, a CFO or COO line keeps RevOps neutral. Forrester notes that a single reporting line for all ops staff is not the only workable model.²

What metrics should RevOps own?

The definitions and data for pipeline coverage, win rate, sales cycle, net and gross revenue retention, and CAC payback, plus forecast accuracy. Other teams own the results. Write each definition down, because public companies calculate retention differently.⁷⁸

How much does a RevOps manager or leader earn?

There is no BLS category for RevOps. As proxies, BLS reports a $148,270 median for sales managers and $101,860 for management analysts (May 2025).¹⁰¹¹ Self-reported data on Levels.fyi shows a $200,000 median total compensation for general US RevOps roles, with the middle half between $138,000 and $241,000.¹²

Does RevOps own commission calculations?

Usually it calculates commissions, issues statements and handles disputes. Finance owns the accounting, including capitalizing commissions where required.⁶ The CRO and CFO agree plan design together.

Sources and notes

1. Source: Forrester, “Change Is Coming: The Revenue Operations Charter Is Born”, accessed Oct 2026. Published April 17, 2019. ↩

2. Source: Forrester, “Revenue Operations: Nine Myths And Two Realities”, accessed Oct 2026. Published September 15, 2023. ↩ ↩² ↩³ ↩⁴ ↩⁵

3. Source: HubSpot Knowledge Base, “Use lifecycle stages”, accessed Oct 2026. ↩ ↩² ↩³

4. Source: Salesforce Trailhead, “Review Your Collaborative Forecasts Setup”, accessed Oct 2026. ↩

5. Source: Salesforce Trailhead, “Design and Manage Territories”, accessed Oct 2026. ↩

6. Source: Workday, Inc., “Form 10-K for the fiscal year ended January 31, 2026”, accessed Oct 2026. See the notes on deferred costs. This is an example, not accounting advice; confirm treatment with your auditor. ↩ ↩² ↩³

7. Source: Workday, Inc., “Form 10-K for the fiscal year ended January 31, 2026”, accessed Oct 2026. Gross revenue retention definition and value in the key metrics discussion. ↩ ↩² ↩³

8. Source: Intapp, Inc., “Form 10-K for the fiscal year ended June 30, 2026”, accessed Oct 2026. ↩ ↩² ↩³

9. Source: Bessemer Venture Partners, “Scaling to $100 Million”, accessed Oct 2026. Published September 21, 2021. The same analysis put gross retention at a relatively consistent 85% to 90% across ARR ranges. ↩ ↩²

10. Source: US Bureau of Labor Statistics, “Sales Managers,” Occupational Outlook Handbook, accessed Oct 2026. ↩ ↩² ↩³ ↩⁴

11. Source: US Bureau of Labor Statistics, “Management Analysts,” Occupational Outlook Handbook, accessed Oct 2026. ↩ ↩² ↩³

12. Source: Levels.fyi, “General Revenue Operations Salary”, accessed Oct 2026. The 90th percentile was $340,000. Self-reported data; sample size not shown on the page. ↩ ↩² ↩³ ↩⁴ ↩⁵

13. Source: Everstage, “State of RevOps Compensation Report 2026”, accessed Oct 2026. Everstage sells commission software; the page summarizes findings without full figures. ↩