A glossary of sales-ops terms nobody defines

Every revenue meeting runs on a shared vocabulary that almost nobody learned on purpose. New reps and new RevOps hires pick it up by context clues over their first few months — nodding along when someone says "we need to fix our rep ramp" without being entirely sure whether that's a timeline, a target, or a program. We've collected the terms that come up constantly, grouped by what they actually help you do, with the plain-language definition nobody gave you in onboarding.

A caveat before the list: several of these terms mean slightly different things at different companies, and that's not a sign anyone is using them wrong. "Pipeline coverage" at a company with a 90-day sales cycle and a 20% win rate should look different from "pipeline coverage" at a company with a 14-day cycle and a 40% win rate, even though both teams use the exact same phrase in exactly the same kind of meeting. Treat the definitions below as the common starting point, not a universal standard to enforce against every team you encounter.

Pipeline and forecasting terms

• Commit, best case, and worst case — the three-tier forecast language most sales orgs use: commit is what a rep or manager will stake their reputation on, best case includes deals that could plausibly close with a good week, and worst case is the floor if nothing goes right.
• Pipeline coverage — total open pipeline value divided by the quota it needs to cover, usually expressed as a ratio (3x coverage means $3 of pipeline for every $1 of quota). Healthy ratios vary by win rate and sales cycle length.
• Slippage — a deal's close date getting pushed into a later period. Occasional slippage is normal; a pattern of slippage concentrated at quarter-end is usually a sign of soft deals being forecast too optimistically.
• Sandbagging — the opposite problem: a rep deliberately forecasting conservatively to guarantee they beat their number, which distorts the aggregate forecast upward in surprise over-performance rather than smooth predictability.

Lead and demand terms

• MQL and SQL — marketing-qualified lead and sales-qualified lead, the two handoff points most commonly used to mark when a lead has met criteria to pass from marketing's ownership to sales's.
• MEDDIC — a qualification framework (Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion) used to assess whether a deal is real and likely to close, popular in complex B2B sales cycles.
• ICP — ideal customer profile: the specific combination of firmographic and behavioral traits that describe the account most likely to buy, renew, and expand.
• Speed to lead — the time between a lead's first inbound signal (a form fill, typically) and the first outbound follow-up from a rep. Widely cited research ties fast speed-to-lead to meaningfully higher conversion rates.

Comp and quota terms

• Rep ramp — the period a new rep spends reaching full productivity, usually measured in months and tracked as a percentage of full quota expected at each stage of ramp.
• OTE — on-target earnings: a rep's total expected compensation (base plus commission) assuming they hit 100% of quota, the number most commonly cited in job postings and comp conversations.
• Accelerators and decelerators — commission rate changes above or below quota attainment, where a rep might earn a higher commission rate past 100% of quota (accelerator) or a lower rate below a minimum threshold (decelerator).
• Clawback — a contractual provision that reclaims a paid commission if the underlying deal churns or is refunded within a defined window, common on annual-contract SaaS deals.

Data and systems terms

• Lead routing — the rules-based process of assigning an incoming lead to the correct rep or team, based on territory, account size, round-robin, or scoring.
• Deduplication (dedupe) — the process of identifying and merging duplicate records in a CRM, a perpetual maintenance task in any org with more than one lead source feeding the same database.
• Field mapping — how data fields in one system (a form field, say) correspond to fields in another (a CRM property), the unglamorous detail that breaks most integrations when it's done carelessly.
• Source of truth — whichever system is treated as authoritative when two systems disagree about a given piece of data, a designation that has to be explicit or every integration eventually produces conflicting numbers.

Deal mechanics and revenue terms

• Net revenue retention (NRR) — the percentage of revenue retained from an existing customer base over a period, accounting for both expansion and churn; above 100% means expansion is outpacing churn.
• Logo churn — the rate at which customer accounts (logos) cancel entirely, distinct from revenue churn, which can be smaller if the churned accounts were lower-spend.
• Multi-threading — maintaining relationships with multiple stakeholders at a target account rather than relying on a single champion, widely considered a leading predictor of deal survival when a champion changes roles mid-cycle.
• Land and expand — a go-to-market motion that deliberately starts with a smaller initial deal (the land) with the explicit intent to grow the account's spend over time (the expand), common in usage-based and seat-based pricing models.

Territory and org-design terms

• Territory carving — dividing accounts or geography among reps, usually by firmographic rules (industry, size, region) rather than arbitrary assignment, to keep coverage fair and comparable.
• Pod structure — organizing a sales team into small cross-functional units (often an SDR, an AE, and sometimes a CSM) that share accounts, rather than siloed functional teams handing off serially.
• Overlay role — a specialist (a solutions engineer or vertical expert, commonly) who supports multiple deals across territories rather than owning any single book of business.
• Span of control — the number of direct reports a frontline manager carries, a number that quietly caps how much coaching and pipeline scrutiny each rep actually gets.

Why the vocabulary matters more than it seems

It's tempting to treat this as jargon-spotting, but imprecise vocabulary has real operational cost. A team that uses "pipeline coverage" to mean two different things in two different dashboards will eventually make a staffing or forecast decision based on a number that quietly meant something different than the person reading it assumed. Getting explicit about definitions, writing them down somewhere everyone can find them, and updating them when your business model changes (land-and-expand math looks different in a usage-based pricing world than a seat-based one) is a small, boring investment that prevents a specific, expensive kind of miscommunication later.

The other reason it's worth doing: onboarding. New hires in sales-ops-adjacent roles spend their first few weeks reverse-engineering vocabulary from context, which is slow and occasionally produces a wrong guess that sticks. A short written glossary, specific to your company's own usage of these terms (because "pipeline coverage" at a 3x-ratio shop means something different than at a shop that runs 5x), turns weeks of osmosis into an afternoon of reading. It's one of the cheapest documentation projects a RevOps team can take on, and one of the most consistently skipped.