Customer success segmentation

Customer success segmentation groups accounts with similar needs, so each group has a service approach the team can deliver. Start with the work customers need to complete, then consider account value and delivery capacity. Contract value may help organise a portfolio, but it does not describe every customer's need for help.

Decide what the segments will change

Define the coverage decision before creating labels. Are you deciding which accounts need a named success lead, which can use a shared team, or where guided resources need a human exception route? If two proposed groups face similar obstacles and receive the same service, they may not need separate segments.

Choose the unit of assignment. One organisation may have several divisions with different workflows and owners. Decide whether coverage applies to the whole account or to a defined part of it, and record exceptions where one label would hide a material difference.

Align segment definitions across teams

Where several functions use account segments, agree on what each label means and how it affects customer coverage. A shared definition across Customer Success, Sales and Marketing can reduce the risk of teams using the same label for different kinds of accounts.

Customer Success leaders can coordinate this work because they see how customers fare after the sale. Include colleagues who work with accounts in other functions so the assignment rule reflects the customer relationship, not only one team’s view.

Describe need and value separately

For each account, assess the coordination its work requires. Consider configuration, dependencies on other teams, customer decision makers and how often the workflow changes. Check those observations with people who know the account; company size is only a possible clue.

Then consider current contract value and any credible strategic value beyond it. Keep a proposed growth opportunity labelled as a possibility until the customer has confirmed a need. The purpose is to allocate limited team time while giving every group a workable service route.

Use the two assessments to propose a default. Repeatable work may suit guidance and a shared contact. Work involving occasional decisions may suit a pooled team. Continuing coordination across stakeholders may warrant a named lead.

These are starting points, not fixed tiers: a small account may need temporary live help with a blocker, while a large account with settled work may need little routine contact.

When identifying patterns, gather observations from people who know accounts and from direct customer interactions. Comparing what customers need, rather than relying on one attribute alone, can reveal differences that a revenue or size threshold would miss.

Assess the value of serving a group alongside the effort and difficulty involved. Potential value can include expansion opportunity, retention, brand value, advocacy or useful product feedback; the balance will vary by business and segment.

Key Metrics in Customer Success Segmentation

Use customer patterns to select inputs

Build the input set from what customers need across their lifecycle, rather than beginning with standard thresholds for revenue or employee size. Compare observations across accounts and look for the attributes that help explain why customers need different kinds of support.

Useful candidate attributes can include industry, growth rate, sales strategy, the type of customer leader, budget and the customer data available. These are possible inputs, not a checklist: retain an attribute only if it helps distinguish customers whose work or support needs differ.

Treat scoring as a local assignment rule

Looker’s example combined annual recurring revenue (ARR) with employee count as an indicator of growth opportunity. Its model assigned one point for every $10,000 of ARR and one for every 1,000 employees, then grouped accounts by score; the top 1–2% were considered natural candidates for a customer success manager. Those figures describe that company’s model, not a universal threshold.

Define the service for each group

Record the guidance customers can use, how they ask a success question, how they report a technical fault and who owns an exception until the next step is clear. State when the assignment will be reviewed. Automated messages alone do not provide an exception route unless someone can act when they reveal a problem.

In a hypothetical approvals product, one group might need a named lead to coordinate regional policy owners. Another might follow a standard approval route and contact a shared team when a policy or access question blocks progress. Both need a way to complete their task; their routine contact differs.

Check capacity and apply the rule

Estimate the preparation, conversations, follow-up, shared programmes, exceptions and handoffs created by the proposed service. Compare that work with available team time. If the promise exceeds capacity, revise the service design or add capacity before assigning more accounts to it. An account-to-manager ratio from another business cannot establish capacity for this portfolio.

Record each assignment, the evidence behind it, the responsible person or team and any exception. Give customer-facing teams the same current contact route. When a named contact changes, transfer open commitments and explain the new route to the customer.

Review an assignment when the work changes: a new integration, a changed customer owner or repeated coordination needs may call for more help; a completed rollout may call for less. Check whether the customer can complete its intended task and reach the right person when it cannot.