Home / Writing

Monetisation

Paywall Checklist for Subscription Apps: 12 Things to Fix Before You Blame the Price

By William Souef · 2026-10-13 · 7 min read

When a subscription app doesn't make money, the first instinct is to change the price. In the apps I've built and audited, price is rarely the first problem. It's usually when the paywall shows up, what the user has experienced before it, and what the screen actually says. Here's the checklist I run through.

Before the paywall

1. Has the user felt the value?

The strongest paywall is the one that appears right after the product has solved something. In Rockie, onboarding shows the AI breaking down a real household task before any purchase screen. The paywall then sells something the user has already seen work.

2. Is the paywall tied to a pain, not a feature list?

"Unlimited projects, themes and sync" is a list. "Stop staring at your to-do list" is a reason. Rewriting a paywall around the user's pain points is one of the cheapest changes you can test.

3. Is the timing deliberate?

Showing the paywall on first launch, after onboarding, or at a premium feature are three different strategies. Pick one on purpose, measure it, and only then try another.

On the paywall

4. Can someone understand it in three seconds?

One headline, a few benefits, the plans, one button. If the screen needs scrolling to find the price, it's doing too much.

5. Is there a clear default plan?

Two or three plans with one visibly recommended option convert better than a row of equal choices. Show the annual plan's monthly equivalent so the comparison is easy.

6. Is the trial explained honestly?

Say how long it lasts, when they'll be charged and how to cancel. Trust is part of the conversion, and it protects your ratings later.

7. Is the price localised?

A price that feels fair in one country can feel steep in another. App Store pricing by territory lets you adjust instead of using automatic conversion everywhere.

8. Can people restore purchases and read the terms?

Restore purchases, terms and privacy links aren't optional: missing them can get an update rejected in review.

After the paywall

9. Does a dismissed paywall leave a good free experience?

Users who close the paywall aren't lost. If the free version still delivers value, many come back later, and they rate the app instead of deleting it.

10. Is entitlement logic tested?

Subscription tools like RevenueCat make purchases easier, but identifiers still need to match exactly between the dashboard and the code. I've seen a display name and an internal identifier differ in a way that made paying users look free.

Measuring it

11. Do you track the full funnel?

Paywall views, trial starts, trial conversions, renewals and refunds, by plan and by entry point. Without the full funnel, you can't tell whether a change helped or just moved the problem.

12. Do you test one thing at a time?

Change the headline, or the timing, or the plans, not all three. Give each test enough time and traffic to mean something.