paywall-upgrade-cro

---
name: paywall-upgrade-cro
description: Use when creating or optimizing in-app paywalls, upgrade screens, upsell modals, or feature gates — trial expiration, usage limits, or freemium-to-paid conversion moments.
category: Marketing
version: 1.0.0
tools: []
---

# Paywall and Upgrade Screen CRO

Convert free users to paid, or upgrade users to higher tiers, at moments when they have experienced enough value to justify the commitment.

## Initial Assessment

Check the Knowledge Base for existing product marketing context before asking questions; use what's already documented and only ask for information not already covered.

Before recommending anything, understand:

1. **Upgrade Context** — Freemium to paid? Trial to paid? Tier upgrade? Feature upsell? Usage limit?
2. **Product Model** — What's free? What's behind the paywall? What triggers prompts? Current conversion rate?
3. **User Journey** — When does this appear? What has the user experienced? What are they trying to do?

## Core Principles

1. **Value Before Ask** — the user should experience real value first; time the upgrade after the "aha moment," not before.
2. **Show, Don't Just Tell** — demonstrate paid features, preview what's missing, make the upgrade tangible.
3. **Friction-Free Path** — make it easy to upgrade when ready; don't make users hunt for pricing.
4. **Respect the No** — never trap or pressure; make it easy to continue free and preserve trust for future conversion.

## Paywall Trigger Points

- **Feature Gates** — when a user clicks a paid-only feature: explain why it's paid, show what it does, offer a quick path to unlock, and an option to continue without it.
- **Usage Limits** — when a user hits a limit: show the limit clearly, show what upgrading provides, don't block abruptly.
- **Trial Expiration** — early warnings at 7, 3, and 1 day before expiration; a clear statement of what happens on expiration; a summary of value received.
- **Time-Based Prompts** — after several days of free use, a gentle upgrade reminder highlighting 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, mark the current plan.
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** — a clear "Not now" or "Continue with Free" option.

## Specific Paywall Types

**Feature Lock Paywall** — lock icon, feature preview/screenshot, 2-3 capability bullets, "Upgrade to Pro" CTA, "Maybe Later" escape hatch.

**Usage Limit Paywall** — progress bar at 100%, free-vs-Pro comparison (e.g. "Free: 3 projects | Pro: Unlimited"), upgrade CTA alongside a workaround option (e.g. "Delete a project").

**Trial Expiration Paywall** — countdown ("Your trial ends in 3 days"), what they'll lose, what they've accomplished, "Continue with Pro" CTA plus "Remind me later" and "Downgrade" options.

## Timing and Frequency

- Show after the value moment and before frustration, after activation/the aha moment, or when hitting genuine limits.
- Don't show during onboarding, mid-flow, or repeatedly after dismissal.
- Cap prompts per session; enforce a cool-down of days (not hours) after a dismissal; track annoyance signals.

## Upgrade Flow Optimization

- Minimize steps from paywall to payment; keep the flow in-context; pre-fill known information.
- Post-upgrade: grant immediate access, confirm and receipt, guide the user to new features.

## A/B Testing

Test trigger timing, headline/copy, price presentation, trial length, feature emphasis, and design/layout. Track paywall impression rate, click-through to upgrade, completion rate, revenue per user, and post-upgrade churn rate.

## Anti-Patterns to Avoid

- Dark patterns: hiding the close button, confusing plan selection, guilt-trip copy.
- Conversion killers: asking before value is delivered, too-frequent prompts, blocking critical flows, a complicated upgrade process.

## Task-Specific Questions

1. What's the current free-to-paid conversion rate?
2. What triggers upgrade prompts today?
3. What features are behind the paywall?
4. What's the "aha moment" for users?
5. What pricing model — per seat, usage, flat?
6. Mobile app, web app, or both?

## Related Skills

- **page-cro** — for the public-facing pricing page, not in-product upgrade screens.
- **onboarding-cro** — when users haven't reached activation and are hitting paywalls too early; fix onboarding first.
- **ab-test-setup** — for controlled experiments on paywall timing, copy, pricing display, or layout.
- **email-sequence** — for trial expiration or upgrade reminder emails that complement in-app prompts.
- **marketing-context** — foundation for ICP, pricing model, and value proposition; check before writing paywall copy.

## Communication

Always confirm whether the aha moment has been reached before recommending upgrade prompt placement. When writing paywall copy, deliver complete screen copy: headline, value statement, feature list, CTA, and escape hatch text. Flag dark patterns proactively and recommend ethical alternatives.

## Output Artifacts

| Artifact | Description |
|----------|-------------|
| Paywall Trigger Map | All trigger points with timing rules, cooldown periods, and frequency caps |
| Full Paywall Screen Copy | Headline, value demonstration, feature comparison, CTA, and escape hatch for each paywall type |
| Upgrade Flow Diagram | Step-by-step from paywall click to post-upgrade confirmation, with friction reduction notes |
| Anti-Pattern Audit | Review of an existing paywall for dark patterns and conversion killers |
| A/B Test Backlog | Prioritized experiment ideas for trigger timing, copy, and pricing display |