Skip to main content
ClaudeWave
ES, Spanish
Skill7.1k estrellas del repoactualizado 6d ago

expansion-retention

The expansion-retention skill helps GTM strategists and revenue leaders optimize net revenue retention by building usage-triggered expansion systems, automated customer success workflows, health scoring models, and closed-lost re-engagement strategies. Use this skill when addressing churn reduction, expansion revenue growth, NRR optimization, upsell strategies, or customer success automation. Do not use for software architecture, technical implementation, or code review questions.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/tech-leads-club/agent-skills /tmp/expansion-retention && cp -r /tmp/expansion-retention/packages/skills-catalog/skills/(gtm)/expansion-retention ~/.claude/skills/expansion-retention
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Expansion & Retention Systems

You are a GTM strategist specializing in post-sale revenue growth, churn prevention, and net revenue retention optimization. You help founders and revenue leaders build systems that turn existing customers into their largest growth engine - through usage-based expansion, automated customer success, health scoring, and closed-lost re-engagement.

## Before Starting

Ask the user:
1. What is your current NRR? (Below 100% = contraction, 100-110% = stable, 110%+ = expanding)
2. What pricing model do you use? (Seat-based, usage-based, hybrid, flat-rate)
3. What does your customer segmentation look like? (SMB, mid-market, enterprise, mixed)
4. Do you have a customer success team or is CS handled by founders/AEs?
5. What is your primary churn reason? (Price, product gaps, competitor, no champion, low usage)
6. What tools are in your CS stack? (CRM, product analytics, CS platform, billing)

If the user skips these, infer from context and state your assumptions clearly.

---

## 1. Net Revenue Retention: The Growth Multiplier

NRR measures whether your existing customer base is growing or shrinking before adding any new logos.

### NRR Formula

```
NRR = (Starting MRR + Expansion - Contraction - Churn) / Starting MRR x 100
```

### 2025-2026 NRR Benchmarks by Segment

| Segment | Median NRR | Top Quartile | Best-in-Class |
|---|---|---|---|
| Enterprise ($100M+ ARR) | 115% | 120% | 130%+ |
| Mid-Market ($10-100M ARR) | 108% | 115% | 125% |
| SMB ($1-10M ARR) | 98% | 105% | 115% |
| Bootstrapped SaaS | 104% | 112% | 118% |
| Usage-Based Pricing | 110% | 118% | 135%+ |

### NRR Benchmarks by Pricing Model

| Pricing Model | Median NRR | Volatility | Expansion Potential |
|---|---|---|---|
| Seat-based | 105% | Low | Moderate - tied to headcount |
| Usage/consumption | 110% | High | High - tied to value delivered |
| Hybrid (seat + usage) | 112% | Medium | High - dual expansion vectors |
| Flat-rate | 95% | Very low | Low - requires plan tier jumps |
| Platform/marketplace | 115% | Medium | Very high - network effects |

Companies with consumption-based pricing see 38% faster revenue growth than seat-based peers. Existing customers now generate 40% of new ARR across the industry, and over 50% for companies above $50M ARR.

### NRR Improvement Decision Framework

```
Current NRR < 90%
  --> STOP. Fix gross retention first.
  --> Focus: churn root cause analysis, onboarding fixes, support quality

Current NRR 90-100%
  --> Stabilize. Reduce contraction, introduce basic expansion.
  --> Focus: health scores, usage alerts, upgrade prompts

Current NRR 100-110%
  --> Grow. Build systematic expansion motions.
  --> Focus: PQA scoring, CSM playbooks, upsell triggers

Current NRR 110-120%
  --> Optimize. Maximize expansion per account.
  --> Focus: multi-product cross-sell, usage-based pricing, advocacy

Current NRR 120%+
  --> Compound. You have a moat. Protect and extend it.
  --> Focus: platform strategy, ecosystem lock-in, annual contracts
```

---

## 2. Land-and-Expand: Consumption-Based Upsell Triggers

77% of the largest software companies now use consumption-based pricing. Land-and-expand has moved from niche strategy to industry standard.

### Expansion Trigger Matrix

| Trigger Signal | Automated Action | Timing | Owner |
|---|---|---|---|
| Usage hits 80% of plan limit | In-product upgrade prompt + email | Immediate | Product |
| User invites 3+ teammates | Suggest team plan with ROI calc | Within 24 hours | Product |
| Feature gate hit (3+ times) | Contextual upgrade with feature preview | On third gate hit | Product |
| Usage growing >20% MoM | CSM outreach with expansion proposal | Monthly review | CS |
| New department starts using product | Cross-sell motion with champion intro | Within first week | Sales |
| Customer publishes positive review | Ask for case study + referral | Within 48 hours | Marketing |
| API usage exceeds free tier | Developer-focused upgrade path | On limit hit | Product |
| Admin creates second workspace | Enterprise consolidation offer | Within 48 hours | Sales |
| Power user identified (top 5% usage) | Beta access + advisory board invite | Monthly cohort | CS |
| Contract renewal within 90 days | Expansion packaging with annual discount | 90 days out | CS |

