paywall-upgrade-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.
What this skill does
# 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 - Repeatedly after dismissal - Before they understand the product ### Frequency Rules - Limit to X per session - Cool-down after dismiss (days, not hours) - Escalate urgency appropriately (trial end) - Track annoyance signals (rage clicks, churn) --- ## Upgrade Flow Optimization ### From Paywall to Payment - Minimize steps - Keep them in-context if possible - Pre-fill known information - Show security signals ### Plan Selection - Default to recommended plan - Annual vs. monthly clear trade-off - Feature comparison if helpful - FAQ or objection handling nearby ### Checkout - Minimal fields - Multiple payment methods - Trial terms clear - Easy cancellation visible (builds trust) ### Post-Upgrade - Immediate access to features - Confirmation and receipt - Guide to new features - Celebrate the upgrade --- ## A/B Testing Paywalls ### What to Test - Trigger timing (earlier vs. later) - Trigger type (feature gate vs. soft prompt) - Headline/copy variations - Price presentation - Trial length - Feature emphasis - Social proof presence - Design/layout ### Metrics to Track - Paywall impression rate - Click-through to upgrade - Upgrade completion rate - Revenue per user - Churn rate post-upgrade - Time to upgrade --- ## Output Format ### Paywall Design For each paywall: - **Trigger**: When it appears - **Context**: What user was doing - **Type**: Feature gate, limit, trial, etc. - **Copy**: Full copy with headline, body, CTA - **Design notes**: Layout, visual elements - **Mobile**: Mobile-specific considerations - **Frequency**: How often shown - **Exit path**: How to dismiss ### Upgrade Flow - Step-by-step screens - Copy for each step - Decision points - Success state ### Metrics Plan What to measure and expected benchmarks --- ## Common Patterns by Business Model ### Freemium SaaS - Generous free tier to build habit - Feature gates for power features - Usage limits for volume - Soft prompts for heavy free users ### Free Trial - Trial countdown prominent - Value summary at expiration - Grace period or easy restart - Win-back for expired trials ### Usage-Based - Clear usage tracking - Alerts at thresholds (75%, 100%) - Easy to add more without plan change - Volume discounts visible ### Per-Seat - Friction at invitation - Team feature highlights - Volume pricing clear - Admin value proposition --- ## Anti-Patterns to Avoid ### Dark Patterns - Hiding the close button - Confusing plan selection - Buried downgrade option - Misleading urgency - Guilt-trip copy ### Conversion Killers - Asking befo
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".