What Is Customer Success? Roles, KPIs, and How to Build the Team — A Practical Guide

As subscription services have become the norm, "sell and move on" no longer works. If customers don't experience results after signing, they churn quickly. The function that takes responsibility for the customer's success after the contract is Customer Success (CS).

But practical questions — "How is it different from customer support?", "How do we divide roles with sales?", "Which KPIs should we track?", "How do we build the team?" — aren't answered by definitions alone.

This article explains customer success from the ground up: the definition, a 3-way comparison matrix against sales and support, a relationship map that organizes easily confused KPIs onto one page, a build-out roadmap for the organization, the failure patterns that commonly occur in the field, and the model for active operations using a digital sales room (DSR). As a pillar (hub) article that routes to detailed posts on each metric and topic, it's designed to give you the full picture of CS.

Key Takeaways

• Customer success is the practice of proactively guiding customers to their outcomes, preventing churn, and maximizing LTV — "offensive" customer engagement.
• Customer support is "reactive problem-solving," sales is "pre-contract new acquisition," and CS is "post-contract outcome creation and revenue expansion."
• KPIs are meaningless in isolation. Design them as a chain from leading to lagging indicators: "onboarding completion rate → health score → churn rate → NRR → LTV."
• Build the organization by switching segments, touch models, headcount, tools, and KPIs by phase (launch → scale → optimize).
• "Turning CS into a support team," "setting churn as the only KPI," and "handling every customer with high-touch" are classic failure patterns.

What Is Customer Success?

Customer success is the practice in which a company proactively and continuously helps customers achieve the outcomes (success) they aim for through a product or service. The premise is that when customers succeed, they continue using and expanding the service, which in turn maximizes the provider's LTV (lifetime value).

Starting from "the customer's success"

Traditional customer engagement centered on the provider's viewpoint: "how do we get them to use our product?" Customer success flips this, starting from the customer's outcome: "what does the customer want to achieve?"

For example, when selling accounting software, the provider's view tends to make "get them to use every feature" the goal. But starting from the customer's success makes the goal the customer's own outcome, such as "cut monthly closing time in half." Feature usage is merely a means. This shift in perspective is the essence of customer success.

Three meanings: "concept," "department," and "role"

The phrase "customer success" is used in three different senses depending on context. Since this is a common source of confusion, let's clarify it first.

This article mainly covers customer success as a "department/organization" and how to operate it. The role that directly handles customers is called a CSM (Customer Success Manager).

A simple example

A gym makes it easy to understand. After a member joins, if you leave them alone, many become inactive within a few months and eventually cancel. That's churn.

In contrast, suppose a trainer interviews the member right after joining about their goal (e.g., "lose 5 kg in three months"), designs a workout plan, reaches out when they stop coming, and proposes a higher goal once results appear — this end-to-end, proactive accompaniment is customer success. When the member feels "I'm seeing results," they continue and even sign up for higher-tier plans like personal training. That's the maximization of LTV.

Sales vs. Customer Support vs. Customer Success

The biggest stumbling block in understanding customer success is the difference from sales and customer support. People frequently search "customer success vs. sales" and "customer success vs. support." Let's make each distinction clear.

Note that, confusingly, the abbreviation "CS" refers to both Customer Success and Customer Support. If you build an organization while it's ambiguous which one "the CS team" means, you create a breeding ground for the "support team" trap described later. For clarity, this article always spells out "customer support."

Difference from customer support: reactive vs. proactive

The decisive difference between customer support and customer success is "reactive vs. proactive."

Customer support acts in response to a customer's inquiry or complaint. When a problem occurs — "I can't log in," "I don't know how to use it" — its job is to resolve it. It is fundamentally "reactive," waiting for the customer to act.

Customer success moves before problems occur. It detects signs — "this customer is two weeks past onboarding but hasn't used the core features," "usage is dropping" — and reaches out first. Intervening proactively even when the customer hasn't reached out is the biggest difference from support.

Difference from sales: pre-contract vs. post-contract

The difference between sales and customer success lies in "which phase they engage the customer" and "how they affect revenue."

Sales has the contract (closing) as its goal. It acquires new customers and generates the "first revenue (flow revenue)" in the form of a contract.

