# The Forgeworks RevOps Glossary

> Authoritative definitions for 140 Revenue Operations, sales, marketing, and CRM terms. Curated by Forgeworks — your AI-first RevOps team, US based, and a HubSpot Solutions Partner.

Canonical URL: https://forgeworks.ai/glossary
Maintained by: Forgeworks (https://forgeworks.ai)
Last updated: 2026-10-15

---

## Categories

- [RevOps Foundations](#revops-foundations)
- [Sales Operations](#sales-operations)
- [Marketing Operations](#marketing-operations)
- [Lead Management](#lead-management)
- [CRM & Systems](#crm-systems)
- [RevOps Tools](#revops-tools)
- [Data & Reporting](#data-reporting)
- [SaaS Metrics](#saas-metrics)
- [Compensation & Forecasting](#compensation-forecasting)
- [Methodologies & Frameworks](#methodologies-frameworks)

---

## RevOps Foundations {#revops-foundations}

### Revenue Operations (RevOps) {#revops}

**Short:** The discipline of aligning sales, marketing, and customer success operations to drive predictable revenue growth.

Revenue Operations, or RevOps, is the strategic alignment of sales, marketing, and customer success operations across the customer lifecycle. RevOps unifies the systems, data, processes, and people that produce revenue under a single accountable function. The goal is predictable, scalable revenue growth through reduced friction between teams, cleaner data, and instrumented workflows. RevOps emerged in the 2010s as B2B companies consolidated previously siloed operations functions (SalesOps, MarketingOps, CustomerSuccessOps) into one team.

*Canonical: https://forgeworks.ai/glossary#revops*

### Sales Operations (SalesOps) {#sales-operations}

**Short:** The function responsible for sales process design, technology, analytics, and enablement.

Sales Operations is the function responsible for the systems, processes, analytics, and enablement that allow a sales team to perform. SalesOps owns CRM administration, sales tooling, territory and quota design, commission plans, forecasting accuracy, and reporting. In modern B2B companies, SalesOps is typically a sub-function of Revenue Operations.

*Canonical: https://forgeworks.ai/glossary#sales-operations*

### Marketing Operations (MarketingOps or MOps) {#marketing-operations}

**Short:** The function responsible for marketing technology, data, lead processes, and campaign infrastructure.

Marketing Operations is the function that owns the marketing technology stack, marketing data, lead lifecycle processes, attribution models, and campaign infrastructure. MOps is responsible for tools like marketing automation platforms, attribution platforms, ABM platforms, and data enrichment, as well as for lead scoring, routing, and handoff to sales.

*Canonical: https://forgeworks.ai/glossary#marketing-operations*

### Customer Success Operations (CS Ops) {#customer-success-operations}

**Short:** The function responsible for the systems, data, and processes that support customer retention and expansion.

Customer Success Operations is the function that supports the customer success team with health scoring, renewal forecasting, expansion playbooks, customer journey instrumentation, and the tools and data the CS team uses day-to-day. CS Ops typically owns the customer success platform (Gainsight, ChurnZero, Catalyst, Vitally) and the renewal forecast.

*Canonical: https://forgeworks.ai/glossary#customer-success-operations*

### Go-to-Market (GTM) {#gtm}

**Short:** The combined strategy and execution for acquiring and retaining customers across marketing, sales, and customer success.

Go-to-Market refers to a company's strategy and execution for acquiring and retaining customers. A GTM motion includes the target market and ICP, positioning and messaging, channels (PLG, sales-led, partner-led, etc.), pricing, sales process, marketing programs, and customer success motion. RevOps is the operational backbone that makes a GTM motion executable at scale.

*Canonical: https://forgeworks.ai/glossary#gtm*

### Service Level Agreement (SLA) {#sla}

**Short:** A formal commitment between teams (often marketing and sales) on volume, quality, and timing.

A Service Level Agreement in RevOps context is a formal, measurable commitment between teams — most commonly marketing and sales — covering lead volume, lead quality, follow-up speed, and disposition. SLAs are reviewed regularly and are typically the formal contract that aligns funnel teams around shared metrics.

*Canonical: https://forgeworks.ai/glossary#sla*

### Product-Led Growth (PLG) {#plg}

**Short:** A go-to-market strategy where the product itself drives acquisition, conversion, and expansion.

Product-Led Growth is a go-to-market strategy in which the product itself is the primary driver of acquisition, activation, conversion, and expansion. PLG companies typically offer free or freemium entry, instrument product usage extensively, and rely on PQLs and self-serve conversion rather than (or alongside) traditional sales motion. Notable PLG companies include Slack, Notion, Figma, and HubSpot's free CRM.

*Canonical: https://forgeworks.ai/glossary#plg*

### Sales-Led Growth (SLG) {#slg}

**Short:** A go-to-market strategy where sales reps drive acquisition through outbound and inbound motion.

Sales-Led Growth is a go-to-market motion in which sales reps drive acquisition through prospecting, demos, and structured sales cycles, typical of enterprise and complex B2B sales. SLG and PLG are increasingly hybridized, with PLG signals feeding sales-led motions in 'product-led sales' or 'enterprise PLG' models.

*Canonical: https://forgeworks.ai/glossary#slg*

### Bowtie Model {#bowtie-model}

**Short:** A revenue model extending the funnel through post-sale retention and expansion.

The Bowtie Model reframes the traditional funnel as a symmetrical bowtie: the left side covers acquisition (awareness to closed-won) and the right side covers post-sale value creation (onboarding, retention, expansion, advocacy). Popularized by Winning by Design, it reflects the reality that in recurring-revenue businesses most value is created after the first sale. RevOps uses it to instrument the full customer lifecycle, not just acquisition.

*Canonical: https://forgeworks.ai/glossary#bowtie-model*

### RevOps Tech Stack {#revops-tech-stack}

**Short:** The integrated set of tools that run a company's revenue operations.

The RevOps Tech Stack is the connected collection of systems that power go-to-market — typically a CRM at the center, surrounded by marketing automation, sales engagement, data enrichment, CPQ, customer success, analytics, and a data warehouse. The value comes less from any single tool than from how cleanly they integrate and share data. Rationalizing and integrating the stack is a core RevOps mandate.

*Canonical: https://forgeworks.ai/glossary#revops-tech-stack*

### Revenue Leakage {#revenue-leakage}

**Short:** Revenue lost to preventable process, data, or billing breakdowns.

Revenue Leakage is earned or earnable revenue that a company fails to capture due to operational breakdowns — missed renewals, under-billing, unenforced price increases, expired contracts, or leads that fall through routing gaps. Because it hides inside broken processes and dirty data, leakage is often invisible until it is instrumented. Finding and sealing leakage is one of the highest-ROI focuses of a RevOps team.

*Canonical: https://forgeworks.ai/glossary#revenue-leakage*

## Sales Operations {#sales-operations}

### Pipeline {#pipeline}

**Short:** The aggregate value of open sales opportunities at various stages of the sales process.

Pipeline refers to the collection of open sales opportunities in a CRM, weighted or unweighted by stage probability. Pipeline coverage (the ratio of pipeline value to quota) is a primary leading indicator of attainment; healthy SaaS pipelines typically maintain 3x-5x coverage. Pipeline reviews are the central operating cadence of sales management.

*Canonical: https://forgeworks.ai/glossary#pipeline*

### Pipeline Coverage {#pipeline-coverage}

**Short:** The ratio of open pipeline to the quota or target for a period.

Pipeline Coverage is the ratio of open pipeline value to the quota or revenue target for a given period. A 3:1 ratio means a team has $3 of pipeline for every $1 of quota. Healthy ratios depend on average win rate, sales cycle length, and forecasting accuracy; under-coverage is a leading indicator of missed quota.

*Canonical: https://forgeworks.ai/glossary#pipeline-coverage*

### Sales Cycle {#sales-cycle}

**Short:** The elapsed time from opportunity creation to close.

Sales Cycle is the elapsed time from opportunity creation (or initial qualification) to close, measured in days. Sales cycle length varies dramatically by ACV and segment, with SMB cycles often under 30 days and enterprise cycles spanning multiple quarters. Average cycle length feeds into forecasting and capacity models.

*Canonical: https://forgeworks.ai/glossary#sales-cycle*

### Win Rate {#win-rate}

**Short:** The percentage of qualified opportunities that close as won.

Win Rate is the percentage of qualified opportunities (or opportunities at a defined stage) that close as won. Win rate is segmented by source, segment, rep, competitor, and reason. Win rate analysis is foundational to forecasting, deal coaching, and capacity planning.

*Canonical: https://forgeworks.ai/glossary#win-rate*

### Average Contract Value (ACV) {#acv}

**Short:** The annualized average revenue per contract.

Average Contract Value is the annualized average revenue per contract, normalized to a one-year period. ACV is distinct from TCV (Total Contract Value), which is the full undiscounted value of a multi-year contract. ACV segmentation drives sales motion design, pricing strategy, and territory carving.

*Canonical: https://forgeworks.ai/glossary#acv*

### CPQ (Configure-Price-Quote) {#cpq}

**Short:** Software that automates quote generation for complex products and pricing.

Configure-Price-Quote (CPQ) is a category of software that automates the process of configuring a product, applying pricing rules and discounts, and generating a quote. CPQ enforces approval workflows, prevents pricing errors, and shortens quote cycle time. Leading CPQ platforms include Salesforce CPQ, DealHub, HubSpot Quotes, and Conga.

*Canonical: https://forgeworks.ai/glossary#cpq*

### Sales Enablement {#sales-enablement}

**Short:** The discipline of equipping reps with content, training, and tools to sell effectively.

Sales Enablement is the function responsible for arming sales reps with the content, training, coaching, and tools needed to engage buyers effectively. Enablement deliverables include playbooks, battle cards, onboarding curricula, certification programs, content libraries (Highspot, Seismic, Showpad), and conversation intelligence (Gong, Chorus).

*Canonical: https://forgeworks.ai/glossary#sales-enablement*

### Conversation Intelligence {#conversation-intelligence}

**Short:** Software that records, transcribes, and analyzes sales conversations.

Conversation Intelligence is a category of software that records, transcribes, and analyzes sales calls and meetings. CI platforms (Gong, Chorus, Clari Copilot) surface patterns in language, competitor mentions, talk-to-listen ratios, and risk signals, and feed structured signals back into the CRM. CI is central to modern sales coaching and deal review.

*Canonical: https://forgeworks.ai/glossary#conversation-intelligence*

### Sales Engagement Platform (SEP) {#sales-engagement}

**Short:** Software that automates and orchestrates outbound prospecting cadences.

A Sales Engagement Platform automates and orchestrates outbound sales cadences across email, phone, LinkedIn, and other channels. SEPs (Outreach, Salesloft, Apollo) sit alongside the CRM, sequence prospects through multi-step touch patterns, and surface engagement data back to reps.

*Canonical: https://forgeworks.ai/glossary#sales-engagement*

### Outbound Sales {#outbound}

**Short:** Prospecting motion initiated by the seller, typically via SDRs or BDRs.

Outbound Sales is a prospecting motion in which the seller initiates contact with prospects, typically through cold email, cold call, and LinkedIn outreach. Outbound is usually executed by Sales Development Representatives (SDRs) or Business Development Representatives (BDRs) who pass qualified opportunities to Account Executives (AEs).

*Canonical: https://forgeworks.ai/glossary#outbound*

### Inbound Sales {#inbound}

**Short:** Sales motion in which prospects initiate contact through marketing-driven channels.

Inbound Sales is a motion in which prospects discover and initiate contact with the seller through marketing-driven channels such as content, search, paid ads, or referrals. Inbound is closely linked to demand generation and is typically optimized through SEO, content marketing, and conversion-rate optimization.

*Canonical: https://forgeworks.ai/glossary#inbound*

### Territory Design {#territory-design}

**Short:** The process of dividing the market into balanced segments for reps to own.

Territory Design is the process of dividing a market into segments — by geography, industry, account size, named accounts, or product — and assigning them to reps to own. Good territory design balances opportunity, equity, and coverage. Territory design is typically revisited annually as part of go-to-market planning.

*Canonical: https://forgeworks.ai/glossary#territory-design*

### Capacity Planning {#capacity-planning}

**Short:** The exercise of modeling required headcount to hit a revenue target.

Capacity Planning is the exercise of modeling the headcount required to hit a future revenue target, accounting for ramp time, productivity assumptions, attainment rates, and attrition. Capacity plans are the bridge between top-down revenue targets and bottom-up hiring plans, and are typically jointly owned by Finance and RevOps.

*Canonical: https://forgeworks.ai/glossary#capacity-planning*

### Ramp Time {#ramp-time}

**Short:** The expected time for a new sales rep to reach full productivity.

Ramp Time is the expected period between a sales rep's start date and reaching full productivity (typically defined as carrying a full quota at expected attainment). Ramp time varies by motion: SMB SDRs may ramp in 60-90 days, while enterprise AEs often take 9-12 months. Ramp assumptions are critical inputs to capacity planning.

*Canonical: https://forgeworks.ai/glossary#ramp-time*

### Deal Desk {#deal-desk}

**Short:** A cross-functional function that reviews and approves non-standard deals.

A Deal Desk is a cross-functional group — typically including sales, finance, legal, and operations — that reviews non-standard deals for pricing, terms, discounting, and contract structure. Deal desks accelerate complex deal velocity, enforce policy, and improve margin discipline. Deal desk software (DealHub, PandaDoc, Conga) supports these workflows.

*Canonical: https://forgeworks.ai/glossary#deal-desk*

### Pipeline Stage {#pipeline-stage}

**Short:** A defined point in the sales process used to track deal progression.

A Pipeline Stage (or Deal Stage) is a defined point in the sales process — such as Discovery, Demo, Proposal, Negotiation, Closed Won, Closed Lost — used to track deal progression. Stages have probability weights for forecasting and exit criteria that govern advancement. Pipeline stage definitions are a foundational RevOps deliverable.

*Canonical: https://forgeworks.ai/glossary#pipeline-stage*

### Exit Criteria {#exit-criteria}

**Short:** The conditions that must be met to advance a deal from one stage to the next.

Exit Criteria are the conditions that must be met to advance a deal from one pipeline stage to the next. Well-defined exit criteria force qualification discipline (e.g., 'Champion identified and confirmed' or 'Economic buyer engaged') and improve forecast accuracy by ensuring stage placement reflects deal reality.

*Canonical: https://forgeworks.ai/glossary#exit-criteria*

### Closed-Lost Reason {#closed-lost-reason}

**Short:** A required field capturing the primary reason a deal did not close.

A Closed-Lost Reason is a structured field on a closed-lost deal capturing the primary reason it did not close — competitor selected, no decision, budget, timing, capability gap, etc. Closed-lost reason data is the highest-signal feedback loop for product, marketing, and competitive strategy and is a non-negotiable RevOps field.

*Canonical: https://forgeworks.ai/glossary#closed-lost-reason*

### Sales Velocity {#sales-velocity}

**Short:** A formula estimating how quickly revenue moves through the pipeline.

Sales Velocity measures how fast a team generates revenue, calculated as (number of opportunities × average deal value × win rate) divided by average sales cycle length. It isolates the four levers a RevOps team can pull to grow faster — more deals, bigger deals, higher win rates, or shorter cycles — and is useful for diagnosing which lever offers the most leverage.

*Canonical: https://forgeworks.ai/glossary#sales-velocity*

### Quota Attainment {#quota-attainment}

**Short:** The percentage of their quota a rep or team achieves in a period.

Quota Attainment is the ratio of actual bookings or revenue to assigned quota, measured per rep, team, or segment. Distribution of attainment — not just the average — reveals whether targets are calibrated correctly; healthy orgs see a meaningful share of reps at or above quota. RevOps tracks attainment to inform quota setting, capacity planning, and comp design.

*Canonical: https://forgeworks.ai/glossary#quota-attainment*

### Sales Playbook {#sales-playbook}

**Short:** A documented set of plays, messaging, and process guidance for sales reps.

A Sales Playbook is the codified collection of qualification criteria, talk tracks, objection handling, competitive positioning, and process steps reps use to sell consistently. It operationalizes a chosen sales methodology and is increasingly delivered in-CRM or via enablement tools rather than static documents. RevOps and enablement co-own keeping playbooks current and measuring adoption.

*Canonical: https://forgeworks.ai/glossary#sales-playbook*

### Pipeline Generation (Pipegen) {#pipeline-generation}

**Short:** The ongoing creation of new qualified pipeline to feed future bookings.

Pipeline Generation, often shortened to 'pipegen,' is the set of activities — outbound prospecting, marketing campaigns, partnerships, and events — that create new qualified opportunities. Because bookings lag pipeline creation by a sales cycle, RevOps tracks pipegen as a leading indicator and sets coverage targets to ensure enough pipeline exists to hit future quotas.

*Canonical: https://forgeworks.ai/glossary#pipeline-generation*

### Quote-to-Cash (QTC) {#quote-to-cash}

**Short:** The end-to-end process from generating a quote to collecting payment.

Quote-to-Cash is the full revenue process spanning configuration and quoting (CPQ), contracting and e-signature, order management, billing, and cash collection. It connects sales, finance, and operations, and breakdowns in QTC create revenue leakage, billing errors, and slow cash flow. RevOps designs and instruments QTC to keep it fast, accurate, and auditable.

*Canonical: https://forgeworks.ai/glossary#quote-to-cash*

## Marketing Operations {#marketing-operations}

### Ideal Customer Profile (ICP) {#icp}

**Short:** The set of firmographic and behavioral traits that define a company's best-fit customer.

An Ideal Customer Profile is a documented definition of the type of company that gets the most value from a product and is most valuable to the seller. ICPs typically include firmographics (industry, size, revenue, geography), technographics (tech stack), and behavioral signals (growth stage, hiring patterns). ICP definitions drive targeting in marketing, prospecting in sales, and segmentation in customer success.

*Canonical: https://forgeworks.ai/glossary#icp*

### Total Addressable Market (TAM) {#tam}

**Short:** The total revenue opportunity available for a product or service in a given market.

Total Addressable Market is the total revenue opportunity for a product or service if 100% market share were achieved. TAM is typically segmented into SAM (Serviceable Addressable Market — the portion a company can realistically serve) and SOM (Serviceable Obtainable Market — the portion a company can realistically capture). TAM analysis informs investment, hiring, and territory design.

*Canonical: https://forgeworks.ai/glossary#tam*

### Account-Based Marketing (ABM) {#abm}

**Short:** A B2B strategy targeting specific named accounts with personalized marketing and sales motion.

Account-Based Marketing is a B2B strategy in which marketing and sales jointly target a finite list of named accounts with coordinated, personalized outreach across channels. ABM treats accounts (not leads) as the unit of conversion and is typically supported by ABM platforms (6sense, Demandbase, RollWorks) that surface intent and engagement at the account level.

*Canonical: https://forgeworks.ai/glossary#abm*

### Intent Data {#intent-data}

**Short:** Behavioral signals indicating an account is researching a product category.

Intent Data is a category of behavioral data that indicates an account or prospect is actively researching a topic, product category, or vendor. Intent data comes from third-party providers (Bombora, G2, TrustRadius, 6sense), first-party signals (website visits, content engagement), and review-site activity. Intent feeds into ABM targeting and prioritization.

*Canonical: https://forgeworks.ai/glossary#intent-data*

### Marketing Automation {#marketing-automation}

**Short:** Software that automates email, nurturing, and lead lifecycle workflows.

Marketing Automation is a category of software that automates email campaigns, lead nurturing, behavioral triggers, lead scoring, and lead-to-sales handoff. Leading platforms include HubSpot Marketing Hub, Marketo Engage, Pardot (Account Engagement), and Customer.io.

*Canonical: https://forgeworks.ai/glossary#marketing-automation*

### Demand Generation {#demand-gen}

**Short:** The marketing discipline focused on driving qualified pipeline and revenue.

Demand Generation is the marketing discipline focused on creating measurable pipeline and revenue, encompassing content marketing, paid acquisition, ABM, lifecycle marketing, and pipeline reporting. Demand gen is distinct from broader brand marketing in its direct revenue accountability and is typically owned by a head of demand gen reporting to the CMO.

*Canonical: https://forgeworks.ai/glossary#demand-gen*

### Customer Journey {#customer-journey}

**Short:** The end-to-end set of stages a customer moves through from awareness to advocacy.

The Customer Journey is the end-to-end set of stages a customer moves through with a company — from awareness through consideration, purchase, onboarding, expansion, and advocacy. Customer journey mapping informs lifecycle stages, content strategy, and CS touchpoints, and is a foundational RevOps artifact.

*Canonical: https://forgeworks.ai/glossary#customer-journey*

### Funnel {#funnel}

**Short:** The visual representation of buyer progression from broad awareness to closed customer.

A Funnel is the visual model of buyer progression from broad market awareness through narrowing stages (visitor, lead, MQL, SQL, opportunity, customer). The funnel metaphor structures reporting, conversion-rate analysis, and bottleneck identification. Many companies have evolved to 'flywheel' or 'bowtie' models that include post-sale stages.

*Canonical: https://forgeworks.ai/glossary#funnel*

## Lead Management {#lead-management}

### Marketing Qualified Lead (MQL) {#mql}

**Short:** A lead that has met marketing-defined criteria indicating readiness for sales contact.

A Marketing Qualified Lead is a lead that has met a marketing-defined threshold of engagement or fit and is ready to be passed to sales for outreach. MQL criteria typically combine demographic fit (ICP match) and behavioral signals (content downloads, pricing page visits, demo requests). An MQL is the formal handoff point between marketing and sales in most B2B funnels.

*Canonical: https://forgeworks.ai/glossary#mql*

### Sales Qualified Lead (SQL) {#sql-lead}

**Short:** A lead that sales has accepted and qualified as a real opportunity.

A Sales Qualified Lead is an MQL that a sales rep has worked, qualified, and accepted as a real opportunity worth pursuing. SQL criteria typically include verified ICP fit, identified pain or initiative, available budget, and authority to buy. Note: SQL (lead) is different from SQL (the database language).

*Canonical: https://forgeworks.ai/glossary#sql-lead*

### Sales Accepted Lead (SAL) {#sal}

**Short:** An MQL that a sales rep has confirmed meets accepted criteria and will work.

A Sales Accepted Lead is the formal handoff state between marketing and sales where a sales rep has reviewed an MQL and accepted it as worth working, but has not yet qualified it as an opportunity. SAL serves as a service-level agreement checkpoint to ensure marketing is sending workable leads.

*Canonical: https://forgeworks.ai/glossary#sal*

### Product Qualified Lead (PQL) {#pql}

**Short:** A user whose in-product behavior signals readiness to buy or expand.

A Product Qualified Lead is a user whose product usage and behavior indicate they are a qualified buying opportunity. PQLs are central to product-led growth (PLG) motions, where free trial usage, feature engagement, or account-level activity signal expansion or upgrade readiness. PQL criteria are defined by data joined from the product, billing, and CRM.

*Canonical: https://forgeworks.ai/glossary#pql*

### Lead Routing {#lead-routing}

**Short:** The automated process of assigning inbound leads to the right rep or queue.

Lead Routing is the automated assignment of inbound leads to the correct sales rep, SDR, or queue based on rules such as territory, account ownership, segment, language, or round-robin. Modern lead routing tools (Chili Piper, Default, Distribute) connect form submissions or CRM events directly to scheduling, eliminating speed-to-lead delay.

*Canonical: https://forgeworks.ai/glossary#lead-routing*

### Speed to Lead {#speed-to-lead}

**Short:** The elapsed time between a lead expressing interest and a rep contacting them.

Speed to Lead is the elapsed time between a prospect expressing interest (form submission, demo request, chat) and a sales rep making contact. Research consistently shows that speed to lead under five minutes dramatically increases conversion rates. Modern RevOps stacks use instant lead routing and scheduling tools to compress speed to lead from hours to seconds.

*Canonical: https://forgeworks.ai/glossary#speed-to-lead*

### Round-Robin Routing {#round-robin}

**Short:** A lead distribution rule that cycles inbound leads evenly through a pool of reps.

Round-robin routing distributes inbound leads evenly across a defined pool of reps in rotating order. Round-robin can be weighted (by capacity or seniority), filtered (by territory or segment), or paused (when a rep is out of office). It is the most common distribution method for inbound SMB and mid-market motions.

*Canonical: https://forgeworks.ai/glossary#round-robin*

### Lead Scoring {#lead-scoring}

**Short:** A model that ranks leads by likelihood to convert.

Lead Scoring is a model that ranks leads by their likelihood to convert into customers, combining demographic fit (ICP match) and behavioral signals (engagement, intent). Lead scores can be rule-based (handcrafted point systems) or predictive (machine learning models trained on historical conversion data). Lead scores feed into MQL definitions, routing, and prioritization.

*Canonical: https://forgeworks.ai/glossary#lead-scoring*

### Lifecycle Stage {#lifecycle-stage}

**Short:** A standardized property tracking where a contact or company is in the funnel.

A Lifecycle Stage is a standardized CRM property that tracks where a contact or company sits in the buyer journey — typically Subscriber, Lead, MQL, SQL, Opportunity, Customer, Evangelist. Lifecycle stage governs handoffs between teams, segmentation for reporting, and downstream automation. Lifecycle stage design is a foundational RevOps decision.

*Canonical: https://forgeworks.ai/glossary#lifecycle-stage*

### Sales Development Representative (SDR / BDR) {#sdr-bdr}

**Short:** A rep focused on qualifying inbound leads and generating outbound pipeline.

A Sales Development Representative (SDR) or Business Development Representative (BDR) is a specialized rep whose job is to qualify inbound interest and prospect outbound to create pipeline, then hand qualified opportunities to Account Executives. SDRs typically handle inbound follow-up while BDRs focus on outbound, though usage varies. RevOps owns their routing, activity metrics, and handoff SLAs.

*Canonical: https://forgeworks.ai/glossary#sdr-bdr*

### Account Executive (AE) {#account-executive}

**Short:** The rep who owns qualifying, advancing, and closing sales opportunities.

An Account Executive is the quota-carrying rep responsible for running discovery, building business cases, managing the deal cycle, and closing opportunities sourced by SDRs, marketing, or their own prospecting. AEs own pipeline accuracy and forecast commits for their deals. RevOps supports them with playbooks, deal desk, and clean pipeline reporting.

*Canonical: https://forgeworks.ai/glossary#account-executive*

### Lead-to-Account Matching (L2A) {#lead-to-account-matching}

**Short:** Linking inbound leads to their corresponding account records automatically.

Lead-to-Account Matching connects incoming person-level leads to the correct company account in the CRM, enabling account-based routing, deduplication, and accurate ABM reporting. Without it, leads sit disconnected from account ownership and buying-group context. Tools like LeanData automate L2A as the foundation for routing and account-based plays.

*Canonical: https://forgeworks.ai/glossary#lead-to-account-matching*

### Discovery Call {#discovery-call}

**Short:** An early sales conversation to uncover a prospect's needs, pain, and fit.

A Discovery Call is the structured early-stage conversation in which a rep uncovers a prospect's pain points, goals, decision process, and budget to determine fit and qualify the opportunity. Strong discovery, often guided by a methodology like MEDDPICC, drives accurate qualification and forecasting. RevOps captures discovery outcomes as structured CRM fields to power pipeline inspection.

*Canonical: https://forgeworks.ai/glossary#discovery-call*

## CRM & Systems {#crm-systems}

### CRM (Customer Relationship Management) {#crm}

**Short:** Software that centralizes customer data and manages sales, marketing, and service workflows.

A Customer Relationship Management system centralizes data about customers, prospects, deals, and interactions, and provides workflows for sales, marketing, and customer service teams. Leading B2B CRMs include HubSpot, Salesforce, and Zoho. The CRM is the system of record at the center of every RevOps stack.

*Canonical: https://forgeworks.ai/glossary#crm*

### HubSpot {#hubspot}

**Short:** An all-in-one CRM platform with Marketing, Sales, Service, and Operations Hubs.

HubSpot is a CRM platform consisting of Marketing Hub, Sales Hub, Service Hub, Operations Hub, and Content Hub, all built on a unified data model. HubSpot is widely adopted by SMB and mid-market B2B companies for its ease of use and integrated marketing-sales-service experience. Forgeworks is a certified HubSpot Solutions Partner.

*Canonical: https://forgeworks.ai/glossary#hubspot*

### Salesforce {#salesforce}

**Short:** The dominant enterprise CRM platform with Sales, Service, Marketing, and Platform clouds.

Salesforce is the largest enterprise CRM platform, comprising Sales Cloud, Service Cloud, Marketing Cloud, Commerce Cloud, and the Lightning Platform. Salesforce is highly customizable via Apex, Flows, and managed packages from the AppExchange, making it the default choice for complex enterprise sales motions. Forgeworks delivers Salesforce implementation, admin support, and Salesforce-to-HubSpot migration.

*Canonical: https://forgeworks.ai/glossary#salesforce*

### Zoho CRM {#zoho-crm}

**Short:** A cost-effective CRM platform popular with SMB and international markets.

Zoho CRM is a customer relationship management platform within the broader Zoho One suite. Zoho is known for its low cost, broad feature set, and strong adoption in SMB and international markets. Forgeworks provides Zoho implementation, customization, and integration.

*Canonical: https://forgeworks.ai/glossary#zoho-crm*

### Salesforce-to-HubSpot Migration {#salesforce-to-hubspot-migration}

**Short:** The process of moving CRM data, workflows, and reporting from Salesforce to HubSpot.

A Salesforce-to-HubSpot migration is the process of moving CRM data, custom objects, workflows, automation, integrations, and reporting from Salesforce to HubSpot. A full migration typically takes 4 to 12 weeks and covers data mapping, schema translation, workflow rebuild, integration reconnection, reporting reconstruction, and rep training. Salesforce-to-HubSpot migration is one of Forgeworks' most common engagements.

*Canonical: https://forgeworks.ai/glossary#salesforce-to-hubspot-migration*

### Custom Object {#custom-object}

**Short:** A CRM data type defined beyond the standard objects (contacts, companies, deals).

A Custom Object is a CRM-defined data type that extends the standard data model (typically contacts, companies, deals, tickets). Custom objects model business-specific entities such as subscriptions, properties, vehicles, or projects, and connect to standard objects via associations. Custom object design is a foundational decision in any CRM implementation.

*Canonical: https://forgeworks.ai/glossary#custom-object*

### Workflow Automation {#workflow-automation}

**Short:** Rule-based or trigger-based sequences that automate CRM actions.

Workflow Automation in CRMs refers to rule-based or trigger-based sequences that automatically execute actions — such as updating a property, sending an email, creating a task, or notifying a rep — when defined criteria are met. Examples include HubSpot Workflows, Salesforce Flows, and Zoho Blueprints. Workflows are the primary lever for scaling RevOps without scaling headcount.

*Canonical: https://forgeworks.ai/glossary#workflow-automation*

### Account Hierarchy {#account-hierarchy}

**Short:** A CRM structure linking parent and child companies to reflect corporate structure.

An Account Hierarchy is a CRM structure that links parent and child companies to mirror real-world corporate structure, enabling roll-up reporting, cross-subsidiary visibility, and ownership rules. Account hierarchy design is a common pain point in M&A and enterprise CRM implementations.

*Canonical: https://forgeworks.ai/glossary#account-hierarchy*

### API Integration {#api-integration}

**Short:** Custom code that connects two systems via their application programming interfaces.

An API Integration is custom-built connectivity between two systems using their published APIs, typically when off-the-shelf connectors do not exist or cannot meet requirements. API integrations support real-time data sync, complex transformations, and bespoke business logic. Forgeworks builds custom API integrations on top of the HubSpot, Salesforce, and other CRM APIs.

*Canonical: https://forgeworks.ai/glossary#api-integration*

### iPaaS (Integration Platform as a Service) {#ipaas}

**Short:** Middleware platforms that orchestrate integrations between SaaS applications.

Integration Platform as a Service is a category of middleware that orchestrates data flows and workflows between SaaS applications without custom code. Leading iPaaS platforms include Workato, Zapier, Make, Tray.io, and Boomi. iPaaS is well-suited for medium-complexity integrations; high-complexity or high-volume cases typically warrant custom API work.

*Canonical: https://forgeworks.ai/glossary#ipaas*

### Webhook {#webhook}

**Short:** A real-time HTTP callback fired by one system when an event occurs.

A Webhook is a real-time HTTP POST callback fired by one system to another when an event occurs (e.g., 'contact created in HubSpot') — enabling event-driven integrations without polling. Webhooks are foundational to modern real-time CRM integrations and are supported natively by HubSpot, Salesforce, Stripe, and most modern SaaS tools.

*Canonical: https://forgeworks.ai/glossary#webhook*

### AI Agent {#ai-agent}

**Short:** A software agent powered by large language models that performs multi-step tasks autonomously.

An AI Agent is a software agent powered by a large language model (LLM) that can plan, take actions, and use tools to complete multi-step tasks autonomously. In RevOps, AI agents are deployed for lead enrichment, account research, meeting summarization, CRM data entry, and intelligent routing. Forgeworks builds custom AI agents on top of the GTM stack as a default capability.

*Canonical: https://forgeworks.ai/glossary#ai-agent*

## RevOps Tools {#revops-tools}

### Outreach {#outreach}

**Short:** A sales engagement platform for automating and tracking multi-step outbound sequences.

Outreach is a leading sales engagement platform (SEP) that lets reps build and execute multi-channel sequences across email, calls, and social, while capturing activity back to the CRM. It provides automation, analytics, and AI-assisted guidance to scale outbound and follow-up. RevOps teams own its sequence governance, CRM sync, and reporting integration.

*Canonical: https://forgeworks.ai/glossary#outreach*

### Salesloft {#salesloft}

**Short:** A sales engagement platform for orchestrating outbound cadences and buyer interactions.

Salesloft is a sales engagement platform that helps reps manage cadences, calls, emails, and deal workflows in one place, with conversation intelligence and analytics built in. It competes directly with Outreach in the SEP category. RevOps configures cadence templates, CRM field mapping, and activity reporting to keep pipeline data clean.

*Canonical: https://forgeworks.ai/glossary#salesloft*

### Apollo.io {#apollo}

**Short:** A combined sales intelligence database and engagement platform for prospecting.

Apollo.io pairs a large B2B contact and company database with built-in sales engagement and enrichment tooling, letting teams find, enrich, and sequence prospects in one platform. It is popular with SMB and mid-market sales orgs for combining data and outreach affordably. RevOps uses it for list building, CRM enrichment, and outbound automation.

*Canonical: https://forgeworks.ai/glossary#apollo*

### ZoomInfo {#zoominfo}

**Short:** A B2B data platform providing contact, company, and intent data for GTM teams.

ZoomInfo is an enterprise B2B intelligence platform supplying firmographic, contact, technographic, and intent data used to build target lists, enrich the CRM, and trigger outreach. RevOps teams integrate it for data enrichment, lead routing inputs, and territory planning. Data hygiene processes govern how its data is matched and written to the CRM.

*Canonical: https://forgeworks.ai/glossary#zoominfo*

### Clay {#clay}

**Short:** A data-enrichment and automation tool that combines many data sources with AI.

Clay is a spreadsheet-style automation platform that aggregates dozens of enrichment providers and uses AI to research, enrich, and personalize prospect data at scale. RevOps and GTM engineering teams use it to build enriched lists, waterfall-enrich records across multiple sources, and feed personalized signals into outbound. It has become a centerpiece of modern 'GTM engineering' workflows.

*Canonical: https://forgeworks.ai/glossary#clay*

### Gong {#gong}

**Short:** A revenue intelligence platform that records and analyzes customer conversations.

Gong is a revenue intelligence platform that captures and analyzes sales calls, emails, and meetings to surface deal risks, coaching opportunities, and market insights. Its conversation intelligence helps managers coach reps and gives RevOps objective data on what happens inside deals. Gong data increasingly feeds forecasting and deal-inspection workflows.

*Canonical: https://forgeworks.ai/glossary#gong*

### Chili Piper {#chili-piper}

**Short:** A lead routing and scheduling platform that books inbound prospects instantly.

Chili Piper is an inbound conversion platform that qualifies, routes, and schedules prospects in real time from forms, chat, or campaigns, eliminating speed-to-lead delay. It connects form submissions directly to the right rep's calendar based on routing rules. RevOps configures its routing logic, qualification, and CRM integration; Forgeworks is a Chili Piper implementation partner.

*Canonical: https://forgeworks.ai/glossary#chili-piper*

### LeanData {#leandata}

**Short:** A lead-to-account matching and routing platform built natively on Salesforce.

LeanData is a revenue orchestration platform best known for lead-to-account matching and flow-based routing inside Salesforce. It connects inbound leads to the correct accounts, owners, and queues, and automates round-robin assignment and SLA enforcement. RevOps teams use it to ensure leads reach the right rep quickly and that attribution stays accurate.

*Canonical: https://forgeworks.ai/glossary#leandata*

### Marketo {#marketo}

**Short:** An enterprise marketing automation platform now part of Adobe.

Marketo (Adobe Marketo Engage) is an enterprise marketing automation platform used for email campaigns, lead nurturing, scoring, and program management. It is common in larger B2B organizations with complex demand-generation needs. Marketing Operations owns its program architecture, lead scoring, and the sync between Marketo and the CRM.

*Canonical: https://forgeworks.ai/glossary#marketo*

### Pardot (Marketing Cloud Account Engagement) {#pardot}

**Short:** Salesforce's B2B marketing automation tool, now branded Account Engagement.

Pardot, now branded Marketing Cloud Account Engagement, is Salesforce's B2B marketing automation platform for email nurturing, lead scoring, and engagement programs with native Salesforce integration. It is a natural fit for organizations standardized on Salesforce. MOps teams manage its scoring models, completion actions, and the connector that syncs prospects to Salesforce.

*Canonical: https://forgeworks.ai/glossary#pardot*

### Stripe {#stripe}

**Short:** A payments and billing platform widely used for SaaS subscriptions and revenue data.

Stripe is a payments infrastructure platform that handles online payments, subscription billing, invoicing, and revenue reporting. For SaaS RevOps, Stripe is often the system of record for billing and MRR, and integrating it cleanly with the CRM and data warehouse is essential for accurate ARR, churn, and expansion reporting.

*Canonical: https://forgeworks.ai/glossary#stripe*

### Zapier {#zapier}

**Short:** A no-code automation tool that connects apps through trigger-and-action workflows.

Zapier is a no-code integration platform that links thousands of apps via 'Zaps' — automated workflows triggered by an event in one tool that perform actions in others. RevOps teams use it for lightweight integrations and glue automations between systems that lack native connectors. For higher-volume or more complex needs, teams graduate to an iPaaS or custom API integration.

*Canonical: https://forgeworks.ai/glossary#zapier*

### Segment {#segment}

**Short:** A customer data platform that collects and routes behavioral data to other tools.

Segment (Twilio Segment) is a customer data platform (CDP) that captures customer and product events once and routes them to analytics, marketing, and data-warehouse destinations. It standardizes tracking so teams avoid implementing tracking separately in every tool. RevOps and data teams use it to unify product behavior with CRM data for PQL scoring and lifecycle automation.

*Canonical: https://forgeworks.ai/glossary#segment*

### Snowflake {#snowflake}

**Short:** A cloud data warehouse that centralizes data for analytics and reverse ETL.

Snowflake is a cloud data platform widely used as the central data warehouse where CRM, product, billing, and marketing data are unified for analytics. In modern RevOps stacks, Snowflake serves as the single source of truth that BI tools query and that reverse-ETL tools sync back into operational systems. It underpins advanced reporting, attribution, and data-activation workflows.

*Canonical: https://forgeworks.ai/glossary#snowflake*

### Gainsight {#gainsight}

**Short:** A customer success platform for health scoring, renewals, and expansion.

Gainsight is a leading customer success platform that centralizes account health scores, renewal forecasting, customer journey playbooks, and CS analytics. CS Ops teams use it to operationalize retention and expansion motions and to give leadership a forecast of renewal risk. It integrates with the CRM, product analytics, and support systems to compute health.

*Canonical: https://forgeworks.ai/glossary#gainsight*

### QuotaPath {#quotapath}

**Short:** A sales commission tracking and compensation management platform.

QuotaPath is a commission tracking and incentive compensation platform that automates the calculation, visibility, and payout of variable pay tied to CRM deal data. It replaces error-prone spreadsheets, gives reps real-time earnings visibility, and gives finance auditable comp records. RevOps configures its plan logic and CRM sync; Forgeworks is a QuotaPath partner.

*Canonical: https://forgeworks.ai/glossary#quotapath*

### DealHub {#dealhub}

**Short:** A CPQ and revenue-workflow platform for quoting, proposals, and contracts.

DealHub is a configure-price-quote (CPQ) and revenue-amplification platform that handles quoting, proposals, e-signature, and subscription management within the sales workflow. It streamlines quote-to-cash by guiding reps through approved pricing and generating compliant documents. RevOps owns its product catalog, pricing rules, and approval workflows; Forgeworks is a DealHub partner.

*Canonical: https://forgeworks.ai/glossary#dealhub*

## Data & Reporting {#data-reporting}

### Attribution {#attribution}

**Short:** The methodology for assigning revenue credit to marketing and sales touchpoints.

Marketing Attribution is the methodology for assigning credit for closed revenue to the marketing and sales touchpoints that influenced the deal. Common models include first-touch, last-touch, linear, time-decay, U-shaped, W-shaped, and data-driven (algorithmic) attribution. Attribution drives marketing budget allocation and channel ROI analysis.

*Canonical: https://forgeworks.ai/glossary#attribution*

### Multi-Touch Attribution (MTA) {#multi-touch-attribution}

**Short:** An attribution methodology that distributes credit across multiple touchpoints in the buyer journey.

Multi-Touch Attribution is an attribution methodology that distributes revenue credit across the multiple marketing and sales touchpoints that influenced a deal, rather than assigning all credit to a single touch. MTA models include linear, time-decay, U-shaped, W-shaped, and algorithmic. MTA is typically operationalized through CRM custom objects or dedicated attribution platforms.

*Canonical: https://forgeworks.ai/glossary#multi-touch-attribution*

### Data Warehouse {#data-warehouse}

**Short:** A centralized analytical database for consolidated company data.

A Data Warehouse is a centralized analytical database designed for reporting and analytics across all company data sources — CRM, billing, product, marketing, finance. Modern cloud data warehouses include Snowflake, BigQuery, Databricks, and Redshift. RevOps teams use the data warehouse as the source of truth for cross-system metrics.

*Canonical: https://forgeworks.ai/glossary#data-warehouse*

### Reverse ETL {#reverse-etl}

**Short:** The practice of syncing data from the warehouse back into operational tools like CRM.

Reverse ETL is the practice of extracting data from a cloud data warehouse and loading it into operational systems such as CRMs, ad platforms, and customer success tools. Reverse ETL inverts the traditional ETL flow (sources to warehouse) and makes warehouse-derived data — such as product usage scores or PQL signals — actionable in the tools sales and marketing use daily. Leading tools include Hightouch and Census.

*Canonical: https://forgeworks.ai/glossary#reverse-etl*

### Source of Truth {#source-of-truth}

**Short:** The authoritative system for a given piece of data across the org.

A Source of Truth is the system designated as authoritative for a given piece of data — such as the CRM for account data, the billing system for revenue, or the data warehouse for combined metrics. Defining and enforcing a single source of truth per data domain is foundational to clean reporting and is a primary deliverable of any RevOps engagement.

*Canonical: https://forgeworks.ai/glossary#source-of-truth*

### BI (Business Intelligence) {#bi}

**Short:** Tools and processes that turn raw data into dashboards and decisions.

Business Intelligence refers to the tools, processes, and practices that turn raw data into reports, dashboards, and insights to support decision-making. Modern BI tools include Looker, Tableau, Power BI, Mode, Sigma, and HubSpot Data Studio. BI sits on top of the data warehouse in modern stacks.

*Canonical: https://forgeworks.ai/glossary#bi*

### Deduplication {#deduplication}

**Short:** The process of identifying and merging duplicate records in a CRM.

Deduplication is the process of identifying duplicate records (typically contacts, companies, or leads) in a CRM and merging or eliminating them. Deduplication relies on matching keys such as email, domain, or fuzzy match algorithms. Persistent deduplication is supported by tools like Cloudingo, Insycle, and native HubSpot/Salesforce merge functionality.

*Canonical: https://forgeworks.ai/glossary#deduplication*

### Data Enrichment {#data-enrichment}

**Short:** Augmenting CRM records with third-party firmographic, technographic, or contact data.

Data Enrichment is the practice of augmenting CRM records with third-party data — firmographic (industry, size, revenue), technographic (tech stack), contact (titles, emails, phone), or intent. Leading enrichment providers include Clearbit, ZoomInfo, Apollo, and Cognism. Enrichment fuels segmentation, scoring, and routing.

*Canonical: https://forgeworks.ai/glossary#data-enrichment*

### ETL (Extract, Transform, Load) {#etl}

**Short:** The process of moving data from sources into a warehouse, transforming it en route.

ETL stands for Extract, Transform, Load — the pattern of pulling data from source systems, transforming it into a consistent model, and loading it into a destination like a data warehouse. Its modern variant, ELT, loads raw data first and transforms it inside the warehouse. ETL pipelines are the backbone of unified RevOps reporting and feed the reverse-ETL syncs that push data back to operational tools.

*Canonical: https://forgeworks.ai/glossary#etl*

### Customer Data Platform (CDP) {#cdp}

**Short:** A system that unifies customer data from many sources into persistent profiles.

A Customer Data Platform unifies first-party customer and behavioral data from across tools into persistent, single-customer profiles that other systems can act on. CDPs (such as Segment) standardize event tracking and audience building, powering personalization, PQL scoring, and lifecycle automation. They sit between data collection and activation in the RevOps stack.

*Canonical: https://forgeworks.ai/glossary#cdp*

### Data Hygiene {#data-hygiene}

**Short:** The ongoing practice of keeping CRM and GTM data accurate, complete, and consistent.

Data Hygiene is the continuous discipline of preventing and correcting bad data — duplicates, missing fields, stale records, and inconsistent formatting — across the CRM and GTM systems. Poor hygiene breaks routing, reporting, scoring, and forecasting. RevOps enforces hygiene through validation rules, deduplication, enrichment, and governance, and it is one of the most common engagements for outside RevOps teams.

*Canonical: https://forgeworks.ai/glossary#data-hygiene*

### Data Governance {#data-governance}

**Short:** The policies and ownership defining how data is created, maintained, and used.

Data Governance is the framework of standards, ownership, and processes that define how GTM data is created, formatted, secured, and maintained. It covers field definitions, picklist values, naming conventions, access controls, and who is accountable for each data domain. Strong governance is what keeps data hygiene durable rather than a one-time cleanup.

*Canonical: https://forgeworks.ai/glossary#data-governance*

### Cohort Analysis {#cohort-analysis}

**Short:** Grouping customers by a shared start period to analyze behavior over time.

Cohort Analysis groups customers by a common starting characteristic — typically signup or close month — and tracks how each group's retention, expansion, or revenue evolves over time. It reveals whether newer customers behave better or worse than older ones, isolating the impact of product, pricing, or onboarding changes. It is a core technique for understanding SaaS retention and LTV.

*Canonical: https://forgeworks.ai/glossary#cohort-analysis*

### Conversion Rate {#conversion-rate}

**Short:** The percentage of records that advance from one funnel stage to the next.

Conversion Rate is the share of records that move from one stage to the next — visitor-to-lead, lead-to-MQL, MQL-to-SQL, or opportunity-to-close. Stage-by-stage conversion analysis exposes the funnel's biggest bottlenecks and informs where to invest. Accurate conversion reporting depends on clean stage definitions and consistent timestamping in the CRM.

*Canonical: https://forgeworks.ai/glossary#conversion-rate*

### Single-Touch Attribution {#single-touch-attribution}

**Short:** Crediting one touchpoint — usually the first or last — for a conversion.

Single-Touch Attribution assigns 100% of the credit for a conversion to a single interaction: first-touch models credit the channel that first acquired the lead, while last-touch models credit the final interaction before conversion. These models are simple to implement but ignore the full buying journey, which is why many teams adopt multi-touch attribution for complex B2B sales.

*Canonical: https://forgeworks.ai/glossary#single-touch-attribution*

## SaaS Metrics {#saas-metrics}

### Customer Acquisition Cost (CAC) {#cac}

**Short:** The total sales and marketing cost to acquire one new customer.

Customer Acquisition Cost is the fully loaded sales and marketing expense required to acquire one new customer, typically calculated over a defined period. CAC is most useful when paired with LTV (lifetime value); the LTV:CAC ratio is a primary measure of business efficiency, with 3:1 considered healthy in SaaS.

*Canonical: https://forgeworks.ai/glossary#cac*

### Lifetime Value (LTV) {#ltv}

**Short:** The total revenue a customer is expected to generate over their relationship.

Customer Lifetime Value is the total revenue (or gross profit) a customer is expected to generate over the lifetime of their relationship with a company. LTV is calculated from average revenue per account, gross margin, and customer retention rate. LTV:CAC ratio drives investment decisions in acquisition channels.

*Canonical: https://forgeworks.ai/glossary#ltv*

### Annual Recurring Revenue (ARR) {#arr}

**Short:** The annualized value of a subscription business's recurring contracts.

Annual Recurring Revenue is the annualized value of all active subscription contracts at a given point in time. ARR excludes one-time revenue (services, setup fees) and is the primary metric for SaaS valuation. ARR is decomposed into New ARR, Expansion ARR, Contraction ARR, and Churned ARR.

*Canonical: https://forgeworks.ai/glossary#arr*

### Monthly Recurring Revenue (MRR) {#mrr}

**Short:** The monthly equivalent of recurring subscription revenue.

Monthly Recurring Revenue is the monthly normalized value of all active subscription contracts. MRR is often preferred over ARR for early-stage or month-to-month businesses. Like ARR, MRR decomposes into New, Expansion, Contraction, and Churn.

*Canonical: https://forgeworks.ai/glossary#mrr*

### Net Revenue Retention (NRR) {#nrr}

**Short:** The percentage of revenue retained from existing customers, including expansion.

Net Revenue Retention is the percentage of recurring revenue retained from existing customers over a period, including expansion and net of contraction and churn. NRR above 100% means existing customers grew revenue more than offset losses. NRR is a top-tier SaaS health metric, with best-in-class companies above 120%.

*Canonical: https://forgeworks.ai/glossary#nrr*

### Gross Revenue Retention (GRR) {#grr}

**Short:** The percentage of revenue retained from existing customers, excluding expansion.

Gross Revenue Retention is the percentage of recurring revenue retained from existing customers, accounting only for churn and contraction (not expansion). GRR cannot exceed 100% and is a pure measure of customer retention. Best-in-class SaaS companies maintain GRR above 90%.

*Canonical: https://forgeworks.ai/glossary#grr*

### Churn Rate {#churn-rate}

**Short:** The percentage of customers or revenue lost over a given period.

Churn Rate is the percentage of customers (logo churn) or revenue (revenue churn) lost over a defined period. Churn can be voluntary (customer cancellation) or involuntary (payment failure). Churn analysis is core to retention strategy and is typically segmented by cohort, segment, and reason code.

*Canonical: https://forgeworks.ai/glossary#churn-rate*

### Average Revenue Per Account (ARPA / ARPU) {#arpa}

**Short:** The average recurring revenue generated per customer account over a period.

Average Revenue Per Account (ARPA), sometimes called Average Revenue Per User (ARPU), is total recurring revenue divided by the number of active accounts in a period. It is a core SaaS efficiency metric used to track monetization, segment customers, and model the revenue impact of pricing and packaging changes. Rising ARPA usually signals successful upsell, expansion, or a shift upmarket.

*Canonical: https://forgeworks.ai/glossary#arpa*

### Rule of 40 {#rule-of-40}

**Short:** A SaaS health benchmark stating that growth rate plus profit margin should exceed 40%.

The Rule of 40 is a benchmark for SaaS health holding that a company's year-over-year revenue growth rate plus its profit margin (often EBITDA or free-cash-flow margin) should sum to at least 40%. It frames the trade-off between growth and profitability: a company growing 60% can afford to burn at -20% margin, while a 10%-growth company should be ~30% profitable. Investors use it to gauge whether growth is being bought at a sustainable cost.

*Canonical: https://forgeworks.ai/glossary#rule-of-40*

### SaaS Magic Number {#magic-number}

**Short:** A sales-efficiency ratio of new ARR generated to sales and marketing spend.

The Magic Number measures go-to-market efficiency by dividing net new ARR added in a period by the sales and marketing spend of the prior period. A result above 0.75 generally indicates efficient, scalable acquisition that justifies further investment; below 0.5 suggests the GTM motion needs fixing before adding spend. It is a fast proxy for whether a company should press the accelerator on growth.

*Canonical: https://forgeworks.ai/glossary#magic-number*

### CAC Payback Period {#cac-payback-period}

**Short:** The number of months it takes to recoup the cost of acquiring a customer.

CAC Payback Period is the time, usually in months, required to recover the fully loaded cost of acquiring a customer from that customer's gross-margin-adjusted recurring revenue. It is calculated as CAC divided by (monthly recurring revenue × gross margin). Shorter paybacks (often targeted under 12 months for SMB and under 24 for enterprise) mean faster capital recycling and lower funding needs.

*Canonical: https://forgeworks.ai/glossary#cac-payback-period*

### LTV:CAC Ratio {#ltv-cac-ratio}

**Short:** The ratio of customer lifetime value to customer acquisition cost.

The LTV:CAC Ratio compares the lifetime value of a customer to the cost of acquiring them, expressed as a multiple. A ratio around 3:1 is commonly considered healthy for B2B SaaS — high enough to be profitable, but not so high that the company is under-investing in growth. A ratio below 1:1 means each customer is acquired at a loss.

*Canonical: https://forgeworks.ai/glossary#ltv-cac-ratio*

### SaaS Quick Ratio {#saas-quick-ratio}

**Short:** A measure of growth efficiency comparing revenue gained to revenue lost.

The SaaS Quick Ratio divides revenue gained (new plus expansion MRR) by revenue lost (churned plus contraction MRR) in a period. It captures how efficiently a company grows net of losses: a quick ratio of 4 means $4 of new and expansion revenue for every $1 lost. It surfaces leaky-bucket problems that top-line growth numbers can mask.

*Canonical: https://forgeworks.ai/glossary#saas-quick-ratio*

### Burn Rate {#burn-rate}

**Short:** The rate at which a company spends its cash reserves, usually per month.

Burn Rate is the monthly net cash a company consumes to operate. Gross burn is total monthly operating cash outflow; net burn is gross burn minus cash inflows from revenue. Burn rate combined with cash on hand determines runway — the number of months before a company must raise more capital or reach profitability — making it a primary board-level metric for venture-backed companies.

*Canonical: https://forgeworks.ai/glossary#burn-rate*

### Bookings {#bookings}

**Short:** The total contractual value a customer commits to when signing a deal.

Bookings represent the value a customer has contractually committed to, recognized at the moment a contract is signed — distinct from revenue (recognized as the service is delivered) and billings (invoiced amounts). Bookings are a forward-looking demand signal often reported as new, renewal, and expansion bookings. Misreporting bookings as revenue is a common source of confusion in SaaS reporting.

*Canonical: https://forgeworks.ai/glossary#bookings*

### Billings {#billings}

**Short:** The amount invoiced to customers in a period, regardless of revenue recognition.

Billings is the total amount invoiced to customers during a period and is closely tied to cash collection. It is calculated from revenue plus the change in deferred revenue. Because billings often lead recognized revenue, investors watch billings growth as an early indicator of future revenue and of a company's cash-generation health.

*Canonical: https://forgeworks.ai/glossary#billings*

### Total Contract Value (TCV) {#tcv}

**Short:** The total value of a contract across its full term, including one-time fees.

Total Contract Value is the entire value of a customer contract over its full duration, including recurring subscription fees, one-time setup or services fees, and any committed expansion. TCV differs from Annual Contract Value (ACV), which normalizes value to a single year. TCV is used to size multi-year deals and to compensate reps on full deal value.

*Canonical: https://forgeworks.ai/glossary#tcv*

### Expansion Revenue {#expansion-revenue}

**Short:** Additional recurring revenue from existing customers via upsell or cross-sell.

Expansion Revenue is the incremental recurring revenue generated from existing customers through upsells (higher tiers, more seats), cross-sells (additional products), and usage growth. It is the engine of Net Revenue Retention above 100% and is typically the most capital-efficient revenue a SaaS company can generate, since it requires no new customer acquisition.

*Canonical: https://forgeworks.ai/glossary#expansion-revenue*

### Logo Retention {#logo-retention}

**Short:** The percentage of customer accounts retained over a period, regardless of revenue.

Logo Retention (the inverse of logo churn) measures the share of customer accounts — 'logos' — retained over a period, counting each customer equally regardless of contract size. It is distinct from revenue retention: a company can have high logo churn among small accounts while maintaining strong net revenue retention from large ones. Tracking both reveals whether churn is concentrated by segment.

*Canonical: https://forgeworks.ai/glossary#logo-retention*

### Gross Margin {#gross-margin}

**Short:** Revenue remaining after the cost of delivering the service, as a percentage.

Gross Margin is revenue minus cost of goods sold (COGS) divided by revenue, expressed as a percentage. For SaaS, COGS includes hosting, support, and delivery costs. Healthy software gross margins typically run 70–85%; the figure is foundational because nearly every efficiency metric (CAC payback, LTV, Rule of 40) is adjusted by gross margin to reflect true economics.

*Canonical: https://forgeworks.ai/glossary#gross-margin*

### Net Promoter Score (NPS) {#nps}

**Short:** A loyalty metric based on how likely customers are to recommend a product.

Net Promoter Score gauges customer loyalty by asking how likely a customer is to recommend the product on a 0–10 scale, then subtracting the percentage of detractors (0–6) from promoters (9–10). Scores range from -100 to 100. In RevOps, NPS is often fed into customer health scores and used as a leading indicator of renewal and expansion likelihood.

*Canonical: https://forgeworks.ai/glossary#nps*

### Customer Health Score {#customer-health-score}

**Short:** A composite signal predicting a customer's likelihood to renew, expand, or churn.

A Customer Health Score is a composite metric that blends product usage, support activity, engagement, NPS, and billing signals into a single indicator of account health. Customer success teams use it to prioritize outreach, forecast renewals, and trigger playbooks for at-risk accounts. Health scores live in CS platforms like Gainsight or ChurnZero and are a core CS Ops deliverable.

*Canonical: https://forgeworks.ai/glossary#customer-health-score*

### Renewal Rate {#renewal-rate}

**Short:** The percentage of customers or revenue that renews at the end of a contract term.

Renewal Rate is the share of contracts up for renewal that actually renew, measured by logo count or by dollar value. It is closely related to retention but is scoped specifically to renewal events rather than all-period churn. Accurate renewal forecasting — owned by CS Ops — depends on clean contract dates, auto-renewal flags, and health scoring in the CRM.

*Canonical: https://forgeworks.ai/glossary#renewal-rate*

## Compensation & Forecasting {#compensation-forecasting}

### Forecast {#forecast}

**Short:** A projection of revenue or bookings for a future period.

A Sales Forecast is a projection of expected revenue or bookings for a future period (typically a quarter), built bottom-up from rep-level call-downs and top-down from market models. Forecast methodologies include weighted pipeline (probability-weighted), commit/best-case categories, and AI-driven models. Forecast accuracy is itself a core RevOps metric.

*Canonical: https://forgeworks.ai/glossary#forecast*

### Quota {#quota}

**Short:** A sales target assigned to a rep, team, or segment for a period.

A Quota is the sales target assigned to a rep, team, or segment for a defined period (monthly, quarterly, annually). Quota is typically denominated in new ARR, total bookings, or revenue, and is set as a function of OTE, sales productivity assumptions, and company targets. Quota attainment is the primary individual performance metric in sales.

*Canonical: https://forgeworks.ai/glossary#quota*

### On-Target Earnings (OTE) {#ote}

**Short:** The total compensation a rep earns at 100% quota attainment.

On-Target Earnings is the total compensation (base salary plus variable commission) a sales rep earns when achieving 100% of quota. OTE is typically expressed as a base/variable split (e.g., 50/50 for closing reps, 70/30 for SDRs). OTE design balances rep motivation, hiring competitiveness, and unit economics.

*Canonical: https://forgeworks.ai/glossary#ote*

### Sales Commission {#sales-commission}

**Short:** Variable compensation paid to a rep based on revenue or deal performance.

Sales Commission is the variable portion of a sales rep's compensation, paid based on closed revenue, bookings, or other quota measures. Commission plans include accelerators (higher rates above quota), decelerators, SPIFFs (one-time bonuses), and clawbacks (recovery for churned deals). Modern commission automation tools (QuotaPath, CaptivateIQ, Spiff) calculate commission from CRM data automatically.

*Canonical: https://forgeworks.ai/glossary#sales-commission*

### Compensation Plan {#compensation-plan}

**Short:** The structured rules that determine how a rep earns variable pay.

A Compensation Plan is the structured set of rules that determines how a sales rep earns variable compensation. Components typically include base, OTE, commission rates, accelerators, accelerator thresholds, SPIFFs, draws, and clawback provisions. Plan design is one of the highest-leverage decisions in revenue operations.

*Canonical: https://forgeworks.ai/glossary#compensation-plan*

### SPIFF {#spiff}

**Short:** A short-term sales incentive paid for hitting a specific, time-bound goal.

A SPIFF (Sales Performance Incentive Fund) is a temporary bonus paid to reps for achieving a targeted behavior — selling a specific product, closing before quarter-end, or booking new logos — outside the standard commission plan. SPIFFs are tactical motivators used to steer focus quickly, but overuse can distort behavior. RevOps tracks SPIFF cost and effectiveness against the intended outcome.

*Canonical: https://forgeworks.ai/glossary#spiff*

### Commission Accelerator {#commission-accelerator}

**Short:** An increased commission rate that kicks in above a quota threshold.

A Commission Accelerator is a higher payout rate applied to bookings above a defined attainment level — for example, paying 1.5x the base rate on everything over 100% of quota. Accelerators reward overperformance and motivate top reps to keep selling past quota. RevOps models accelerator costs carefully so that strong attainment remains profitable.

*Canonical: https://forgeworks.ai/glossary#commission-accelerator*

### Clawback {#clawback}

**Short:** A provision that reclaims paid commission when a deal churns or is reversed.

A Clawback is a comp-plan clause allowing a company to recover commission already paid when a customer cancels, refunds, or fails to pay within a defined window. Clawbacks align rep incentives with durable, collectible revenue rather than just signed deals. RevOps and finance define the clawback period and automate the adjustments in the commission system.

*Canonical: https://forgeworks.ai/glossary#clawback*

### Sales Draw {#sales-draw}

**Short:** Guaranteed pay advanced against future commissions, often during ramp.

A Sales Draw is a guaranteed minimum payment advanced to a rep against future commissions, commonly used during ramp or territory transitions to stabilize income. A recoverable draw must be paid back from earned commissions; a non-recoverable draw does not. RevOps tracks draw balances to ensure comp plans stay fair and within budget.

*Canonical: https://forgeworks.ai/glossary#sales-draw*

## Methodologies & Frameworks {#methodologies-frameworks}

### MEDDIC / MEDDPICC {#meddic}

**Short:** A B2B sales qualification framework covering metrics, decision criteria, and champion.

MEDDIC is a B2B sales qualification framework standing for Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion. MEDDPICC adds Paper Process and Competition. Originally developed at PTC in the 1990s, MEDDIC is widely adopted in enterprise SaaS for deal qualification and forecast accuracy.

*Canonical: https://forgeworks.ai/glossary#meddic*

### BANT {#bant}

**Short:** A lead qualification framework covering Budget, Authority, Need, and Timeline.

BANT is a lead qualification framework developed by IBM standing for Budget, Authority, Need, and Timeline. Sales reps qualify leads by confirming these four dimensions. BANT is widely used in SMB and mid-market motions but is often considered too rigid for modern complex sales, where MEDDIC, SPICED, or GPCTBA/C&I frameworks are preferred.

*Canonical: https://forgeworks.ai/glossary#bant*

### Command of the Message {#command-of-message}

**Short:** A sales methodology focused on tying product capabilities to differentiated business outcomes.

Command of the Message is a sales methodology developed by Force Management that trains reps to articulate the customer's required capabilities, link them to differentiated product capabilities, and quantify business outcomes. Command of the Message is frequently paired with MEDDIC in enterprise sales orgs.

*Canonical: https://forgeworks.ai/glossary#command-of-message*

### The Challenger Sale {#challenger-sale}

**Short:** A methodology where reps teach, tailor, and take control to reframe a buyer's thinking.

The Challenger Sale is a sales methodology based on research finding that top performers win by teaching prospects something new about their business, tailoring the message to stakeholders, and taking control of the buying conversation. Rather than simply building relationships, Challenger reps lead with provocative insight. It is widely used in complex B2B sales to differentiate on perspective.

*Canonical: https://forgeworks.ai/glossary#challenger-sale*

### SPIN Selling {#spin-selling}

**Short:** A questioning framework using Situation, Problem, Implication, and Need-payoff questions.

SPIN Selling is a consultative methodology that structures discovery around four question types: Situation, Problem, Implication, and Need-payoff. By leading prospects to articulate the cost of their problems and the value of solving them, reps build urgency without pressure. It is foundational to modern consultative and value-based selling approaches.

*Canonical: https://forgeworks.ai/glossary#spin-selling*

### Sandler Selling System {#sandler-selling-system}

**Short:** A methodology emphasizing mutual qualification and upfront contracts.

The Sandler Selling System is a methodology built on establishing mutual fit early, setting clear expectations through 'up-front contracts,' and qualifying hard on pain, budget, and decision process before investing in a deal. It positions the rep as a trusted advisor rather than a pursuer, reducing wasted cycles on poor-fit deals. It remains popular for transactional and mid-market sales.

*Canonical: https://forgeworks.ai/glossary#sandler-selling-system*

### Value Selling {#value-selling}

**Short:** Selling based on quantified business outcomes rather than features.

Value Selling is an approach that anchors the sale in the measurable business value a solution delivers — revenue gained, cost avoided, risk reduced — rather than product features. Reps build ROI cases and business justification tailored to each buyer. It is essential in enterprise deals where multiple stakeholders must justify spend, and it pairs naturally with frameworks like MEDDPICC.

*Canonical: https://forgeworks.ai/glossary#value-selling*

### GAP Selling {#gap-selling}

**Short:** A methodology centered on diagnosing the gap between current and desired state.

GAP Selling is a problem-centric methodology that focuses on deeply diagnosing a prospect's current state, defining their desired future state, and quantifying the 'gap' between them. The size and cost of that gap creates the business case for change. It pushes reps to do rigorous discovery before proposing solutions, improving qualification and win rates.

*Canonical: https://forgeworks.ai/glossary#gap-selling*

### Quarterly Business Review (QBR) {#qbr}

**Short:** A recurring review of performance, goals, and plans with customers or internal teams.

A Quarterly Business Review is a structured quarterly meeting used in two contexts: customer success teams run QBRs with customers to demonstrate value and plan ahead, while internal teams run QBRs to review performance against targets and set priorities. RevOps prepares the data — pipeline, attainment, retention, and forecast — that makes QBRs fact-based rather than anecdotal.

*Canonical: https://forgeworks.ai/glossary#qbr*

---

## About Forgeworks

Forgeworks is your AI-first RevOps team, US based: an AI RevOps agency that embeds full RevOps pods — strategy, systems, AI and execution, shipped every week — inside VC-backed startups and trades companies. Forgeworks has brought clarity to over $1B in B2B SaaS revenue, supported $1.7B in capital raises, and implemented 50+ CRMs. Partner status: HubSpot Solutions Partner, Zuper Solutions Partner, QuotaPath Implementation Partner, and Chili Piper Implementation Specialist. Services: https://forgeworks.ai/#services

- Website: https://forgeworks.ai
- Book a free strategy call: https://forgeworks.ai/
- Email: support@forgeworks.ai
- Phone: +1-845-558-1855
- LinkedIn: https://www.linkedin.com/company/forgeworks/