Subscription Lifecycle logo

Subscription Lifecycle

CommunityPopular
Eronred
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.

Overview

PublisherEronred
Repositoryaso-skills
Skill namesubscription-lifecycle
Stars
1.9K
Forks
116
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Eronred on GitHub. Read the source before you install it.

Installation

Install the Subscription Lifecycle AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Eronred/aso-skills.git /tmp/aso-skills
mkdir -p .claude/skills
cp -r /tmp/aso-skills/skills/subscription-lifecycle .claude/skills/subscription-lifecycle
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Subscription Lifecycle in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Subscription Lifecycle on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Subscription Lifecycle is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 alternativeMonitor 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

Frequently asked questions

What does the Subscription Lifecycle AI 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.

Why use Subscription Lifecycle on TypingMind?

Because you install it once and use it with any model. Subscription Lifecycle is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Subscription Lifecycle in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Eronred/aso-skills/tree/main/skills/subscription-lifecycle. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Subscription Lifecycle?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Subscription Lifecycle?

As many as you like. As long as a model supports skills, you can use Subscription Lifecycle with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Subscription Lifecycle AI skill free?

Yes. It is published on GitHub by Eronred under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