subscription-lifecycle
When the user wants to optimize their subscription business end-to-end — from trial start through renewal, cancellation, and win-back. Use when the user mentions "subscription lifecycle", "trial conversion", "churn", "cancellation", "win-back", "lapsed subscribers", "dunning", "billing retry", "grace period", "renewal rate", "subscriber LTV", or "resubscribe". For paywall design and pricing strategy, see monetization-strategy. For subscription analytics dashboards, see app-analytics.
npx skills add Eronred/aso-skills --skill subscription-lifecycle --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Subscription Lifecycle You optimize every stage of the subscription journey: trial → paid → renewal → cancellation recovery → win-back. ## The Subscription Lifecycle ``` Install → Trial start → [Trial period] → Conversion → Renewal → ... → Cancel → Win-back ↓ ↓ ↓ ↓ No convert Voluntary Involuntary Lapsed (nurture) (exit survey) (dunning) (campaign) ``` ## Key Metrics at Each Stage | Stage | Metric | Formula | Benchmark | |-------|--------|---------|-----------| | Trial | Trial start rate | Trials / Downloads | > 20% | | Trial | Trial-to-paid | Conversions / Trials | 25–40% strong | | Retention | Month 1 renewal | M1 renewals / Subscribers | > 70% | | Retention | Month 6 renewal | M6 renewals / Subscribers | > 50% | | Churn | Monthly churn | Lost subs / Start subs | < 5% good; < 2% excellent | | Revenue | MRR | Active subs × monthly price | — | | Revenue | LTV | ARPU / Monthly churn rate | — | | Recovery | Dunning recovery | Recovered / Failed payments | > 30% | | Win-back | Resubscribe rate | Returns / Lapsed | 5–15% | ## Stage 1 — Trial Optimization ### Trial Length | App Type | Recommended trial | Notes | |----------|------------------|-------| | Simple utility | 3–7 days | Val
- The Subscription Lifecycle
- Key Metrics at Each Stage
- Stage 1 — Trial Optimization
- Trial Length
- Trial Nurture Sequence
- Trial End — Conversion Moment
- Stage 2 — Reducing Voluntary Churn
- Why Users Cancel (and How to Fix It)
- The Cancellation Flow
- Engagement Signals to Watch
- Stage 3 — Involuntary Churn (Failed Payments)
- Dunning Strategy
- RevenueCat Integration
- Stage 4 — Win-Back Campaigns
What does the subscription-lifecycle skill do?
When the user wants to optimize their subscription business end-to-end — from trial start through renewal, cancellation, and win-back. Use when the user mentions "subscription lifecycle", "trial conversion", "churn", "cancellation", "win-back", "lapsed subscribers", "dunning", "billing retry", "grace period", "renewal rate", "subscriber LTV", or "resubscribe". For paywall design and pricing strategy, see monetization-strategy. For subscription analytics dashboards, see app-analytics.
How do I install it?
Run `npx skills add Eronred/aso-skills --skill subscription-lifecycle --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Eronred/aso-skills, a repository with 1,708 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.