Customer success team structure: tiers, book sizes and who does what
How many accounts should one CSM carry? Should CS own renewals? When do you need CS operations? There's no single right answer, but there are patterns that work, and most of them start with splitting customers by how much attention they need.
Three coverage tiers
| Tier | Who | Rough accounts per CSM | How they're served |
|---|---|---|---|
| Named (high touch) | Largest or most complex accounts | 10 to 25 | Dedicated CSM, QBRs, exec sponsor program |
| Pooled (mid touch) | Mid-size accounts | 30 to 80 | Named CSM, lighter cadence, playbooks do more |
| Digital (tech touch) | Smaller accounts | Hundreds, often a shared team | Emails, in-app guidance, webinars, a pooled team for issues |
These ranges are common rules of thumb, not standards. Adjust for how complex your product is, how much onboarding it needs, and how much revenue sits in each account.
Sizing a book by workload, not count
Example book check Account type Count Hours/month each Total Enterprise, stable 8 6 48 Enterprise, at risk 2 15 30 Mid-market 20 2.5 50 Total 128 hours/month
If a full-time CSM has about 110 hours a month for account work after meetings and admin, this book is overloaded even though 30 accounts sounds fine. The weekly workload check helps you see it early, and the free CSM capacity calculator does this math for you.
Core roles and when to add them
- CSM: owns outcomes, adoption and risk for a book of accounts. Your first hire.
- Onboarding specialist: add when onboarding is long and eats CSM time.
- Renewals or account manager: add when commercial work crowds out success work. Keep a clean handoff.
- CS operations: add around 8 to 10 CSMs, when data, tooling and reporting start slipping.
- Team lead: roughly one per 5 to 8 CSMs.
Who owns renewals?
Both models work. CS owning renewals keeps context in one place. A separate renewals team keeps CSMs out of price talks. Whichever you pick, write down who leads the conversation at 90, 60 and 30 days. Use the renewal prep checklist as the shared timeline.
Write it down
For each role, one paragraph: what it owns, what it hands off, and the two numbers it's measured on. Most CS confusion comes from overlap nobody named. Pair it with CS metrics and KPIs so every role has a scoreboard.
Questions
How many accounts should a CSM manage?
It depends on segment. Common ranges are 10 to 25 for large accounts, 30 to 80 for mid-size, and far more for digital coverage.
When should a company hire CS operations?
Often around 8 to 10 CSMs, when data, tools and reporting start slipping.
Should customer success own renewals?
Either model can work. What matters is a written owner for each step of the renewal.
Want the full routines?
The CS Agent Playbook has 14 ready-to-paste agent routines like this one, each with guardrails, a sample result and the failure to check for first. $39 for the PDF and a plain-text prompts file.
Related guides
- Customer success OKRs: examples you can adapt this quarter
- A weekly workload check that catches burnout before it shows up in tickets
- Customer success metrics and KPIs: the 8 worth tracking, and what each misses
- Customer success manager interview questions, and what good answers sound like
Free: prompt templates | churn risk calculator | churn rate calculator | CSM capacity calculator | escalation email generator | health score calculator | NRR and GRR calculator