Here's a question worth auditing honestly: what fraction of your CS team's time goes to expansion — the conversations that grow accounts and drive NRR — versus repeat onboarding and reactive explanation? For most teams the ratio is backwards. The people best positioned to grow revenue from existing customers spend most of their time on work that doesn't grow anything.
The opportunity cost is enormous. Expansion is where net revenue retention comes from, and NRR is what determines whether the business compounds. A CSM in an expansion conversation is doing some of the highest-leverage work in the company. A CSM re-explaining the same onboarding step is doing some of the lowest. Every hour shifted from the second to the first is a direct lift on the metric that matters most.
Why the ratio is backwards. Onboarding and reactive explanation are urgent and constant — a confused customer needs help now — so they crowd out expansion, which is important but rarely urgent. Without a way to handle the urgent repetitive work, CSMs are perpetually reactive, and expansion gets whatever time is left over, which is little.
The fix is freeing the time, then pointing it at expansion. Move the repetitive onboarding and reactive explanation to a conversational agent, and the CSM's time opens up. Point that freed time deliberately at expansion — the in-product upgrade moments, the usage-cap conversations, the "what would help you next" discussions — and CS becomes an NRR engine instead of a cost center. The team didn't get bigger; its work got more valuable.
Frequently asked questions
What should CSMs spend their time on?
Expansion — the conversations that grow accounts and drive net revenue retention — rather than repeat onboarding and reactive explanation, which don't grow revenue.
Why do CSMs end up doing so little expansion?
Because urgent, constant onboarding and reactive support crowd out expansion, which is important but rarely urgent. Freeing the repetitive work lets CSMs redirect to expansion.