Paywall and Upgrade Screen CRO

VerifiedSafe

Specializes in designing and optimizing in-app paywalls and upgrade screens to convert free users to paid subscribers or upgrade existing users. Provides actionable guidance on timing, messaging, screen components for feature gates, usage limits, trial expirations, and time-based prompts. Best used to improve freemium conversion rates or upgrade screen performance.

Sby Skills Guide Bot
ProductivityIntermediate
6/2/2026
Claude Code
#paywall#upgrade-cro#conversion-rate-optimization#freemium#in-app-pricing

Recommended for

Automated summary

This skill helps design and optimize in-app paywalls and upgrade flows to convert free users into paying subscribers or upgrade existing users.

Strengths

  • Provides concrete templates for different paywall types (feature lock, usage limit, trial expiration)
  • Emphasizes timing after users have experienced value
  • Includes respect for user choice and friction minimization

Limitations

  • Does not cover A/B testing or conversion data analysis
  • Assumes an existing freemium or trial model
  • May need adjustments for specific industries or app types
When to use it

Use this skill when designing or refining in-app paywalls, upgrade prompts, or trial expiration screens.

When not to use it

Do not use it for public pricing pages or external marketing campaigns, as it focuses on in-app purchase moments.

Security analysis

Safe
Quality score92/100

The skill provides advice on UI/UX design for in-app paywalls and does not involve any system-level operations, data exfiltration, or destructive actions.

No concerns found

How this analysis is made

Examples

Feature lock paywall
I need to create a paywall for a premium feature in my app. When free users tap on 'advanced analytics', show a screen explaining the benefit and offering an upgrade. Help me write the copy and structure.
Trial expiration screen
My SaaS app has a 14-day free trial ending soon. I want to show a screen that summarizes what the user accomplished and encourages them to continue with a paid plan. Give me a template and wording suggestions.
Usage limit upgrade prompt
Users hit a limit of 3 projects in my free tier. I want a polite but persuasive upgrade prompt that doesn't block them entirely. What should the screen look like?

name: paywall-upgrade-cro description: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see page-cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing-strategy. metadata: version: 1.1.0

Paywall and Upgrade Screen CRO

You are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment.

Initial Assessment

Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before providing recommendations, understand:

  1. Upgrade Context - Freemium → Paid? Trial → Paid? Tier upgrade? Feature upsell? Usage limit?

  2. Product Model - What's free? What's behind paywall? What triggers prompts? Current conversion rate?

  3. User Journey - When does this appear? What have they experienced? What are they trying to do?


Core Principles

1. Value Before Ask

  • User should have experienced real value first
  • Upgrade should feel like natural next step
  • Timing: After "aha moment," not before

2. Show, Don't Just Tell

  • Demonstrate the value of paid features
  • Preview what they're missing
  • Make the upgrade feel tangible

3. Friction-Free Path

  • Easy to upgrade when ready
  • Don't make them hunt for pricing

4. Respect the No

  • Don't trap or pressure
  • Make it easy to continue free
  • Maintain trust for future conversion

Paywall Trigger Points

Feature Gates

When user clicks a paid-only feature:

  • Clear explanation of why it's paid
  • Show what the feature does
  • Quick path to unlock
  • Option to continue without

Usage Limits

When user hits a limit:

  • Clear indication of limit reached
  • Show what upgrading provides
  • Don't block abruptly

Trial Expiration

When trial is ending:

  • Early warnings (7, 3, 1 day)
  • Clear "what happens" on expiration
  • Summarize value received

Time-Based Prompts

After X days of free use:

  • Gentle upgrade reminder
  • Highlight unused paid features
  • Easy to dismiss

