Designing Tiered Customer Success Playbooks
When a CS team runs one playbook for every customer, two things happen at once. Your biggest accounts feel under-served, and your smallest ones quietly eat up time that should be going toward work that scales. Everybody's a little unhappy and nobody can say exactly why.
Tiering fixes that, as long as you think about it the right way. The point is to give each group of customers a different experience, not a smaller one. Once you've drawn the basic line between scaled and strategic customers, the next step is getting more specific about the tiers inside that split and what each one actually gets.
Pick criteria that mean something
ARR is the obvious place to start, and it's a fine baseline for deciding where people spend their time. But if it's the only input, you'll misjudge a lot of accounts. The criteria I'd look at together:
Revenue or ARR, as the starting point.
Strategic value: accounts that give you brand visibility, case studies, or a foothold in a new market.
Deployment complexity: customers who need more technical guidance or customization to succeed.
Growth potential: real room for expansion or a second product.
Engagement: customers who show up to business reviews and give you product feedback.
Then keep the number of tiers small. Three, maybe four. Something like Strategic (high-value, often multi-market, with dedicated CSM coverage), Growth (mid-tier accounts with strong expansion potential) and Scaled (lower ARR or self-serve, supported mostly through automation and education). More tiers than that and your reporting and execution both get messy fast.
A different playbook for each tier
Every tier's playbook should have the same bones: a clear objective, measurable outcomes, and actions a CSM can repeat. What changes is the intensity.
For Strategic accounts, the goal is partnership, retention and multi-year expansion. That usually means executive business reviews twice a quarter, a dedicated CSM plus a technical lead, a custom success plan with health metrics built around the customer's goals, and things like roadmap previews or joint workshops that make them feel like insiders.
For Growth accounts, you're trying to speed up adoption and catch expansion triggers early. One structured QBR a quarter, shared CSM coverage or a pod, automated usage dashboards, and a clear playbook for upsell and cross-sell conversations. This is the tier where CSMs most need to recognize the expansion signals worth acting on, because nobody is going to hand them the opportunity.
For Scaled accounts, the goal is consistent value at a low cost to serve. Automated onboarding and success nudges, a community or knowledge base for self-service, on-demand webinars and office hours, and a data-driven health score that tells you when a human needs to step in.
Your systems have to talk to each other
Tiering falls apart when the data is scattered. At a minimum you need a CRM as the source of truth for account data, ARR and stage; a CS platform to run health scores, alerts and playbook automation; a data warehouse or BI tool for deeper analysis of churn and usage; and communication tools that can deliver automated engagement.
When those line up, the tiers start running themselves in useful ways. A Growth account whose health drops can trigger a save play automatically. A Scaled account with heavy usage can drop into an upsell sequence. None of that is possible if your health score lives in a spreadsheet nobody trusts.
Mistakes I'd avoid
The most common one is overcomplicating it. Too many tiers or too many criteria and nobody can explain where an account belongs. Close behind is treating segments as permanent. Customers change, so review your tiers every quarter based on ARR changes and behavior.
Watch for customers whose value isn't in their spend. A mid-size account that's a vocal advocate may deserve more attention than its contract suggests. And make sure every tier has its own training, resources and playbooks. A tier without enablement is just a label.
Check whether it's working
Once the model is live, look at retention and expansion by tier, account coverage per CSM, health score changes after playbook interventions, satisfaction or NPS by tier, and churn reasons by tier. If one tier is growing while another struggles, you probably have a resourcing imbalance or a playbook that doesn't fit. Metrics by tier also keep you honest about which numbers actually matter for each group.
Over time, I expect tier assignment to get more dynamic, with CS platforms using behavior, usage and sentiment to move a customer from Scaled to Growth after sustained adoption, or to flag an enterprise account before renewal risk builds. The data can make the suggestion. Someone on your team should still make the call.
If you're trying to figure out where your tiers should land, let's compare notes.
