Expansion Selling

SkillDev tools

Complete expansion and upsell playbook for B2B SaaS — consumption-based upsell triggers, cross-sell identification, seat expansion, tier upgrades, NRR growth strategies, land-and-expand motions, expansion propensity scoring, and measuring expansion revenue. Use when designing expansion motions, identifying upsell opportunities, or growing NRR. Triggers on: "expansion selling", "upsell strategy", "NRR growth", "land and expand", "cross-sell", "expansion revenue", "seat expansion".

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Expansion Selling skill

What this skill tells your AI

The instructions your AI receives, as published by leadmagic/gtm-skills in skills/growth/expansion-selling/SKILL.md and read by ahel’s review.

Overview

The most profitable revenue doesn't come from new customers — it comes from existing ones. New customer acquisition costs 5-7x more than expanding an existing account. Yet most companies treat expansion as an afterthought. The mistake: waiting for customers to ask for more instead of systematically identifying and executing expansion opportunities. This skill covers the complete expansion playbook: triggers, scoring, execution, and measurement.

Frameworks Referenced

  • Winning by Design — Bowtie Funnel — Post-sale expansion as revenue system
  • Jason Lemkin (SaaStr) — NRR drives exit multiples (PE/strategic)
  • Marc Benioff — Land-and-expand enterprise motion
  • Randy Seidl — Relationship-led expansion: map stakeholders beyond the original champion; score trust before upsell. Load sales-coachingskills/management-leadership/sales-coaching/references/randy-seidl-relationship-selling.md. Complements Benioff CRM land-expand structure (crm-toolkit → land-expand-account-plan).
  • Snowflake consumption model (Slootman, Degnan). Land with paid pilot (low ACV entry); expand via use cases tracked in CRM; rep comp on booking and consumption so hit-and-run deals are penalized. Slootman aligned entire exec team to usage metrics. See gtm-leadership/references/cro-enterprise-strategy.md.
  • Databricks DBU expansion. Revenue grows with data volume and query analysis — expansion triggers are workload adoption, not seat adds. Technical sellers drive POC → production workloads. Gabrisko: structure field vs inside by ACV and buyer complexity.

When to Use

Trigger phrases: "expansion strategy", "upsell playbook", "NRR growth", "land and expand", "cross-sell identification", "seat expansion triggers", "tier upgrade strategy", "expansion revenue playbook"

Expansion Triggers (Ranked by Conversion Rate)

TriggerSignalConversion RateAction
Usage approaching limit"You've used 85% of your plan"25-35%Proactive upgrade offer + migration support
Feature request for higher tier"Can we get SSO?"40-60%"That's in Growth tier. Here's an instant upgrade path."
Multi-team adoptionMultiple departments using product20-30%Enterprise upsell with centralized billing
New hire at customerCustomer adds headcount15-25%Seat expansion + training for new team
QBR uncovers new use caseCustomer articulates expansion use case30-50%Proposal within 1 week of QBR
Champion requests API accessBuilding on your platform50%+Platform/Enterprise tier with API + support
Positive NPS + healthy usageHappy, active customer15-25%Case study ask, then expansion conversation

Step-by-Step Process

Phase 1: Identify Expansion Opportunities

Expansion Propensity Score:

Score = (Usage approaching limit: +30) +
        (Multi-team adoption: +25) +
        (Requested higher-tier feature: +25) +
        (NPS Promoter: +10) +
        (QBR attendance: +10)

Score > 70: Expansion playbook NOW
Score 40-69: Nurture — showcase advanced features
Score < 40: Focus on adoption before expansion

Phase 2: Expansion Plays

Play 1: Seat Expansion

  • Trigger: Customer adds team members. Usage per seat increasing.
  • Play: "Your team has grown. 5 new team members will benefit from [product]. Here's a prorated seat expansion for this month."
  • Economics: ACV increases linearly with seats. Simple. Predictable.

Play 2: Tier Upgrade

  • Trigger: Customer requests feature in higher tier, or usage exceeds plan limits.
  • Play: "All the features you've asked for are in Growth. Here's a side-by-side of what you get. First month at current rate to make the transition easy."
  • Economics: ARPU increases. Margin typically improves at higher tiers.

Play 3: Cross-Sell

  • Trigger: Customer buys Product A. Complementary Product B solves adjacent need.
  • Play: "Customers who use [Product A] typically add [Product B] within 6 months. Here's how they work together. Bundled pricing for existing customers."
  • Economics: New product line revenue without new logo acquisition cost.

