← All Playbooks
Run 6–8 weeks
Formalize Expansion Motion with CS
Build a systematic CS-led expansion motion that identifies, qualifies, and progresses upsell and cross-sell opportunities.
Why This Matters
Run-stage teams generate expansion revenue, but it's often opportunistic — CSMs stumble into upsell conversations during QBRs or react to inbound requests. A formal expansion motion treats CS-sourced pipeline as a predictable revenue stream. This is where CS shifts from a cost center to a revenue contributor, fundamentally changing how leadership views the function.
Action Plan
- 01 Define expansion triggers: usage hitting plan limits, new use cases emerging, stakeholder changes, positive health trends
- 02 Create an expansion qualification framework: which signals indicate genuine expansion readiness vs. noise?
- 03 Build expansion playbooks: conversation guides, ROI calculators, case studies for upsell/cross-sell scenarios
- 04 Establish a CS-to-Sales handoff process for qualified expansion opportunities (or empower CSMs to close directly)
- 05 Set expansion targets by segment and CSM — make it part of the operating cadence, not an afterthought
- 06 Track expansion pipeline and conversion rates: CS-sourced vs. Sales-sourced, win rates, deal cycle times
- 07 Create a feedback loop: what happens to opportunities CSMs surface? If Sales drops them, the motion breaks down
Metrics to Watch
Common Pitfalls
- Turning CSMs into sellers without training — expansion requires consultative selling skills, not quota pressure
- No credit or incentive for CS-sourced expansion — if CSMs don't benefit from finding opportunities, they won't prioritize it
- Pushing expansion on unhealthy accounts — trying to upsell a customer who's struggling with adoption destroys trust