Customer success starts after the contract. It gets signed customers to achieve outcomes and maximizes the "accumulating revenue (stock revenue)" of renewals and add-ons. While sales creates revenue at a "point," CS keeps growing revenue along a "line."

That said, the two are not disconnected. When sales hands off the information gathered at signing (the customer's challenges, decision-making structure, expectations for adoption) to CS, the onboarding ramp changes dramatically. The quality of the sales-to-CS handoff becomes a major dividing line for churn, as discussed later.

3-way comparison matrix

Organizing sales, customer support, and customer success along five axes — scope of responsibility, primary KPIs, time horizon, definition of success, and effect on revenue — makes the role differences clear at a glance. Many explanations stop at a "CS vs. support" two-way comparison, but what searchers truly confuse is the three-way picture that includes sales.

The key point of this table is that only customer success engages the customer "continuously throughout the contract" and is responsible for "expanding revenue." It neither completes per problem like support nor completes at the contract like sales.

If you want a broader view of role division across the entire revenue organization (marketing, inside sales, field sales, CS) from pre- to post-contract, see our guide on visualizing sales KPIs.

Why Customer Success Matters Now

Customer success is a relatively new concept that spread among U.S. SaaS companies in the late 2000s. It is generally said to have been established by subscription companies such as Salesforce as a specialized function to prevent churn. Why is it so emphasized now? Three structural changes lie behind it.

From perpetual licenses to subscriptions: a shift in revenue structure

The biggest factor is the shift in business models.

In perpetual (sell-once) businesses, almost all revenue is locked in the moment a contract is signed. Bluntly put, how the customer used the product afterward had little effect on the provider's revenue.

Subscriptions are the opposite. The revenue obtained at signing is only a small fraction of the total; revenue accumulates only as the customer keeps using the product. For a one-year contract, the first month yields one-twelfth of annual revenue. The remaining eleven-twelfths depend on whether the customer keeps wanting to continue. In other words, because most revenue is now decided "after the contract," a function responsible for post-contract customer success became indispensable.

The economic value of retaining existing customers

The idea that "retention is more efficient than acquisition" is backed by data.

Research by Frederick Reichheld and colleagues at Bain & Company found that increasing customer retention by 5% increases profits by 25% to 95% (source: Harvard Business Review, "The Value of Keeping the Right Customers," 2014; the underlying research is Reichheld & Sasser, "Zero Defections," HBR 1990). Note that the upper bound of 95% is based on a specific industry case and doesn't apply directly to every sector, but the direction — "retaining existing customers strongly drives profit" — is widely supported.

It's also commonly said that "acquiring a new customer costs about five times as much as retaining an existing one" (the so-called 1:5 rule). This is cited more as a rule of thumb than rigorous research, but it's widely referenced as a warning against an acquisition-heavy cost structure. Either way, customer success — which prevents churn and grows existing customers — is a reasonable investment from a revenue-efficiency standpoint.

Changing buying behavior: customers want to "self-serve"

The third factor is the change in customer behavior.

According to Gartner, B2B buyers spend only 17% of their time meeting with potential suppliers (sales reps) during the evaluation process (source: Gartner, "The B2B Buying Journey"). Furthermore, a 2026 Gartner survey reports that 67% of B2B buyers prefer a "rep-free experience" (source: Gartner, March 2026).

The same is true after the contract. Customers want a state in which they can master the product and produce results on their own (self-serve) without asking a rep about every little thing. That's precisely why customer success — which grasps usage through data and delivers needed support before customers stumble — is growing in importance.

The Main Roles and Responsibilities of Customer Success

Customer success work is easiest to understand when organized along the customer's contract lifecycle (sign → adopt → retain → expand). The main roles are the following five.

1. Onboarding (realizing initial value)

Onboarding is the process of supporting customers from signing until they realize their first outcome (initial value). It includes setup, initial training, and creating an adoption plan.

This is the most important stage in customer success. Customers who stumble during onboarding are hard to recover no matter how much you follow up later, and it is the single biggest cause of early churn. Conversely, if you can create a success experience of "I'm glad we signed" here, subsequent retention rises dramatically. For concrete onboarding design and DSR usage, see How to Use a DSR for Customer Success Onboarding.

2. Adoption (driving usage and entrenchment)

After onboarding, you support customers as they embed the product in daily work and expand their usage. Watching usage data, you encourage adoption of unused features and propose more advanced ways to use the product.

The role of adoption support is to prevent the "signed but unused" state (so-called shelfware).

3. Retention and churn prevention

At renewal time, you work to get customers to continue. Yet renewal outcomes aren't decided in the negotiation just before renewal — they're decided by months (or a year) of accumulated usage.

Great customer success doesn't scramble when the renewal month arrives; it routinely monitors customer health (health score), detects churn signals early, and acts.

4. Upsell and cross-sell (expansion / NRR)

In line with the customer's growth and outcomes, you propose moving to higher-tier plans (upsell) or adding related services (cross-sell).

This is not mere additional selling. It's accepted precisely because you propose the "next step" when the customer has produced results and is aiming for the next level. This expansion revenue is the main driver that pushes NRR (net revenue retention), discussed later, above 100% — the growth engine of a SaaS business.

5. The product feedback loop

Customer success, which engages customers at the closest distance, is where the customer's raw voice (requests, complaints, points of friction) gathers. Bridging this to product and marketing teams to drive product improvement is also an important role. Resolving factors that block customer success at the product level reduces churn across all customers.

The CSM's Role and a Day in the Life

For those who want to know "what customer success is" as a job, let's look concretely at how a CSM (Customer Success Manager) — who directly handles customers — works.

Three abilities a CSM needs

A CSM's job is to "understand customers best and accompany them to success." The abilities needed for that fall into three broad areas.

• Listening ability: The ability to draw out the outcome (the result the customer truly wants to achieve). You capture the real challenge behind surface-level requests.
• Data analysis ability: The ability to read what's happening to each customer from usage and health scores. It's the starting point for proactive support.
• Cross-functional influence: The ability to move product for improvements, coordinate with sales for handoffs, and move stakeholders within the customer's organization.

These differ in nature from the "accurate, rapid problem-solving" required of customer support. The proactivity to find issues and act on your own — rather than waiting passively — is most valued as a CSM's aptitude.

A typical day for a CSM

A dedicated CSM's day roughly flows like this.

• Morning: Check the health-score dashboard, list customers whose scores dropped or whose usage stalled, prioritize them, and decide the day's actions.
• Late morning to afternoon: Recurring online meetings with assigned customers — reviewing usage, resolving friction, and proposing the next adoption step.
• Afternoon: Follow up on the progress of new customers in onboarding — setup support and adjusting the adoption plan.
• Evening: Share customer requests with the product team. Organize the status of customers nearing renewal and prepare renewal and upsell proposals.

The key is that the day starts with "checking data," not "handling inquiries." Rather than waiting for customers to reach out, you act proactively from the data — this concisely captures the essence of the CSM's job.

CSM and CS Operations (CS Ops)

As the organization scales, a behind-the-scenes role called CS Operations (CS Ops) emerges to support CSMs. It handles health-score design, tool setup, and building data-analysis infrastructure, creating an environment where CSMs can focus on customers. In the launch phase a CSM does double duty, but this division pays off in the scale phase.

Customer Success KPIs and a Relationship Map

Customer success has many KPIs, and it's the biggest stumbling block for beginners. LTV, churn rate, NRR, NPS, health score, onboarding completion rate — there are plenty of explanations that merely "list" these, but what matters is the relationship among the metrics.

KPIs split into "leading" and "lagging" indicators

Think of customer success KPIs in two broad types.

• Leading indicators: Indicators that predict future outcomes and move early. Onboarding completion rate, product usage rate, health score. Improvable in daily operations.
• Lagging indicators: Indicators that express final outcomes and move with a delay. Churn rate, NRR, LTV. They appear as a result of accumulated leading indicators.

A common failure is watching only lagging indicators (churn or LTV) and reacting to every swing. By the time a lagging indicator worsens, it's too late. The right approach is to improve leading indicators daily and design lagging indicators as "things that follow."

KPI relationship map: understand the connections on one page

The main KPIs are connected in a chain of cause and effect like the following. This relationship map is the foundation of customer success KPI design.

[Leading indicators: improve daily]        [Lagging indicators: follow later]

Onboarding completion rate ↑
        │
        ▼
   Product usage / adoption ↑
        │
        ▼
   Health score ↑   ──────►  Churn rate ↓
                                  │
                                  ▼
                            NRR (net revenue retention) ↑
                                  │
        Upsell / cross-sell ──────┤
                                  ▼
                             LTV (lifetime value) ↑

Read it like this: customers who complete onboarding master the product and have high health. Healthy customers are less likely to churn, so churn rate falls. As churn falls and unit price rises via upsell and cross-sell, NRR (net revenue retention) exceeds 100%. That accumulation maximizes lifetime value (LTV) per customer — this is the KPI story of customer success.

Quick reference for each metric

Let's grasp the outline of each metric. We'll dive deeper in each metric's dedicated article.

"Healthy" levels for NRR and LTV vary widely by industry and business model. For instance, NRR "above 100% means existing customers alone are growing revenue — a good state," and around 120% is often cited as a benchmark for top SaaS companies, but that's only a general reference value. It's important to set benchmarks appropriate to your own business phase.

Key concepts to keep in mind

As a pillar article, this post won't go deep into each metric's calculation, but here are concepts you should know as design premises.

There are two types of churn rate: customer churn measured by the "number of customers" lost, and revenue churn measured by the "revenue" lost. Many small customers churning may have little revenue impact, while a single large customer's churn can cut revenue significantly. Watching only one misreads reality, so use both. Looking at "net revenue churn," which accounts for the increase from upsell, shows the real revenue change including expansion.

NRR incorporates "expansion": NRR (Net Revenue Retention) is calculated against the existing customer revenue at the start of a period, subtracting decreases from churn and downgrades and adding increases from upsell and cross-sell. If the increase from upsell exceeds the decrease from churn, revenue grows even with zero new customers. That's why NRR is called the "SaaS growth engine."

LTV is the "goal of maximization": LTV (lifetime value) is the total profit one customer brings over the entire relationship. When churn falls, the relationship lengthens; when upsell raises unit price, LTV grows. In other words, improvements in the other metrics explained so far all converge on LTV.

We plan to explain each metric's formulas, improvement tactics, and benchmarks in detail in dedicated articles. In this post, first grasp the big picture of "how the metrics connect."

The trap of narrowing to a single KPI

When asked "which KPI should we track after all," it's tempting to answer "churn rate." But narrowing to a single KPI is dangerous.

For example, if you track only churn rate, "preventing cancellations" becomes the goal, and you forcibly retain even customers who should churn (those poorly matched to you). The field burns out, attention to expansion (upsell) fades, and NRR ultimately fails to grow. The iron rule is to balance leading and lagging indicators and operate across the entire relationship map.

How to build a health score

Within the relationship map, the health score is the linchpin for "detecting churn signals earliest." A health score aggregates multiple data points into a single indicator of customer health. There's no fixed formula; you design it to fit your own churn patterns. Typically, you score and sum elements like the following.

• Usage: Login frequency, core-feature usage rate, active users. The most basic and predictive element.
• Engagement: Responses to inquiries/support, viewing of shared content, attendance at meetings.
• Progress toward outcomes: Degree of achievement of the goals set during onboarding.
• Relationships: Connections with key persons in the customer's organization, and whether the champion is still there (a champion's departure is a classic churn risk).

