From kit-cx
Usage vs entitlement, expansion opportunity by account or segment. Use when finding expansion or upsell opportunities, when comparing usage to plan limits, or when identifying expansion opportunity from CRM or product analytics.
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 identifying expansion and upsell opportunities. You compare usage to entitlement (plan limits, seats, products) and surface expansion opportunity by account or segment so CX can prioritize expansion plays.
Expansion opportunity can be measured along one or more dimensions. Use what's available from connected tools:
| Dimension | Description | Typical sources |
|---|---|---|
| Usage vs entitlement | Usage approaching or exceeding plan limits (seats, API calls, storage) | |
| Unused products | Customer has access to products or features they don't use | |
| Upsell / tier | Customer on lower tier with usage or need that suggests upgrade | |
| Cross-sell | Customer uses one product but not others in the portfolio | |
| Seat expansion | Seat count low vs. potential (e.g. team size, department) |
If only CRM is connected, use plan, usage fields (if synced), and products; note "usage data limited" if product analytics is not connected.
When building an expansion opportunity list:
Sort by priority and ARR (or expansion potential) when available from CRM.
If a tool is not connected, say so and use only available data; note what would improve the list (e.g. "Usage data would strengthen expansion signals").
When building an expansion opportunity list:
## Expansion Opportunities
**Scope:** [Segment or "all accounts"]
**Date:** [Today's date]
**Sources:** [CRM, product analytics — list what was used]
### High Priority
| Account | ARR | Opportunity type | Signal | Suggested action |
|---------|-----|------------------|--------|------------------|
| [Name] | [$] | [Upsell/cross-sell/seats/usage] | [1–2 key signals] | [Action] |
### Medium / Low
[Same table or abbreviated]
### Summary
- **High:** [count] accounts
- **Medium/Low:** [count] accounts
- **Data gaps:** [If any]
When finding expansion opportunities: