Revenue Operations Glossary: 24 RevOps Terms Defined for 2026

30-second answer: Revenue operations (RevOps) unifies the people, process, and tooling that runs marketing, sales, and customer success as one revenue motion. The vocabulary spans organizational terms (RevOps, Marketing Ops, Sales Ops, CS Ops), process terms (lead-to-account, lead routing, MEDDIC, MEDDPICC, BANT), system terms (CRM, MAP, CDP, CPQ, data warehouse), and metric terms (CAC, LTV, payback, NRR, GRR, magic number). This glossary defines 24 RevOps terms.

See RevOps systems orchestrated through Abmatic AI, book a demo.

Organizational terms

Revenue Operations (RevOps)

RevOps is the unified function responsible for the systems, processes, and analytics across marketing, sales, and customer success. It centralizes ownership of the revenue tech stack, the data model, and cross-functional process design.

Marketing Operations

Marketing operations owns the marketing tech stack: marketing automation, attribution, campaign instrumentation, and marketing-side data hygiene. In larger orgs, MarOps reports into RevOps; in smaller orgs the two are the same function.

Sales Operations

Sales operations owns territory design, quota setting, sales tooling, forecasting, and pipeline hygiene. SalesOps is the operational counterpart to the sales leadership team.

Customer Success Operations

Customer success operations owns retention, expansion, health-score modelling, and the CS tech stack (success platform, NPS, customer health dashboards).

Deal Desk

A deal desk reviews non-standard contracts, pricing exceptions, legal terms, and deal structures before they go to legal. It sits inside RevOps in most modern orgs.

Process terms

Lead-to-Account Matching

Lead-to-account matching links inbound leads to existing accounts in the CRM, preventing duplicate accounts and ensuring leads route to the right opportunity owner. It is the foundation of account-based reporting.

Lead Routing

Lead routing assigns inbound leads to the correct sales rep based on territory, account ownership, deal stage, or signal-based rules. See how to route leads from intent signals.

MEDDIC

MEDDIC is a sales qualification framework: Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion. It structures how reps qualify enterprise opportunities.

MEDDPICC

MEDDPICC extends MEDDIC with two additional letters: Paper process and Competition. The added rigor matters in highly procurement-driven enterprise deals.

BANT

BANT is a legacy sales qualification framework: Budget, Authority, Need, Timeline. It is simple but increasingly seen as too rep-centric for modern committee-driven B2B selling.

SLA Between Marketing and Sales

A service-level agreement defines response-time, lead-acceptance, and follow-up commitments between marketing and sales. SLAs are the operating contract that turns marketing handoffs into measurable sales action. See how to coordinate marketing and SDRs.

System terms

CRM (Customer Relationship Management)

The CRM is the system of record for accounts, contacts, opportunities, and customer interactions. Salesforce and HubSpot dominate the B2B category. Every other revenue system stitches back to the CRM record.

MAP (Marketing Automation Platform)

The MAP runs email campaigns, lead scoring, nurture sequences, and form processing. Marketo, HubSpot, and Pardot are the main B2B MAPs.

CDP (Customer Data Platform)

A customer data platform unifies first-party customer data from many sources into a single profile that downstream tools query. See customer data platform CDP.

CPQ (Configure, Price, Quote)

CPQ tooling generates configured quotes for complex products with discount controls, approval workflows, and contract generation. It removes pricing errors and accelerates deal cycles.

Data Warehouse

A data warehouse (Snowflake, BigQuery, Redshift, Databricks) consolidates data from across the revenue stack into a single queryable store. Modern RevOps stacks treat the warehouse as the single source of truth.

Reverse ETL

Reverse ETL pushes warehouse data back into operational tools (CRM, MAP, ad platforms) so the analytics layer drives the action layer. It is the architecture pattern that makes the warehouse-as-source-of-truth practical.

Pipeline and forecasting terms

Pipeline Coverage

Pipeline coverage is the ratio of open pipeline to revenue target in a period, often expressed as 3x or 4x coverage. It is the most-watched leading indicator of quarterly attainment.

