component-common-domai…
Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common…
When the user wants to reduce churn, build expansion revenue, automate customer success, or optimize net revenue retention. Also use when the user mentions 'churn,' 'retention,' 'expansion revenue,' 'upsell,' 'NRR,' 'net revenue retention,' 'customer success,' 'land and expand,'
$ npx -y skills add tech-leads-club/agent-skills --skill expansion-retention --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/expansion-retentionContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to reduce churn, build expansion revenue, automate customer success, or optimize net revenue retention. Also use when the user mentions 'churn,' 'retention,' 'expansion revenue,' 'upsell,' 'NRR,' 'net revenue retention,' 'customer success,' 'land and expand,'
name: expansion-retention description: "When the user wants to reduce churn, build expansion revenue, automate customer success, or optimize net revenue retention. Also use when the user mentions 'churn,' 'retention,' 'expansion revenue,' 'upsell,' 'NRR,' 'net revenue retention,' 'customer success,' 'land and expand,' 'closed-lost,' or 'renewal.' This skill covers expansion and retention systems from usage triggers through automated customer success. Do NOT use for technical implementation, code review, or software architecture." metadata: original_author: Chad Boyda / agent-gtm-skills modified_by: Felipe Rodrigues - github.com/felipfr source: https://github.com/chadboyda/agent-gtm-skills version: '1.0.0'
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.
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.
---
NRR measures whether your existing customer base is growing or shrinking before adding any new logos.
NRR = (Starting MRR + Expansion - Contraction - Churn) / Starting MRR x 100
| 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%+ |
| 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.
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
---
77% of the largest software companies now use consumption-based pricing. Land-and-expand has moved from niche strategy to industry standard.
| 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 |
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.
Free/Starter
|
[usage threshold]
|
Professional
/ \
[seats > 10] [usage > X]
| |
Team Plan GrowThe secure, validated skill registry for professional AI coding agents. Extend Antigravity, Claude Code, Cursor, Copilot and more with absolute confidence.
Repo: tech-leads-club/agent-skills
Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common…
Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level. Use when asking…
Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?",…
Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when…
Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract…
Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?",…