You don't need to build a precise score from the start. The realistic approach is to first score one or two tendencies you can observe in-house — such as "customers whose login frequency dropped are more likely to churn" — and improve accuracy as you operate. What matters is not staring at the score but actually taking action on customers whose score has fallen.

Touch Models (High/Low/Tech) and Segment Design

Handling every customer with the same intensity isn't realistic. In customer success, you segment customers by contract size and the like, and serve each with a suitable "touch model."

The three touch models

Segmentation criteria by ARR / contract size

Which customer gets which model is generally divided by ARR (annual recurring revenue) or contract size. Large accounts have a big revenue impact when they churn, so serve them high-touch and intensively. Small accounts are numerous and have small LTV, so serve them efficiently with tech-touch — that's the basic idea.

That said, you also factor in elements other than ARR (growth potential, strategic importance, influence) — for example, exceptionally making a small-contract customer high-touch when their future growth potential is large.

Different KPIs for each model

The KPIs you emphasize change by touch model. In high-touch, per-account NRR and relationship quality are central; in tech-touch, "how much you raised product usage and onboarding completion rate without human effort" is central. Note that evaluating with a single company-wide KPI without designing touch models will fail to match field reality.

A Roadmap to Build the Customer Success Organization

"We understand CS matters. So how do we build the team?" — this is the practical core that many explanations omit. Rather than abstractions like "do it company-wide" or "collaborate across departments," here's what to change by phase.

