paywalls

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

Show prompts at feature gates, usage limits, trial expiration, or after an aha moment. Avoid showing them during onboarding or mid-flow, cap frequency per session, and enforce a cool-down period of days after dismissal.

Use loss framing by summarizing what the user accomplished and what they will lose, highlight features they actually used, present clear plan options, and add social proof. Send early warnings at 7, 3, and 1 day before expiration.

Avoid dark patterns like hidden close buttons, confusing plan selection, and guilt-trip copy. Also avoid conversion killers such as asking before value is delivered, prompting too frequently, blocking critical flows, and complicated upgrade processes.

No. It focuses on in-product upgrade moments for users who have already experienced value. Public pricing page optimization is deferred to the cro skill, and pricing model decisions to the pricing skill.

Start with trigger timing, headline and CTA copy variations, and monthly versus annual price presentation. The references/experiments.md file catalogs additional tests across design, trials, personalization, and frequency capping.