Skip to content
Development
Skill

/paywall-upgrade-cro

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

From plugin
claude-code-templates
31k200 skills200 agents200 commands32 MCP
Install
$ npx -y skills add davila7/claude-code-templates --skill paywall-upgrade-cro --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/paywall-upgrade-cro

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

paywall-upgrade-cro.SKILL.md
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," or "in-app pricing." Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value.

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

Before providing recommendations, understand:

1. **Upgrade Context**

  • Freemium → Paid conversion
  • Trial → Paid conversion
  • Tier upgrade (Basic → Pro)
  • Feature-specific upsell
  • Usage limit upsell

2. **Product Model**

  • What's free forever?
  • What's behind the paywall?
  • What triggers upgrade prompts?
  • What's the current conversion rate?

3. **User Journey**

  • At what point does this appear?
  • What have they experienced already?
  • What are they trying to do when blocked?

---

Core Principles

1. Value Before Ask

  • User should have experienced real value first
  • The upgrade should feel like a 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
  • Remove barriers to conversion

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 what limit was reached
  • Show what upgrading provides
  • Option to buy more without full upgrade
  • Don't block abruptly

Trial Expiration

When trial is ending:

  • Early warnings (7 days, 3 days, 1 day)
  • Clear "what happens" on expiration
  • Easy re-activation if expired
  • Summarize value received

Time-Based Prompts

After X days/sessions of free use:

  • Gentle upgrade reminder
  • Highlight unused paid features
  • Not intrusive—banner or subtle modal
  • Easy to dismiss

Context-Triggered

When behavior indicates upgrade fit:

  • Power users who'd benefit
  • Teams using solo features
  • Heavy usage approaching limits
  • Inviting teammates

---

Paywall Screen Components

1. Headline

Focus on what they get, not what they pay:

  • "Unlock [Feature] to [Benefit]"
  • "Get more [value] with [Plan]"
  • Not: "Upgrade to Pro for $X/month"

2. Value Demonstration

Show what they're missing:

  • Preview of the feature in action
  • Before/after comparison
  • "With Pro, you could..." examples
  • Specific to their use case if possible

3. Feature Comparison

If showing tiers:

  • Highlight key differences
  • Current plan clearly marked
  • Recommended plan emphasized
  • Focus on outcomes, not feature lists

4. Pricing

  • Clear, simple pricing
  • Annual vs. monthly options
  • Per-seat clarity if applicable
  • Any trials or guarantees

5. Social Proof (Optional)

  • Customer quotes about the upgrade
  • "X teams use this feature"
  • Success metrics from upgraded users

6. CTA

  • Specific: "Upgrade to Pro" not "Upgrade"
  • Value-oriented: "Start Getting [Benefit]"
  • If trial: "Start Free Trial"

7. Escape Hatch

  • Clear "Not now" or "Continue with Free"
  • Don't make them feel bad
  • "Maybe later" vs. "No, I'll stay limited"

---

Specific Paywall Types

Feature Lock Paywall

When clicking a paid feature:

[Lock Icon]
This feature is available on Pro

[Feature preview/screenshot]

[Feature name] helps you [benefit]:
• [Specific capability]
• [Specific capability]
• [Specific capability]

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

Usage Limit Paywall

When hitting a limit:

You've reached your free limit

[Visual: Progress bar at 100%]

Free plan: 3 projects
Pro plan: Unlimited projects

You're active! Upgrade to keep building.

[Upgrade to Pro]    [Delete a project]

Trial Expiration Paywall

When trial is ending:

Your trial ends in 3 days

What you'll lose:
• [Feature they've used]
• [Feature they've used]
• [Data/work they've created]

What you've accomplished:
• Created X projects
• [Specific value metric]

[Continue with Pro - $X/mo]
[Remind me later]    [Downgrade to Free]

Soft Upgrade Prompt

Non-blocking suggestion:

[Banner or subtle modal]

You've been using [Product] for 2 weeks!
Teams like yours get X% more [value] with Pro.

[See Pro Features]    [Dismiss]

Team/Seat Upgrade

When adding users:

Invite your team

Your plan: Solo (1 user)
Team plans start at $X/user

• Shared projects
• Collaboration features
• Admin controls

[Upgrade to Team]    [Continue Solo]

---

Mobile Paywall Patterns

iOS/Android Conventions

  • System-like styling builds trust
  • Standard paywall patterns users recognize
  • Free trial emphasis common
  • Subscription terminology they expect

Mobile-Specific UX

  • Full-screen often acceptable
  • Swipe to dismiss
  • Large tap targets
  • Plan selection with clear visual state

App Store Considerations

  • Clear pricing display
  • Subscription terms visible
  • Restore purchases option
  • Meet review guidelines

---

Timing and Frequency

When to Show

  • **Best**: After value moment, before frustration
  • After activation/aha moment
  • When hitting genuine limits
  • When using adjacent-to-paid features

When NOT to Show

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

-

Read more
Ships withclaude-code-templates

Ready-to-use configurations for Anthropic's Claude Code. A comprehensive collection of AI agents, custom commands, settings, hooks, external integrations (MCPs), and project templates to enhance your development workflow.

Get the whole plugin

Other skills on claude-code-templates.