Phase 0: Aligning premises before launch

Before hiring, first define "what does customer success mean for us." If you build the organization while this is vague, CSMs become "order-takers by default." Also grasp current churn reasons even roughly, and identify the first problem to solve (often onboarding failures). This "definition of customer success" becomes the starting point for KPI design, health-score design, and CSM evaluation criteria, so it's worth articulating at the executive level even if it takes time.

Phase 1: Launch (high-touch focus, standardize onboarding)

At first, narrow your targets, face large accounts with high-touch, and build the onboarding "template." What matters at this stage isn't heroics by individuals but articulating success patterns as reproducible processes. The template you build here becomes the foundation for later low-touch and tech-touch.

Phase 2: Scale (segmentation, introduce low-touch)

When customer count grows and high-touch alone can't keep up, segment customers and introduce low-touch (group seminars, shared content) for mid-size customers. At the same time, set up the health-score mechanism so you can judge by data which customers to intervene with.

Phase 3: Optimize (tech-touch, data operations)

To scale further, build tech-touch (automated emails, in-app guides, community) for small, numerous customers and support self-serve without human effort. CSMs concentrate effort on customers who need intervention, based on data.

Phase-by-phase roadmap table

The important point is that as phases progress, the KPIs you track shift from leading to lagging indicators. Chasing NRR right away in the launch phase is impossible to improve if the foundation (onboarding) isn't built. Choosing KPIs that fit your phase is what determines the success of your org build-out.

