paywall-upgrade-cro
by coreyhaines31Expert guidance for designing and optimizing in-app paywalls, upgrade screens, upsell modals, and feature gates to convert free or trial users into paying customers.
Overview
What this skill does
The paywall-upgrade-cro skill turns your agent into a specialist in in-app paywalls and upgrade flows. It focuses on moments inside your product where you ask users to upgrade, pay, or move to a higher plan—after they have already experienced value.
Use paywall-upgrade-cro when you want to create or improve:
- In-app paywalls and upgrade screens
- Upsell modals and feature gates
- Trial expiration and limit-reached screens
- Plan upgrade prompts and in-app pricing presentations
It is distinct from public pricing page optimization: for marketing site pricing pages, use page-cro; for pricing strategy questions, use pricing-strategy.
Who it’s for
This skill is a good fit for:
- SaaS and product teams running freemium or trial models
- Product managers and growth teams owning in-product conversion
- UX and UI designers working on upgrade flows, modals, and gates
- Marketing teams responsible for in-app messaging and paywall copy
- Shopify or frontend developers implementing upgrade prompts
If your main challenge is “free users won’t upgrade,” “trial users don’t convert,” or “our upgrade screen isn’t working,” paywall-upgrade-cro is designed for that problem.
Problems it solves
With the structure defined in SKILL.md and the experiment ideas in references/experiments.md, the skill helps the agent:
- Diagnose why your current paywall or upgrade screen underperforms
- Align paywall timing with the user’s aha moment, limit reached, or trial status
- Design screens that emphasize value over friction, not just “you hit a limit”
- Structure upgrade flows with clear headlines, value demos, plan comparison, social proof, and strong CTAs
- Avoid dark patterns and anti-patterns that hurt trust and long-term retention
- Generate A/B test ideas for copy, layout, pricing display, and trigger logic
When it is and isn’t a good fit
Use paywall-upgrade-cro when:
- You are working on a paywall or upgrade moment inside a product or app
- You need to improve trial-to-paid, freemium conversion, or plan upgrades
- You want structured recommendations (not just random copy suggestions)
- You’re planning CRO experiments for in-app screens
It may not be the best fit when:
- You only want to redesign a public marketing or pricing page (use
page-cro) - You are setting overall price levels or packaging strategy (use
pricing-strategy) - You need deep backend billing logic or payment gateway implementation help (this skill focuses on UX, copy, and conversion, not billing integrations)
How to Use
Installation
To add the paywall-upgrade-cro skill to your agent setup, install it from the marketingskills repository:
npx skills add https://github.com/coreyhaines31/marketingskills --skill paywall-upgrade-cro
After installation, locate the skill directory:
- Repository:
coreyhaines31/marketingskills - Skill path:
skills/paywall-upgrade-cro/ - Key files:
SKILL.mdevals/evals.jsonreferences/experiments.md
Core workflow
SKILL.md defines how the agent should think and work when using paywall-upgrade-cro. The typical workflow is:
-
Load product context first
If your repo includes.agents/product-marketing-context.md(or.claude/product-marketing-context.mdin older setups), the agent is instructed to read that file before asking questions. This ensures recommendations match your:- Product model (freemium, trial, paid tiers)
- Key value propositions
- Target segments and use cases
-
Clarify the upgrade scenario
The skill pushes the agent to understand:- Upgrade context: freemium → paid, trial → paid, plan upgrade, or feature upsell
- Product model: what’s free, what’s behind the paywall, and what triggers the prompt
- User journey: where the user is, what they were trying to do, and what emotional state they’re likely in (e.g., frustration at a limit)
-
Apply a structured paywall framework
Using guidance encoded inSKILL.mdand the examples inevals/evals.json, the agent structures paywalls and upgrade screens with components such as:- Headline that communicates the value of upgrading—not just that access is blocked
- Value demonstration: what the user unlocks (features, outcomes, time savings)
- Plan comparison between free and paid where appropriate
- Social proof (testimonials, usage stats, logos) to reduce risk
- CTA that is clear, specific, and action-oriented
- Escape hatch so users can return to what they were doing without feeling trapped
-
Generate targeted copy and layout recommendations
Based on the specific trigger (usage limit, trial expiration, feature gate, etc.), the agent proposes detailed copy options, layout ideas, and UX patterns. The evaluations inevals/evals.jsonshow how it should:- Tailor copy to the user’s emotional state (e.g., frustration at hitting a project limit)
- Warn against anti-patterns (e.g., surprise hard locks without context, confusing plan options)
- Suggest concrete examples of headlines, body text, and CTAs instead of generic advice
-
Plan experiments and iterations
Thereferences/experiments.mdfile lists extensive A/B test ideas across:- Triggers & timing (aha moment vs. limit reached, time-based vs. usage-based prompts)
- Paywall design (full-screen vs. modal, minimal vs. feature-rich layouts)
- Pricing presentation (single plan vs. comparison, discounts, framing)
- Copy & messaging (headlines, CTAs, objection handling)
- Trial & conversion flows (reminders, expiration screens, upgrade paths)
- Personalization and frequency capping
The agent can use these to outline a prioritized test roadmap rather than one-off changes.
Example use cases
1. Usage limit paywall in a SaaS tool
You run a project management app where free users can create 3 projects. When they try to create the 4th, you want a paywall that feels fair and persuasive, not punitive.
With paywall-upgrade-cro, the agent will:
- Recognize this as a usage limit trigger
- Recommend a screen that:
- Acknowledges what the user has accomplished so far
- Explains succinctly what upgrading unlocks (e.g., unlimited projects, priority support)
- Shows a simple free vs. paid comparison
- Includes social proof and a direct “Upgrade to continue” CTA
- Provides an escape hatch (e.g., “Cancel and keep your 3 projects”) to avoid a dead end
2. Trial expiration upgrade screen
Your 14-day trial ends and users see a generic “Your trial has expired” message, with a low upgrade rate.
Using paywall-upgrade-cro, the agent will:
- Identify this as a trial expiration trigger
- Recommend emphasizing:
- The value the user already experienced during the trial
- What they will lose or keep access to if they upgrade now
- Clear plan details and pricing
- Optional incentives (like limited-time discounts or extended trials, if appropriate)
- Suggest alternative screens for pre-expiration reminders and post-expiration flows
3. Feature gate for premium functionality
You want to lock a premium feature (e.g., advanced reporting) behind an upgrade prompt.
The skill helps the agent:
- Decide whether to use a hard gate (block access) or soft gate (preview with a prompt)
- Structure messaging that frames the feature as a solution to a specific problem
- Suggest visuals or previews that show what the user is missing
- Ensure the gate appears after users have seen enough value to consider paying
FAQ
What is paywall-upgrade-cro specifically designed to do?
paywall-upgrade-cro is designed to help agents craft and optimize in-product paywalls, upgrade screens, upsell modals, and feature gates. It emphasizes conversion rate optimization for users who have already interacted with your product, rather than broad marketing site traffic.
How do I install paywall-upgrade-cro?
Install the skill into your skills-enabled environment with:
npx skills add https://github.com/coreyhaines31/marketingskills --skill paywall-upgrade-cro
Then explore the skill directory at skills/paywall-upgrade-cro/, focusing on SKILL.md, evals/evals.json, and references/experiments.md.
What files should I look at first?
Start with:
SKILL.md– defines the role, scope, and step-by-step reasoning for paywall and upgrade screen optimization.evals/evals.json– shows example prompts and detailed expected outputs, useful to understand how the skill should behave in real scenarios.references/experiments.md– a structured list of A/B test ideas and experiment categories for ongoing CRO work.
These three files give a solid mental model of how paywall-upgrade-cro approaches in-app conversion problems.
Does this skill help with pricing strategy?
paywall-upgrade-cro focuses on presentation and conversion of existing plans inside the product: when to show paywalls, what to say, and how to design them. If you need to decide price points, packaging, or discount strategy, you should pair it with pricing-strategy, which is more suitable for underlying pricing decisions.
Is this only for SaaS, or can I use it with Shopify and other platforms?
The skill is written in a platform-agnostic way and can be applied to:
- SaaS web apps
- Mobile apps
- Shopify themes and storefront upgrade prompts
- Any frontend environment where you control in-app screens and modals
It focuses on UX, UI, copy, and experiment ideas. You can implement the recommended patterns in your chosen frontend framework or commerce platform.
How does paywall-upgrade-cro handle anti-patterns and user trust?
The evaluations in evals/evals.json explicitly instruct the agent to:
- Address the user’s emotional state (e.g., frustration at hitting a limit)
- Warn against deceptive patterns (like surprise locks, confusing pricing, or disappearing data)
- Include escape hatches and clear messaging
This keeps your upgrade flows persuasive but respectful, supporting long-term retention and brand trust.
Can I customize the recommendations to my brand and segments?
Yes. The skill expects the agent to:
- Read
.agents/product-marketing-context.md(or.claude/product-marketing-context.mdin older setups) when available - Use your existing positioning, ICP definitions, and feature narratives
You can further tailor outputs by providing additional brand guidelines, tone of voice notes, or segment descriptions in your prompt or context files.
How do I get the most value from this skill over time?
To get ongoing value from paywall-upgrade-cro:
- Use it whenever you design or update in-app upgrade moments
- Combine its recommendations with analytics and experiment results
- Pull new test ideas from
references/experiments.mdas you see what works - Document winning paywalls and screens so the agent can reference them as proven patterns
This turns the skill into a living playbook for in-app conversion, not just a one-off helper.
