SkillAgentSearch skills...

expansion-retention

When the user wants to reduce churn, build expansion revenue, automate customer success, or optimize net revenue retention.

Install / Use

npx skills add tech-leads-club/agent-skills --skill expansion-retention

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

96/100

Category

Automation

Supported Platforms

Universal

Our assessment of expansion-retention

expansion-retention scores 96/100 on our quality scale, 176th of 1,987 Automation skills we index (top 9%).

Its SKILL.md is 22 KB long, well organised into 45 sections with 6 code examples: a thorough specification that gives an agent plenty to work with.

With 6,832 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 7 days ago, so expansion-retention is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

expansion-retention compared with similar skills

All 4 of these similar skills score higher than expansion-retention; compare them before choosing.

SkillScoreStarsUpdatedFormat
expansion-retention (this skill)by tech-leads-club966.8k7d agoSKILL.md
Agent-Reachby Panniantong10085.9k12d agoCLAUDE.md
rufloby ruvnet10073.4ktodayCLAUDE.md
Scraplingby D4Vinci10084.1ktodayMCP Server
algorithmic-artby anthropics100177.9k5d agoSKILL.md

Frequently asked questions

How do I install expansion-retention?
Run npx skills add tech-leads-club/agent-skills --skill expansion-retention. The install tabs above show the steps for each supported agent.
Which AI agents does expansion-retention work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is expansion-retention safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is expansion-retention still maintained?
The repository was last updated 7 days ago, so expansion-retention is actively maintained.

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'


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 health scores can predict churn 3-6 months in advance with 85%+ accuracy.

Health Score Components

| Signal Category | Weight | Data Source | Refresh Rate | |---|---|---|---| | Product Usage | 35% | Product analytics | Daily | | Engagement (emails, meetings) | 20% | CRM + email | Weekly | | Support Health | 15% | Ticketing system | Real-time | | Business Outcomes | 15% | Customer reporting | Monthly | | Relationship Strength | 10% | CRM + surveys | Quarterly | | Contract/Financial | 5% | Billing system | On change |

Health Score by Segment

Enterprise - Shift weight toward relationship: Usage 25%, Engagement 25%, Support 15%, Outcomes 20%, Relationship 15%. Track exec sponsor activity, QBR attendance, multi-thread depth.

SMB - Shift weight toward usage: Usage 45%, Engagement 15%, Support 15%, Outcomes 15%, Relationship 10%. Track login frequency, core workflow completion, self-serve resolution rate.

Health Score Ranges and Actions

| Score Range | Label | Action | Cadence | |---|---|---|---| | 85-100 | Thriving | Expansion outreach, advocacy asks | Monthly check-in | | 70-84 | Healthy | Monitor, share best practices | Bi-weekly check-in | | 50-69 | Neutral | Proactive feature training | Weekly check-in | | 30-49 | At Risk | CSM intervention, exec sponsor call | 2x weekly | | 0-29 | Critical | Save team deployed, exec escalation | Daily until resolved |

Churn Risk Signals and Automated Responses

| Risk Signal | Severity | Automated Response | Escalation | |---|---|---|---| | Login frequency dropped >40% | High | Re-engagement email sequence | CSM alert at day 7 | | Support tickets spiking (3x normal) | High | Proactive CSM outreach | Manager alert at 5x | | Key user left company (LinkedIn) | Critical | Identify new champion campaign | CSM call within 48 hrs | | Usage plateau for 30+ days | Medium | "Did you know?" feature email | CSM review at day 45 | | Competitor evaluation detected | Critical | Competitive displacement content | AE + CSM war room | | Payment failure | High | Dunning sequence (3-5-7-14 day) | Finance + CS at day 14 | | NPS detractor score (<6) | High | CSM call + issue resolution | Manager review | | Champion goes silent (14+ days) | Medium | Multi-channel re-engagement | CSM direct outreach | | Contract renewal < 60 days, no contact | Critical | Renewal rescue sequence | CS leadership involved |


4. Product-Qualified Accounts (PQAs)

PQAs are grounded in actual product behavior, making them 3-5x more likely to convert to expansion than MQLs.

PQA Scoring Model

| Behavior | Points | Decay | Notes | |---|---|---|---| | Activated core feature | +20 | None | One-time credit | | Daily active user (per user) | +2/day | -1/day inactive | Tracks engagement depth | | Invited teammate | +15 | None | Strong expansion signal | | Hit usage limit | +25 | Resets monthly | Immediate upsell opportunity | | Feature gate interaction | +10 | Resets weekly | Shows unmet need | | API integration built | +30 | None | High switching cost | | Data imported (>threshold) | +20 | None | Investment signal | | Admin settings configured | +15 | None | Customization = commitment |

PQA Threshold Actions

Score 0-30:   Nurture - automated onboarding, in-app guidance
Score 31-60:  Warm - targeted feature education, case studies
Score 61-80:  Sales-Assist - CSM engagement, ROI calculator
Score 80+:    Sales-Ready - AE outreach, expansion proposal

Recalculate PQA scores daily. Route score-80+ accounts to sales within 4 hours. Review conversion rates quarterly to adjust thresholds.

PQA vs. PQL vs. MQL

| Attribute | MQL | PQL | PQA | |---|---|---|---| | Signal source | Marketing activity | Individual user behavior | Account-level product usage | | Conversion rate | 1-3% | 8-15% | 15-25% | | Best for | Top-of-funnel | PLG new business | Expansion + cross-sell | | Sales effort | High | Medium | Low - value already proven |


5. Automated Onboarding Sequences

Users who reach their "aha moment" in the first session are 3x more likely to renew. Cutting time-to-value by 20% lifts ARR growth by 18%.

Onboarding Milestone Framework

| Milestone | Target Timing | Success Metric | If Missed | |---|---|---|---| | Account created | Day 0 | Signup completed | Abandon recovery email | | First value action | < 5 minutes | Core workflow completed | In-app tooltip nudge | | Data connected | Day 1 | Integration or import done | Setup assistance email | | Team invited | Day 3 | 2+ users active | Collaboration benefit email | | Habit formed | Day 7 | 3+ sessions in 7 days | Usage tip drip sequence | | ROI realized | Day 14 | Outcome metric visible | Success story + CSM check | | Expansion ready | Day 30 | Usage approaching limit | Upgrade path presented |

Automated Onboarding Email Sequence

Day 0:  Welcome + quickstart guide (first value in <2 min)
Day 1:  "Complete your setup" - missing integration/data import
Day 3:  "Invite your team" - collaboration benefits + one-click link
Day 5:  "Power user tip" - advanced feature for their use case
Day 7:  "Your first week recap" - usage stats + next milestone
Day 14: "Your results so far" - ROI metrics + peer benchmarks
Day 21: "Meet your CSM" (if qualified) or "Join our community"
Day 

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars6.8k
CategoryAutomation
Updated7d ago
Forks551

Languages

TypeScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium