Subscription Lifecycle
Skill Verified ActiveWhen 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.
To help users optimize their subscription business end-to-end by providing actionable guidance for each stage of the customer lifecycle.
Features
- Optimizes subscription trial conversion and nurture sequences.
- Provides strategies for reducing voluntary and involuntary churn.
- Details dunning processes and recommended grace periods.
- Outlines win-back campaign strategies and channels.
- Defines key subscription lifecycle metrics and benchmarks.
Use Cases
- Use when optimizing trial conversion rates and maximizing lead-to-paid conversion.
- Use when seeking to reduce subscriber churn through proactive engagement and retention strategies.
- Use when addressing involuntary churn caused by failed payments and implementing dunning.
- Use when planning and executing win-back campaigns for lapsed subscribers.
Non-Goals
- Designing paywall and pricing strategies (see `monetization-strategy`).
- Setting up subscription analytics dashboards (see `app-analytics`).
- Developing in-app purchase mechanics or fraud prevention.
Trust
- info:Issues Attention0 issues opened and 1 issue closed in the last 90 days, indicating minimal recent activity but no backlog.
Practical Utility
- info:Usage examplesWhile the SKILL.md details metrics and strategies, it lacks concrete end-to-end examples demonstrating the invocation and observable outcome for each major capability.
- info:Edge casesThe skill discusses potential failure modes like failed payments and reasons for cancellation, but does not explicitly document observable symptoms and recovery steps for each.
Installation
First, add the marketplace
/plugin marketplace add Eronred/aso-skills/plugin install aso-skills@aso-skillsQuality Score
VerifiedSimilar Extensions
Churn Prevention
95When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.
SaaS Economics Efficiency Metrics
100Evaluate SaaS unit economics and capital efficiency. Use when deciding whether the business can scale efficiently or needs correction.
Office Hours
100/cs:office-hours <topic> — YC-style 6-question founder interrogation before any advice. Forces clarity on problem, customer, distribution, defensibility, capital, and founder fit.
Traction Eos
99Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "Entrepreneurial Operating System", or "business operating system". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.
Cross Eval
99/cs:cross-eval <memo> — Multi-model consensus on a board memo or strategy brief. Claude + Codex + Gemini cross-review with graceful degradation.
Hooked Ux
99Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "engagement loops", "habit formation", "push notifications", "variable rewards", "daily active users", "habit zone", or "user retention loops". Also trigger when designing notification strategies, building streaks or progress systems, or analyzing why users stop using a product after initial signup. Covers ethics evaluation and onboarding for habits. For friction reduction and B=MAP, see improve-retention. For viral sharing, see contagious.