Reviewing whether segmentation matches customer needs

Compare the work customers need to do with the help promised by their assigned segment. Use customer conversations, direct customer observations and the experience of CSMs and executives involved in accounts to test whether the assignment still fits. Track exceptions alongside accounts following the default rule.

Look for a mismatch that changes coverage

Write down the assignment rule and service promise that applied, including when either changed. Separate accounts assigned under each version from accounts given exceptions so you can compare the default with the exceptions.

Look for recurring differences in the work customers need, not just in account labels. Gainsight’s customer conversations surfaced needs such as shaping a customer-success organisation and managing PMO-led change, executing a customer-success strategy in Gainsight, and building a customer-success team; repeated needs unlike a segment’s intended work warrant review.

Check for accounts whose opportunity or needs are hidden by the assignment signal. Looker’s ARR-only approach could have placed IBM, with a $12,000 pilot and hundreds of thousands of employees worldwide, in a digital-led programme despite its large expansion opportunity; Looker identified this as a limitation of using ARR alone.

Treat one outlier as a prompt, not proof that the rule should change. Look for the same unmet need or missed opportunity recurring among default assignments or exceptions, then test whether the current criteria explain it.

Default Segment Assignment vs. Exception Accounts: Customer Needs and Work

Inspect the route customers actually took

Gather observations from CSMs, executives involved in accounts and customers themselves. Gainsight describes detecting customer patterns through those conversations and by getting directly involved with customers; use that evidence to check what customers need across the lifecycle.

Compare the needs the segment is meant to serve with the work customers actually describe. Record the assigned segment, rule version, customer need, evidence gathered, exception status and any unresolved questions; keep accounts without confirmed evidence visible rather than treating them as a match.

Use the attributes that matter to the existing rule, such as ARR or employee count, alongside evidence of customer needs. Looker combined ARR and employee count to identify growth opportunity, while noting that employee count may not be the right metric for every company; Gainsight found reporting levels useful for its customer base but noted they may not distinguish another company’s customers.

Reviewing Segmentation Fit Against Real Customer Needs

Compare evidence fairly

Use the same definition of customer work and promised help when comparing accounts. Review a period long enough for that work to occur, count the accounts considered in each segment, and show how many still lack confirmed evidence.

Look for recurring exception patterns within each segment rather than relying on a memorable account. Compare the needs and opportunities of accounts following the default rule with those given exceptions, and note where the evidence does not explain why they were assigned differently.

Keep customer evidence separate from assumptions based on a single attribute. ARR alone failed to reveal IBM’s expansion opportunity in Looker’s example; a profile signal can prompt investigation, but customer needs and the rule’s other relevant attributes help test whether the assignment fits.

Key Metrics in Segment Review Process

Change the rule or fix the route

Change a segment’s default when recurring customer evidence shows that its current rule misses a shared need or opportunity. If the evidence concerns one account only, record an exception instead; state the affected accounts, revised service promise, capacity effect and reason for the decision.

Looker’s change illustrates how a missed opportunity can prompt a rule revision: it combined ARR and employee count, assigning one point for every $10,000 of ARR and one point for every 1,000 employees. The top 1–2% scoring hundreds of points were considered natural candidates for CSMs; Looker also noted that employee count may not suit every company.

Have a CSM leader coordinate the evidence and a leadership team make the decision, reflecting the roles Gainsight describes in segmentation work. Record the decision, the accounts affected and what evidence will be checked at the next review; explain any changed route to customers and invite corrections to their account information.

Updating Segment Rules Based on Recurring Evidence