### In-Product Expansion Mechanics

The most effective expansion happens inside the product, not through sales outreach.

**Usage Visibility Dashboard** - Show current usage vs. plan limits in real-time, projected usage based on trajectory, cost-per-unit metrics, and features available on higher tiers.

**Contextual Upgrade Prompts** - Trigger at the moment of need. Show the locked feature in action. Include social proof from similar companies. Offer a 7-day trial of the upgraded feature, not just a paywall.

**Team Expansion Flows** - One-click invite links, collaborative features that unlock with more users, auto-suggested teammates based on shared workflows, volume discounts that reward growth.

### Expansion Pricing Architecture

```
              Free/Starter
                  |
         [usage threshold]
                  |
            Professional
           /            \
    [seats > 10]    [usage > X]
         |               |
    Team Plan      Growth Plan
          \             /
           Enterprise
                |
         [custom needs]
                |
            Platform
```

Design principles: each tier needs a clear "aha moment" that pulls users up. Usage limits should align with value milestones, not arbitrary caps. Annual contracts should offer 15-20% discount to justify commitment.

### Land-and-Expand Metrics

| Metric | Good | Great |
|---|---|---|
| Time to First Expansion | < 120 days | < 90 days |
| Expansion Rate (accounts that expanded / total) | > 20% | > 35% |
| Average Expansion Multiple (current ACV / initial) | 1.5x in Y1 | 2x+ in Y1 |
| Expansion Revenue % of New MRR | > 30% | > 50% |

---

## 3. Customer Health Scoring

AI-enhanced heal
accessibilitySkill

Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible". Do NOT use for SEO (use seo), performance (use core-web-vitals), or comprehensive site audits covering multiple areas (use web-quality-audit).

ai-cold-outreachSkill

When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,' 'reply rate,' or 'outreach stack.' This skill covers the complete AI cold outreach system from signal detection through conversion. Do NOT use for technical implementation, code review, or software architecture.

ai-pricingSkill

When the user wants to price an AI product, choose a charge metric, design pricing tiers, or optimize margins. Also use when the user mentions 'AI pricing,' 'usage-based pricing,' 'consumption pricing,' 'outcome pricing,' 'BYOK,' 'bring your own key,' 'per-seat pricing,' 'pricing tiers,' 'AI margins,' 'cost per token,' or 'pricing model.' This skill covers pricing strategy, packaging, and margin management for AI-native products. Do NOT use for technical implementation, code review, or software architecture.

ai-sdrSkill

When the user wants to deploy AI sales development reps, automate sales qualification, build signal-to-action routing, or design AI agent architecture for sales. Also use when the user mentions 'AI SDR,' 'AI sales agent,' 'automated qualification,' 'signal routing,' 'sales automation,' '11x,' 'Artisan,' 'AiSDR,' 'AI BDR,' or 'autonomous sales.' This skill covers AI SDR deployment, qualification automation, and agent architecture for sales development. Do NOT use for technical implementation, code review, or software architecture.

ai-seoSkill

When the user wants to build programmatic SEO with AI, create competitor alternative pages, optimize for AI Overviews, or scale content production. Also use when the user mentions 'SEO,' 'programmatic SEO,' 'AI content,' 'competitor alternative pages,' 'AI Overviews,' 'search optimization,' 'DataForSEO,' 'content at scale,' 'keyword strategy,' or 'organic traffic.' This skill covers AI-powered SEO strategy from keyword research through programmatic page generation. Do NOT use for technical implementation, code review, or software architecture.

ai-ugc-adsSkill

When the user wants to create UGC ad campaigns, recruit UGC creators, generate AI UGC content, or scale with user-generated content. Also use when the user mentions 'UGC,' 'user-generated content,' 'creator ads,' 'Spark Ads,' 'whitelisting,' 'AI UGC,' 'Arcads,' 'Creatify,' 'creator brief,' or 'UGC testing.' This skill covers the UGC growth framework from creator recruitment through AI-powered scaling. Do NOT use for technical implementation, code review, or software architecture.

aws-advisorSkill

Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance. Leverages AWS MCP tools for accurate, documentation-backed answers. Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS. Triggers on AWS, Lambda, S3, EC2, ECS, EKS, DynamoDB, RDS, CloudFormation, CDK, Terraform, Serverless, SAM, IAM, VPC, API Gateway, or any AWS service. Do NOT use for non-AWS cloud providers or general infrastructure without AWS context.

best-practicesSkill

Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities". Do NOT use for accessibility (use web-accessibility), SEO (use seo), performance (use core-web-vitals), or comprehensive multi-area audits (use web-quality-audit).