# Paywall Optimization

When the user wants to design, test, or optimize their app's paywall, layout, copy...

- Repository: https://github.com/appeeky/aso-skills (2243 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-06
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add appeeky/aso-skills --skill paywall-optimization -g -a claude-code -y`
Codex: `npx skills add appeeky/aso-skills --skill paywall-optimization -g -a codex -y`
Cursor: `npx skills add appeeky/aso-skills --skill paywall-optimization -g -a cursor -y`
Gemini CLI: `npx skills add appeeky/aso-skills --skill paywall-optimization -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add appeeky/aso-skills`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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):

The rest: https://github.com/appeeky/aso-skills/blob/HEAD/skills/paywall-optimization/SKILL.md