expansion-revenue-coach

by charlie-morrison

Install this Skill

curl -fsSL -o expansion-revenue-coach.zip https://skill.seembox.com/api/v1/skills/expansion-revenue-coach/download && unzip expansion-revenue-coach.zip

Download expansion-revenue-coach.zip

SKILL.md About

---
name: expansion-revenue-coach
description: Coach a B2B SaaS company on building expansion revenue (the "land and expand" engine) — designing the expansion motion (seat-based, usage-based, feature-tier, cross-sell, multi-product), instrumenting expansion triggers (usage thresholds, team-growth signals, feature-adoption depth, value-realization milestones), aligning CSM / AM / sales structures (post-sales-led vs sales-AE-led vs PLG self-serve), pricing for expansion (avoiding the deflationary "all-in-one" trap, building tiered ladders, structuring add-ons), Net Revenue Retention (NRR) playbook (target 110-130% NRR, gross retention floor 90%+), and avoiding common traps (over-discounting initial deal then can't expand, over-bundling so customers don't see the upgrade, under-instrumenting so expansion happens at renewal not in-year). Use when founder says "NRR is flat", "expansion is broken", "build expansion playbook", "post-sales motion", "CSM vs AM", "land and expand", "ARR expansion", "grow existing accounts". Triggers on phrases like "expansion revenue", "NRR", "net revenue retention", "land and expand", "account growth", "upsell motion", "cross-sell SaaS", "CSM expansion", "in-year expansion", "renewal expansion", "expansion ARR".
---

# expansion-revenue-coach

Coach a B2B SaaS company on building or fixing the expansion engine — the operating motion that grows revenue from existing customers. Most healthy SaaS companies derive 30-60% of their net new ARR from expansion, not new logos. Companies stuck at <100% NRR have a structural problem (wrong value metric, wrong motion, wrong incentives) that cannot be fixed by "trying harder on upsells".

The 2025-2026 reality: enterprise selling has gotten harder, new-logo CAC has risen, and capital efficiency matters more than land-grab growth. NRR is the dominant lever for sustainable growth. A company at 120% NRR doubles ARR every 4 years on existing customers alone. A company at 90% NRR shrinks if new logos slow.

## When to engage

Trigger when the founder / CRO / VP CS says:
- Direct NRR / GRR terms: "NRR is flat", "GRR dropped", "net retention", "expansion ARR", "expansion booking"
- Expansion motion design: "build expansion playbook", "post-sales motion", "CSM vs AM split", "expansion comp plan", "land and expand"
- Pricing-tied expansion: "no upgrade path", "customers stuck at Pro tier", "all-you-can-eat trap", "tier ladder"
- Triggers / instrumentation: "when do we trigger expansion", "usage threshold", "expansion playbook signals"
- Org / role: "do we need CSMs", "AMs vs CSMs", "PLG expansion vs sales-led expansion"
- Specific symptoms: "expansion happens at renewal not in-year", "expansion is one-time only", "cross-sell isn't working"

Do not engage for: pure new-logo / top-of-funnel growth (different skill), single-product SaaS with no possible expansion vector (rare; usually wrong analysis), or churn-recovery from already-departed customers (different skill — win-back).

## Diagnostic sweep

1. **Current state.**
   - NRR: trailing-12 months (rolling)
   - GRR: trailing-12 months
   - Logo retention: trailing-12 months
   - Expansion ARR: as % of total new ARR
   - Average ACV at signup vs. average ACV at year 2 (cohort progression)