Play 4: Enterprise Expansion

  • Trigger: Multi-team usage, SSO request, API access, security review.
  • Play: Enterprise tier with dedicated CSM, SSO, API access, custom SLA, volume pricing. "You've outgrown self-serve. Here's the enterprise experience."
  • Economics: 3-10x ACV increase. Stickier customer. Higher retention.

Phase 3: Expansion Economics

NRR Formula: NRR = (Starting MRR + Expansion - Contraction - Churn) / Starting MRR

Target NRR by stage (reconcile with references/benchmark-reconciliation.md):

  • Seed: 100%+ (aspirational)
  • Series A: 105%+
  • Series B: 110%+
  • Growth: 115%+
  • Public-company comp (Meritech): median ~108–111%; leaders 120%+

Flywheel note (Dharmesh Shah / HubSpot): Expansion + advocacy = Delight stage fuel. See references/dharmesh-shah-hubspot-inbound.md.

Expansion as % of New Revenue: Best-in-class SaaS: 30-40% of net new ARR comes from expansion Median SaaS: 15-25%

Phase 4: Expansion Playbook Execution

CSM expansion cadence:

  • Month 1-2: Onboarding. No expansion talk. Deliver value first.
  • Month 3: Identify expansion triggers. Document use cases.
  • Month 4-6: First expansion conversation. Plant the seed.
  • Month 6-12: Execute expansion. Close upgrade or cross-sell.

Implementation Checklist

  • Expansion triggers automated (usage approaching limit = alert)
  • Expansion propensity scored for every account
  • NRR tracked monthly with target by customer segment
  • CSM comp tied to NRR (not just retention)
  • Expansion plays documented for each trigger type

Common Pitfalls

  1. Expanding too early. Asking for upsell during onboarding = churn risk. Fix: Deliver value first. Expand after month 3+.
  2. No expansion comp for CSMs. CSMs comped on retention only = no expansion. Fix: Variable comp tied to NRR. 50% base, 50% variable on NRR target.
  3. Missing consumption triggers. Customer usage spikes. Nobody notices. Fix: Automated alerts when usage hits 80% of plan limit.
  4. One-size expansion play. Seat expansion for every customer ignores cross-sell and tier upgrade opportunities. Fix: Multiple playbooks.

Output Format

Expansion playbook containing: (1) expansion propensity score formula with threshold bands (expand now / nurture / focus on adoption) applied to the target account set; (2) trigger table — each expansion signal mapped to the corresponding play, conversion rate benchmark, and recommended action with timing; (3) NRR formula with stage-appropriate targets (Seed through Growth) and expansion-as-percentage-of-new-ARR benchmarks; (4) four named expansion plays (Seat Expansion, Tier Upgrade, Cross-Sell, Enterprise Expansion) with trigger conditions, talk-track outline, and economics per play; (5) CSM expansion cadence by month (1-2 onboarding, 3 trigger identification, 4-6 first conversation, 6-12 close); (6) implementation checklist with automated trigger alerts, comp structure tied to NRR, and monthly measurement cadence.

Quality Check

Before delivering, verify:

  • All required sections complete
  • Output matches the user's stated need
  • No vague or unsupported claims
  • Frameworks cited where applicable

Execution Artifacts

  • references/framework-notes.md — Bowtie expansion, propensity score, NRR benchmarks
  • templates/output-template.md — Deliverable shell for agent output
  • scripts/check-output.py — Lightweight deliverable validator
  • ../../management-leadership/gtm-leadership/references/cro-enterprise-strategy.md — Snowflake consumption + Databricks workload expansion (Pattern 31)
  • sales-coaching/references/randy-seidl-relationship-selling.md — Stakeholder trust map for expansion (canonical) Lifecycle (Revenue stage): references/gtm-lifecycle-stages.md · references/lifecycle-skill-index.md · Pattern 18 in using-gtm-skills Cross-skill: saas-metrics-calculator/references/metric-definitions-exit-weight.md (NRR exit weight) · references/saas-metrics-reference.md Canonical lifecycle (repo root): references/gtm-lifecycle-stages.md (Revenue) · references/lifecycle-metrics-by-stage.md · skills/analytics/gtm-metrics/templates/stage-health-scorecard.md

Related Skills

  • churn-prevention — Retention is the foundation of expansion
  • cs-playbooks — Customer success framework
  • cs-analytics-dashboards — Health scores, expansion propensity
  • pricing-strategy — Tier design that enables expansion
  • customer-onboarding — Onboarding that sets up expansion

Signals

GitHub stars
50
Forks
15
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
expansion-selling
Source
github.com/leadmagic/gtm-skills