Pipeline Velocity

Pipeline velocity multiplies opportunity count, average deal size, and win rate, then divides by sales cycle length. It is a single number that summarizes the throughput of the sales engine.

Forecast Category

Forecast categories (commit, best case, pipeline, omitted) classify opportunities by likelihood of closing in the period. Disciplined forecasting depends on consistent category usage.

Bookings vs Revenue

Bookings are signed contract value (typically TCV or ACV); revenue is recognized in line with the accounting policy (usually ratable for SaaS). RevOps reports both because they answer different questions.

Unit-economics terms

CAC (Customer Acquisition Cost)

CAC is total sales and marketing spend in a period divided by new customers acquired. Fully-loaded CAC includes salaries, tools, and overhead.

LTV (Lifetime Value)

LTV is the expected total revenue from a customer over the lifetime of the relationship. The standard B2B SaaS shorthand is gross-margin LTV equals ARR times gross margin divided by gross churn rate.

CAC Payback

CAC payback is the number of months for gross profit from a new customer to repay the CAC of acquiring them. Healthy B2B SaaS targets 12 to 24 months.

Net Revenue Retention (NRR)

NRR is gross revenue from existing customers in a period divided by the same cohort's revenue 12 months prior. NRR above 100 percent indicates expansion outpaces churn.

Magic Number

Magic number is net new ARR in a period multiplied by four, divided by sales-and-marketing spend in the prior period. A magic number above 0.75 is the standard rule for go-to-market efficiency.

Ready to see RevOps tooling orchestrated together? Book a demo of Abmatic AI.

Frequently asked questions

What is the difference between RevOps and Sales Ops?

Sales Ops focuses on the sales function. RevOps spans marketing, sales, and customer success as one revenue motion. RevOps owns the cross-functional data model and process; Sales Ops owns sales-specific tooling and territory design.

Should small companies have a RevOps function?

Most companies under 50 employees combine RevOps with finance or with the founder's executive office. The named function usually appears between 50 and 150 employees as the tech stack and process complexity exceed informal coordination.

Where does ABM live in the RevOps stack?

ABM is the operating model that uses the RevOps data model. The TAL, ICP, account scoring, and account-level reporting all sit on the RevOps data layer. See account-based marketing and how to set up account scoring.

Is the data warehouse really required for RevOps?

For companies under 50 employees, native CRM reporting often suffices. Above 100 employees, the warehouse becomes essential because no single SaaS tool can answer multi-system questions on its own.

How does RevOps interact with finance?

RevOps owns the operational forecast (pipeline, deal velocity, attainment). Finance owns the financial forecast (revenue, EBITDA, cash). The two reconcile monthly because they use different views of the same numbers.

Stack architecture patterns

Modern RevOps stacks settle into one of two architectural patterns. The CRM-centric pattern keeps Salesforce or HubSpot as the operational source of truth, with the data warehouse used mainly for reporting. The warehouse-centric pattern treats Snowflake or BigQuery as the source of truth, with reverse ETL pushing curated data into operational tools. The CRM-centric pattern is faster to implement and adequate for most companies under 200 employees. The warehouse-centric pattern scales better when the stack exceeds a dozen integrated tools and when the analytics complexity outgrows native CRM reporting.

Both patterns now include an AI-orchestration layer that sits across CRM and warehouse and runs agentic workflows for routing, scoring, deduplication, and outreach drafting. AI agents are not a replacement for the data layer; they are a workflow layer on top of it. The cleanest implementations write all agent decisions back to the warehouse for audit and replay, which is a discipline that distinguishes mature from fragile RevOps stacks.

Closing

RevOps vocabulary keeps changing as the discipline matures, especially around AI agents and agentic workflows entering the stack. Use this glossary as a reference when reading RevOps job descriptions, vendor documentation, and operating playbooks.

See ABM running on top of a clean RevOps stack inside Abmatic AI. Book a demo.