bundles/sales/skills/retention-engine/SKILL.md
Designs and executes customer retention systems to reduce churn, maximize LTV, and build recurring revenue using Hormozi's ascension frameworks. Activates when users need retention strategy, subscription optimization, upsell/cross-sell design, or are facing "customers keep leaving" problems.
npx skillsauth add shipshitdev/library retention-engineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill applies Alex Hormozi's retention and ascension frameworks to help indie founders reduce churn, maximize customer lifetime value (LTV), and build recurring revenue machines. It diagnoses churn causes and designs complete ascension paths.
Hormozi's Core Principle: "Acquiring customers is expensive. Keeping them is profitable."
This skill auto-activates when:
LTV = (Average Revenue Per Customer × Average Customer Lifespan) - CAC
To maximize LTV:
Ask the user:
Tell me about your customer journey after purchase:
- What happens immediately after they buy? (First hour, first day)
- What's the experience in the first week?
- What happens at 30 days? 90 days? 1 year?
- How long does the average customer stay?
- Do they buy anything else from you? What?
Journey Assessment:
| Stage | Question to Answer | |-------|-------------------| | Immediate (0-1 day) | Do they feel excited and confident? | | Activation (1-7 days) | Do they get a quick win? | | Engagement (7-30 days) | Are they using what they bought? | | Retention (30-90 days) | Are they seeing results? | | Expansion (90+ days) | Are they ready for more? |
Ask the user:
Why do customers leave?
- What are the top 3 reasons people cancel or don't return?
- When do most customers leave? (After 1 month? 3 months? 1 purchase?)
- What do customers who stay have in common?
- What do customers who leave have in common?
- Do you ask for feedback when they leave? What do they say?
Churn Cause Framework:
| Symptom | Likely Cause | Solution | |---------|--------------|----------| | Leave within 30 days | Never got value | Better onboarding | | Leave at 90 days | Hit a plateau | Add next-level offering | | Leave after success | Nothing else to buy | Create ascension path | | Leave due to price | Wrong positioning | Reframe value | | Leave due to non-use | No engagement | Activation campaigns |
Ask the user:
What's the natural next step for successful customers?
- What do customers want after they succeed with your current offer?
- What related problems do they have?
- What would a "premium" or "advanced" version look like?
- What would recurring access or support look like?
- What would a "done-for-you" tier look like?
Ascension Ladder Framework:
Level 1: Entry Offer → Solves first problem
↓
Level 2: Core Offer → Deeper solution
↓
Level 3: Premium Offer → Advanced/faster results
↓
Level 4: Done-For-You → They pay you to do it
↓
Level 5: Ongoing Relationship → Retainer/subscription
Example Ascension Paths:
| Business Type | L1 | L2 | L3 | L4 | L5 | |--------------|-----|-----|-----|-----|-----| | Course Creator | Free Workshop | Core Course | Mastermind | 1:1 Coaching | Annual Membership | | Agency | Audit | One-Off Project | Retainer | White Label | Partner | | SaaS | Free Trial | Basic Plan | Pro Plan | Enterprise | Custom Development | | Coach | Free Call | 1:1 Sessions | Group Program | VIP Day | Ongoing Retainer |
Design systems for each retention lever:
Lever 1: Onboarding Excellence
Goal: Get them a win in the first 24-48 hours
- What's the fastest win possible?
- How do you ensure they actually start?
- What's the "aha moment" they need to hit?
- How do you celebrate their first success?
Lever 2: Engagement Systems
Goal: Keep them using/engaging regularly
- What triggers regular engagement?
- What brings them back weekly/monthly?
- How do you re-engage inactive users?
- What creates habit formation?
Lever 3: Success Milestones
Goal: Make progress visible and celebrated
- What are the key milestones?
- How do you track and display progress?
- How do you celebrate achievements?
- What happens when they hit each milestone?
Lever 4: Community/Connection
Goal: Create belonging and peer accountability
- Is there a community component?
- How do customers connect with each other?
- Who do they become accountable to?
- What creates identity/belonging?
Lever 5: Ascension Triggers
Goal: Move them to the next level at the right time
- What signals they're ready for more?
- How do you introduce the next offer?
- What makes the upgrade feel natural?
- How do you create FOMO for the next level?
Design early warning systems:
Warning Signs to Track:
| Signal | What It Means | Action | |--------|--------------|--------| | Login frequency drops | Disengagement | Re-engagement email | | Support tickets increase | Frustration | Proactive outreach | | Usage plateau | Hit ceiling | Introduce next level | | Payment failure | May churn | Recovery sequence | | No engagement for 30 days | High churn risk | Win-back campaign |
Cancellation Prevention:
When someone tries to cancel:
- Understand: "Can you share what's not working?"
- Solve: "We can fix that. Here's how..."
- Offer alternative: "Would a pause or downgrade help?"
- Create urgency: "You'll lose [specific benefit]"
- Exit gracefully: "We're here when you're ready"
Tactic 1: Upsells (More of Same)
Tactic 2: Cross-Sells (Complementary)
Tactic 3: Referrals (Multiplied)
Tactic 4: Expansion (New Segments)
# Retention Engine: [Business Name]
## Current State Analysis
**Average Customer Lifespan:** X months
**Current Churn Rate:** X%/month
**Average Revenue Per Customer:** $X
**Current LTV:** $X
**Primary Churn Reasons:**
1. [Reason 1]
2. [Reason 2]
3. [Reason 3]
## Customer Journey Redesign
### Day 0: Purchase
- [ ] Welcome email with immediate value
- [ ] Quick start guide/video
- [ ] First win opportunity
### Day 1-7: Activation
- [ ] [Specific activation milestone]
- [ ] Check-in email/message
- [ ] Community introduction
### Day 8-30: Engagement
- [ ] [Weekly engagement triggers]
- [ ] Progress tracking
- [ ] Success celebration
### Day 31-90: Results
- [ ] [Monthly milestone]
- [ ] Case study opportunity
- [ ] Ascension introduction
### Day 91+: Expansion
- [ ] Upgrade offer
- [ ] Referral request
- [ ] Renewal/annual offer
## Ascension Ladder
| Level | Offer | Price | Transition Trigger |
|-------|-------|-------|-------------------|
| L1: Entry | [Offer name] | $X | [Who this is for] |
| L2: Core | [Offer name] | $X | [When they're ready] |
| L3: Premium | [Offer name] | $X | [Upgrade signal] |
| L4: DFY | [Offer name] | $X | [Who needs this] |
| L5: Ongoing | [Offer name] | $X/mo | [Retention play] |
## Churn Prevention System
### Early Warning Signals
| Signal | Detection | Action |
|--------|-----------|--------|
| [Signal 1] | [How to detect] | [Response] |
| [Signal 2] | [How to detect] | [Response] |
| [Signal 3] | [How to detect] | [Response] |
### Cancellation Flow
1. Survey: "[Question to ask]"
2. Save Offer: "[What to offer to keep them]"
3. Downgrade Option: "[Cheaper alternative]"
4. Pause Option: "[Temporary pause terms]"
5. Exit: "[Graceful goodbye + door open]"
## LTV Improvement Actions
### Immediate (This Week)
- [ ] [Quick win action 1]
- [ ] [Quick win action 2]
### Short-Term (30 Days)
- [ ] [System to build]
- [ ] [Offer to create]
### Long-Term (90 Days)
- [ ] [Full ascension ladder]
- [ ] [Retention automation]
## Projected Impact
| Metric | Current | Target | Improvement |
|--------|---------|--------|-------------|
| Churn Rate | X%/mo | X%/mo | X% reduction |
| Customer Lifespan | X mo | X mo | Xx increase |
| Revenue/Customer | $X | $X | Xx increase |
| **LTV** | **$X** | **$X** | **Xx increase** |
Ask: "What would a 3-year relationship with a customer look like?"
Design backwards:
| Skill | How It Works Together |
|-------|----------------------|
| offer-architect | Design each level of the ascension ladder |
| pricing-strategist | Price each tier appropriately |
| constraint-eliminator | Remove friction that causes churn |
| copywriter | Write retention/upgrade communications |
Why retention matters:
Example:
lead-channel-optimizeroffer-architectconstraint-eliminatorbusiness-model-auditordevelopment
TypeScript refactoring and modernization guidelines from a principal specialist perspective. This skill should be used when refactoring, reviewing, or modernizing TypeScript code to ensure type safety, compiler performance, and idiomatic patterns. Triggers on tasks involving TypeScript type architecture, narrowing, generics, error handling, or migration to modern TypeScript features.
tools
Resolves TypeScript and JavaScript problems across type-level programming, performance, monorepo management, migration, and modern tooling. Invoke when diagnosing "type instantiation excessively deep" errors, migrating JS to TS, configuring strict tsconfig, debugging module resolution, or choosing between Biome/ESLint/Turborepo/Nx.
tools
Turborepo monorepo build system guidance. Triggers on: `turbo.json`, task pipelines, `dependsOn`, caching, remote cache, the `turbo` CLI, `--filter`, `--affected`, CI optimization, environment variables, internal packages, monorepo structure, and package boundaries. Use when the user configures tasks or workflows, creates packages, sets up a monorepo, shares code between apps, runs changed packages, debugs cache behavior, or works in an `apps/` plus `packages/` workspace.
tools
Provides Tailwind CSS v4 performance optimization and best practices guidelines. Triggers when writing, reviewing, or refactoring Tailwind CSS v4 code; when working with Tailwind configuration, @theme directive, utility classes, responsive design, dark mode, container queries, or CSS generation optimization.