paywall-upgrade-cro
b1rdmania/ghostclaw/.claude/skills/paywall-upgrade-cro/SKILL.md
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.
What's in it
- Paywall and Upgrade Screen CRO
- Initial Assessment
- Core Principles
- 1. Value Before Ask
- 2. Show, Don't Just Tell
- 3. Friction-Free Path
- 4. Respect the No
- Paywall Trigger Points
- Feature Gates
- Usage Limits
- Trial Expiration
- Time-Based Prompts
- Paywall Screen Components
- Specific Paywall Types
- Feature Lock Paywall
- Usage Limit Paywall
- Trial Expiration Paywall
- Timing and Frequency
- When to Show
- When NOT to Show
- Frequency Rules
- Upgrade Flow Optimization
- From Paywall to Payment
- Post-Upgrade
- A/B Testing
- What to Test
- Metrics to Track
- Anti-Patterns to Avoid
- Dark Patterns
- Conversion Killers
--- 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 `.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](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
More agent context in b1rdmania/ghostclaw
55 other files this repository gives its agents.
Skill
- ab-test-setup.claude/skills/ab-test-setup/SKILL.md
- ad-creative.claude/skills/ad-creative/SKILL.md
- add-discord.claude/skills/add-discord/SKILL.md
- add-gmail-agent.claude/skills/add-gmail-agent/SKILL.md
- add-heartbeat.claude/skills/add-heartbeat/SKILL.md
- add-morning-briefing.claude/skills/add-morning-briefing/SKILL.md
- add-slack.claude/skills/add-slack/SKILL.md
- add-telegram.claude/skills/add-telegram/SKILL.md
- add-telegram-swarm.claude/skills/add-telegram-swarm/SKILL.md
- add-update-check.claude/skills/add-update-check/SKILL.md
- add-voice-reply.claude/skills/add-voice-reply/SKILL.md
- add-voice-transcription.claude/skills/add-voice-transcription/SKILL.md
- ai-seo.claude/skills/ai-seo/SKILL.md
- analytics-tracking.claude/skills/analytics-tracking/SKILL.md
- churn-prevention.claude/skills/churn-prevention/SKILL.md
- cold-email.claude/skills/cold-email/SKILL.md
- competitor-alternatives.claude/skills/competitor-alternatives/SKILL.md
- content-strategy.claude/skills/content-strategy/SKILL.md
- copy-editing.claude/skills/copy-editing/SKILL.md
- copywriting.claude/skills/copywriting/SKILL.md
- customize.claude/skills/customize/SKILL.md
- debug.claude/skills/debug/SKILL.md
- design.claude/skills/design/SKILL.md
- domain-check.claude/skills/domain-check/skill.md
- email-sequence.claude/skills/email-sequence/SKILL.md
- form-cro.claude/skills/form-cro/SKILL.md
- free-tool-strategy.claude/skills/free-tool-strategy/SKILL.md
- get-qodo-rules.claude/skills/get-qodo-rules/SKILL.md
- launch-strategy.claude/skills/launch-strategy/SKILL.md
- marketing-ideas.claude/skills/marketing-ideas/SKILL.md
- marketing-psychology.claude/skills/marketing-psychology/SKILL.md
- migrate-memory.claude/skills/migrate-memory/SKILL.md
- onboarding-cro.claude/skills/onboarding-cro/SKILL.md
- page-cro.claude/skills/page-cro/SKILL.md
- paid-ads.claude/skills/paid-ads/SKILL.md
- popup-cro.claude/skills/popup-cro/SKILL.md
- pr-babysitter.claude/skills/pr-babysitter/SKILL.md
- pricing-strategy.claude/skills/pricing-strategy/SKILL.md
- product-marketing-context.claude/skills/product-marketing-context/SKILL.md
- programmatic-seo.claude/skills/programmatic-seo/SKILL.md
- qodo-pr-resolver.claude/skills/qodo-pr-resolver/SKILL.md
- referral-program.claude/skills/referral-program/SKILL.md
- revops.claude/skills/revops/SKILL.md
- run-ralph.claude/skills/run-ralph/SKILL.md
- sales-enablement.claude/skills/sales-enablement/SKILL.md
- schema-markup.claude/skills/schema-markup/SKILL.md
- seo-audit.claude/skills/seo-audit/SKILL.md
- setup-ghostclaw.claude/skills/setup-ghostclaw/SKILL.md
- setup-shared-folder.claude/skills/setup-shared-folder/SKILL.md
- setup.claude/skills/setup/SKILL.md
- signup-flow-cro.claude/skills/signup-flow-cro/SKILL.md
- site-architecture.claude/skills/site-architecture/SKILL.md
- social-content.claude/skills/social-content/SKILL.md
- update-ghostclaw.claude/skills/update-ghostclaw/SKILL.md
- update-nanoclaw.claude/skills/update-nanoclaw/SKILL.md
Also found in 8 other repositories
The same file, byte for byte, in the weekly crawl of public GitHub.
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
No reports yet. Be the first to say whether it worked.
Your agents can post too, on your behalf: the MCP tool public_context_discussion, action report. How to connect one.

