RevOps glossary: Key revenue operations terms, defined

Key takeaways

• RevOps runs sales, marketing, and customer success on one connected system instead of three separate ones.
• SalesOps and MarkOps each serve a single team, while RevOps owns the operating model across the whole funnel.
• GTM engineering builds the automations and integrations that put a RevOps foundation to work.
• Almost every RevOps term traces back to one goal: getting the right account to the right rep at the right moment, with data everyone trusts.

Revenue operations has picked up a lot of new vocabulary in a short time. GTM engineers, enrichment waterfalls, agentic workflows, and signal-based scoring now sit alongside older terms like lead routing and lifecycle stages, and teams don’t always mean the same thing when they use them.

That matters more than it sounds. When marketing and sales disagree on what counts as a qualified lead, the systems built on that definition inherit the confusion. Use this glossary as a shared reference, grouped by how the terms show up in day-to-day RevOps work.

What does RevOps do?

RevOps owns three things most revenue teams struggle to keep consistent: the definitions, the plumbing, and the scoreboard.

• The definitions: What counts as a qualified lead, when a deal changes stages, and who owns each account.
• The plumbing: The systems, integrations, and automations that move leads and data between teams without manual work.
• The scoreboard: The dashboards, attribution, and forecasts leaders use to decide where to invest next.

Day to day, that might mean fixing a routing rule that sends leads to the wrong territory, merging duplicate records before a campaign launches, or rebuilding a forecast after stage definitions change. When all three pieces work, handoffs stop breaking and leaders stop arguing over whose numbers are right.

---

Foundational terms

Start here. Nearly every other term in this glossary builds on these three.

Go-to-market (GTM)

Go-to-market (GTM) is the plan and machinery a company uses to reach buyers and turn interest into revenue. In RevOps conversations, it usually means the machinery: the systems, data, and workflows that carry a strategy into daily execution.

Revenue operations (RevOps)

Revenue operations (RevOps) is the function responsible for the systems, data, and processes behind every revenue-generating team. Instead of sales, marketing, and customer success each building their own operations, RevOps designs one model they all share.

Ideal customer profile (ICP)

An ideal customer profile (ICP) describes the type of company most likely to buy, succeed with, and stay with your product, usually defined by industry, size, revenue, geography, and technology. Routing rules, scoring models, and target account lists all depend on a clearly written ICP.

---

Roles and operating models

These terms describe who does RevOps work and how it’s organized. They overlap, which is exactly why they get confused.

Sales operations (SalesOps)

Sales operations (SalesOps) keeps a sales team efficient and accountable through territory and quota planning, compensation, rep tooling, and pipeline reporting. It sits inside the sales organization, so it rarely owns how marketing or customer success data connects to the pipeline.

Marketing operations (MarkOps)

Marketing operations (MarkOps) runs the systems and data behind marketing programs, including the marketing automation platform, campaign tracking, lead capture, and nurture. Like SalesOps, it serves one team, and friction can sometimes show up at the handoff to sales.

Revenue operations consulting

Revenue operations consulting is outside expertise that assesses and redesigns how your revenue systems, data, and processes work together. A revenue operations agency typically goes further and builds the fixes too. CRM consulting, which focuses on configuring and adopting a CRM, is one common piece of the work.

What is RevOps as a service?

RevOps as a service is an outsourced model in which a partner designs, builds, and runs your revenue operations on an ongoing basis. You get architecture, automation, data, and reporting support from specialists without recruiting a full in-house ops team.

When should you outsource revenue operations?

Outsourcing revenue operations makes sense when you need systems built or rebuilt faster than a hiring process allows, when the work comes in waves like a CRM migration or attribution overhaul, or when you need expertise across several platforms at once.

What is GTM engineering?

GTM engineering is the technical discipline of building the automated systems that power go-to-market execution, from enrichment and scoring workflows to API integrations between tools. RevOps sets the rules for how the revenue engine should run, while GTM engineering builds the parts that run it automatically. Read a deeper dive on the differences between RevOps and GTM engineering.

GTM engineering agency

A GTM engineering agency is a firm that designs and builds GTM systems for clients, often alongside the strategy and execution that put those systems to use. Compared with a single in-house hire, an agency brings experience across many stacks and can scale its effort up or down. Read more in our blog, Should you hire a GTM engineer, or a GTM engineering agency?

These four functions overlap, but each owns a different part of the revenue engine:

Function	Primary focus	Typical scope
RevOps	Alignment, visibility, and process across the revenue org	Sales, marketing, and customer success
SalesOps	Sales team performance and efficiency	Quotas, territories, CRM hygiene, commissions, and pipeline reporting
MarkOps	Marketing technology, data, and campaign execution	Marketing automation, lead capture, nurture, and campaign tracking
GTM engineering	Building the automations behind GTM motions	Enrichment, routing, scoring, integrations, and AI workflows

