Agent skill
account-expansion
Filed under Onboarding, retention and expansion.
From VijayMatt/go-to-market-agent-skills · 12 skills · 1 · pushed 2026-03-29
What it does when it runs
Read from the skill and the 3 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/VijayMatt/go-to-market-agent-skills.git /tmp/go-to-market-agent-skills git -C /tmp/go-to-market-agent-skills sparse-checkout set "account-expansion" mkdir -p ~/.claude/skills/account-expansion cp -R "/tmp/go-to-market-agent-skills/account-expansion/." ~/.claude/skills/account-expansion/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from VijayMatt/go-to-market-agent-skills/blob/c948db28e7a0147976cc91ad91479900a75f7904/account-expansion/SKILL.md, which is licensed MIT (repository). 2,864 words, 33 headings.
Account Expansion: Full Methodology
Why Expansion Revenue Is Different from New Business
Expansion revenue is the single most efficient revenue motion in B2B SaaS. Consider the numbers:
| Metric | New Business | Expansion |
|---|---|---|
| Average sales cycle | 60-120 days | 15-30 days |
| Win rate | 15-25% | 60-80% |
| CAC (customer acquisition cost) | 1.0x | 0.15-0.30x |
| Average discount | 15-25% | 0-10% |
Yet most teams have no structured expansion playbook. They either (a) wait for the customer to ask for more, (b) tack upsell conversations onto renewal calls, or (c) surprise customers with price increases. All three are leaving money on the table or, worse, destroying trust.
This skill gives you a systematic approach to detecting expansion opportunities early, approaching the right person with the right offer at the right time, and executing without damaging the customer relationship.
The 4 Expansion Motions
Not all expansion is the same. Each motion has a different buyer, conversation, and execution approach.
Motion 1: Upsell (Same Buyer, More Value)
What it is: The current buyer moves to a higher tier, adds premium features, or increases their commitment level.
Example: Customer on the Standard plan moves to Enterprise for advanced analytics and SSO.
Key dynamics:
- Lowest friction — same buyer, same use case, more depth
- Buyer already understands and values the product
- The conversation is about unlocking value they can already see (gated features, usage limits they're hitting)
- Works best when the customer is already bumping against limits of their current plan
When to approach: When usage data shows them consistently hitting plan limits, or when they ask about features available in higher tiers.
Motion 2: Cross-Sell (New Buyer, Different Product)
What it is: A different team, department, or business unit within the same organization adopts your product (or a different product in your portfolio).
Example: You sell to the audit team; now the tax team wants to evaluate.
Key dynamics:
- Higher friction — new buyer needs to go through their own evaluation
- Your existing champion can make an introduction, but the new buyer needs their own reasons to buy
- Internal reference is your superpower (their colleague can vouch for you)
- Often requires navigating organizational politics (business units may have separate budgets and priorities)
When to approach: When you hear about adjacent teams facing problems you solve, when your champion mentions a reorg that puts new teams under the same leader, or when you see new users logging in from different departments.
Motion 3: Seat Expansion (Same Use Case, More Users)
What it is: More people within the existing buying unit get added to the product.
Example: Started with 10 audit team members; growing to 50 as they roll out across regional offices.
Key dynamics:
- Often the easiest expansion — value is already proven, it's just "more of the same"
- Usually triggered by the customer's own growth, not your sales motion
- Can often be structured as automatic expansion (usage-based pricing, auto-add provisions in the contract)
- Risk: if you don't proactively manage seat expansion, the customer finds workarounds (sharing logins, using the product for only critical tasks)
When to approach: When the customer hires new people in the relevant function, when usage per seat is high (indicating demand exceeds current access), or at natural expansion moments (new offices, new projects, fiscal year planning).
Motion 4: Platform Adoption (Deeper Integration, Strategic Partnership)
What it is: The customer moves from using you as a point solution to embedding you as a strategic platform — deeper integrations, API usage, custom workflows, executive sponsorship.
Example: Customer goes from using your audit tool for one engagement type to standardizing all audit workflows on your platform, integrating with their practice management system, and sponsoring a company-wide rollout.
Key dynamics:
- Highest value, highest effort — this is a strategic sell, not a transactional one
- Requires executive-level relationships and a multi-stakeholder business case
- Lock-in cuts both ways — the customer gets more value but also more switching cost
- Often requires professional services, implementation support, and ongoing customer success investment
When to approach: When the customer's executive leadership starts asking about your roadmap, when they begin requesting API access or custom integrations, or when they reference you as a "strategic partner" (not just a vendor).
The Expansion Signal Framework
Expansion doesn't happen randomly. There are leading indicators. The best expansion teams monitor these signals proactively, not reactively.
Usage-Based Signals (Product Data)
These come from your product analytics. See references/expansion-signals.md for the complete list.
| Signal | What It Indicates | Expansion Motion |
|---|---|---|
| User consistently hitting plan limits | Upsell readiness | Upsell to higher tier |
| New users from different departments logging in | Cross-sell opportunity | Cross-sell to new department |
| Usage growing month-over-month for 3+ months | Healthy adoption, seat expansion opportunity | Seat expansion |
| High feature adoption depth (using 70%+ of features) | Power user, ready for advanced capabilities | Upsell to premium features |
| API usage growing | Platform adoption potential | Platform expansion |
| Users requesting features available in higher tiers | Natural upsell trigger | Upsell |
| Usage spikes around specific events (quarter-end, audit season) | Timing signal for expansion conversation | Any, timed to peak usage |
Relationship-Based Signals (People Data)
These come from your CS and sales interactions.
| Signal | What It Indicates | Expansion Motion |
|---|---|---|
| Champion gets promoted | More budget, more influence, more ambition | Any (bigger opportunity) |
| New executive sponsor joins the account | Fresh mandate, new budget, willingness to invest | Platform adoption |
| Customer asks for a case study or reference | They're selling you internally to someone else | Cross-sell |
| Customer invites you to present to their leadership | Executive visibility = expansion opportunity | Upsell or platform |
| Customer's competitor becomes your customer | Competitive pressure to deepen their investment | Any |
| Customer mentions a new strategic initiative | Potential alignment with your roadmap | Cross-sell or platform |
External Signals (Market Data)
These come from monitoring the account externally.
| Signal | What It Indicates | Expansion Motion |
|---|---|---|
| Funding round or strong earnings | More budget available | Any |
| New office openings or geographic expansion | More users needed | Seat expansion |
| Leadership change (new CTO, CFO, VP) | New priorities, new budget, new willingness to evaluate | Any (reset the conversation) |
| Regulatory change affecting their industry | New compliance requirements you can help with | Cross-sell or upsell |
| M&A activity | Integration challenges you can help with | Seat expansion or platform |
| Job postings for roles related to your product | Growing the team that uses you | Seat expansion |
Account Health Scoring
Not every account is ready for expansion. Some need stabilization first. Health scoring helps you sort accounts into four quadrants.
The Health Score Model
See references/health-score.md for the full weighted model. Summary:
| Dimension | Weight | What It Measures |
|---|---|---|
| Product adoption | 30% | Are they using what they bought? Feature depth, breadth, frequency |
| Outcome achievement | 25% | Are they getting the results they expected? Metrics vs. targets |
| Relationship health | 20% | NPS/CSAT, executive engagement, champion strength, responsiveness |
| Support health | 15% | Ticket volume, resolution satisfaction, escalation frequency |
| Financial health | 10% | Payment timeliness, contract value trend, discount level |
The Four Quadrants
| Quadrant | Health Score | Expansion Signal | Action |
|---|---|---|---|
| Expand | High health + Strong signals | Ready for expansion conversation | Execute expansion playbook |
| Nurture | High health + Weak signals | Happy but not growing | Build the case; plant seeds for next quarter |
| Stabilize | Low health + Strong signals | Interested in more but struggling with what they have | Fix adoption/outcomes first; expansion will backfire if current deployment isn't working |
| Save | Low health + Weak signals | At risk of churn | Churn prevention mode; expansion conversation would be tone-deaf |
Critical rule: Never pitch expansion to an account in the Stabilize or Save quadrant. Fix the foundation first. Asking a struggling customer to buy more is the fastest way to accelerate churn.
Stakeholder Mapping for Expansion
Who to Approach (In What Order)
For Upsell:
- Your champion (gut-check the idea, get their input on timing)
- The economic buyer (they need to approve additional spend)
- End users who would benefit (build bottom-up demand)
For Cross-Sell:
- Your champion (ask for an introduction to the new department)
- The champion's peer in the target department (warm introduction)
- The target department's decision-maker
For Seat Expansion:
- Your champion (align on the rollout plan)
- The operations/IT lead (they'll manage the rollout)
- The economic buyer (for budget approval if above threshold)
For Platform Adoption:
- Executive sponsor (this is a strategic decision, not a tactical one)
- Your champion (they'll lead the implementation)
- IT/Architecture team (integration requirements)
- Procurement (contract restructuring)
The "Land, Adopt, Expand, Renew" Sequence
Expansion should be planned from the initial sale. The best AEs seed expansion during onboarding:
- Land: Sell the initial use case. Keep it focused and achievable.
- Adopt: Ensure the initial deployment succeeds. Measure outcomes. Build a track record.
- Expand: Once adoption is strong and outcomes are proven, have the expansion conversation.
- Renew: Expansion conversations should be completed before renewal, not during it. Bundling expansion with renewal creates negotiation leverage for the buyer that reduces your deal size.
The Expansion Conversation
How It's Different from New Business
| New Business | Expansion |
|---|---|
| Buyer doesn't trust you yet | Trust is established (don't break it) |
| You need to prove value | Value is (should be) already proven |
| You create urgency | Urgency comes from their own success and growth |
| Discovery is about uncovering pain | Discovery is about uncovering what's next |
| ROI is projected | ROI can be actual, demonstrated |
The Expansion Conversation Framework
Step 1: Lead with value delivered (not "we have more to sell you") "Over the past 6 months, your team has processed X transactions through our platform, which based on your initial metrics has saved approximately Y hours of manual work. I wanted to check — does that match what you're seeing on your end?"
Step 2: Ask about what's next for their team "What's on the roadmap for your team over the next 6-12 months? Are there new projects, new mandates, or new challenges on the horizon?"
Step 3: Connect their goals to your capabilities "You mentioned [their goal]. We actually have customers in a similar situation who [specific example]. Would it be useful to explore how that could work for your team?"
Step 4: Make a specific recommendation (not a menu) Don't say "we have three tiers, which would you like?" Say "Based on your usage patterns and what you've told me about your goals, I'd recommend [specific option] because [specific reason]. Here's what that would look like."
Step 5: Make it easy "We can add this to your existing contract with a simple amendment. Your billing would change from $X to $Y. I can send over the paperwork today and your team could have access by [date]."
See references/conversation-templates.md for full scripts for each expansion motion.
Timing: When to Have the Expansion Conversation
The Ideal Window
| Contract Length | Best Time for Expansion Conversation | Why |
|---|---|---|
| Annual | Months 6-9 of the contract | Early enough that it's about value, not about renewal leverage |
| Multi-year | 12-18 months in, or after a major milestone | Enough time for adoption proof; enough time left on contract to realize value |
| Month-to-month | After 3+ consecutive months of strong usage | Expansion + annual commitment = win-win |
When NOT to Have the Expansion Conversation
- During a support escalation or outage
- When the champion just left and you don't have a new one yet
- At the same time as a price increase communication
- During the last 30 days before renewal (now it's a negotiation, not an expansion)
- When the customer's NPS/CSAT is below threshold
Pricing Expansion: Structuring Upgrade Offers
Principles
- Anchor to value, not cost. The expansion price should be framed as an investment with a return, not an additional expense.
- Offer a bridge, not a cliff. If moving from $50K to $100K, consider a phased approach: $75K for the first 6 months as they ramp, then $100K at renewal.
- Bundle strategically. If the expansion includes multiple components, bundle them at a small discount vs. a la carte. This increases deal size and stickiness.
- Don't cannibalize. If you're adding features to the base plan for competitive reasons, make sure your expansion pricing still offers clear differentiation.
- Protect the floor. If a customer wants to expand but also wants to renegotiate their existing pricing, don't let the expansion conversation become a discount negotiation.
Expansion Pricing Models
| Model | Best For | Example |
|---|---|---|
| Tier upgrade | Upsell | Standard to Enterprise: $X/user/month to $Y/user/month |
| Add-on modules | Cross-sell or feature expansion | Base platform + Analytics module at $Z/month |
| Volume pricing | Seat expansion | Tiered per-seat pricing with breakpoints (1-50, 51-200, 201+) |
| Platform deal | Strategic expansion | Custom pricing for enterprise-wide deployment; often annual commitment with volume discounts |
Anti-Patterns: Trust-Destroying Moves to Avoid
The "Surprise Renewal Bump"
What it is: Waiting until renewal to inform the customer their price is going up 20-40%, with no warning and no corresponding increase in value.
Why it's destructive: It breaks trust instantly. The customer feels ambushed. Even if they renew (because switching costs are high), they'll start evaluating alternatives immediately.
What to do instead: Communicate price changes 90+ days before renewal. Tie the increase to concrete value added (new features, better support, platform improvements). Offer a loyalty discount for multi-year commitment.
The "Commission Breath" Upsell
What it is: Pushing expansion aggressively when the customer isn't ready, because you have a quota to hit or a quarter to close.
Why it's destructive: Customers can smell commission breath. It transforms a trusted advisor relationship into a transactional vendor relationship. It's also usually ineffective — pressured upsells have high buyer's remorse and churn.
What to do instead: Time expansion conversations to the customer's readiness, not your quota deadline. If you need the deal this quarter, be transparent: "I want to be upfront — there's an incentive for us to finalize this before [date], which is why I can offer [specific incentive]. But I don't want to rush your decision if the timing isn't right."
The "Feature Hostage"
What it is: Removing features the customer already has access to and moving them to a higher tier, then calling it an "upsell opportunity."
Why it's destructive: This is a bait-and-switch. Customers who discover they're losing capabilities they've been using will churn, leave bad reviews, and tell their peers.
What to do instead: Grandfather existing customers on their current feature set. New features can be premium, but never take away what someone already has.
The "Spray and Pray" Cross-Sell
What it is: Emailing every contact at an account about every product in your portfolio, without regard for relevance, relationship, or timing.
Why it's destructive: It annoys your existing champions (who feel spammed), confuses contacts who don't know you, and dilutes your brand from "trusted partner" to "annoying vendor."
What to do instead: Cross-sell through warm introductions from your champion. Only approach new contacts with a clear, relevant reason to talk. One well-placed introduction beats 50 cold emails.
The "CSM as Salesperson" Confusion
What it is: Making your customer success manager responsible for expansion revenue without changing their title, compensation, or the customer's expectations.
Why it's destructive: Customers build trust with their CSM as a neutral advisor. When the CSM starts pitching products, the relationship dynamic changes and the customer starts filtering everything through a "is this person trying to sell me something?" lens.
What to do instead: Either (a) give CSMs clear expansion targets with appropriate compensation and train them to have commercial conversations, or (b) keep CSMs as advisors who identify and flag expansion signals, then bring in an account executive or expansion specialist for the commercial conversation. Don't split the difference.
Reference Files
| File | Purpose |
|---|---|
references/expansion-signals.md | Complete signal inventory for expansion readiness |
references/conversation-templates.md | Expansion conversation scripts for each motion |
references/health-score.md | Customer health scoring model with weighted dimensions |
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- find-lead-account-owner by zapier · 329
- ai-audit-account-report by zapier · 329
- named-account-trigger-radar by zapier · 329
- territory-account-launch by louisblythe · 136
- account-structure-review by thatrebeccarae · 119
- expansion-retention by chadboyda · 74
- account-qualification by kenny589 · 63
- account-research-brief by Othmane-Khadri · 55
Need help setting it up?
This page tells you what account-expansion does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.