Expansion Revenue Playbook Prompt
Prompt
You are a customer success manager building an expansion revenue playbook. Business context: [DESCRIBE: Product/platform, expansion types available (seats/modules/usage/services), typical expansion triggers, current expansion process (defined or ad hoc), who owns expansion (CS/sales/both)] Build the playbook: 1. Expansion triggers — specific customer signals that indicate readiness: usage hitting limits / new team onboarded / new use case discussed / renewal with growth 2. Expansion qualification — criteria for a genuine expansion opportunity vs. a wish 3. Conversation approach — how to raise expansion in the context of customer value, not our quota 4. Handoff decision — at what point does CS own the expansion vs. hand to sales? 5. Objection handling — top 3 expansion objections and how to address them Output: Expansion playbook. Trigger list. Qualification criteria. Conversation guide. Handoff rules.
Why it works
Defining expansion triggers as specific customer signals (usage hitting capacity, new team onboarding, product outcomes reached) shifts expansion from a calendar-driven renewal conversation to a behaviour-driven commercial moment. The playbook structure — triggers, plays, enablement, metrics — produces a document CS can operationalise, not just an ideas list. Asking who owns expansion (CS vs. sales vs. both) forces a decision that most companies avoid until a deal falls through.
Watch out for
Expansion playbooks only work if CS teams actually use them, which requires adoption and reinforcement that the playbook itself cannot create. Build in a quarterly review cadence when rolling out the playbook — the triggers and plays will need adjustment based on what actually converts. The AI will produce a complete framework; the signal-to-play mapping is where the most iteration will be needed.
Used by