The Customer Journey Glossary: 146 Terms From Prospect to Advocate
Every stage of a B2B customer relationship, defined in plain language: pipeline and qualification, the deal and its pricing, onboarding and implementation, support, success and value, renewal and expansion, advocacy, the metrics underneath all of it, the roles that run it, and the AI-era terms reshaping it. Each definition stands alone, each has its own link, and the ones coined on this site say so.
No terms match that filter.
Pipeline, Prospecting and Qualification
15 termsIdeal Customer Profile (ICP)
The written description of the company your product serves best: size, industry, stack, problem shape, and the conditions under which they succeed. The ICP is as much a retention document as a sales one, because most churn is fit that was wrong on the day the deal closed.
TAM, SAM and SOM
Three nested market sizes: Total Addressable Market is everyone who could theoretically buy, Serviceable Addressable Market is the slice your product and model can actually serve, Serviceable Obtainable Market is what you can realistically win. Discipline lives in the second one, where ICP and capacity meet.
Lead
A person or company that has shown some signal of potential interest but has not yet been qualified against fit or intent. A lead is a hypothesis, not a buyer, and the entire top-of-funnel machinery exists to test that hypothesis cheaply before expensive humans engage.
MQL and SQL
A Marketing Qualified Lead has crossed a marketing-defined interest threshold, downloads, visits, event attendance. A Sales Qualified Lead has been accepted by sales as worth working after a fit and intent check. The handoff between the two is the first of the journey's many places where context dies.
Product-Qualified Lead (PQL)
A lead qualified by what they did in the product rather than what they downloaded: a free-tier team hitting a usage limit, a trial reaching the activation event. PQLs anchor product-led sales because behavior inside the product predicts buying far better than content consumption outside it.
Product-Led Growth (PLG)
A go-to-market model where the product itself acquires, converts and expands users: self-serve signup, free tier or trial, in-product upgrade paths, with sales entering late and only on qualified accounts. PLG shifts work from persuasion to activation, which moves the revenue burden toward the post-sale team.
Intent Data
Signals that a company may be in-market before they contact you: research activity on relevant topics, review-site comparisons, hiring patterns, technology changes. Intent data prioritizes outbound effort; its failure mode is treating a statistical hint as a fact about a specific buyer.
Signal-Based Selling
Prospecting triggered by concrete observable events, a funding round, a leadership change, a champion changing jobs, a stack migration, rather than by list order. The craft is matching the message to the signal, because a relevant trigger with a generic email wastes the only advantage the signal gave you.
Outbound and Inbound
The two directions demand arrives from: outbound is you initiating contact with prospects who did not ask, inbound is prospects arriving through content, search, referral or product. Most durable B2B motions blend both, with inbound carrying efficiency and outbound carrying targeting control.
Discovery Call
The structured conversation where the seller maps the prospect's actual problem, current state, decision process and success criteria before showing anything. Discovery quality decides everything downstream: what was learned here becomes the success plan, and what was skipped here becomes the onboarding surprise.
Qualification Frameworks (BANT, MEDDICC)
Checklists that test whether a deal is real before the pipeline claims it is. BANT covers budget, authority, need and timeline; MEDDICC adds metrics, economic buyer, decision criteria and process, identified pain, champion and competition. The framework matters less than answering its questions with evidence rather than optimism.
Demo
The guided showing of the product against the prospect's stated problem. A strong demo is discovery played back with the product as proof, in the prospect's language and data shape. A feature tour in vendor order is the reliable sign discovery never happened.
Proof of Concept (POC) and Pilot
A bounded evaluation where the prospect runs the product against agreed success criteria before committing: defined scope, defined data, defined finish line, defined decision. A POC without written exit criteria is a free deployment with no decision attached, and it ages into exactly that.
Buying Committee
The group that actually decides a B2B purchase: economic buyer, technical evaluator, security and legal, end users, and often a procurement function with its own incentives. Enterprise deals are usually lost to a committee member the seller never met, which is what multi-threading exists to prevent.
Land and Expand
Entering an account with a small, fast initial deal and growing it after value is proven: one team, one use case, then breadth. The model moves revenue responsibility to the post-sale side, because the expand half is earned by delivery, not promised by sales.
Deal, Pricing and Close
12 termsMutual Action Plan (MAP)
A shared, dated plan from today to go-live that both buyer and seller maintain: steps, owners on each side, and the dates that make the target signature date arithmetically possible. Its power is diagnostic; a buyer who will not engage with the plan is telling you the deal's real status.
Digital Sales Room
A single shared link holding everything a buying committee needs: proposal, demo recordings, security documents, pricing, the mutual action plan. It replaces the forwarded-attachment chain, and its analytics show who on the committee is actually engaging, which is intent data about your own deal.
Security Review
The buyer's assessment of your security posture before purchase: questionnaires, certifications such as SOC 2 or ISO 27001, data residency and processing terms. In enterprise and regulated deals it is routinely the longest pole in the timeline, which is why mature sellers start it at proposal, not at signature.
Procurement
The buyer's purchasing function, with its own process, thresholds and incentives, usually price and risk rather than outcomes. Procurement enters late and controls the clock, so discovering its steps early, through the champion or the mutual action plan, is the difference between a quarter-end close and a surprise.
MSA, Order Form and SOW
The contract stack: the Master Service Agreement holds the standing legal terms, the Order Form holds what is being bought and for how much, the Statement of Work defines any services to be delivered. Renewals and expansions amend the order form; the MSA is negotiated once and endures.
Seat-Based Pricing
Charging per licensed user. Simple to sell and forecast, and increasingly strained in the AI era, because software that does work autonomously decouples value from headcount. When revenue stops tracking seats, the team that drives and evidences usage starts influencing the invoice.
Consumption-Based Pricing
Charging on usage of a metered unit: API calls, records processed, compute, tasks completed. It aligns price with value delivered and makes revenue a post-sale outcome, since the invoice now moves with adoption. Under-consumption becomes an early churn signal rather than a billing footnote.
Outcome-Based Pricing
Charging against a result rather than access or usage: per resolved ticket, per qualified meeting, per successful transaction. The model in current use for AI agents, because the agent's unit of work is countable. It demands measurement both sides trust, which is a contract problem before a product one.
Auto-Renewal and Notice Period
Contract clauses under which the agreement renews automatically unless cancelled a defined number of days before term end. Operationally they set the real renewal calendar: the decision date is the notice deadline, not the renewal date, and save plays run against the earlier of the two.
Ramp Period
A contractual phase-in of price or volume while the customer deploys: fewer seats or units in early quarters, stepping up on an agreed schedule. Ramps trade near-term revenue for adoption time, and they quietly transfer deal risk to onboarding, which must hit the dates the step-ups assume.
Closed-Won
The CRM stage where the contract is signed and the deal counts. For the customer nothing has been received yet, which is why mature teams treat closed-won as the start of delivery risk rather than the end of sales risk, and wire the handoff to fire from this exact event.
Sales-to-CS Handoff
The structured transfer of everything sales learned into the team that must now deliver it: success criteria, stakeholders, promises made, risks known. Done as fields and documents attached to closed-won, not as a meeting from memory, because every detail that fails to cross becomes onboarding re-discovery.
Onboarding, Lifecycle and Handoffs
20 termsCustomer Lifecycle
The whole arc of a customer relationship: evaluation, purchase, onboarding, adoption, value realization, renewal, expansion, and in the bad case offboarding. Lifecycle management means each stage has defined entry criteria, exit criteria, and an owner, instead of being whatever happens to happen.
Onboarding
The stage between signature and the customer reliably getting value on their own: technical setup, data migration, training, and the first measured win. Onboarding quality is the strongest early predictor of first-year retention, because customers decide whether they bought well long before renewal.
Go deeper: Customer Onboarding guide →Implementation
The technical and project work inside onboarding: configuration, integrations, data migration, environment setup, and testing. Implementation is where timelines are won or lost, and in regulated industries its sequencing is usually dictated by approval chains rather than by the engineering effort itself.
Kickoff
The first structured working session after signature, where success criteria, stakeholders, timeline, and responsibilities are agreed and written down. A kickoff that does not produce documented success criteria is a greeting, and the gap it leaves resurfaces months later as a value dispute nobody can adjudicate.
Go-Live
The moment the customer starts running real work through the product. Go-live is a milestone, not the finish line: a customer can be live and still weeks from value. Treating go-live as onboarding complete is how accounts enter the adoption stage already stalled.
Handoff
The transfer of an account between teams: sales to implementation, implementation to CS, CS to support and back. Handoffs are where context dies, which is why mature teams define what information must cross each one. Most escalations trace back to a handoff that dropped something.
Success Plan
A shared, written document stating what the customer is trying to achieve, how it will be measured, by when, and who owns what on both sides. The test of a real success plan is that the customer would recognize and defend it, not just the CSM who wrote it.
Quarterly Business Review (QBR)
A recurring executive conversation that reviews outcomes against the success plan and decides what changes next quarter. A QBR earns its meeting slot by producing decisions; a usage recap with slides is a report, and executives correctly stop attending reports.
Go deeper: QBR guide →Executive Business Review (EBR)
A QBR aimed explicitly at executive sponsors rather than day-to-day users, usually less frequent and more strategic: business outcomes, roadmap alignment, and the renewal and expansion trajectory. The naming varies by company; the distinguishing feature is the audience, not the calendar.
Renewal
The contract decision point, and in a well-run book the least dramatic day of the year. Renewal is a process that starts months early, with value evidenced, risks surfaced, and procurement mapped, not an event that starts when the notice period does.
Go deeper: Customer Retention guide →Upsell and Cross-sell
Upsell increases spend on what the customer already uses: more seats, higher tier, more volume. Cross-sell adds a different product. Both land best when anchored to an outcome the customer already achieved, which is why expansion conversations belong where the value evidence lives.
Expansion Whitespace
The mapped gap between what a customer buys today and what they could credibly use: unlicensed teams, unactivated modules, adjacent use cases. Whitespace analysis turns expansion from opportunism into coverage, because the map exists before the conversation does.
Save Play
A predefined intervention run when an account shows churn risk: a defined trigger, a named owner, a diagnostic conversation, an executive touch, and a concrete remediation offer with a clock on it. The point of predefining it is speed; saves are won early or not at all.
Go deeper: Customer Retention guide →Win-back
A structured attempt to recover a churned customer after the exit, typically once the cause of the original departure has actually changed: new capability shipped, new team on their side, new pricing. Win-backs work on facts that changed, not on persistence.
Offboarding
The managed exit of a churning customer: data export, access wind-down, final billing, and an honest exit interview. Done well it costs little and preserves the relationship that win-backs and references later depend on. Done badly it converts a lost account into a vocal detractor.
Churn Post-mortem
A structured review after a loss: what signals existed, when they were visible, what was tried, and what would have had to be true to keep the account. The output is a change to the system, a trigger, a play, an ownership rule, not a narrative of blame.
Change Management
The work of getting the customer's people to actually alter how they work: communication, training, incentives, and the removal of the old way. Software deployments rarely fail on configuration; they fail on humans quietly continuing the previous process, which is a managed problem, not a mystery.
Parallel Run
Operating the old and new systems side by side for one or more live cycles and reconciling the outputs before cutting over. Non-negotiable where errors carry legal or financial consequences, payroll being the canonical case: the go-live date is chosen so a full parallel cycle fits before the immovable deadline.
Customer Enablement
The structured transfer of capability to the customer: training paths, certification, admin playbooks, office hours, academy content. Enablement is what lets adoption survive contact with staff turnover on the customer side, because trained individuals leave and documented capability stays.
Data Migration
Moving the customer's historical data from old systems into yours: extraction, mapping, cleaning, loading, validation. The source data is usually dirtier than anyone admitted, so the discipline is classification and quarantine, migrate what is clean, surface what is not in writing, and never silently fix fields you do not own.
Support, Service and Operating Systems
18 termsPlaybook
A documented, repeatable response to a recurring situation: the trigger that starts it, the steps, the owner of each, and the exit condition that ends it. A playbook nobody can execute without its author is tribal knowledge with a title page.
Go deeper: Playbook generator →Standard Operating Procedure (SOP)
The step-level documentation of how one motion is performed, specific enough that a competent new hire can run it unassisted. SOPs are what make quality independent of who happened to be on shift, and they are the raw material automation is later built from.
Health Score
A composite indicator of how likely an account is to renew, expand, or churn, built from usage, support, engagement, and relationship signals. A health score is a prediction and should be scored like one: checked against what actually happened to the accounts it rated.
Go deeper: Health Score guide →Early Warning System
The set of triggers that surface account risk while intervention is still cheap: usage drops, champion departure, stalled onboarding, ticket spikes, missed QBRs. The design goal is lead time, because the same signal ninety days before renewal is a save and thirty days before is a negotiation.
Go deeper: Customer Retention guide →Churn Prediction
Using historical behavioral data to score which current accounts resemble the ones that left: declining usage breadth, support friction, engagement silence, stakeholder change. The model’s value is not the score itself but the lead time it buys before the risk becomes a renewal conversation.
Leading vs Lagging Indicators
Lagging indicators report outcomes already decided: churn, NRR, renewal rate. Leading indicators move earlier and are still influenceable: time to value, adoption depth, escalation volume, QBR attendance. Teams commit to lagging numbers but manage by leading ones, because by the time NRR moves, the causes are months old.
North Star Metric
The single measurable thing that best represents customers receiving value, chosen so that improving it genuinely improves retention rather than vanity. A good north star is an outcome the customer would recognize, not an activity count the vendor finds flattering.
Service Level Agreement (SLA)
A contractual commitment to response or resolution speed, usually tiered by severity. An SLA is a promise, not a mechanism: hitting it consistently requires the triage, staffing, and escalation design underneath. Teams that manage to the SLA alone optimize first response and quietly degrade resolution.
Go deeper: Support Operations guide →Severity Tiers
Classification of issues by business impact, production down versus degraded versus cosmetic, each with its own response clock and escalation path. Severity is defined by impact on the customer’s operation, not by how loudly the ticket is written, and the definitions only work when published both ways.
Ticket Triage
Routing incoming issues by intent and severity rather than by arrival order, so the right queue sees the right problem at the right speed. Triage quality compounds: everything downstream, deflection, SLAs, escalation, staffing, inherits the accuracy of this first sort.
Go deeper: Support Operations guide →Deflection
Resolving a would-be ticket without an agent: knowledge base, in-product guidance, automated status checks, AI answers. Honest deflection is measured by resolution, meaning the customer got the answer and did not come back, not by how many contacts were merely prevented from reaching a human.
First Response Time (FRT)
The elapsed time from a customer raising an issue to the first substantive human or automated reply. FRT shapes trust disproportionately because it is the moment the customer learns whether they have been heard. It is also gameable with empty acknowledgments, so it is read alongside resolution time.
Go deeper: Support Operations guide →Escalation Path
The predefined route a problem takes when it exceeds the current owner’s authority or clock: who is engaged, at what threshold, with what information attached. A real escalation path names people and time triggers. Escalate as needed is the absence of one, discovered at the worst moment.
Knowledge Base
The structured library of answers customers and agents search before asking: setup guides, troubleshooting, how-tos, built from the actual top contact reasons rather than from the product manual’s table of contents. In the AI era it doubles as the grounding corpus automated support answers draw from.
Operational Leverage
The ability to serve more customers without a proportional increase in cost or headcount, built from three sources: automation, standardization, and knowledge infrastructure. A team with leverage doubles its base without doubling itself. The term’s use for CS operations is developed in the SaaS Complexity Trap on this site.
Go deeper: The SaaS Complexity Trap →Support Swarming
A support model that replaces tiered escalation ladders with pulling the right expertise directly into the case as a temporary team. Swarming trades the efficiency of tiers for speed on complex issues and removes the repeat-your-problem tax that each escalation level charges the customer.
Incident Communication
What customers are told while something is broken, on a clock, regardless of whether the cause is known: what is affected, what is not, what to do now, and when the next update lands. Hitting the promised update time even with nothing new is the mechanism; silence is read as concealment.
Status Page
The public, continuously updated record of system health and incidents. Its value is that it answers the question before the ticket is filed, and its credibility is binary: a status page that shows green during a visible outage spends trust the product team never earns back.
Success, Value and Advocacy
11 termsValue Realization
The point where the customer is measurably receiving the outcome they bought, against the criteria set at kickoff, and knows it. The second clause is the operational one: value that the customer cannot see or report internally behaves, at renewal time, exactly like value that never happened.
Value Engineering
The discipline of building the quantified business case with the customer: baseline measured before deployment, the levers the product moves, and the arithmetic connecting them. It front-loads the renewal argument into the sale and onboarding, when the baseline can still be captured honestly.
Business Case
The customer-facing document stating what the purchase is expected to change, by how much, measured how, and what it costs: the artifact the economic buyer defends internally. Accounts with a written business case renew on evidence; accounts without one renew on mood and budget weather.
ROI Review
The periodic comparison of delivered results against the business case, with the customer in the room and the baseline on the page. Run well inside QBRs, it converts renewal from a negotiation into a summary, because the decision-grade evidence has been accumulating in both parties' hands all year.
Customer Education
The scaled teaching layer around a product: academy courses, certifications, webinars, documentation paths. Education is the highest-leverage adoption asset because it works while the team sleeps, survives champion turnover, and gives power users a credential they carry, which quietly builds the advocate bench.
Customer Advisory Board (CAB)
A recurring forum where a selected set of strategic customers shapes roadmap and strategy directly with leadership. A real CAB trades genuine influence for genuine candor; one that presents slides and collects applause is a dinner, and the attendees know which one they are at.
Reference Program
The managed pool of customers willing to take prospect calls, with tracking of who has been asked, how often, and what they got back. References are a depletable resource drawn from delivered outcomes, and burning the same three enthusiasts for every deal is how programs quietly die.
Case Study
The documented before-and-after of a customer outcome: baseline, intervention, measured result, in the customer's own numbers and words. Beyond marketing, the discipline of producing them forces the measurement conversation that many accounts otherwise never have, which is its quiet second value.
Referral Loop
The repeatable motion by which satisfied customers introduce new ones: asks timed to moments of realized value, made specific, and reciprocated. Referral-sourced deals close faster and churn less because fit screening happened socially before the funnel ever saw them.
Champion Job-Change Tracking
Monitoring when past champions and power users change companies, because each move is two signals at once: the account they left just lost its internal advocate, and the company they joined just gained someone predisposed to buy. Current practice treats this as a first-class pipeline and risk source.
Customer Advocacy
The stage past retention where customers actively generate growth: references, case studies, reviews, referrals, community answers. Advocacy is earned output, not a program to extract quotes; the program only harvests what delivered outcomes have already planted.
Renewal and Expansion Commercials
6 termsRenewal Forecast
The forward-looking call on which renewable revenue will close, categorized by confidence: committed, best case, at risk, lost. A forecast is a claim about the future that gets scored, and the discipline is reviewing last quarter's calls against what happened, which is how calibration is earned.
Price Uplift
The increase applied at renewal, whether contractual escalators or repricing. Uplift lands in proportion to evidenced value: an account with a running ROI story absorbs it as fairness, an account without one experiences it as the trigger for the evaluation you least wanted.
True-up
The periodic reconciliation between contracted and actual usage, with the difference invoiced, typical in consumption and seat-audit models. Handled transparently on a schedule it is bookkeeping; discovered by the customer as a surprise invoice it is a trust event dressed as an accounting one.
Overage
Usage beyond the contracted allowance, billed at a defined rate. Well-designed overage is a signal and a conversation, the account has outgrown its tier, which is an expansion opportunity. Punitive overage teaches customers to throttle their own adoption, which is retention damage sold as revenue.
Seat Compression
Renewal shrinkage driven by the customer needing fewer licensed users for the same work, increasingly because AI handles a share of it. The defining commercial pressure of the current cycle: value delivered can rise while seats fall, which is exactly why pricing is migrating toward usage and outcomes.
Multi-threading
Deliberately holding relationships across several stakeholders in an account, economic buyer, champion, users, executive sponsor, so no single departure orphans the relationship. The renewal corollary of the buying committee: accounts threaded through one person are one resignation away from at-risk.
Revenue and Retention Metrics
16 termsNet Revenue Retention (NRR)
Net Revenue Retention measures how much recurring revenue a fixed cohort of existing customers generates a period later, expansion included: starting revenue plus upsell, minus downgrades and churn, divided by starting revenue. NRR above 100 percent means the existing base grows before any new logo is signed.
Go deeper: Customer Retention guide →Gross Revenue Retention (GRR)
Gross Revenue Retention measures the same fixed cohort with expansion excluded: starting revenue minus downgrades and churn, divided by starting revenue. GRR can never exceed 100 percent, which makes it the cleaner read on whether customers actually stay. A GRR above 100 is a calculation error, not a result.
Go deeper: Customer Retention guide →Churn Rate
The share of customers or revenue lost over a period, measured against what existed at the start of it. Logo churn counts customers, revenue churn counts money, and the two routinely tell different stories: losing forty small accounts and losing one enterprise account can be the same revenue churn.
Logo Churn vs Revenue Churn
Logo churn is the count of customers lost; revenue churn is the money they represented. Both are needed because each hides what the other shows. High logo churn with low revenue churn means the small end of the base is leaking. The reverse means a concentration problem just materialized.
Monthly Recurring Revenue (MRR)
The subscription revenue a business books every month, normalized: annual contracts divided by twelve, one-time fees excluded. MRR is the base unit most retention math is computed on, which is why its definition drifting, such as quietly including services revenue, corrupts every metric built on top of it.
Annual Recurring Revenue (ARR)
The annualized value of all active recurring contracts, MRR multiplied by twelve. ARR is the headline size metric for subscription businesses and the denominator behind most Customer Success ratios, including accounts per CSM and ARR per segment, which is why coverage models start from it.
Annual Contract Value (ACV)
The average annualized value of a single customer contract. ACV drives the economics of coverage: what a company can afford to spend serving an account, which segment it belongs to, and whether it gets a named CSM, a pooled team, or a purely digital motion.
Customer Lifetime Value (LTV)
The total profit a customer is expected to generate across the whole relationship, driven by average revenue, margin, and how long they stay. Retention compounds it: extending average customer life directly multiplies LTV, which is the financial argument underneath every Customer Success investment.
Customer Acquisition Cost (CAC)
Everything spent to win a customer, sales and marketing included, divided by customers won. CAC matters to Customer Success because retention determines whether it was ever paid back: a customer who churns before the payback point was acquired at a loss, however clean the sale looked.
Expansion Revenue
Additional recurring revenue from existing customers: more seats, higher tiers, added products, or increased usage. Expansion is the difference between NRR and GRR, and it is the cheapest revenue a company has, because the relationship, the trust, and the data already exist.
Contraction
Revenue lost from customers who stay but pay less: fewer seats, a lower tier, a negotiated discount at renewal. Contraction is churn’s quieter sibling and often its leading indicator, because a customer who downgrades has usually already concluded the product is worth less than they are paying.
Net Churn
Churned and contracted revenue minus expansion revenue over the same period. Negative net churn, where expansion outweighs the losses, means the installed base grows by itself. It is the same fact NRR above 100 percent expresses, stated from the loss side instead of the retention side.
Renewal Rate
The share of contracts, or of renewable revenue, that actually renews in a period. The denominator matters: it is measured against what came up for renewal, not against the whole base. A 95 percent renewal rate in a quarter where little renewed can hide a difficult year.
Quick Ratio
New plus expansion revenue divided by churned plus contracted revenue over the same period. It compresses growth efficiency into one number: how many dollars came in for every dollar that leaked out. A high quick ratio built mostly on new logos still conceals a retention problem.
Payback Period
How long a customer must stay before their margin has repaid the cost of acquiring them. Everything before that point is financed hope. Payback is why early churn is disproportionately expensive, and why onboarding, the stage that most determines early churn, is an economic function rather than a courtesy.
Cohort Analysis
Tracking a fixed group of customers who started together, by signup quarter or segment, through time. Cohorts are how retention is honestly measured, because blending new customers into the base flatters every number. The rule: revenue acquired during the period never belongs in that period’s retention math.
Experience and Adoption Metrics
10 termsNet Promoter Score (NPS)
A loyalty survey asking how likely the customer is to recommend you, zero to ten. Promoters score nine or ten, detractors zero through six; NPS is promoters minus detractors as percentages. Useful as a trend and a conversation trigger, misused when treated as an outcome metric in itself.
Customer Satisfaction Score (CSAT)
A transactional survey, usually one to five, asked right after an interaction: a support ticket, an onboarding milestone, a QBR. CSAT measures the moment, not the relationship, which is its strength. A customer can rate every ticket five and still churn, because tickets were never the problem.
Customer Effort Score (CES)
A survey measuring how hard the customer had to work to get something done: resolve an issue, complete setup, find an answer. Effort predicts churn better than delight in support-heavy products, because customers rarely leave over a bad day and often leave over persistent friction.
Time to Value (TTV)
The elapsed time from purchase to the customer first receiving the outcome they bought, not from purchase to go-live. Shortening it is the highest-leverage onboarding goal, because the period between paying and benefiting is where early churn decisions quietly form.
Go deeper: Customer Onboarding guide →Activation
The point where a new user or account has done the specific actions that correlate with sticking around: the setup completed, the first real task performed, the first output shared. Activation is a product-defined event, not a feeling, and defining it precisely is prerequisite to improving it.
Aha Moment
The first instant the product visibly does the job the customer bought it for, in their own context with their own data. Onboarding design is largely the engineering of a shorter path to this moment, because everything before it runs on faith and everything after it runs on evidence.
Adoption
The degree to which a customer uses the product in their real workflow: breadth across features and teams, depth of meaningful actions, and frequency. Logins are not adoption. An account can log in daily and churn, because presence is not the same as the product doing a job.
Product Breadth and Depth
Two axes of usage: breadth is how many modules, features, or teams an account touches; depth is how intensively the core workflows are used. Breadth predicts retention because multi-surface customers are harder to replace; depth predicts it because habitual workflows are expensive to unlearn.
DAU and MAU
Daily and monthly active users, with the ratio between them indicating habit strength. In B2B the raw counts mislead without context: a payroll tool used heavily three days a month is healthy, so active-user metrics must be read against the product’s natural cadence, not against consumer norms.
Voice of Customer (VoC)
The practice of systematically collecting and routing what customers say across surveys, tickets, calls, and reviews, into decisions. A VoC program is working when product and leadership can name the top recurring complaints and what changed because of them, and not before.
Roles, Org Design and Coverage
23 termsCustomer Success Manager (CSM)
The owner of a set of customer relationships and their outcomes: adoption, health, renewal readiness, and expansion signals. The role is proactive by mandate, which is what separates it from support. What a CSM carries varies enormously by segment, from eight enterprise accounts to hundreds digitally.
Go deeper: CSM role guide →Customer Success Operations (CS Ops)
The function that builds and runs the machinery Customer Success works inside: health scoring, playbooks, tooling, reporting, forecasting, and process design. CS Ops is to CS what RevOps is to sales, and its existence is usually the difference between a methodology and a collection of habits.
Technical Account Manager (TAM)
A technically deep, named resource for complex accounts: architecture guidance, integration health, escalation shepherding, and roadmap translation. TAMs exist where the product is technical enough that outcome ownership requires engineering fluency the standard CSM profile does not carry.
Account Manager (AM)
The commercial owner of the customer relationship: renewal negotiation, expansion closing, and contract mechanics. In some models the CSM carries this; in others AM and CSM split value delivery from commercials. The split works only when the two share one account plan rather than two agendas.
Chief Customer Officer (CCO)
The executive accountable for the post-sale customer: success, support, services, and often renewal revenue. The role exists to give retention a seat where trade-offs are made, because a company where nobody at the executive table owns churn will systematically underinvest in preventing it.
Book of Business
The set of accounts a CSM owns, described by count, total ARR, and segment mix. Book construction is an economic decision: how much revenue one person can genuinely influence at a given touch level. A book built by splitting the alphabet is a workload, not a design.
Go deeper: CSM role guide →Coverage Ratio
Accounts or ARR per CSM, the central staffing arithmetic of Customer Success. Ratios follow from segment economics and from how much of the standard motion is systematized: the more the repeatable work runs digitally, the more accounts one human can genuinely cover without quality decaying.
Go deeper: Org Design generator →Segmentation
Dividing the customer base, usually by revenue, complexity, and growth potential, so each segment gets a deliberately chosen service model. Segmentation is the decision that makes every other CS decision affordable: who gets a named CSM, who gets pooled coverage, who gets a digital-only motion.
High-touch, Low-touch, Tech-touch
The spectrum of service intensity: high-touch means named ownership and bespoke attention, low-touch means pooled or lighter-cadence coverage, tech-touch means the motion is delivered by product, email, and automation. Mature orgs run all three on purpose, assigned by segment economics rather than by accident.
Pooled CS Model
A coverage model where a team collectively serves a set of accounts instead of each account having a named CSM. Customers get faster coverage and no vacation gaps; the cost is relationship depth. It fits mid-market and SMB tiers where ACV cannot carry named ownership.
Digital Customer Success
Delivering the Customer Success motion through product experiences, lifecycle email, in-app guidance, webinars, and community rather than human time: the standard play executed by systems, with humans reserved for exceptions and judgment. It is how coverage scales without headcount scaling with it.
Champion
The person inside the customer who actively sells your product internally: defends the budget, drives adoption, and pulls you into the right rooms. Champion departure is one of the most reliable churn precursors, which is why single-threaded accounts are a risk category of their own.
Economic Buyer
The person who owns the budget the subscription is paid from and can unilaterally decide to keep or cut it. The economic buyer and the users often experience entirely different products, and renewal is decided by the buyer’s version, evidenced or not.
Stakeholder Map
A living record of who matters in an account: champion, economic buyer, admin, skeptics, and executive sponsor, with each one’s stake and current disposition. The map’s value is in its gaps, because every unmapped role is a renewal conversation you have not had.
RACI
An ownership model naming who is Responsible, Accountable, Consulted, and Informed for each motion. In Customer Success it exists to kill the phrase everyone owns the customer, which in practice means nobody does. One Accountable name per row is the entire discipline.
SDR and BDR
Sales and Business Development Representatives: the roles that generate and qualify pipeline, working inbound responses and outbound prospecting respectively, booking qualified meetings for closers. The first human a future customer meets, which makes their targeting discipline a silent driver of later retention.
Account Executive (AE)
The seller who owns the deal from qualified opportunity to signature: discovery, demo orchestration, business case, negotiation, close. What the AE promises and documents becomes the post-sale team's inheritance, which is why the handoff quality from this seat prices the whole first year.
Sales Engineer (SE)
The technical counterpart to the AE: demos against real requirements, proof-of-concept design, architecture and security answers, integration feasibility. The SE is the deal's honesty layer, because they are the person in the room who knows precisely what the product cannot do.
Revenue Operations (RevOps)
The function that runs the shared machinery under sales, marketing and customer success: one data model, one funnel definition, forecasting, tooling, territory and compensation mechanics. RevOps exists because three teams optimizing three disconnected systems reliably produces one broken customer journey.
GTM Engineer
A recent role that builds automated go-to-market systems: enrichment pipelines, signal-triggered outreach, AI-assisted research and routing, connecting the stack so one operator does what ten manual SDRs did. The title is new; the leverage logic is the same one operations teams have always run.
Onboarding Specialist
The role that owns the implementation window as a repeatable production process rather than a bespoke project: running kickoffs, driving configuration and migration, tracking time to value against a dated plan, then handing a live, adopted account to its long-term owner with context intact.
Renewal Manager
A commercial specialist who owns the renewal transaction across a book: notice periods, procurement cycles, uplift application, negotiation. Splitting this from the CSM keeps the value relationship clean of price tension, at the cost of one more handoff that must carry context.
Customer Marketing Manager
The role that markets to and through the existing base: advocacy programs, references, case studies, community, expansion campaigns. It sits deliberately between marketing and customer success, monetizing delivered outcomes into proof the pipeline can spend.
AI Across the Customer Journey
15 termsAI Agent
Software that pursues a goal across multiple steps and systems on its own: reading context, deciding an action, executing it, and checking the result, rather than producing a single answer to a single prompt. In customer operations, agents handle bounded workflows such as status checks, renewals prep, and tier-one resolution.
Copilot
AI that drafts and suggests while a human stays in the loop and owns the output: ticket reply drafts, QBR narratives, call summaries, account briefs. The copilot pattern trades autonomy for safety, which is why it is usually the first AI deployment a customer team makes.
Agentic Workflow
A multi-step process executed by AI across systems, querying the CRM, composing an action, triggering it through an API, with defined entry conditions and guardrails. The distinguishing feature is that the workflow consumes data through interfaces built for software, not screens built for people.
Human-in-the-loop
A control design where defined categories of AI output require human review before they take effect: anything sending commitments to customers, touching contract or invoice numbers, or where being confidently wrong costs more than being slow. The discipline is in naming the categories, not in reviewing everything.
Guardrails
The explicit boundaries on what an automated system may do without review: which actions, which data, which spending or commitment thresholds. Guardrails are defined before autonomy is granted, because the cost of an agent acting wrong at scale is categorically higher than one person acting wrong once.
Grounding
Constraining AI answers to a trusted corpus, the knowledge base, the contract, the account record, so the system answers from evidence rather than from plausibility. An ungrounded support answer is a confident guess, and in customer operations confident guesses are more expensive than silence.
Explainability
The ability to trace why an automated system did what it did: which signals, which rules, which data. In customer operations it has become a buying criterion, because when an agent acts autonomously on an account, someone must be able to reconstruct the reasoning afterward.
The Intelligence Layer
The structured customer data, health logic, playbook rules, and permissioning that AI agents query and act through, replacing the dashboard as the primary interface to customer data. The term’s use for the CS platform shift was developed on this site, in The Intelligence Layer.
Go deeper: The Intelligence Layer →The Handoff Cliff
The failure mode where an AI-handled conversation reaches a human without the context already gathered, forcing the customer to repeat themselves to someone who should know. AI without context is worse than no AI, because it adds a round trip while appearing to save one. Coined on this site.
Go deeper: The Customer Success Reset →AI Tourist
A customer who signs up for an AI product, explores it, never reaches a repeatable use case, and leaves. It presents as a churn problem and is actually an activation problem: there was never a recurring job to retain. Coined on this site, in The Customer Success Reset.
Go deeper: The Customer Success Reset →Autonomous Customer Organization
An operating model in which systems handle the predictable customer work, onboarding steps, health monitoring, intervention triggers, routine renewals, and humans hold judgment, relationships, and design. Not an organization without people: one where no human effort is spent on work a system should do.
Go deeper: Building the Autonomous Customer Organization →Shadow Mode
Running an AI system alongside humans without customer exposure: it drafts answers agents see and grade, while customers only ever receive the human output. Shadow mode is how acceptance rates are earned before autonomy is granted, replacing faith in a vendor demo with evidence from your own queue.
AI SDR
An agent that executes prospecting end to end: researching accounts, drafting personalized outreach, handling replies, booking meetings. In current deployment it works best on the research and drafting layers with humans owning send decisions, because tone failures at scale damage a domain faster than they fill a calendar.
Conversation Intelligence
Software that records, transcribes and analyzes customer calls at scale: objections, competitor mentions, sentiment, talk ratios, commitments made. Its post-sale value is memory, the QBR promise and the escalation nuance survive the person who heard them, searchable by whoever inherits the account.
Predictive Health Scoring
Health scoring where the weights are learned from historical outcomes rather than set by committee: the model finds which behaviors actually preceded past churn and expansion, and scores the current base against them. Its honesty test is unchanged: checked predictions, not impressive inputs.
About This Glossary
What does this glossary cover? +
The full B2B customer journey rather than Customer Success alone: pipeline and qualification, the deal and its pricing models, onboarding and implementation, support and service operations, success and value delivery, renewal and expansion commercials, advocacy, the revenue and experience metrics underneath all of it, the roles that run each stage, and the AI-era terms reshaping the whole arc. 146 terms in ten stages.
How are the definitions written? +
Each definition is 35 to 60 words, defines the term in its first sentence, and is written to stand alone, so it can be quoted, cited, or lifted whole. Where a term touches an opinion, the definition says the quiet part out loud: what the metric hides, where the practice fails, which version of the term is theater.
Which terms were coined on this site? +
Four are developed or coined here and say so in their definitions: the Intelligence Layer, describing CS platforms becoming the data layer AI agents act through; the Handoff Cliff, the failure where AI passes a conversation to a human without its context; AI Tourist, a customer who churns because they never found a repeatable use case; and the Autonomous Customer Organization. Each links to its source essay.
Who is this glossary for? +
Anyone operating any stage of the journey: sellers who inherit what marketing qualified, onboarding teams who inherit what sales promised, CSMs and support who inherit both, and leaders who need one shared vocabulary across all of them. It is also written for candidates, since interviews test this vocabulary constantly.
How is the glossary maintained? +
Terms are added as the vocabulary genuinely shifts, with the page's modified date updated when content changes. Recent-era entries such as seat compression, outcome-based pricing, AI SDR and GTM engineer are included because they are in real circulation, not because they are fashionable; invented jargon does not get entries.