subscription-lifecycle
Audit an app Product's subscription lifecycle — trial, conversion, renewal, churn, win-back — against benchmarks and rank the fixes.
Written by Kwern, after the skill of the same name in Eronred's aso-skills, MIT. Updated 2026-09-24.
The file, as Kwern runs it
Nothing below is rewritten or cut. The description a model routes on comes first, then the file itself. The whole thing, frontmatter included, is at /skills/subscription-lifecycle.md.
description
Audit an app Product's subscription lifecycle — trial, conversion, renewal, churn, win-back — against benchmarks and rank the fixes. Use for "trial conversion", "churn", "renewal rate", "billing retry", "grace period", "win-back offers", "lapsed subscribers", "subscriber LTV". For the paywall itself use paywalls; for price points use pricing.
A subscription business leaks at five stages: trial start, trial-to-paid, renewal, involuntary churn (failed payments), and win-back of lapsed subscribers. Output is a lifecycle audit: each stage measured against its benchmark, the fixes ranked by revenue recovered.
Gather
read_context— pricing, plans, trial length, activation event, cancellation flow if documented.connector_revenuecat_metricswhen the RevenueCat Connector exists — MRR, active subscriptions, trials, trial conversion, churn, revenue 28d, per product. Without it there is no public fallback: work from the Foundation doc's pricing and trial, mark every stage metric "unmeasured", and say the RevenueCat Connector would add trial conversion, churn, and per-product revenue.connector_asc_in_app_purchaseswhen the ASC Connector exists — the in-app purchases and subscriptions as visitors see them: display names, groups, periods and product page promotion. Without it, take the plans from the Foundation doc and say the ASC Connector would add them. Price points come from the Foundation doc, or stay unknown.connector_asc_analyticswhen available — downloads for the trial start rate, retention curve (renewal risk shows up as retention first).connector_asc_reviewswhen available (fallbackapp_store_reviews) — pricing and paywall complaints, cancellation reasons users state in public.
Audit
Benchmarks per stage and the formulas are in references/benchmarks.md; read it before scoring. Walk the stages in order:
- Trial — trial start rate, length per app type, the nurture sequence (day 0 → last day), the trial-end moment.
- Conversion — trial-to-paid; the paywall's job. Point to
paywallsfor the paywall itself andpricingfor the price ladder. - Renewal and voluntary churn — M1/M6 renewal, cancel reasons, engagement signals that precede a cancel, the cancellation flow (pause, value recap, exit survey, discount last).
- Involuntary churn — Billing Grace Period length, billing retry, the in-app "update payment" moment; 20–40% of all cancellations are involuntary.
- Win-back — offer ladder over 12 weeks, channels, StoreKit win-back offers configured in App Store Connect.
Score each stage: metric, benchmark, gap, revenue at stake (gap × subscribers × price), one recommended fix. Playbooks for stages 1, 3, 4, 5 are in references/stage-playbooks.md; read the section for any stage that scores below benchmark.
Output: lifecycle audit
Period · data source (RevenueCat / Foundation doc only)
Stage Metric Value Benchmark Gap $ at stake
Trial start rate
Trial trial-to-paid
Renewal M1 renewal
Churn monthly churn
Involuntary billing recovery
Win-back resubscribe rate
MRR · LTV (ARPU / monthly churn)
Fixes, ranked by $ at stake:
1. [stage] — [fix] — [effort] — [expected effect]
2. …
This week: the single highest-leverage change.
Done when all five stages carry a value or "unmeasured", every gap below benchmark has a ranked fix with a revenue estimate, and the audit names what the RevenueCat Connector would add when it was absent.
Related Skills
paywalls— design of the trial-end and cancel-flow paywalls.pricing— plan structure, annual discount, lower tiers.churn-prevention— engagement strategy behind voluntary churn.onboarding— activation before the trial ends.rating-prompt-strategy— a renewing subscriber is a strong prompt moment.
What it discloses
The Skill reads these files only when it needs them, so the model spends nothing on them the rest of the time.
references/benchmarks.md
references/stage-playbooks.md
Someone is asking for what you built today.
On Reddit, on X, in ChatGPT's answers. Kwern finds them every morning and drafts the reply in your voice; you decide what goes out.