expansion-playbook
Skill15 starsChanged 9 months agoMITView on GitHub
Create upsell, cross-sell, and renewal playbooks for existing customers — identify expansion signals, build business cases, and run expansion conversations. Use this skill whenever a CS or sales team wants to grow existing accounts, identify upsell opportunities, prepare for renewal conversations, build expansion strategies, or says "how do I upsell [customer]", "renewal strategy", "cross-sell opportunity", "expand this account", or "net revenue retention". Also trigger when someone mentions land-and-expand, account expansion, customer growth, or NRR.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- vijaysuperpositionist/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- battle-cardsSkill
- buyer-personaSkill
- campaign-to-fieldSkill
- content-healthSkill
- deal-qualificationSkill
- discovery-guideSkill
- gtm-memorySkill
- handoff-builderSkill
- objection-handlingSkill
- partner-enablementSkill
- pipeline-intelligenceSkill
- playbook-builderSkill
- proposal-builderSkill
- rep-profileSkill
- roi-calculatorSkill
- sales-coachingSkill
- win-loss-analysisSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
27 rules. About 0 are common, 12 are distinctive, and 15 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
15
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 59
CRITICAL: Before asking about the customer, pull everything from connected tools.
- Very specific: line 63
Check if you have access to CRM tools (look for tools containing search_crm_objects, get_crm_objects, or similar).
- Distinctive: line 65
If CRM tools ARE available:
- Very specific: line 67
Find the customer's deals: Search deals for the company name — pull all deals (won, open, lost).
- Distinctive: line 77
Check renewal date: Look for contract end date or renewal fields.
- Distinctive: line 78
If renewal within 6 months → trigger renewal strategy section
- Distinctive: line 79
Pull deal notes and activity: Check for support tickets, NPS scores, or health metrics if tracked.
- Very specific: line 84
Get current company data: Use zoominfo_search_company with the customer company name/domain.
- Very specific: line 88
Get org chart: Use zoominfo_get_org_chart for the customer.
- Very specific: line 91
Get tech stack: Use zoominfo_get_tech_stack for the customer.
- Very specific: line 96
Enrich the company: Use clay_enrich_company with customer domain.
- Very specific: line 98
Trigger enrichment: Use clay_trigger_enrichment for expansion-specific signals.
- Very specific: line 101
Check champion status: Use linkedin_get_profile for your champion contact.
- Very specific: line 104
Search company updates: Use linkedin_search_companies for customer company.
- Very specific: line 110
Check if you have access to Gong tools (look for tools prefixed with gong_).
- Distinctive: line 112
If Gong tools ARE available:
- Very specific: line 113
Find recent calls with this customer: Use gong_search_calls with the company name.
- Very specific: line 114
Pull transcripts from QBRs or check-ins: Use gong_get_transcript.
- Very specific: line 121
If chat tools are available (slack_search_public, slack_search_public_and_private):
- Distinctive: line 122
Search for the customer name in CS and sales channels
- Distinctive: line 124
Look for champion feedback or internal advocacy signals
- Distinctive: line 128
If calendar/email tools are available:
- Distinctive: line 129
Search for recent meetings with the customer — frequency and recency of engagement
- Distinctive: line 130
Check for any expansion discussions already in progress
- Distinctive: line 138
After the auto-pull, ask ONLY for what the tools couldn't provide:
- Very specific: line 150
Update memory/deal-patterns.md with expansion patterns (what triggers work)
- Very specific: line 151
Update memory/team.md with CSM/AE expansion skills and patterns
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Expansion Playbook
Growing existing customers is cheaper and faster than acquiring new ones. This skill helps CS and sales teams identify expansion signals, build compelling business cases, and run expansion conversations that feel like partnership — not a sales pitch.
Why Expansion Matters
- 3-5x cheaper to expand an existing customer than acquire a new one
- NRR (Net Revenue Retention) is the #1 metric investors and boards care about
- Happy customers who expand become your strongest references
- Expansion validates your product-market fit in the deepest way
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ EXPANSION PLAYBOOK │
├─────────────────────────────────────────────────────────────────┤
│ PLAYS │
│ 1. Upsell — More of the same (more seats, higher tier) │
│ 2. Cross-sell — New products or modules │
│ 3. Renewal — Protect and grow at renewal │
│ 4. Land-and-Expand — Strategy from initial deal to full deploy │
│ │
│ SIGNALS │
│ • Usage patterns (high adoption → ready for more) │
│ • Team growth (hiring → need more seats) │
│ • New use cases (expanding beyond original intent) │
│ • Champion promotion (your advocate now has more budget) │
│ • Competitor displacement (using something else for adjacent) │
│ • Contract milestones (renewal approaching, initial ROI proven) │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM: Customer deal history, ARR, and contract dates │
│ + ~~CRM: Contact roles and champion mapping │
│ + ~~CRM: Usage data and health scores (if tracked) │
│ + ~~data enrichment (ZoomInfo): Company growth and hiring │
│ + ~~data enrichment (ZoomInfo): Tech stack changes │
│ + ~~data enrichment (Clay): Expansion signals and triggers │
│ + ~~data enrichment (LinkedIn): Champion job changes │
│ + ~~data enrichment (LinkedIn): Company news and updates │
│ + ~~chat: Internal customer discussions and feedback │
│ + ~~calendar/email: Recent customer correspondence │
└─────────────────────────────────────────────────────────────────┘Execution Flow
Step 0: Automatic Data Pull (Before Asking the User Anything)
CRITICAL: Before asking about the customer, pull everything from connected tools. Expansion intelligence is most powerful when grounded in real account data, growth signals, and relationship history.
CRM Data Pull
Check if you have access to CRM tools (look for tools containing search_crm_objects, get_crm_objects, or similar).
If CRM tools ARE available:
- Find the customer's deals. Search
dealsfor the company name — pull all deals (won, open, lost).- Properties:
dealname,amount,dealstage,closedate,createdate,pipeline,hubspot_owner_id,dealtype,description - Calculate: current ARR, total contract value, deal history timeline
- Identify: what products/modules they bought, what they didn't
- Properties:
- Pull contacts. Get all associated contacts for the customer.
- Properties:
firstname,lastname,jobtitle,email,phone,lifecyclestage - Map: champion (your advocate), economic buyer, power users, new stakeholders added since initial deal
- Properties:
- Pull company. Get company profile.
- Properties:
name,domain,industry,numberofemployees,annualrevenue,description,founded_year - Compare current employee count to when they signed — growth = expansion signal
- Properties:
- Check renewal date. Look for contract end date or renewal fields.
- If renewal within 6 months → trigger renewal strategy section
- Pull deal notes and activity. Check for support tickets, NPS scores, or health metrics if tracked.
Sales Intelligence Data Pull
ZoomInfo (if available):
- Get current company data. Use
zoominfo_search_companywith the customer company name/domain.- Employee count change since they signed → hiring = seat expansion signal
- Revenue growth → validates they can afford expansion
- New departments or initiatives → cross-sell opportunities
- Get org chart. Use
zoominfo_get_org_chartfor the customer.- New leaders or VPs hired → potential new buying centers
- Champion's current reporting structure → has their scope grown?
- Get tech stack. Use
zoominfo_get_tech_stackfor the customer.- New tools adopted → integration opportunities or adjacent needs
- Competitor tools still in use → displacement opportunity
Clay (if available):
- Enrich the company. Use
clay_enrich_companywith customer domain.- Growth signals, funding events, product launches → expansion triggers
- Trigger enrichment. Use
clay_trigger_enrichmentfor expansion-specific signals.
LinkedIn (if available):
- Check champion status. Use
linkedin_get_profilefor your champion contact.- Promoted? → More budget and influence — perfect upsell timing
- Left the company? → Risk alert — identify new champion immediately
- Search company updates. Use
linkedin_search_companiesfor customer company.- Hiring trends, new offices, product launches → expansion signals
- Strategic initiatives they announced → align expansion to their priorities
Gong Data Pull
Check if you have access to Gong tools (look for tools prefixed with gong_).
If Gong tools ARE available:
- Find recent calls with this customer. Use
gong_search_callswith the company name. - Pull transcripts from QBRs or check-ins. Use
gong_get_transcript.- Extract: new pain points mentioned, feature requests, adjacent use cases discussed
- Extract: satisfaction signals or risk signals
- Extract: mentions of other departments wanting access
Chat Data Pull
If chat tools are available (slack_search_public, slack_search_public_and_private):
- Search for the customer name in CS and sales channels
- Surface: customer health discussions, feature requests, support escalations, expansion discussions
- Look for champion feedback or internal advocacy signals
Calendar/Email Data Pull
If calendar/email tools are available:
- Search for recent meetings with the customer — frequency and recency of engagement
- Check for any expansion discussions already in progress
Present What You Found
"I pulled the full account picture for [Customer]: $[X] current ARR across [N] deals since [date]. Per CRM, they have [N] contacts with [N] users on [products]. Per ZoomInfo, they've grown from [N] to [N] employees since signing (+[X]%). [If LinkedIn:] Your champion [Name] was recently promoted to [new title]. [If Gong:] On the last QBR, they mentioned [new need/pain]. Expansion signals detected — building your playbook now..."
Step 1: Gather Remaining Context
After the auto-pull, ask ONLY for what the tools couldn't provide:
- Customer health — How happy are they? Any open issues or risks?
- Relationship dynamics — Who's your best contact? Any internal politics to navigate?
- Expansion goal — Upsell, cross-sell, renewal, or full land-and-expand strategy?
- Products available — What else could they buy? (if not in memory/product.md)
Step 2: Generate the Expansion Plan
Build using ALL evidence. Cite sources: "Per CRM:", "Per ZoomInfo:", "Per LinkedIn:", "Per Gong:", "Per Slack:", "User reported:"
Step 3: Store Insights
- Update
memory/deal-patterns.mdwith expansion patterns (what triggers work) - Update
memory/team.mdwith CSM/AE expansion skills and patterns - Log the expansion plan in
memory/changelog.md
Getting Started
- "Build an expansion strategy for [Customer]"
- "How should I approach the renewal conversation with [Customer]?"
- "What upsell opportunities exist in our customer base?"
- "[Customer] just hired 50 people — should I reach out?"
- "Create a land-and-expand playbook for our enterprise motion"
Output Format: Account Expansion Plan
# Expansion Plan: [Customer Name]
**CSM:** [Name] | **AE:** [Name]
**Current ARR:** $[amount]
**Contract Renewal:** [Date]
**Expansion Potential:** $[amount] | [X]% confidence
---
## Current State
| Metric | Value |
|--------|-------|
| Users / Seats | [Current] of [Licensed] |
| Adoption Rate | [X]% |
| Health Score | [X]/100 |
| NPS / CSAT | [Score] |
| Modules Used | [List] |
| Modules Available | [Not yet purchased] |
## Expansion Signals Detected
| Signal | Evidence | Opportunity |
|--------|----------|-------------|
| 🟢 [Signal] | [Specific evidence] | [What to propose] |
| 🟢 [Signal] | [Evidence] | [Opportunity] |
| 🟡 [Signal] | [Weaker evidence] | [Worth exploring] |
## Recommended Plays
### Play 1: [Upsell/Cross-sell/Tier Upgrade]
**What:** [Specific expansion proposal]
**Why Now:** [Trigger or signal that makes this timely]
**Value to Customer:** [In their terms — not yours]
**Estimated ARR Impact:** $[amount]
**Approach:** [How to position this conversation]
**Talk Track:**
> "[Opening that connects to their business goals, not your quota]"
### Play 2: [Second opportunity]
[Same structure]
---
## Renewal Strategy (if renewal within 6 months)
**Renewal Date:** [Date]
**Risk Level:** 🟢🟡🔴
**Expansion at Renewal:** [Likely / Possible / Unlikely]
### Pre-Renewal Timeline
| Weeks Before | Action | Owner |
|-------------|--------|-------|
| 12 weeks | Executive business review | CSM |
| 8 weeks | Renewal + expansion proposal | AE |
| 4 weeks | Negotiate and finalize | AE |
| 2 weeks | Contract execution | Legal |
### Renewal Conversation Guide
1. Start with value delivered (their ROI, not your features)
2. Review success against original criteria
3. Introduce expansion as a natural next step
4. Handle any concerns proactivelyRelated Skills
- handoff-builder → Initial handoff identifies expansion opportunities
- roi-calculator → Build expansion business case with ROI data
- proposal-builder → Create formal expansion proposals
- deal-qualification → Qualify expansion opportunities rigorously
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

