Skip to main content
ClaudeWave
Skill1.5k estrellas del repoactualizado 1mo ago

paywall-optimization

The paywall-optimization skill helps developers diagnose and improve subscription conversion rates by auditing layout, copy, pricing display, and plan structure. Use this when your paywall view-to-trial or trial-to-paid conversion rates underperform, when designing paywall variants for A/B testing, or when implementing RevenueCat, Superwall, Adapty, or native StoreKit paywalls. The skill runs a conversion funnel analysis and seven-element audit to identify which stage is broken before recommending targeted redesigns.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/Eronred/aso-skills /tmp/paywall-optimization && cp -r /tmp/paywall-optimization/skills/paywall-optimization ~/.claude/skills/paywall-optimization
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# 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

1. Check for `app-marketing-context.md` — read it for app, audience, and price-point context
2. Ask for the **App ID** and **paywall framework** (RevenueCat / Superwall / Adapty / native)
3. Ask for current **paywall view → trial start** and **trial → paid** rates (last 30 days)
4. Ask for a **screenshot of the current paywall** (or 2–3 if there are variants)
5. 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):

1. **Headline** — does it state the outcome (not the feature)? "Unlock unlimited workouts" beats "Pro Plan".
2. **Value props** — 3–5 max, benefit-led, scannable in <3 seconds.
3. **Social proof** — rating, review count, user count, or named testimonials. Required above the fold.
4. **Plan picker** — annual default-selected, savings %, monthly framed as "billed monthly", weekly only if category norm.
5. **Price anchoring** — annual shown as monthly equivalent ("$3.33/mo, billed annually") + total ("$39.99/yr").
6. **Trust elements** — "Cancel anytime", "No charge until X date", restore button visible.
7. **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):

1. Headline copy (highest leverage)
2. Trial offer (3-day vs 7-day vs no trial)
3. Plan default (annual vs monthly pre-selected)
4. CTA copy ("Start free trial" vs "Try free for 7 days" vs "Continue")
5. Social proof element (rating vs user count vs testimonial)
6. Visual style (clean vs bold vs photo background)
7. 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 wr
ab-test-store-listingSkill

When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.

android-asoSkill

When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.

app-analyticsSkill

When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.

app-clipsSkill

When the user wants to implement, optimize, or use App Clips for app discovery and conversion. Use when the user mentions "App Clip", "app clip code", "mini app", "instant app", "App Clip card", "App Clip link", "no download required", "instant experience", or wants to understand how App Clips appear in App Store search. For general App Store discoverability, see aso-audit. For marketing campaigns, see ua-campaign.

app-icon-optimizationSkill

When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.

app-launchSkill

When the user wants to plan a launch strategy for a new app or major update. Also use when the user mentions "app launch", "launch plan", "launch checklist", "pre-launch", "launch day", or "how to launch my app". For ongoing ASO after launch, see aso-audit. For paid acquisition during launch, see ua-campaign.

app-marketing-contextSkill

When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.

app-preview-videoSkill

When the user wants to plan, script, produce, or optimize App Store Preview videos or Google Play promo videos — the autoplay videos that show in App Store/Play Store search and product pages. Use when the user mentions "App Preview", "preview video", "app store video", "promo video", "Play Store video", "video poster frame", "YouTube promo for Play Store", "30 second app video", "video script", "video specs", or "should I add a preview video". For static screenshots, see screenshot-optimization. For A/B testing the video, see ab-test-store-listing. For broader creative briefs, see screenshot-optimization (covers stills).