Expansion & Upsell Identification Playbook
Detects signals of growth opportunity within customer conversations. Identifies expansion intent, budget discussion, and product gap themes to support proactive revenue expansion.
Start building
Deploy this kit stack into your workspace. Customize bricks, scoring, and outputs to match your team.
Without this playbook
Most teams handle expansion & upsell identification through scattered call reviews, manager opinion, and isolated examples. Without a shared operational definition, the signals stay inconsistent and difficult to act on across volume.
With this playbook
A shared, repeatable lens for expansion & upsell identification - with structured outputs you can route into coaching, reporting, and workflow automation. Every conversation produces evidence, not just opinions.
Built for
CS managers, renewal teams, and account managers
When teams use it
- Renewal review and health scoring
- Churn risk alerting and escalation routing
- QBR preparation with structured evidence
Knowledge base
Supporting materials
The kits in this playbook work best when backed by reference materials that ground the evaluation. Upload these into your workspace knowledge base to improve accuracy and relevance.
Learn more about Knowledge BasesProduct catalogue and upsell/cross-sell pathways
Customer segmentation and expansion potential scoring
Pricing tiers and packaging for expansion conversations
Customer success plans with growth milestones
Account planning templates and expansion playbooks
In practice
How teams use these outputs
The structured outputs from this stack integrate into your existing workflows. Use them wherever you need repeatable, evidence-based signal from conversations.
Renewal review and health scoring
Churn risk alerting and escalation routing
QBR preparation with structured evidence
Account planning and expansion signals
Get started
Deploy this playbook in your workspace
Customizing creates a workspace-owned draft with this playbook's full kit stack. Adjust bricks, scoring, and outputs to fit your team, then publish when ready.