paywalls

Show a clear indication that the limit was reached, demonstrate what upgrading unlocks, and include a plan comparison with a specific value-oriented CTA. Always provide an escape hatch like "Maybe later" so users can continue on the free plan without feeling trapped.

Show prompts after users experience real value, such as after an aha moment, when they attempt a paid feature, or when they hit a genuine usage limit. Avoid prompting during onboarding, mid-flow, or repeatedly after dismissal.

Summarize what the user accomplished during the trial, highlight the specific features and data they would lose, and present clear plan options with social proof. Send early warnings at 7, 3, and 1 day before expiration rather than a single generic expired message.

Common mistakes include asking before value is delivered, hiding the close button, blocking critical flows, prompting too frequently, and using guilt-trip copy. Good paywalls feel helpful and respect the user's decision to decline.

No, this skill focuses on in-app upgrade moments where users have already experienced product value. Public-facing pricing page optimization is handled by a separate CRO skill, and pricing strategy decisions belong to a pricing skill.

You can test trigger timing, headline and CTA copy, price display formats, plan comparison layouts, trial lengths, discount offers, and frequency capping rules. The references file catalogs experiments across triggers, design, pricing, copy, trials, and personalization.