← Back to Skills Marketplace
mariokarras

Paywall Upgrade Cro

by Mario Karras · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
139
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install abm-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," "upgr...
README (SKILL.md)

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


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
Usage Guidance
This skill is instruction-only and internally consistent for designing in-app paywalls. Before installing, note that it will attempt to read optional local project marketing context files ('.agents/product-marketing-context.md' or '.claude/product-marketing-context.md') to avoid asking redundant questions — remove any sensitive credentials or secrets from those files if you do not want them exposed to the agent. There are no installs or credential requests, and 'always' is false. If you need public pricing page work instead, use the separate page-cro skill referenced in the instructions.
Capability Analysis
Type: OpenClaw Skill Name: abm-paywall-upgrade-cro Version: 1.0.0 The skill bundle 'abm-paywall-upgrade-cro' is a legitimate tool designed to guide an AI agent in optimizing in-app paywalls and upgrade flows. The instructions in SKILL.md and the supporting documentation in references/experiments.md focus entirely on conversion rate optimization (CRO) principles, user experience, and A/B testing strategies without any evidence of malicious intent, data exfiltration, or unauthorized execution.
Capability Assessment
Purpose & Capability
Name and description (in-app paywalls/upgrade flows) match the SKILL.md content. The skill is a content/UX guidance tool and does not request unrelated binaries, credentials, or system-level access.
Instruction Scope
The runtime instructions ask the agent to read project marketing context files if present ('.agents/product-marketing-context.md' or '.claude/product-marketing-context.md') before asking questions. Reading such local project files is coherent for a contextual UX recommendation, but it means the skill may access workspace files that could contain sensitive project information; the skill otherwise stays within paywall-design guidance and templates.
Install Mechanism
No install spec and no code files — instruction-only. This minimizes disk installation and executable risk.
Credentials
No environment variables, credentials, or external endpoints are requested. The skill does not ask for unrelated secrets or config paths.
Persistence & Privilege
always is false and the skill does not request persistent agent modifications or system-wide configuration. It can be invoked by the agent (default), which is expected for skills of this type.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install abm-paywall-upgrade-cro
  3. After installation, invoke the skill by name or use /abm-paywall-upgrade-cro
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of the paywall-upgrade-cro skill. - Provides comprehensive guidance for creating and optimizing in-app paywalls, upgrade screens, upsell modals, and feature gates. - Focuses on converting free users to paid or encouraging upgrades at key in-product moments after users have experienced value. - Includes best practices for feature gating, usage limits, trial expiration, and timing/frequency of upgrade prompts. - Offers actionable templates, core principles, anti-patterns to avoid, and suggestions for effective A/B testing. - Distinguishes in-product paywall optimization from public pricing pages and other related skills.
Metadata
Slug abm-paywall-upgrade-cro
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Paywall Upgrade Cro?

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," "upgr... It is an AI Agent Skill for Claude Code / OpenClaw, with 139 downloads so far.

How do I install Paywall Upgrade Cro?

Run "/install abm-paywall-upgrade-cro" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Paywall Upgrade Cro free?

Yes, Paywall Upgrade Cro is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Paywall Upgrade Cro support?

Paywall Upgrade Cro is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Paywall Upgrade Cro?

It is built and maintained by Mario Karras (@mariokarras); the current version is v1.0.0.

💬 Comments