Catalog
coreyhaines31/paywall-upgrade-cro

coreyhaines31

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 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.

global
version:1.1.0
0installs0uses~1.4k
v1.1Saved Apr 20, 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-context.md exists (or .claude/product-marketing-context.md 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


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?

  • 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
Files3
3 files · 12.6 KB

Select a file to preview

Overall Score

87/100

Grade

A

Excellent

Safety

95

Quality

85

Clarity

88

Completeness

82

Summary

This skill guides AI agents in optimizing in-app paywalls, upgrade screens, and upsell modals for converting free users to paid. It provides frameworks for identifying trigger points (feature gates, usage limits, trial expiration), designing paywall components, timing strategies, and avoiding dark patterns. The skill emphasizes delivering user value before requesting upgrade commitment.

Detected Capabilities

Paywall design framework (headline, value demo, comparison, social proof, CTA, escape hatch)Trigger point identification (feature gates, usage limits, trial expiration, time-based)Copy and messaging optimization for upgrade promptsA/B testing guidance with experiment ideasAnti-pattern detection and avoidanceTiming and frequency rules for paywall presentationTrial-to-paid conversion strategiesPlan comparison and pricing presentation strategies

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

paywall designupgrade screen optimizationtrial to paid conversionfeature gate strategyfreemium conversionin-app upsellusage limit prompttrial expiration screen

Risk Signals

INFO

No hardcoded secrets, no shell execution, no file system writes, no external data transmission

SKILL.md and supporting files
INFO

Skill references product-marketing-context.md with fallback to .claude/ path for older setups. This is expected context-aware behavior.

SKILL.md, 'Initial Assessment' section
INFO

No destructive or privileged operations detected

All files

Use Cases

  • Design an in-app paywall triggered when free users hit a usage limit
  • Optimize trial expiration screens to improve conversion rates
  • Create feature gate paywalls for locked capabilities
  • Plan A/B tests for paywall timing, copy, and pricing presentation
  • Audit existing paywalls for dark patterns and anti-patterns

Quality Notes

  • Strong structural organization with clear sections (Core Principles, Paywall Trigger Points, Components, Specific Types, etc.)
  • Well-defined paywall types with concrete examples (Feature Lock, Usage Limit, Trial Expiration paywalls include ASCII mockups)
  • Comprehensive anti-patterns section explicitly warns against dark patterns and conversion killers with clear reasoning
  • Task-specific questions at the end help agents gather required context before recommendations
  • Supporting experiments.md file provides actionable A/B test ideas across 7 categories with specific variations to test
  • Evals.json includes 6 realistic test cases covering edge cases: casual phrasing, deferral to other skills (page-cro), and low conversion diagnosis
  • Clear skill boundaries established: explicitly distinguishes from page-cro (public pricing) and pricing-strategy (pricing decisions)
  • Value-first principle is consistently reinforced throughout, reflecting best practices in ethical monetization
  • Timing and frequency rules address user fatigue and trust preservation, not just conversion maximization
  • Copy examples provided are template-like but not prescriptive, allowing flexibility for specific products
Model: claude-haiku-4-5-20251001Analyzed: Apr 20, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

v1.1

Content updated

2026-04-20

Latest
v1.0

No changelog

2026-04-19

Add coreyhaines31/paywall-upgrade-cro to your library

Command Palette

Search for a command to run...