paywalls

Structure the paywall with a benefit-focused headline, a value demonstration or preview, a plan comparison marking the current plan, social proof, a specific CTA, and a clear escape hatch. Show it only after the user has experienced real value, not before.

Show prompts at feature gates when users click paid features, at usage limits when thresholds are reached, near trial expiration, and after aha moments. Avoid showing them during onboarding, mid-flow, or repeatedly after dismissal.

Show what the user accomplished during the trial, highlight features they actually used, and frame what they will lose rather than what they gain. Add clear plan options, social proof from similar users, and early warnings at 7, 3, and 1 day before expiration.

Avoid hiding the close button, confusing plan selection, guilt-trip copy, blocking critical flows, and asking before value is delivered. Good paywalls include an obvious escape hatch like "Not now" and respect dismissal with cool-down periods of days, not hours.

Track paywall impression rate, click-through to upgrade, checkout completion rate, revenue per user, and post-upgrade churn. Use these to evaluate A/B tests on trigger timing, headlines, price presentation, and trial length.

No, it focuses on in-product upgrade moments where users have already experienced value. Public pricing page optimization is handled by the separate cro skill, and pricing model decisions belong to the pricing skill.