Catalog
coreyhaines31/paywalls

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," "mobile app paywall," "subscription app paywall," or "App Store subscription pricing." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

NewUpdated Oct 28, 2026

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 .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), 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

For consumer iOS/Android subscription apps (paywall inside onboarding, yearly-first plans, trials and reminders, store fees, web checkout, revenue per download): See references/mobile-subscription-paywalls.md


Anti-Patterns to Avoid

Dark Patterns

  • Hiding the close button
  • Confusing plan selection
  • Guilt-trip copy
  • Fake countdowns or "limited" offers with no real deadline

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?

  • churn-prevention: For cancel flows, save offers, and reducing churn post-upgrade
  • cro: For public pricing page optimization
  • onboarding: For driving to aha moment before upgrade
  • ab-testing: For testing paywall variations
Files4
4 files · 19.9 KB

Select a file to preview

Overall Score

87/100

Grade

A

Excellent

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

95

Quality

88

Clarity

85

Completeness

82

Summary

This skill provides expert guidance for designing in-app paywalls and upgrade screens that convert free users to paid or upgrade existing users to higher tiers. It covers trigger points (feature gates, usage limits, trial expiration), paywall screen components, timing and frequency rules, anti-patterns to avoid, and specific paywall types. Supporting references cover A/B testing experiments and mobile subscription app mechanics.

Detected Capabilities

file read (product-marketing.md context lookup)documentation review (evals.json validation)structured paywall design guidanceA/B testing framework and experiment suggestionsmarket and unit-economics calculation

Trigger Keywords

Phrases that agents use to match this skill to user intent.

design paywallupgrade screen conversionin-app pricingtrial to paidfeature gate messagingusage limit promptmobile subscription paywallreduce churn with paywall

Use Cases

  • Design a usage-limit paywall that appears when a free user hits a project creation cap
  • Improve trial-expiration messaging and conversion rate from 2% to double digits
  • Choose optimal timing for upgrade prompts without creating user fatigue
  • Create a feature-gate paywall for a premium analytics dashboard feature
  • Design a mobile app paywall for a freemium or hard-paywall consumer subscription
  • A/B test paywall variations including trigger timing, messaging, pricing presentation, and trial structure
  • Avoid dark patterns and respect-the-no principles while maintaining conversion goals

Quality Notes

  • Well-structured with clear sections for trigger points, paywall types, components, and anti-patterns
  • Comprehensive evals.json with 7 test cases covering the full scope of the skill
  • Supporting references (experiments.md, mobile-subscription-paywalls.md) are specific and actionable
  • Explicit anti-pattern warnings help prevent dark patterns and unethical UX choices
  • Good cross-referencing to related skills (churn-prevention, cro, onboarding, ab-testing)
  • Tone is consultative (asks clarifying questions) rather than prescriptive
  • Task-specific questions at the end guide conversation structure
  • Mobile subscription reference is detailed and includes current fees and unit economics with dates
  • Evaluations include specific copy recommendations and diagnosis of conversion issues
  • Instructions explicitly check for product-marketing.md context before providing recommendations
  • No file write, network, or shell operations — pure guidance skill
  • Some file path references (references/experiments.md, references/mobile-subscription-paywalls.md) could be more standardized in frontmatter, but content is clearly present
Model: claude-haiku-4-5-20251001Analyzed: Oct 28, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v2.1

    Content updated

    ✦ AIAdds guidance to avoid fake countdowns and false urgency tactics in paywall copy.

    2026-10-28

    LATEST
  2. v2.0

    Contract changed: description

    ✦ AIExtends description to activate on mobile app paywalls; adds dedicated reference guide for iOS/Android subscription monetization.

    triggering2026-10-27

    View This Version
  3. v1.0

    2026-05-15

    View This VersionInitial version

Use coreyhaines31/paywalls in your dev environment

Command Palette

Search for a command to run...