Receber por email
← Voltar para o catálogo

paywall-upgrade-cro

In-app paywall and upgrade screen optimization covering feature gate design, usage limit UX, trial expiration flows, upgrade trigger timing, save offer strategy, and ethical monetization patterns.

288estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: NOASSERTION

Como adicionar

/plugin marketplace add borghei/Claude-Skills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/paywall-upgrade-cro-borghei/svg)](https://www.skillteca.com.br/skills/paywall-upgrade-cro-borghei)

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Paywall & Upgrade Screen CRO

Production-grade framework for in-product upgrade flows. Covers feature gate design, usage limit UX, trial expiration sequences, upgrade trigger timing, dark pattern avoidance, and ethical monetization. Distinct from public pricing pages (use page-cro for those) -- this focuses on in-product moments where users have already experienced value.

Table of Contents

  • [Initial Assessment](#initial-assessment)
  • [The Value-First Principle](#the-value-first-principle)
  • [Paywall Trigger Architecture](#paywall-trigger-architecture)
  • [Paywall Screen Design](#paywall-screen-design)
  • [Feature Gate Patterns](#feature-gate-patterns)
  • [Usage Limit UX](#usage-limit-ux)
  • [Trial Expiration Flows](#trial-expiration-flows)
  • [Timing and Frequency Rules](#timing-and-frequency-rules)
  • [Upgrade Flow Optimization](#upgrade-flow-optimization)
  • [Dark Pattern Avoidance](#dark-pattern-avoidance)
  • [Platform-Specific Considerations](#platform-specific-considerations)
  • [Metrics and Benchmarks](#metrics-and-benchmarks)
  • [A/B Test Framework](#ab-test-framework)
  • [Output Artifacts](#output-artifacts)
  • [Related Skills](#related-skills)

Initial Assessment

Required Context

| Question | Why It Matters | |----------|---------------| | What is the upgrade model? (freemium to paid, trial to paid, tier upgrade) | Determines the paywall type | | What is free vs paid? | Defines the value gap to communicate | | What triggers upgrade prompts today? | Identifies current trigger points | | What is the current free-to-paid conversion rate? | Baseline for improvement | | What is the aha moment for users? | Determines when the paywall should appear | | What pricing model? (per seat, usage, flat) | Affects paywall messaging | | Mobile app, web app, or both? | Platform-specific requirements |

The Value-First Principle

The single most important rule in paywall design: The user must have experienced real value before seeing an upgrade prompt.

Value-First Checklist

  • [ ] User has completed the activation event (aha moment reached)
  • [ ] User has used the product at least 2-3 times
  • [ ] User has created or stored data they would lose
  • [ ] The upgrade feels like a natural next step, not a trap

When to Show vs When NOT to Show

| Show | Do Not Show | |------|------------| | After aha moment is reached | During onboarding | | When user hits a genuine limit | On first login | | When user clicks a paid feature | When user is in the middle of a task | | After milestone completion | Immediately after a frustrating experience | | On session start (gentle reminder) | After every action |

Paywall Trigger Architecture

Trigger Types

| Trigger | When It Fires | Best For | |---------|--------------|----------| | Feature gate | User clicks a locked feature | Feature-differentiated tiers | | Usage limit | User reaches a quota | Usage-based pricing | | Trial expiration | Trial period ending | Time-limited trial models | | Time-based | After N days of active use | Freemium nurture | | Milestone-based | After user achieves X | Upsell at success moments | | Team-based | When team grows past free seat limit | Per-seat models |

Trigger Priority Map

| User State | Primary Trigger | Timing | |-----------|----------------|--------| | Activated, under limits | Feature gate (when they try paid feature) | On click | | Approaching limit | Soft warning (80% of limit) | Proactive | | Hit limit | Usage limit paywall | On action that exceeds limit | | Trial day 7 of 14 | Trial ending reminder | Session start | | Trial day 13 of 14 | Urgent trial expiration | Session start + email | | Trial day 14 | Trial expired | On login | | Active for 30+ days, free | Value-based upgrade prompt | Session start, once per week |

Paywall Screen Design

Screen Anatomy

┌─────────────────────────────────────┐
│ [X Close / "Not now"]               │  Escape hatch (always visible)
│                                     │
│ HEADLINE: Value-focused             │  "Unlock [feature] to [benefit]"
│                                     │
│ [Feature preview / screenshot]      │  Show what they are missing
│                                     │
│ KEY BENEFITS:                       │
│ - Benefit 1                        │
│ - Benefit 2                        │
│ - Benefit 3                        │
│                                     │
│ PRICE: $X/month                    │  Clear, simple pricing
│ (or plan comparison)               │
│                                     │
│ [UPGRADE CTA - Primary]           │  "Start Pro Plan"
│ [Maybe Later - Secondary]          │  Clear secondary action
│                                     │
│ "Join 5,000+ teams on Pro"        │  Social proof
└─────────────────────────────────────┘

Copy Patterns by Trigger Type

| Trigger | Headline Pattern | CTA Pattern | |---------|-----------------|-------------| | Feature gate | "Unlock [Feature] to [Benefit]" | "Upgrade to [Plan]" | | Usage limit | "You've used all [N] [resources]" | "Get Unlimited [Resources]" | | Trial expiring | "Your trial ends in [N] days" | "Continue with [Plan]" | | Milestone | "You just hit [milestone]! Keep growing with Pro" | "Upgrade & Keep Growing" | | Time-based | "[Product] Pro helps teams like yours [benefit]" | "See Pro Features" |

Feature Gate Patterns

Soft Gate (Preview + Lock)

User can see what the feature does but cannot use it fully.

┌──────────────────────────────┐
│  [Feature Preview]           │  Blurred screenshot or partial result
│                              │
│  [Lock Icon] Pro Feature     │
│                              │
│  [Feature name] lets you:    │
│  - Capability 1              │
│  - Capability 2              │
│                              │
│  [Upgrade to Pro - $X/mo]   │
│  [Maybe Later]              │
└──────────────────────────────┘

Hard Gate (Block + Explain)

User cannot access the feature at all. Show the value clearly.

┌──────────────────────────────┐
│  [Lock Icon]                 │
│                              │
│  This feature is available   │
│  on the Pro plan             │
│                              │
│  What you get:               │
│  - Benefit 1                 │
│  - Benefit 2                 │
│  - Benefit 3                 │
│                              │
│  [Upgrade to Pro]            │
│  [Compare Plans]             │
└──────────────────────────────┘

Feature Gate Design Rules

  • Always explain WHY the feature is valuable (not just that it is locked)
  • Show what the feature produces (output preview) when possible
  • Include a "Compare Plans" link for users who want more detail
  • Do not gate features the user was already using during trial

Usage Limit UX

Approaching Limit (80% Warning)

┌──────────────────────────────────┐
│  [Progress Bar: 80%]            │
│  You've used 80 of 100 credits  │
│                                  │
│  [Get More Credits]  [Dismiss]  │
└──────────────────────────────────┘

At Limit (100%)

┌──────────────────────────────────────┐
│  [Progress Bar: 100%]               │
│  You've reached your monthly limit  │
│                                      │
│  Free: 100 credits | Pro: Unlimited │
│                                      │
│  [Upgrade to Pro]                   │
│  [Delete items to free space]       │  Alternative action
└──────────────────────────────────────┘

Usage Limit Rules

  • Show usage context before the limit hits (progress indicators in the UI)
  • Provide an alternative action (delete, archive, export) when possible
  • Never delete user data when limits are reached
  • Allow grace period (do not cut off mid-task)

Trial Expiration Flows

Trial Countdown Sequence

| Day | Channel | Message | Tone | |-----|---------|---------|------| | Day 7 (of 14) | In-app banner | "7 days left in your trial" | Informational | | Day 10 | Email | "4

Compartilhar X LinkedIn