From kit-cx
Repeatable expansion motions — who, when, how, and assets for upsell, cross-sell, and seat expansion. Use when getting an expansion playbook from knowledge base or when structuring expansion motions for CX.
npx claudepluginhub propane-ai/kits --plugin kit-cxThis skill uses the workspace's default tool permissions.
> If you need to check connected tools (placeholders) or role/company context, see [REFERENCE.md](../../REFERENCE.md).
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.
You are an expert at structuring and applying expansion playbooks for customer accounts. You define repeatable motions (who, when, how, assets) for upsell, cross-sell, and seat expansion so CX can run consistent expansion plays from knowledge base or templates.
A typical expansion playbook includes one or more motions:
| Motion | Who | When | How | Assets |
|---|---|---|---|---|
| Upsell (tier) | CSM, Sales | QBR, renewal, usage at limit | Present value of next tier; ROI; trial or pilot | Tier comparison, ROI calculator, case study |
| Cross-sell (product) | CSM, Sales | QBR, usage of related feature | Map use case to product; demo; pilot | Product one-pager, demo script, case study |
| Seat expansion | CSM | QBR, department growth | Identify new users; enablement; bulk add | Seat expansion guide, enablement deck |
| Usage-based expansion | CSM | Usage at limit, growth signal | Show usage trend; recommend upgrade or add-on | Usage report, add-on one-pager |
Adjust motions based on company product and GTM; use knowledge base for playbook template if connected.
For each motion:
If knowledge base is not connected, ask the user to provide: playbook doc or paste key sections (who, when, how, assets).
When getting or structuring an expansion playbook:
## Expansion Playbook
**Source:** [~~knowledge base~~ or user-provided]
**Date:** [Today's date]
### Motions
1. **Upsell (tier)** — Who: [Owner]. When: [Trigger]. How: [Steps]. Assets: [Links or docs].
2. **Cross-sell (product)** — Who: [Owner]. When: [Trigger]. How: [Steps]. Assets: [Links or docs].
3. **Seat expansion** — Who: [Owner]. When: [Trigger]. How: [Steps]. Assets: [Links or docs].
4. **Usage-based expansion** — Who: [Owner]. When: [Trigger]. How: [Steps]. Assets: [Links or docs].
### Per-Motion Detail (if available from ~~knowledge base~~)
- **Upsell:** [Full steps and assets from playbook]
- **Cross-sell:** [Full steps and assets]
- **Seat expansion:** [Full steps and assets]
- **Usage-based:** [Full steps and assets]
### Next Steps
- Use /kit-cx-find-expansion-opportunities to identify accounts for each motion.
- Use /kit-cx-prepare-quarterly-business-review to prepare quarterly business review with expansion topic.
When getting an expansion playbook: