CRM Glossary: Key Terms You Need to Understand Customer Relationship Management

Customer relationship management sounds simple – until you’re in a project meeting and people start using the same word to mean three different things: “lead,” “prospect,” “account,” “opportunity,” “pipeline,” “CRM,” “platform,” “data model.”

A shared CRM glossary fixes that fast. It helps marketing, sales, and operations teams align on how customer data moves, how revenue is attributed, and what “done” actually means when you implement Salesforce, integrate a marketing platform, or redesign lifecycle automation.

At a practical level, understanding CRM is a must. Otherwise, you’ll get lost in meetings where people throw around terms like MQL, SQL, SAL, SDR, AE, BDR, ICP, TAM, ACV, ARR, LTV, CAC, CPL, ROAS, CTR, CVR, SLA, SLO, SoR, SoT, CDP, DMP, ETL, API, and UTM as if everyone defines them the same way.

This is not a theoretical glossary. This is the version you actually need when building or debugging a CRM setup.

CRM Basics

CRM

CRM – Customer Relationship Management – can refer to both the strategy and the system.

Practically, the system is your operational database and workflow layer. It stores customer data, tracks interactions, and coordinates sales and service processes across teams.

In implementation terms: always clarify whether “CRM” means the business process or the actual system configuration (objects, fields, flows, integrations).

CRM platform vs. CRM instance

• Platform: the product and its capabilities (Salesforce, HubSpot, etc.)
• Instance: your configured environment (data model, automations, permissions)

This distinction matters when someone says “Salesforce is broken.” Most of the time, it’s not Salesforce – it’s your configuration.

System of Record (SoR)

The authoritative source for a dataset.

Example:

• CRM is usually the SoR for accounts and opportunities
• Marketing platform might hold engagement data, but should not override core customer records

If two systems disagree and you don’t know which one wins, you don’t have a system of record – you have a problem.

Source of Truth (SoT)

Often confused with SoR.

• SoR = where data is maintained
• SoT = which data you trust for decisions

They are not always the same.

Core CRM Objects

Lead

An unqualified potential customer.

Typical sources:

• forms
• events
• imports
• paid campaigns

Common mistake: treating every email address as a lead. That kills scoring, routing, and reporting.

Account

A company or organization you do business with.

Contact

An individual associated with an account.

Opportunity

A revenue deal in progress.

This is where pipeline, forecasting, and revenue tracking live.

Case

A support request or issue.

Important when CRM includes service processes.

Lifecycle and Funnel Terms

MQL, SAL, SQL

These are lifecycle states, not just labels.

• MQL (Marketing Qualified Lead): ready for sales review
• SAL (Sales Accepted Lead): sales accepted ownership
• SQL (Sales Qualified Lead): validated opportunity

If you don’t define entry criteria, these terms become meaningless.

SDR / BDR / AE

• SDR (Sales Development Representative): qualifies leads
• BDR (Business Development Representative): often outbound prospecting
• AE (Account Executive): closes deals

These roles directly affect ownership, routing, and reporting.

Handoff

Transfer of ownership between teams.

Example:

• Marketing → SDR
• SDR → AE

If handoffs are unclear, your funnel breaks.

SLA / SLO

• SLA (Service Level Agreement): expected response time
• SLO (Service Level Objective): internal performance target

Used to enforce follow-up discipline.

Revenue and Business Metrics

ARR / MRR

• ARR: Annual Recurring Revenue
• MRR: Monthly Recurring Revenue

ACV

Annual Contract Value – average contract revenue per deal.

LTV / CAC

• LTV: Lifetime Value of a customer
• CAC: Customer Acquisition Cost

If CAC > LTV, your business model is broken.

TAM / ICP

• TAM (Total Addressable Market): total market size
• ICP (Ideal Customer Profile): your target customer definition

ICP should directly influence segmentation and routing.

Marketing and Attribution Terms

CPL

Cost per Lead

CTR / CVR

• CTR: Click-through Rate
• CVR: Conversion Rate

ROAS

Return on Ad Spend

Attribution

How you assign credit for revenue.

This is where most companies argue endlessly because definitions are not aligned.

UTM

Tracking parameters used to identify traffic sources.

If UTMs are inconsistent, attribution becomes unreliable.

Data and Architecture

Data model

Structure of objects, fields, and relationships.

This is the foundation of everything. If it’s wrong, nothing scales.

Object / Record / Field

• Object: table
• Record: row
• Field: column

Basic, but shows up in every conversation.

Standard vs. Custom objects

• Standard: provided by the platform (Account, Contact, Opportunity)
• Custom: built for your business

Custom objects add flexibility – and complexity.

Relationships (lookup vs. master-detail)

Define how records connect.

This affects:

• ownership
• security
• rollups
• deletion behavior

Bad relationship design creates long-term pain.

CDP / DMP

• CDP (Customer Data Platform): unified customer profiles
• DMP (Data Management Platform): anonymous audience data (ads)

People often mix these up.

ETL

Extract, Transform, Load – moving and shaping data between systems.

API

Application Programming Interface – how systems communicate.

Integration

Data movement between systems.

If integrations are not clearly defined, data drift happens.

Deduplication

Process of preventing or merging duplicate records.

Duplicates destroy reporting and personalization.

Execution and Operations

Pipeline

All open opportunities and their value.

Sales stages

Defined steps in your sales process.

If not clearly defined, forecasting becomes guesswork.

Forecasting

Predicting revenue based on pipeline.

Depends heavily on clean data and consistent stage usage.

Routing / AssignmentHow records are assigned.

Example:

• “Route enterprise leads in the US to ENT SDR queue”

If routing rules are vague, everything downstream breaks.

Role hierarchy / permissions

Controls who can see and edit data.

Too strict = slow teams
Too open = data chaos

Common CRM Pitfalls

“CRM” as a catch-all

Teams call everything CRM – marketing tools, data warehouses, service platforms.

This creates confusion fast.

Be precise:

• CRM
• CDP
• ESP
• data warehouse

Duplicate definitions

“Customer” can mean different things to marketing, sales, and finance.

Fix this by tying definitions to actual fields:

• Customer = Account.Customer_Status__c = Active

Data quality issues

Most automation failures are data problems:

• missing values
• inconsistent formats
• conflicting sources

Not platform issues.

Final Thought

If your glossary is just documentation, nobody will use it.

If your glossary is tied to:

• fields
• lifecycle stages
• routing rules

then it becomes the control panel for how your CRM actually behaves.

That’s when alignment stops being theoretical and starts showing up in your dashboards.

If you want, next step we can turn this into:

• SEO version with internal linking
• downloadable cheat sheet
• or “CRM glossary for Salesforce specifically” (more technical)

Share With Others