The often-overlooked "sales-to-CS handoff" design

What's often neglected even though it determines success in every phase is the design of the handoff from sales to customer success.

In the process of winning the deal, sales accumulates information essential for onboarding: the customer's challenges, the outcomes they expect from adoption, the people involved in the decision, the temperature of the field. Yet if this information isn't handed off and CS takes over, CS has to rebuild the relationship from scratch, and the ramp slows dramatically. In the worst case, CS learns only at its first meeting with the customer that sales had over-promised to close the deal.

To prevent this, don't leave the handoff to individual goodwill — standardize it as a process. Template the items to hand off (the customer's goals, definition of success, risk factors, key persons), and always hold a handoff meeting with both sales and CS right after signing. If you manage the sales-stage information in a form you can also share with the customer, this handoff becomes far smoother. The value of having a single information foundation from sales through CS is also important from the perspective of building a digital sales room.

Common Failure Patterns and How to Avoid Them

In launching customer success, similar failures recur. Here are five representative patterns, with their signs and how to avoid them.

Especially common is the first one, "turning into a support team." It's not rare for a company to simply rename its existing customer support department to customer success. Swapping the sign doesn't help; if the work remains reactive — waiting for inquiries — it can't be called customer success. "Are you moving on your own even when the customer hasn't reached out?" is the litmus test that separates support from success.

Next, easy to fall into is "high-touch for every customer." Early on, with few customers, you can serve everyone intensively, but trying to keep that intensity as customers grow breaks CSM capacity. The time per company shrinks, service quality drops, and everything ends up half-baked. It's important to decide early to switch touch models as customer count grows.

And hard to see is "becoming an order-taker." Even if you think you're responding politely to customer requests, if it doesn't connect to the customer's outcomes, you're just a convenient help desk. Not "listening to what the customer says" but "proposing what the customer needs to succeed" — the presence or absence of this initiative separates a customer success org that drives outcomes from one that doesn't.

Active Customer Success with a DSR

The ideal of customer success is "proactive support," but in reality you hit a wall: you lack the material to judge "which customer, when, and what to act on." If you can't see what state a customer is in now, you can't anticipate.

This is where a digital sales room (DSR) is effective. A DSR consolidates documents and content in a dedicated space shared with the customer and lets you visualize, as viewing data, when, what, and how much the customer viewed. DSRs are often used in the sales phase, but they show their true value precisely in post-contract customer success.

