expansion-caselisted

Builds the internal business case your champion has to carry without you in the room, rather than the pitch you would give. Trigger whenever the user says "expansion case", "business case", "upsell", "cross-sell", "expand the account", "they want to add seats", "second department", "justify the spend", "my champion needs to sell this internally", "build the case for", "how do I get budget for", or names an account and additional scope in the same breath. Also trigger when a customer asks what it would take to roll out further. It anchors on a problem their leadership already agreed exists, finds where the budget actually comes from, sizes the ask so it can survive one meeting, and answers the objections their finance team will raise before they raise them. Use business-review when the meeting is the value review, and renewal-negotiation when scope and price are being agreed together.
CSPulse/customer-success-skills · ★ 1 · AI & Automation · score 67

Install: claude install-skill CSPulse/customer-success-skills

# Expansion Case You are not going to present this. Your champion is, in a meeting you will not be in, to people who have never met you, against three other things asking for the same money. That single fact decides everything about how it should be written. It is not a pitch with your logo on it. It is ammunition, in their language, short enough to be carried. The failure this exists to prevent: **the beautiful deck that dies in someone's inbox**, because the champion could not defend slide four when their CFO pushed on it. --- ## What this needs **Shared context.** If an `account-context` document exists, read it first: the value metric, the contract shapes and how segments differ. Where it is absent, carry on and name the assumption. **Minimum: what you want to expand into and who would sponsor it.** Enough to produce the case structure, the likely objections and the sizing. **Better with** current outcome data from the existing deployment, their stated goals, and the original business case. The first is what earns you the right to ask at all. **Best with** a stakeholder map, because an expansion needs a budget holder who is frequently not the person you have been working with, and knowing whether you have met them changes the plan. --- ## Step 0: Check you have earned the ask One question, and it disqualifies more expansions than any other: **is the first deployment demonstrably working, in a way the customer would state out loud?** If not, stop. An expansion