subscription-lifecycle

eronred/aso-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/eronred/aso-skills --skill subscription-lifecycle
0 commentsdiscussion
summary

You optimize every stage of the subscription journey: trial → paid → renewal → cancellation recovery → win-back.

skill.md

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 Value obvious quickly
Health/fitness 7–14 days Habit formation needs time
Productivity 7–14 days Workflow integration
Education 7–14 days First lesson completion
Entertainment 7 days Binge behavior

Test: Monthly apps with a 7-day trial vs. 14-day trial — conversion rate may drop slightly but LTV often increases.

Trial Nurture Sequence

Send in-app (or push) messages during the trial to drive activation:

Day 0: Welcome — "Your trial has started. Here's how to get the most from it."
Day 1: Core feature highlight — "Try [key feature] today"
Day 3: Progress / social proof — "Users who do X get 3× better results"
Day 5 (7-day trial): Urgency — "2 days left in your trial"
Day 6: Value recap — "Here's what you've done / could do with premium"
Day 7: Last day — "Your trial ends today"

Rule: Messages should show value, not just create pressure.

Trial End — Conversion Moment

At trial end, show a paywall that:

  • Recaps what the user achieved during the trial
  • Shows the most-used premium features
  • Offers 3 plan options (monthly / annual / lifetime if applicable)
  • Highlights savings on annual ("Save 40%")

See monetization-strategy for paywall design details.

Stage 2 — Reducing Voluntary Churn

Why Users Cancel (and How to Fix It)

Reason Signal Fix
Forgot they subscribed Low sessions, no activation Improve onboarding + notification strategy
Not enough value Low feature usage Push underused high-value features
Too expensive Price sensitivity Introduce lower-tier or pause option
Problem with app 1-star reviews Fix the bug, reply to reviews
Found alternative Monitor competitor installs
Seasonal use Churns at same time yearly Offer a pause option

The Cancellation Flow

When a user initiates cancellation (iOS — ManagedSubscriptionGroup):

  1. Offer a pause before full cancel: "Pause for 1–3 months instead of cancelling"
  2. Show value recap: "You've used [feature] X times this month"
  3. Offer a discount: Only as last resort — 20–30% off for 3 months
  4. Exit survey: Always ask "Why are you cancelling?" (1 tap, not an essay)

Cancellation exit survey options:

  • Too expensive
  • Not using it enough
  • Missing a feature I need
  • Switching to a competitor
  • Technical issues
  • Just taking a break

Engagement Signals to Watch

Users at high churn risk:

  • Sessions < 1 per week (down from higher baseline)
  • Core feature not used in 14+ days
  • Push notifications disabled
  • Last session > 7 days ago

Trigger a re-engagement push or in-app message before they cancel.

Stage 3 — Involuntary Churn (Failed Payments)

Involuntary churn accounts for 20–40% of all subscription cancellations.

Dunning Strategy

Day Action
0 Payment fails silently — Apple/Google retry
3 Apple/Google retry #2
7 Apple/Google retry #3 — show in-app "Update payment method" banner
10 Send push: "Your subscription couldn't be renewed — tap to update"
14 Grace period ends — subscription suspended
15 Final in-app message: "Reactivate to keep access"

Grace period:

  • iOS: 6 days (configurable up to 16 in App Store Connect)
  • Android: 3 days (configurable)

Maximize grace period length — every extra day recovers more subscribers.

RevenueCat Integration

RevenueCat handles dunning automatically. Key settings:

  • Enable Billing Retry (iOS) / Account Hold (Android)
  • Configure grace period to maximum allowed
  • Use RevenueCat webhooks to trigger in-app messaging at each failure event

See revenuecat.md integration guide.

Stage 4 — Win-Back Campaigns

Target lapsed subscribers (cancelled or expired in last 30–90 days).

Win-Back Offer Ladder

Start with the softest offer; escalate only if no response:

Week 1 after lapse:  "We miss you" — highlight new features added since they left
Week 3:              "Come back for 30% off your first month back"
Week 6:              "3 months at 50% off — best offer we'll make"
Week 12+:            Archive — low conversion probability

Win-Back Channels

Channel How
Push notification In-app if app still installed
Email If email was collected
Apple Win-Back Offer Native iOS win-back offer in StoreKit 2
Paid retargeting Meta/Google retargeting to lapsed subscriber list

StoreKit 2 Win-Back Offers (iOS 18+)

Apple natively supports win-back subscription offers for lapsed subscribers:

  • Set up in App Store Connect → Subscriptions → Win-Back Offers
  • Presented automatically in the App Store to eligible lapsed users
  • No additional code needed beyond StoreKit 2 integration

Output Format

Subscription Health Report

Lifecycle Metrics ([period]):

Trial start rate:    [X]%  (benchmark: >20%)
Trial conversion:    [X]%  (benchmark: 25-40%)
M1 renewal:          [X]%  (benchmark: >70%)
Monthly churn:       [X]%  (benchmark: <5%)
Dunning recovery:    [X]%  (benchmark: >30%)
Win-back rate:       [X]%  (benchmark: 5-15%)

LTV (estimated):    $[N]
MRR:                $[N]

Top issues:
1. [Stage] — [metric] is [X]% vs benchmark [Y]% — [recommended fix]
2. [Stage] — [metric] is [X]% vs benchmark [Y]% — [recommended fix]

Priority action:
[Single highest-leverage change to implement this week]

Related Skills

  • monetization-strategy — Paywall design, pricing tiers, trial setup
  • retention-optimization — Engagement strategy to reduce voluntary churn
  • app-analytics — Track the metrics above with Firebase + RevenueCat
  • onboarding-optimization — Fix early-stage drop-off that prevents trial starts
  • rating-prompt-strategy — Satisfied subscribers are your best raters
how to use subscription-lifecycle

How to use subscription-lifecycle on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add subscription-lifecycle
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/eronred/aso-skills --skill subscription-lifecycle

The skills CLI fetches subscription-lifecycle from GitHub repository eronred/aso-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/subscription-lifecycle

Reload or restart Cursor to activate subscription-lifecycle. Access the skill through slash commands (e.g., /subscription-lifecycle) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.750 reviews
  • Pratham Ware· Dec 28, 2024

    We added subscription-lifecycle from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Neel Singh· Dec 20, 2024

    subscription-lifecycle reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Aditi Zhang· Dec 20, 2024

    Useful defaults in subscription-lifecycle — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Liam Rao· Dec 4, 2024

    subscription-lifecycle has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Ira Reddy· Nov 27, 2024

    Solid pick for teams standardizing on skills: subscription-lifecycle is focused, and the summary matches what you get after install.

  • Soo Jackson· Nov 23, 2024

    Useful defaults in subscription-lifecycle — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ira Sethi· Nov 11, 2024

    Registry listing for subscription-lifecycle matched our evaluation — installs cleanly and behaves as described in the markdown.

  • James Kim· Nov 11, 2024

    subscription-lifecycle has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Neel Sharma· Oct 18, 2024

    We added subscription-lifecycle from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Nia Wang· Oct 14, 2024

    subscription-lifecycle is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 50

1 / 5