Visualize customer health with view tracking

When you share onboarding materials, adoption guides, and QBR (Quarterly Business Review) materials on a DSR, you can see which content the customer is interested in and where they're stuck. This becomes valuable input for the health score. A customer who "hasn't opened the shared materials at all after signing" is a clear churn signal.

Detect churn signals

Changes in viewing data function as an early warning of churn. A previously frequent customer's access suddenly stops; they're not viewing materials even though renewal is near — catching such signals lets you act before churn is decided. It's far faster than relying solely on surveys and interviews for a qualitative read.

Identify the best timing for upsell proposals

Conversely, rising engagement signals (repeatedly viewing higher-tier plan materials, showing interest in related-feature pages) are a good chance for upsell and cross-sell. Gartner reports that buyers who used supplier-provided digital tools in combination with a sales rep were 1.8 times more likely to reach a high-quality, low-regret deal than buyers who proceeded on their own (source: Gartner, "The B2B Buying Journey," cited above). In other words, the key is combining human accompaniment with digital tools. Even as customers who "prefer a rep-free experience" increase, a DSR that respects the customer's pace while proactively delivering needed information is a concrete implementation of this "human × data" active customer success.

For concrete examples of operating QBR and renewal-proposal sharing on a DSR, also see How to Share QBR Materials and A CS Team Case Study.

The Benefits of Adopting Customer Success

Let's organize what we've covered as adoption benefits.

• Lower churn rate: Catch churn signals early and raise retention.
• Maximized LTV: Grow lifetime value through continuation and upsell/cross-sell.
• Higher NRR: Aim for a state where existing customers alone grow revenue (NRR above 100%).
• Higher customer loyalty: Accompanying outcomes deepens trust and leads to recommendation (NPS).
• Accelerated product improvement: The customer's raw voice reaches the product, raising satisfaction for all customers.
• Better acquisition efficiency: Referrals and word-of-mouth from loyal customers lower acquisition cost.

These aren't independent benefits; as the KPI relationship map shows, they chain together. The strength of customer success is that once you spin up one virtuous cycle, the other benefits grow in tandem.

A Typical Success Scenario: Start with Onboarding Improvement

Finally, here's how everything connects in practice, shown as a typical success scenario. Read this not as a specific company's case but as a commonly seen pattern of improvement.

A certain SaaS company struggled with early churn after the contract. Investigating, it found that many churned customers shared a trait: "they had barely used the core features in the first month after signing." Onboarding wasn't working.

So the company first built an onboarding "template." Right after signing, it interviewed the customer about the outcomes they wanted, defined the adoption steps to reach in the first 30 days, and had CSMs accompany that progress. It also made each customer's progress through the adoption steps trackable via data, so reps could proactively reach out to stuck customers.

This first improved the leading indicator "onboarding completion rate." As completion rate rose, the lagging indicator "churn rate" began to fall a few months later. With more customers ramping up healthily, CSMs could devote time to upsell proposals, and eventually NRR exceeded 100%, approaching a state where existing customers alone grew revenue.

This flow is exactly the "chain from leading to lagging indicators" explained repeatedly in this article. What matters is not chasing lagging indicators like NRR or LTV from the outset, but identifying "the first leading indicator to solve" from your own churn patterns and starting there. In many cases, the starting point is improving onboarding.

For the reality of team operations and launch, also see A CS Team Case Study and An Interview with a CS Leader.

Summary

Customer success is "offensive" customer engagement that proactively accompanies customers' outcomes, prevents churn, and maximizes LTV. Unlike customer support, which waits for inquiries, and unlike sales, whose goal is winning the contract, it is responsible for both the customer's success and revenue expansion throughout the contract.

To produce results in practice, the keys are: design KPIs connected as a relationship map ("onboarding completion rate → health score → churn → NRR → LTV") rather than chasing them in isolation; segment customers and use touch models appropriately; and switch the indicators you track according to the organization's phase.

And what underpins proactive support is customer data. If you visualize customer state with a mechanism like a DSR, the judgment of "which customer, when, and what" for proactive support can be made based on data rather than intuition. Start by defining what "customer success" means for you, and take your first step into customer success.

Frequently Asked Questions (FAQ)