agentleFS
EronredEronred/aso-skills/skills/subscription-lifecycle/SKILL.md

subscription-lifecycle

Skill2.2k starsChanged 9 months agoMITView on GitHub

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.

2 other projects use a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Eronred/aso-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Eronred/aso-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When a user initiates cancellation (iOS — ManagedSubscriptionGroup):

    line 89
  2. Distinctive:

    Offer a pause: before full cancel: "Pause for 1–3 months instead of cancelling"

    line 91
  3. Distinctive:

    Offer a discount: Only as last resort — 20–30% off for 3 months

    line 93
  4. Distinctive:

    Exit survey: Always ask "Why are you cancelling?" (1 tap, not an essay)

    line 94
  5. Distinctive:

    Not using it enough

    line 98
  6. Distinctive:

    Use RevenueCat webhooks to trigger in-app messaging at each failure event

    line 140
  7. Distinctive:

    Start with the softest offer.

    line 150
  8. Distinctive:

    No additional code needed beyond StoreKit 2 integration

    line 173

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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

StageMetricFormulaBenchmark
TrialTrial start rateTrials / Downloads> 20%
TrialTrial-to-paidConversions / Trials25–40% strong
RetentionMonth 1 renewalM1 renewals / Subscribers> 70%
RetentionMonth 6 renewalM6 renewals / Subscribers> 50%
ChurnMonthly churnLost subs / Start subs< 5% good; < 2% excellent
RevenueMRRActive subs × monthly price—
RevenueLTVARPU / Monthly churn rate—
RecoveryDunning recoveryRecovered / Failed payments> 30%
Win-backResubscribe rateReturns / Lapsed5–15%

Stage 1 — Trial Optimization

Trial Length

App TypeRecommended trialNotes
Simple utility3–7 daysValue obvious quickly
Health/fitness7–14 daysHabit formation needs time
Productivity7–14 daysWorkflow integration
Education7–14 daysFirst lesson completion
Entertainment7 daysBinge 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)

ReasonSignalFix
Forgot they subscribedLow sessions, no activationImprove onboarding + notification strategy
Not enough valueLow feature usagePush underused high-value features
Too expensivePrice sensitivityIntroduce lower-tier or pause option
Problem with app1-star reviewsFix the bug, reply to reviews
Found alternative—Monitor competitor installs
Seasonal useChurns at same time yearlyOffer 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

DayAction
0Payment fails silently — Apple/Google retry
3Apple/Google retry #2
7Apple/Google retry #3 — show in-app "Update payment method" banner
10Send push: "Your subscription couldn't be renewed — tap to update"
14Grace period ends — subscription suspended
15Final 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

ChannelHow
Push notificationIn-app if app still installed
EmailIf email was collected
Apple Win-Back OfferNative iOS win-back offer in StoreKit 2
Paid retargetingMeta/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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.