2. **Pricing structure.**
   - Value metric (per-seat / usage / asset / hybrid)
   - Tier ladder (Starter → Pro → Business → Enterprise)
   - Add-on catalog (what's purchasable post-initial-deal)
   - Bundle vs. à la carte

3. **Customer journey.**
   - Onboarding velocity (time-to-value, time-to-first-power-feature)
   - Usage telemetry (do you have it? Do you track per-customer feature adoption?)
   - Health scoring (do you have one? What does it measure?)

4. **Org structure.**
   - CSM (Customer Success Manager) team: exists? Quota? Comp on expansion?
   - AM (Account Manager) team: separate from CSM? Quota structure?
   - AE / sales: do they own renewal? Expansion?
   - Support: relationship to expansion?

5. **Customer segmentation.**
   - SMB / mid-market / enterprise split
   - High-touch vs. low-touch coverage (and where the line is)
   - Top-20% accounts (do they get differentiated treatment?)

6. **Expansion motion present today.**
   - In-year (expansion sold mid-contract)
   - At-renewal (expansion captured at contract refresh)
   - PLG self-serve (customer adds seats / upgrades tier without sales touch)

## NRR target ranges by company stage

- **Pre-PMF / first 50 customers**: NRR is mostly noise; don't optimize. Focus on activation + early retention.
- **PMF / $1-5M ARR**: target 105-115% NRR. Expansion engine is forming.
- **Scaling / $5-50M ARR**: target 110-125% NRR. Best-in-class is 125-135%.
- **Mature / $50M+ ARR**: target 115-125% NRR. Maintaining 130%+ at scale is rare but signal of category-defining product.

GRR target: 90%+ across all stages. Below 85% = fix retention first, expansion later.

If NRR < 100%: structural problem. Do not chase expansion plays before fixing the underlying churn / contraction issue.

## Expansion vectors — choose the right one(s)

Most B2B SaaS has 2-4 simultaneous expansion vectors. Identify which apply.

### Seat expansion (per-user pricing)
- Customer adds users as their team grows / adopts the tool
- Mechanism: invitation flow, admin self-serve, billing automation
- Required: per-seat pricing model, observable team growth
- Best when: collaboration product (Slack, Linear, Notion, Figma, Asana)

### Usage expansion (consumption-based)
- Customer's usage grows over time as they integrate the product deeper
- Mechanism: tier overage charges, committed-spend agreements, on-demand-overage
- Required: usage-based or hybrid pricing
- Best when: API platform, infrastructure, observability, AI tools, message-passing platforms

### Tier upgrade (Pro → Business → Enterprise)
- Customer's needs grow into the next tier
- Mechanism: feature gates that pull customer up (SSO, audit, advanced controls), or volume thresholds
- Required: meaningful tier differentiation, not just price differences
- Best when: traditional B2B SaaS workflow tools

### Cross-sell (multi-product)
- Customer buys an additional product/module
- Mechanism: product-led entry into adjacent product, sales-led discovery of need
- Required: product portfolio, not single-product
- Best when: company has 2+ related products (HubSpot, Salesforce, Atlassian model)

### Geographic / org expansion (enterprise multi-deployment)
- Customer expands deployment to additional teams, business units, geographies
- Mechanism: account-based selling, organizational mapping
- Required: enterprise customers with significant org breadth
- Best when: $50K+ ACV with Fortune 5000 customers

### Service / Premium expansion
- Customer buys premium support, dedicated CSM, professional services
- Mechanism: tiered support / services packages
- Required: enterprise-tier customers
- Best when: complex implementations, regulated industries

## Designing the expansion motion

### High-touch (sales-led) expansion
- Suited to: $30K+ ACV, complex products, enterprise customers
- Structure: AM (Account Manager) team owns named accounts, quotaed on net-new ARR within account (expansion + renewal)
- Comp: 60-80% on-target earnings tied to quota; SPIFs for in-year expansion
- Cadence: QBRs, account planning, opportunity management in CRM

### Low-touch (CSM-led) expansion
- Suited to: $10-30K ACV, mid-market, scale customer count
- Structure: CSM team manages portfolio of 20-50 accounts each, runs playbooks
- Comp: 80% base + 20% variable on portfolio NRR / expansion outcomes
- Cadence: monthly / quarterly check-ins, automated health-score-driven outreach

### Tech-touch / PLG expansion
- Suited to: <$10K ACV, SMB, self-serve
- Structure: in-product upgrade prompts, automated email triggers, in-product chat
- Comp: small expansion-ops team manages the system; minimal individual quotas
- Cadence: triggered by product events, not calendar

### Hybrid (most modern B2B SaaS)
- Tech-touch for SMB / Starter tier; CSM for Pro/Business; AM for Enterprise
- Clear thresholds for graduation (ACV / employee count / vertical)
- Coordinated handoffs between motions

## CSM vs AM — the role split

- **CSM (Customer Success Manager)**: drives adoption + retention; owns renewal
- **AM (Account Manager)**: drives expansion (upsell + cross-sell); often shares renewal accountability

### Three structural patterns

**Pattern 1: Single role (CSM owns adoption + retention + expansion)**
- Pros: simpler org, single throat-to-choke for customer
- Cons: CSM often non-quota'd or under-compensated for expansion; expansion motion atrophies
- Best when: small org (<$10M ARR), low-touch motion

**Pattern 2: CSM + AE for expansion (CSM identifies, AE closes)**
- Pros: CSM stays adoption-focused; AE has selling motion
- Cons: handoff friction, attribution disputes, customer feels "hunted" mid-engagement
- Best when: mid-stage SaaS ($10-50M ARR)

**Pattern 3: CSM + AM split (CSM = adoption / retention; AM = expansion / renewal)**
- Pros: clear accountability, AM has commercial focus, CSM has trust focus
- Cons: customer has 2+ contacts, requires tighter coordination
- Best when: enterprise SaaS ($50M+ ARR)

### Compensation alignment

- CSM compensation should include expansion outcomes. CSMs without expansion-tied comp will not behave commercially. Common: 70-80% base + 20-30% variable tied to portfolio NRR.
- AM compensation: ~60% base, ~40% variable on net new ARR within accounts.
- Avoid: AM and CSM both quotaed on the same expansion dollars (creates conflict, double-comp, customer confusion).

## Instrumenting expansion triggers

Expansion that "happens at renewal" misses 6-9 months of in-year revenue. Build trigger instrumentation.

### Usage triggers
- Customer at 80%+ of seat allowance for 30 days → triggers expansion playbook
- Customer at 80%+ of monthly usage cap → triggers usage-tier upsell
- Customer creating new workspaces / projects rapidly → org-expansion signal

### Adoption triggers
- Customer adopts feature X (gateway feature for next tier) → tier-upgrade conversation
- Customer's user-count growth >20% MoM → seat expansion conversation
- Customer integrates with adjacent product (your product or competitor's) → cross-sell signal

### Health-score triggers
- Customer health drops below threshold → retention playbook (not expansion — fix the underlying issue first)
- Customer health is GREEN for 90+ days → expansion-ready signal

### Lifecycle triggers
- Customer hits 90 days post-onboarding (full activation) → first expansion conversation
- Customer hits 1-year anniversary → strategic review + expansion mapping
- Customer's contract has 90 days to renewal → renewal + expansion combined motion

### Bad triggers (avoid)
- Calendar-only triggers ("monthly check-in regardless of state")
- Random AE / CSM outreach without signal
- Customer-side requests as the only expansion signal (you're losing in-year volume)

## Pricing for expansion

### Tier ladder design
- 3-4 tiers spaced 3-5x apart
- Each tier has a clear "graduation trigger" (feature, scale, persona)
- Top tier "Contact us" (Enterprise) creates ceiling-removal capacity

### Common tier-ladder mistakes
- Tiers too close together ($29 / $49 / $79) — customer doesn't graduate
- Tiers too far apart ($29 / $299) — customer can't cross the gap
- Tiers without clear feature differentiation — customer doesn't see why to upgrade
- "All-you-can-eat" tier at the top (Enterprise = unlimited everything) — caps revenue per customer

### Add-on catalog
- Modular add-ons (advanced security, dedicated CSM, premium integration) priced separately
- Add-ons should be ~10-30% of the relevant tier price
- Avoid making everything an add-on (creates negotiation friction)

### Per-unit metric pricing
- Per-seat / per-API-call / per-asset pricing creates natural expansion as customer grows
- The metric should be observable to customer (not hidden) and aligned with their value
- Caution: customers rebel against per-unit pricing if they feel they're being penalized for usage they didn't choose

### Anti-deflationary patterns
- Don't bundle expansions into existing tiers (deflates per-customer ARR)
- Don't grandfather customers at low prices forever (eventually re-price)
- Don't offer "lifetime deals" or "early adopter forever pricing" (poison for expansion)

## Renewal as expansion lever

Most NRR is realized at renewal, not in-year. The renewal motion is the most under-built piece in many SaaS orgs.

### Pre-renewal preparation (T-90 days)
- Account review: usage, adoption, value-realization, expansion-opportunities
- Customer business review: any changes in their org, leadership, strategy
- Risk identification: who could push back on renewal, who's a champion

### Renewal conversation structure
- Open with value-delivered (specific outcomes, ROI)
- Surface expansion opportunities (new modules, additional seats, advanced features)
- Negotiate price / term: list price increase (5-10% standard for steady customers; market shifts), multi-year discount tradeoff
- Land tier upgrade or add-on alongside renewal

### Common renewal mistakes
- Last-minute renewal (T-7 days) — no leverage, defaults to status-quo
- Renewal without expansion ask — leaves money on table
- "Auto-renew" without conversation — misses opportunity to expand
- Discounting at renewal to "keep the customer" — trains customer to negotiate annually

## In-year expansion vs renewal expansion

In-year: expansion mid-contract (extra seats, tier upgrade, add-ons)
Renewal: expansion at contract refresh

### Why in-year matters
- 6-9 months of additional revenue per expansion event
- Faster "expansion velocity" metric (key VC / acquirer signal)
- Renewal becomes simpler ("you're already paying $X, here's the renewal")

### How to enable in-year
- Per-seat / usage pricing models that auto-expand as customer grows
- Add-on flow that customer can self-serve (in-product upgrade)
- AM/CSM-driven expansion conversations triggered by usage signals
- Pricing flexibility for mid-contract upgrades (don't lock customer into old contract value for 12 months)

### Auto-expansion mechanics
- Per-seat: invitations expand seat count; billing system invoices the delta
- Per-usage: monthly invoices reflect current usage; commitment tier upgrades automatic at threshold
- Cleanup: never charge customer in arrears for previous-year usage (creates anxiety, churn)

## Expansion playbooks

### Seat-expansion playbook
- Trigger: customer at 80%+ of seat allowance for 14+ days
- Action 1: in-app banner showing usage + invite-flow
- Action 2: CSM email at day 21 if no self-serve action
- Action 3: AM call at day 30 if mid-market or higher

### Tier-upgrade playbook
- Trigger: customer adopts feature X (gateway to next tier) AND has stable usage
- Action 1: in-app upgrade prompt
- Action 2: CSM email with case study of similar customer at next tier
- Action 3: AM call to discuss upgrade

### Cross-sell playbook
- Trigger: customer integrates with adjacent product OR has high health score
- Action 1: CSM introduces second-product use case in QBR
- Action 2: 30-day trial of adjacent product
- Action 3: AM negotiates bundle pricing

### Renewal expansion playbook
- T-90: account review, expansion opportunity sizing
- T-60: opening conversation about renewal terms + expansion
- T-30: formal renewal proposal with expansion built-in
- T-15: negotiation, contract finalization

## Common anti-patterns

- Discounting at initial sale to win the deal, then unable to expand because customer's budget is tied to the original contract amount
- Bundling everything into "all you can eat" → no upgrade path
- CSMs without expansion comp → CSMs avoid commercial conversations
- Renewal handled by support (not sales / CSM) → no expansion conversation
- Over-discounting at renewal to retain customer → trains negotiation behavior
- Multi-year contracts at fixed price → can't capture expansion mid-term
- "Forever free" or "lifetime deal" customers in cohort → drag down NRR mathematically
- Expansion motion only at renewal → leave 6-9 months of revenue on the table

## Metric instrumentation

### Cohort NRR / GRR (monthly cohorts)
- For each cohort, track ARR over time (M3, M6, M12, M24)
- Healthy: NRR climbing for first 12 months as cohort matures, then stable
- Concerning: NRR declining year-over-year for cohorts (retention degradation)

### Expansion ARR by source
- In-year vs renewal
- Seat / usage / tier / cross-sell / geo
- By customer segment (SMB / mid / enterprise)

### Expansion velocity
- Time from initial contract to first expansion event
- Number of expansion events per customer per year
- Average expansion ARR per event

### Comp plan effectiveness
- AM / CSM quota attainment
- Expansion ARR per AM / CSM
- Cost-of-expansion (% of expansion ARR going to comp + ops)

## Output to founder / CRO

After diagnostic:

1. **NRR / GRR baseline** (current state, target by stage)
2. **Expansion vector inventory** (which 2-4 vectors apply to this product)
3. **Motion design recommendation** (tech-touch / CSM-led / sales-led / hybrid by segment)
4. **Org structure recommendation** (CSM, AM, AE roles + comp plan adjustments)
5. **Trigger instrumentation plan** (usage / adoption / lifecycle / health-score signals)
6. **Pricing structural changes needed** (tier ladder fixes, add-on catalog, anti-deflation moves)
7. **Renewal motion overhaul** (T-90 to T-0 playbook)
8. **In-year expansion playbooks** (top 3-5 plays specific to this product)
9. **Metric dashboard** (NRR / GRR / expansion ARR / velocity / comp plan tracking)
10. **90-day implementation plan** (high-leverage moves to start now; structural changes for 6-12 month plan)

NRR is the dominant lever for capital-efficient growth in 2025-2026. Most NRR pain is structural (wrong pricing, wrong motion, wrong comp), not tactical. This coach surfaces the structural issues and builds the operating motion that captures expansion as a discipline, not as occasional luck.

_meta.json Metadata

{
  "ownerId": "kn7d5eszdfwftk153ymhdm4qhs83qsqy",
  "publishedAt": 1778114767380,
  "slug": "expansion-revenue-coach",
  "version": "1.0.0"
}