paywall-auditlisted
Install: claude install-skill ua5er/user-acquisition-skills
# Paywall audit
Adapted from `paywalls` in coreyhaines31/marketingskills (MIT, copyright Corey Haines) and `paywall-optimization` in appeeky/aso-skills (MIT, copyright Erencan). Their licence texts are reproduced in THIRD_PARTY_NOTICES.md. What is kept: the idea of scoring a paywall element by element and the principle of showing value before the ask. What is changed: the method below is rebuilt around evidence from the user's own funnel, a price-display and disclosure check, a stack of decision rules and a test queue. No benchmark tables from the source skills are carried over.
## When to use
- Trial start or paid conversion is below the business target.
- A redesign is planned and nobody knows what to keep.
- A web checkout or first-month offer is being added to an app funnel.
- Before an A/B test, to choose what to test first.
## Inputs
1. Screenshots or a prototype of every paywall state: first view, plan selected, checkout sheet, restore and error states.
2. Plan structure, prices, trial rules, renewal terms, regions.
3. Funnel numbers from the user's own data: paywall views, plan selections, checkout starts, trial starts, paid conversions, refunds. Last 30 days or the available window.
4. Where the paywall sits: after onboarding, after a value moment, on a feature gate.
5. What the traffic source promised (the ad or store page that brought the user).
## Method
### Step 1. Find the weakest funnel step
Compute step conversion from the user's own numbers and rank s