How do the best teams cover a long tail of customers without a CSM per account?
They split the book deliberately and then invest properly in the scaled half. Strategic accounts keep named CSMs. Everything below a revenue line goes to a pool where a small group of CSMs share the accounts, with no named owner, and the pool specialises by product area or segment so the depth comes from expertise rather than familiarity. This only works with one source of truth for account data, because a pooled CSM picking up an account cold has no memory to fall back on. The failure mode is calling it pooled when what you actually did was stop covering those accounts.
Go deeper
5 resources, 5 link-checked.
📄 Article
✓ Link checkedFreeAdvanced
How to cover a long tail without a named CSM per account, with two working models (strategic plus pooled, and centres of excellence) and named companies running each.
Lays out the three real ways to organise a CS team (by segment, by lifecycle stage, by engagement model) and what each one costs you, which is the actual decision a first-time CS leader faces.
Names three scalable structures: embedded digital experience team, centralised content with distributed strategy, and community hub with program satellites.
Forrester's read is that most CS organisations struggle for lack of a clear charter and a segmentation framework.
Tie each program to NRR, gross retention, time to value, renewal forecast accuracy, and health score accuracy.
The most complete breakdown of what goes into a health score: which four to six categories to weight, how to segment scores by journey stage, and the failure modes (too many metrics, too much subjective input).
Shows what a productised CS play looks like when written down for a whole team: a named motion, tied to a product stage, with the assets attached. Rare to see this published.
Notion has far more customers than CSMs, so its head of customer success has to cover the long tail with product and programs. She explains where a human is worth it and where it is not.