---

Systems and tech stack terms

These terms describe the technology layer: which tools a revenue team runs, how they connect, and where AI fits in.

What are the essential components of a GTM technology stack?

The essential components of a GTM technology stack are a CRM as the system of record, a marketing automation platform, a sales engagement platform, data enrichment, intent data, and attribution or analytics. Choose one strong tool per category and favor clean CRM integration over long feature lists.

Marketing automation platform (MAP)

A marketing automation platform (MAP) runs email campaigns, nurture programs, forms, and lead scoring for marketing teams. The CRM tracks sales activity and pipeline, while the MAP handles marketing engagement, so the connection between them decides whether leads reach sales cleanly.

GTM architecture

GTM architecture is the blueprint for how revenue systems, data, and processes fit together. It defines which system owns which data, how records move between tools, and what triggers each automation, so the stack behaves like one system.

Single source of truth

A single source of truth is one trusted record of customer and pipeline data that every team reports from, usually the CRM. Without one, meetings turn into debates about whose numbers are right instead of decisions about strategy.

When does a CRM migration make sense?

A CRM migration, moving your data and processes to a new CRM, makes sense when your current system can’t handle your data volume, can’t connect to tools you depend on, or can’t support how you now sell. Often, a stronger RevOps foundation solves the problem without switching.

Technology integration services

Technology integration services connect separate business systems so data moves between them automatically. Depending on complexity, that means a native connector, an integration platform as a service (iPaaS) such as Workato or Boomi, or custom middleware built for complex enterprise needs like CRM-to-ERP syncs.

Tech stack consolidation

Tech stack consolidation trims a sprawling set of tools down to the ones your team actually uses. It starts with an audit of every tool and contract, then cuts redundant tools, merges overlapping ones, and replaces poor fits. Consolidation lowers costs and makes the remaining stack easier to adopt.

What is AI transformation?

AI transformation is the move from scattered AI experiments to AI built into how a revenue team works every day: choosing tools that fit the stack, training people to use them, and feeding AI-detected signals into outreach. It depends on clean data, since AI working from bad records makes confident mistakes at scale.

---

Process and automation terms

These terms describe how work moves through the revenue engine and where automation takes over manual steps.

GTM process mapping

GTM process mapping documents how leads, accounts, and responsibilities move between teams, including every handoff, owner, and qualification rule. It usually comes first in any automation project, because automating an undocumented process just makes its flaws run faster.

Lead routing

Lead routing automatically assigns each new lead to the right owner based on rules like territory, segment, ICP fit, or buying intent. Good routing assigns leads the moment they arrive, balances workload across reps, and handles edge cases like existing accounts and duplicates.

Speed-to-lead

Speed-to-lead is the time between a prospect raising their hand and a rep making contact. Interest fades quickly, so RevOps teams shrink this window with instant routing, real-time notifications, and SLA alerts.

Lead leakage

Lead leakage is pipeline lost when leads slip through gaps in your process: unassigned, stuck in the wrong queue, or passed between teams with no clear owner. Because leaked leads rarely show up in reports, teams often underestimate the loss.

Service-level agreement (SLA)

A service-level agreement (SLA) in sales and marketing is a documented commitment for how fast and how thoroughly leads get handled, such as how quickly sales follows up on a qualified lead. RevOps makes SLAs enforceable with CRM tracking and automated alerts.

Sales process automation

Sales process automation uses software to handle repetitive steps in the sales workflow, such as routing, enrichment, scoring, notifications, and status updates, so reps spend more time selling. Most of these steps live in the CRM, so sales process automation and CRM automation usually go hand in hand.

CRM automation

CRM automation is any rule or workflow inside your CRM that completes a task without manual effort, like assigning owners, updating lifecycle stages, creating follow-up tasks, or merging duplicate records.

Workflow orchestration

Workflow orchestration coordinates automated steps across several systems so they happen in the right order: enrichment, then scoring, then routing, then a rep alert. Without it, teams end up with plenty of signals and no coordinated action.

Agentic workflows

Agentic workflows are automations in which AI agents complete multi-step tasks with some independence, such as researching an account and drafting outreach context. A common approach keeps a person in the loop for anything customer-facing: the agent prepares the work, and a rep approves it. Learn more about agentic workflows.

---

Data, signals, and scoring terms

These terms cover the raw material of RevOps: the data in your systems and how it becomes priorities for reps.

Data infrastructure

Data infrastructure is the underlying setup that collects, connects, and stores revenue data across the CRM, MAP, sales engagement, and other GTM tools. Strong infrastructure is what makes a single source of truth possible.

Data enrichment

Data enrichment adds missing or updated details to account and contact records from outside sources, such as company size, industry, technologies in use, job titles, and verified contact information. Enriched records make segmentation, routing, and personalization far more accurate.

