paywalls

Usage limit paywalls should clearly show the limit reached, demonstrate what upgrading provides, and avoid blocking the user abruptly. Include a benefit-focused headline, a free-vs-paid comparison, social proof, a specific CTA, and an escape hatch like deleting an item to stay on the free plan.

Show upgrade prompts after users experience an aha moment, when they attempt a paid feature, or when they hit genuine usage limits. Avoid showing them during onboarding or mid-flow, and apply frequency caps with cool-down periods of days after dismissal.

Trial expiration screens convert better when they show what the user accomplished during the trial, highlight features they actually used, and frame what they will lose. Add early warnings at 7, 3, and 1 days, clear plan options, and social proof from similar users.

Avoid hiding the close button, confusing plan selection, guilt-trip copy, and blocking critical flows. These dark patterns may produce short-term conversions but damage trust and increase churn after upgrade.

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

Track paywall impression rate, click-through to upgrade, checkout completion rate, revenue per user, and post-upgrade churn. Test variables include trigger timing, headlines, price presentation, trial length, and feature emphasis.