paywall-upgrade-cro

Designs and optimizes in-app paywalls, upgrade screens, and feature gates for freemium conversion.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/yo16/cc_dev_team --skill paywall-upgrade-cro-yo16
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paywall-upgrade-cro
Source: https://github.com/yo16/cc_dev_team/tree/main/specific_set/seo/skills/paywall-upgrade-cro
Command: npx skills add https://github.com/yo16/cc_dev_team --skill paywall-upgrade-cro-yo16

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Free users often never convert to paid plans because in-app paywalls and upgrade prompts are poorly timed, generic, or pushy. This Skill provides structured guidance for designing upgrade screens, feature gates, usage-limit prompts, and trial expiration flows that convert without damaging user trust. ## Core Features & Use Cases - Paywall Design Frameworks: Provides component-level guidance (headline, value demonstration, plan comparison, social proof, CTA, escape hatch) for feature locks, usage limits, and trial expiration screens. - Trigger Timing & Frequency Rules: Defines when to show upgrade prompts (after value moments, at genuine limits) and how to cap frequency to avoid annoying users. - A/B Testing Playbook: Ships a references/experiments.md catalog of experiments covering triggers, pricing presentation, copy, trials, personalization, and dismiss behavior. - Use Case: When a free user hits the 3-project limit in your project management tool, use this Skill to design the upgrade screen with benefit-focused copy, a free-vs-pro comparison, and a respectful escape hatch. ## Quick Start Ask the assistant to design an upgrade paywall for your product's usage limit or feature gate, describing your free tier, paid features, and current conversion rate.

Frequently Asked Questions about paywall-upgrade-cro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design an in-app paywall that converts free users to paid?▼

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

When should I show upgrade prompts to free users?▼

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

How do I improve a low-converting trial expiration screen?▼

Apply loss framing by showing what the user built and which features they used during the trial, then 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.

What paywall anti-patterns should I avoid?▼

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, blocking critical flows, overly frequent prompts, and complicated upgrade processes.

What paywall elements should I A/B test first?▼

Start with trigger timing, headline copy, price presentation (monthly vs. annual framing), and CTA wording. The references/experiments.md file catalogs additional tests across layout, discounts, trial structure, personalization, and frequency capping.

Does this Skill cover public pricing page optimization?▼

No, it focuses on in-product upgrade moments where users have already experienced value. For public-facing pricing pages, use the page-cro skill; for pricing model decisions, use pricing-strategy.