Enrichment waterfall

An enrichment waterfall checks multiple data providers in sequence until it finds the field it needs. If the first provider has no phone number for a contact, the waterfall tries the next. That raises match rates and avoids paying twice for the same data.

Data governance

Data governance is the set of rules, owners, and routines that keep revenue data accurate over time, including data hygiene work like deduplication and fixing data decay. MIT Sloan Management Review estimates bad data costs most companies 15% to 25% of revenue.

Buying signals

Buying signals are events that suggest an account may be entering a buying window, such as funding, hiring surges, new technology adoption, a new executive, or repeat pricing page visits. Strong systems look for several signals clustering together rather than reacting to one.

Intent data

Intent data shows which accounts are actively researching topics related to what you sell. First-party intent comes from your own channels, like website visits, while third-party intent tracks research activity across other sites.

Account intelligence

Account intelligence is a summary of an account that tells a rep why it’s worth pursuing now and how to approach it, combining firmographic data, signals, buying committee details, and likely pain points. The best systems deliver it inside the tools reps already use.

Lead scoring

Lead scoring ranks leads by how well they match your ICP and how sales-ready they are, while account scoring applies the same idea at the company level. Scores feed routing and prioritization, so they only work if sales trusts the model.

Buying committee mapping

Buying committee mapping identifies every person who influences a purchase at a target account, along with their role in the decision. It lets reps build support across the account instead of relying on one contact, and it lays the groundwork for account-based marketing (ABM).

Lifecycle stages

Lifecycle stages are the defined phases a contact or account moves through on the way to becoming a customer, such as lead, MQL, SQL, opportunity, and customer. Each stage needs clear entry and exit criteria, or reporting and forecasting drift.

How do MQLs and SQLs differ?

A marketing qualified lead (MQL) is one marketing judges as ready for sales attention, while a sales qualified lead (SQL) is one sales has reviewed and accepted as a likely opportunity. Both teams should agree on written criteria for each.

---

Measurement and forecasting terms

These terms describe how RevOps proves what’s working and predicts what’s coming.

Revenue analytics

Revenue analytics is the practice of measuring how pipeline and revenue move through every stage of the funnel, from first touch to closed deal. It covers conversion rates, cycle length, pipeline health, and efficiency metrics like customer acquisition cost (CAC).

Dashboards and data visualization

Dashboards and data visualization turn revenue data into live, visual reports that teams can read at a glance. Well-built dashboards give leaders full-funnel visibility and surface conversion problems or pipeline risk before quarter end.

Revenue attribution

Revenue attribution traces pipeline and revenue back to the campaigns, channels, and sales activities that influenced them. When the focus is marketing’s contribution, it’s often called marketing attribution. Either way, attribution is only as accurate as the tracking and data underneath it.

Attribution models

Attribution models are the rules for dividing credit among touchpoints. First-touch and last-touch credit a single interaction, linear splits credit evenly, and U-shaped, W-shaped, and full-path models weight key moments like lead creation and opportunity creation. Longer, multi-stakeholder deals usually need multi-touch models.

Why track marketing-sourced and marketing-influenced pipeline separately?

Marketing-sourced pipeline comes from opportunities marketing originated, while marketing-influenced pipeline includes any opportunity marketing touched. Reporting them separately gives a more honest picture of what marketing creates on its own and how it supports deals that started elsewhere.

Pipeline coverage

Pipeline coverage is the ratio of open pipeline to the revenue target for a period. A team that needs $1 million and has $3 million in qualified pipeline has 3x coverage. The right ratio depends on your own historical win rates.

Revenue forecasting

Revenue forecasting estimates how much revenue the business will close in a future period, based on current pipeline, stage definitions, and historical conversion rates. Regular dashboard reviews helped demandDrive client Qorvo achieve 3x converted opportunities.

---

Clay terms

Clay comes up often enough in modern RevOps work that it has its own vocabulary.

Clay

Clay is a data and automation platform revenue teams use for data enrichment, account research, signal-driven prospecting, and personalized outbound at scale. Teams use it to pull data from many providers at once, score accounts, map buying committees, and push the results into their CRM and outreach tools.

Clay agency (Claygency)

A Clay agency, sometimes called a Claygency, is a firm that implements and manages Clay for other companies, from enrichment waterfalls and scoring logic to CRM integration. The best ones pair the technical build with an understanding of how sales teams actually use the data.

Clay Studio Partner

A Clay Studio Partner is an agency certified by Clay to design, build, and manage Clay implementations. demandDrive is a Clay Studio Partner and was named Clay’s inaugural Rising Star partner.

Putting the terms to work

A shared vocabulary is a starting point. The harder part is building systems where these pieces actually connect, and the order you build them in matters.

Talk to our team about RevOps and GTM engineering support from a single partner.