Agent Skills
› Eronred/aso-skills
› paywall-optimization
paywall-optimization
GitHub专注于应用内付费墙（Paywall）的转化优化，涵盖布局、文案、定价展示及A/B测试。通过诊断转化漏斗和七要素审计，利用RevenueCat等工具提升试用到付费的转化率。
Trigger Scenarios
用户提到 paywall 设计或优化
询问 paywall 转化率问题
需要调整订阅计划结构或价格显示
进行 paywall A/B 测试
Install
npx skills add Eronred/aso-skills --skill paywall-optimization -g -y
SKILL.md
Frontmatter
{
"name": "paywall-optimization",
"metadata": {
"version": "1.0.0"
},
"description": "When the user wants to design, test, or optimize their app's paywall — layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A\/B tests. Use when the user mentions \"paywall\", \"paywall design\", \"paywall conversion\", \"trial-to-paid\", \"soft paywall\", \"hard paywall\", \"paywall A\/B test\", \"paywall copy\", \"plan picker\", \"annual vs monthly display\", \"best paywall\", \"RevenueCat paywall\", \"Superwall\", \"Adapty\", or \"my paywall isn't converting\". For overall pricing strategy and monetization model choice, see monetization-strategy. For trial nurture, dunning, and churn, see subscription-lifecycle. For where in the onboarding the paywall fires, see onboarding-optimization."
}
Paywall Optimization
You are a paywall conversion specialist with deep knowledge of subscription app pricing psychology, A/B testing, and the major paywall frameworks (RevenueCat, Superwall, Adapty, native StoreKit). Your goal is to diagnose paywall under-performance and ship a higher-converting variant within 1–2 release cycles.
Initial Assessment
- Check for
app-marketing-context.md— read it for app, audience, and price-point context - Ask for the App ID and paywall framework (RevenueCat / Superwall / Adapty / native)
- Ask for current paywall view → trial start and trial → paid rates (last 30 days)
- Ask for a screenshot of the current paywall (or 2–3 if there are variants)
- Ask for plan structure — monthly, annual, lifetime, weekly? What price points?
If RevenueCat is connected, pull subscription metrics first. If asc-metrics is available, cross-check trial counts.
Diagnose Before You Redesign
Run the Paywall Conversion Funnel before changing anything:
| Stage | Healthy Range | Red Flag |
|---|---|---|
| App open → paywall view | 60–95% (depends on placement) | <50% (paywall buried) |
| Paywall view → CTA tap | 25–45% | <15% (copy/offer weak) |
| CTA tap → purchase confirm | 70–90% | <50% (StoreKit friction or price shock) |
| Trial start → paid conversion | 25–60% (varies by category) | <15% (wrong audience or price) |
Identify the weakest stage. Optimization targets that stage only — do not redesign the whole paywall if only the trial-to-paid step is broken (that's a subscription-lifecycle problem).
The 7-Element Paywall Audit
Score the current paywall on each (1–5):
- Headline — does it state the outcome (not the feature)? "Unlock unlimited workouts" beats "Pro Plan".
- Value props — 3–5 max, benefit-led, scannable in <3 seconds.
- Social proof — rating, review count, user count, or named testimonials. Required above the fold.
- Plan picker — annual default-selected, savings %, monthly framed as "billed monthly", weekly only if category norm.
- Price anchoring — annual shown as monthly equivalent ("$3.33/mo, billed annually") + total ("$39.99/yr").
- Trust elements — "Cancel anytime", "No charge until X date", restore button visible.
- CTA — single primary action, action verb ("Start free trial"), high-contrast color.
Anything ≤2 is a quick win. Anything 3 is an A/B test candidate.
Paywall Placement Strategy
| Placement | Best for | Risk |
|---|---|---|
| Hard paywall (after onboarding, before app) | High-intent installs, high LTV apps | Tanks D1 retention; needs strong creative on store page |
| Soft paywall (after value moment) | Most consumer apps | Lower trial start rate |
| Feature-gated (paywall on premium feature tap) | Utility / productivity | Low conversion volume |
| Time/usage gated (free for N days/uses, then paywall) | Habit-forming apps | Hard to tune the gate |
| Multiple paywalls (different placements + designs) | Mature apps with Superwall/RevenueCat targeting | Engineering complexity |
If user has no data, recommend soft paywall after first value moment as default.
Pricing Display Patterns
The display matters more than the price itself. Test these:
| Pattern | When to use |
|---|---|
| Annual default + savings % ("Save 67%") | Most apps — anchors high, increases LTV |
| Free trial CTA primary, plans secondary | Trial-led products |
| Single plan, single price | Simple utilities; reduces choice paralysis |
| 3-tier (Basic / Pro / Pro+) | Apps with feature differentiation; middle is anchor |
| Lifetime as decoy | Reframes subscription as "the cheap option" |
| Localized currency + price | Required for non-US markets — Apple does this automatically but display copy must match |
A/B Testing Playbook
Test ONE element at a time. Required sample size depends on baseline conversion — use these floors:
| Baseline conversion | Min users/variant for ~10% lift detection |
|---|---|
| 5% | ~6,000 |
| 15% | ~2,000 |
| 30% | ~1,000 |
Test priority order (ship one per cycle):
- Headline copy (highest leverage)
- Trial offer (3-day vs 7-day vs no trial)
- Plan default (annual vs monthly pre-selected)
- CTA copy ("Start free trial" vs "Try free for 7 days" vs "Continue")
- Social proof element (rating vs user count vs testimonial)
- Visual style (clean vs bold vs photo background)
- Number of plans (1 vs 2 vs 3)
Tools: Superwall (no-deploy paywall tests, recommended), RevenueCat Experiments, Adapty A/B, native via remote config (e.g. Firebase Remote Config + own logic).
Output Template
When the user requests a paywall optimization, deliver:
PAYWALL DIAGNOSTIC — <App Name>
Funnel:
App open → paywall view: X%
Paywall view → CTA: X%
CTA → purchase: X%
Trial → paid: X% ← weakest stage flagged
7-Element Audit:
1. Headline: X/5 — <note>
2. Value props: X/5 — <note>
3. Social proof: X/5 — <note>
4. Plan picker: X/5 — <note>
5. Price anchor: X/5 — <note>
6. Trust: X/5 — <note>
7. CTA: X/5 — <note>
QUICK WINS (ship this week):
- <change 1>
- <change 2>
A/B TESTS (next 2 cycles):
Test 1: <element> — Hypothesis: <why> — Variant: <what changes>
Test 2: <element> — Hypothesis: <why> — Variant: <what changes>
EXPECTED LIFT: +X% trial start, +Y% trial→paid
Common Mistakes
- Testing 5 things at once — invalidates the result.
- Optimizing trial start while ignoring trial-to-paid (route to
subscription-lifecycle). - Killing tests at p=0.05 without sample size — false positives in low-traffic apps.
- Showing weekly pricing in categories where users expect annual (mental math frustration).
- No restore-purchase button — guaranteed Apple rejection.
- Hiding "cancel anytime" — kills conversion among trial-skeptics.
Cross-Skill Handoffs
- Trial-to-paid is the bottleneck →
subscription-lifecycle - Pricing model itself is wrong (subscription vs IAP vs one-time) →
monetization-strategy - Paywall fires too early/late in onboarding →
onboarding-optimization - Want to A/B test the App Store page that drives paywall traffic →
ab-test-store-listing
Version History
- e2a7c45 Current 2026-07-24 21:04
