A Practical Framework for CS Segmentation: Scaled vs. Strategic
Most segmentation models I've seen start and end with ARR. Sort the customer list by contract value, draw a line or two, and assign CSMs. It's a reasonable first cut, but it tells you nothing about what a customer actually needs from you.
The better question is how much touch each customer needs to get to value, and what outcomes you're trying to drive with them. That leads to two lanes.
Two lanes
Scaled success is for SMB, transactional or long-tail customers. They need self-service onboarding, usage nudges and a good help center. Coverage is pooled CSMs or tech-touch only.
Strategic success is for enterprise and high-potential mid-market customers. They need deeper integration work, stakeholder alignment, business reviews and expansion planning. Coverage is a named CSM with support layered around them, like a solutions resource and an executive sponsor.
Everything else in the framework is about deciding which lane a customer belongs in and what happens once they're there.
What to segment by besides revenue
I'd look at four things alongside ARR.
Growth potential. Is there room to expand? Is their market growing? Are they launching new teams or products?
Complexity of the use case. How deeply integrated are they, and do they need configuration or training to be successful?
Relationship stage. Are they new, at risk, or champions? And are you actively engaged with them, or mostly reacting to whatever they send?
Strategic value. Are they a lighthouse account? Could they influence product direction or how the market sees you?
A small customer with big growth potential and a complex rollout might belong in the strategic lane. A large one with a simple, stable use case might do fine with less. If you want to go past two lanes into finer tiers, I've written about designing tiered playbooks for each segment.
Putting it into practice
Once you've decided the lanes, three things make the model real.
First, build journeys by segment. SMB customers get drip onboarding, usage-based nudges and lifecycle marketing. Mid-market gets CS playbooks, scaled QBRs and success templates. Enterprise gets strategic planning, relationships across multiple stakeholders, and executive reviews. Mapping the journey for each one is worth the time.
Second, assign coverage to match. Something like:
Tier 1: a dedicated CSM for strategic accounts and expansion targets.
Tier 2: pooled CSMs for mid-size accounts with moderate growth.
Tier 3: tech-touch for SMB accounts with stable or low engagement.
Third, measure each segment differently. For SMB, look at time-to-value, support deflection and activation rate. For mid-market, usage consistency, NPS and small expansions. For enterprise, retention, multi-product adoption and NRR. Holding a tech-touch segment to enterprise metrics just makes everyone look bad. There's more on picking metrics that actually matter if you're rethinking yours.
Keep it moving
Revisit the model every quarter. Customers grow, shrink, get acquired and change priorities, and a segment assignment from a year ago is probably wrong for some of them. When you add headcount, the lanes also tell you where it should go, which is most of the work in scaling the team without losing the personal touch.
Assigning accounts is the easy part. The real work is designing the experience each customer gets, and segmentation is where that starts.
If you want a second set of eyes on your segmentation model, get in touch.
