# Optimize Paywalls and Upgrade Flows

In-app upgrade prompts often lose users when timing, value, or trust signals are unclear. This skill helps Claude, Codex, and Claude Code design better paywalls, copy, flows, and tests.

## Install

```bash
npx skillstore add coreyhaines31/paywall-upgrade-cro
```

## Metadata

- Status: approved
- Slug: coreyhaines31-paywall-upgrade-cro
- Skillstore revision: r1
- Version status: missing
- Tree hash: 10c63b360c353b8c0dceed0bdca1520bb21dcd5113ce8a9831b8f60a7c199fe2
- Author: coreyhaines31
- GitHub username: coreyhaines31
- License: MIT
- Repository: https://github.com/coreyhaines31/marketingskills/tree/main/skills/paywall-upgrade-cro
- Ref: d11af420e07cd866fe39cfa937efef3223896c06
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/coreyhaines31-paywall-upgrade-cro
- Manifest: https://skillstore.pages.dev/api/skills/coreyhaines31-paywall-upgrade-cro/manifest

## Capabilities

- Design feature gate, usage limit, trial expiration, soft prompt, and team upgrade paywalls.
- Draft paywall copy with headlines, body text, calls to action, and dismiss options.
- Recommend timing, frequency caps, and exit paths for in-product upgrade prompts.
- Plan A/B tests for trigger timing, layout, pricing presentation, copy, and trial structure.
- Define funnel metrics such as impressions, click-through, upgrade completion, revenue, churn, and time to upgrade.
- Identify dark patterns and trust risks in upgrade flows.

## Use Cases

- Improve Free Plan Conversion: Create a usage-limit paywall that explains the limit, shows the paid value, and keeps a respectful free-plan path.
- Plan Paywall Experiments: Build a focused A/B testing plan for copy, timing, layout, pricing display, and trial offers.
- Design Upgrade Screen UX: Turn an upgrade moment into clear screen content, layout notes, mobile behavior, and exit options.

## Prompt Templates

### Create a Basic Paywall

```
Create a feature gate paywall for [product]. The user is trying to access [paid feature]. Include the trigger, screen copy, CTA, dismiss option, and trust signals.
```

### Improve an Existing Screen

```
Review this upgrade screen for [product]: [paste current copy or describe screen]. Improve the headline, body copy, CTA, pricing clarity, and exit path while avoiding dark patterns.
```

### Design an Experiment Plan

```
Create an A/B test plan for our [feature gate or trial expiration] paywall. Include hypotheses, variants, target segments, primary metric, guardrail metrics, and success criteria.
```

### Map a Full Upgrade Flow

```
Design the full upgrade flow for [product model]. Cover trigger timing, paywall screen, plan selection, checkout handoff, success state, frequency rules, mobile notes, and measurement plan.
```

## Limitations

- It cannot analyze live product analytics unless the user provides data.
- It does not guarantee revenue lift or choose final prices without business context.
- It does not implement checkout, billing, or app store subscription systems.
- It needs product model, user journey, pricing, and paywall trigger details for precise recommendations.

## Best Practices

- Show upgrade prompts after users experience value, not during early onboarding.
- Pair every hard gate with a clear reason, a value preview, and a respectful exit path.
- Measure both conversion lift and trust signals such as churn, dismissals, and support complaints.

## Anti Patterns

- Hiding close buttons, downgrade paths, cancellation details, or subscription terms.
- Using misleading urgency, guilt-based copy, or surprise charges to force upgrades.
- Repeating prompts too often after users dismiss them.

## Security Audit

- Audited at: 2026-07-06T08:07:36.768\+00:00
- Summary: The flagged external command findings are false positives from Markdown code fences around paywall examples. The low blocker findings are ordinary CRO vocabulary and mobile UI terms, not system or network reconnaissance. No prompt injection, exfiltration intent, or unsafe execution behavior was found in SKILL.md.

## Stats

- Views: 127
- Downloads: 8
- Favorites: 0
- Popularity score: 0