Paywall Screen Components

  1. Headline - Focus on what they get: "Unlock [Feature] to [Benefit]"

  2. Value Demonstration - Preview, before/after, "With Pro you could..."

  3. Feature Comparison - Highlight key differences, current plan marked

  4. Pricing - Clear, simple, annual vs. monthly options

  5. Social Proof - Customer quotes, "X teams use this"

  6. CTA - Specific and value-oriented: "Start Getting [Benefit]"

  7. Escape Hatch - Clear "Not now" or "Continue with Free"


Specific Paywall Types

Feature Lock Paywall

[Lock Icon]
This feature is available on Pro

[Feature preview/screenshot]

[Feature name] helps you [benefit]:
• [Capability]
• [Capability]

[Upgrade to Pro - $X/mo]
[Maybe Later]

Usage Limit Paywall

You've reached your free limit

[Progress bar at 100%]

Free: 3 projects | Pro: Unlimited

[Upgrade to Pro]  [Delete a project]

Trial Expiration Paywall

Your trial ends in 3 days

What you'll lose:
• [Feature used]
• [Data created]

What you've accomplished:
• Created X projects

[Continue with Pro]
[Remind me later]  [Downgrade]

Timing and Frequency

When to Show

  • After value moment, before frustration
  • After activation/aha moment
  • When hitting genuine limits

When NOT to Show

  • During onboarding (too early)
  • When they're in a flow
  • Repeatedly after dismissal

Frequency Rules

  • Limit per session
  • Cool-down after dismiss (days, not hours)
  • Track annoyance signals

Upgrade Flow Optimization

From Paywall to Payment

  • Minimize steps
  • Keep in-context if possible
  • Pre-fill known information

Post-Upgrade

  • Immediate access to features
  • Confirmation and receipt
  • Guide to new features

A/B Testing

What to Test

  • Trigger timing
  • Headline/copy variations
  • Price presentation
  • Trial length
  • Feature emphasis
  • Design/layout

Metrics to Track

  • Paywall impression rate
  • Click-through to upgrade
  • Completion rate
  • Revenue per user
  • Churn rate post-upgrade

For comprehensive experiment ideas: See references/experiments.md


Anti-Patterns to Avoid

Dark Patterns

  • Hiding the close button
  • Confusing plan selection
  • Guilt-trip copy

Conversion Killers

  • Asking before value delivered
  • Too frequent prompts
  • Blocking critical flows
  • Complicated upgrade process

Task-Specific Questions

  1. What's your current free → paid conversion rate?
  2. What triggers upgrade prompts today?
  3. What features are behind the paywall?
  4. What's your "aha moment" for users?
  5. What pricing model? (per seat, usage, flat)
  6. Mobile app, web app, or both?

Related Skills

  • churn-prevention: For cancel flows, save offers, and reducing churn post-upgrade
  • page-cro: For public pricing page optimization
  • onboarding-cro: For driving to aha moment before upgrade
  • ab-test-setup: For testing paywall variations

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/paywall-and-upgrade-screen-cro-mmlj2nsd/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/paywall-and-upgrade-screen-cro-mmlj2nsd' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/paywall-and-upgrade-screen-cro-mmlj2nsd/download' --output '.skill-downloads/paywall-and-upgrade-screen-cro-mmlj2nsd/SKILL.md.part' && mv '.skill-downloads/paywall-and-upgrade-screen-cro-mmlj2nsd/SKILL.md.part' '.skill-downloads/paywall-and-upgrade-screen-cro-mmlj2nsd/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/paywall-and-upgrade-screen-cro-mmlj2nsd/SKILL.md' && test -s '.skill-downloads/paywall-and-upgrade-screen-cro-mmlj2nsd/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/paywall-upgrade-cro' && cp -R '.skill-downloads/paywall-and-upgrade-screen-cro-mmlj2nsd' '.claude/skills/paywall-upgrade-cro'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/paywall-and-upgrade-screen-cro-mmlj2nsd'

openskills read 'paywall-and-upgrade-screen-cro-mmlj2nsd'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/paywall-and-upgrade-screen-cro-mmlj2nsd/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills