Paywall Upgrade Cro

Paywall and Upgrade Screen CRO

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/paywall-upgrade-cro from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

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.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Initial Assessment, Paywall Screen Components, Specific Paywall Types, Mobile Paywall Patterns, Timing and Frequency, Upgrade Flow Optimization.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Clear explanation of why it's paid
• Show what the feature does
• Quick path to unlock
• Option to continue without
• Clear indication of what limit was reached
• Show what upgrading provides

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Initial Assessment

Before providing recommendations, understand:

1. Upgrade Context

   • Freemium → Paid conversion
   • Trial → Paid conversion
   • Tier upgrade (Basic → Pro)
   • Feature-specific upsell
   • Usage limit upsell

2. Product Model

   • What's free forever?
   • What's behind the paywall?
   • What triggers upgrade prompts?
   • What's the current conversion rate?

3. User Journey

   • At what point does this appear?
   • What have they experienced already?
   • What are they trying to do when blocked?

Examples

Example 1: Ask for the upstream workflow directly

Use @paywall-upgrade-cro to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @paywall-upgrade-cro against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @paywall-upgrade-cro for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @paywall-upgrade-cro using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• User should have experienced real value first
• The upgrade should feel like a natural next step
• Timing: After "aha moment," not before
• Demonstrate the value of paid features
• Preview what they're missing
• Make the upgrade feel tangible
• Easy to upgrade when ready

Imported Operating Notes

Imported: Core Principles

1. Value Before Ask

• User should have experienced real value first
• The upgrade should feel like a 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
• Remove barriers to conversion

4. Respect the No

• Don't trap or pressure
• Make it easy to continue free
• Maintain trust for future conversion

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/paywall-upgrade-cro, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Imported Reference Notes

Imported: Paywall Screen Components

1. Headline

Focus on what they get, not what they pay:

• "Unlock [Feature] to [Benefit]"
• "Get more [value] with [Plan]"
• Not: "Upgrade to Pro for $X/month"

2. Value Demonstration

Show what they're missing:

• Preview of the feature in action
• Before/after comparison
• "With Pro, you could..." examples
• Specific to their use case if possible

3. Feature Comparison

If showing tiers:

• Highlight key differences
• Current plan clearly marked
• Recommended plan emphasized
• Focus on outcomes, not feature lists

4. Pricing

• Clear, simple pricing
• Annual vs. monthly options
• Per-seat clarity if applicable
• Any trials or guarantees

5. Social Proof (Optional)

• Customer quotes about the upgrade
• "X teams use this feature"
• Success metrics from upgraded users

6. CTA

• Specific: "Upgrade to Pro" not "Upgrade"
• Value-oriented: "Start Getting [Benefit]"
• If trial: "Start Free Trial"

7. Escape Hatch

• Clear "Not now" or "Continue with Free"
• Don't make them feel bad
• "Maybe later" vs. "No, I'll stay limited"

Imported: Specific Paywall Types

Feature Lock Paywall

When clicking a paid feature:

[Lock Icon]
This feature is available on Pro

[Feature preview/screenshot]

[Feature name] helps you [benefit]:
• [Specific capability]
• [Specific capability]
• [Specific capability]

[Upgrade to Pro - $X/mo]
[Maybe Later]

Usage Limit Paywall

When hitting a limit:

You've reached your free limit

[Visual: Progress bar at 100%]

Free plan: 3 projects
Pro plan: Unlimited projects

You're active! Upgrade to keep building.

[Upgrade to Pro]    [Delete a project]

Trial Expiration Paywall

When trial is ending:

Your trial ends in 3 days

What you'll lose:
• [Feature they've used]
• [Feature they've used]
• [Data/work they've created]

What you've accomplished:
• Created X projects
• [Specific value metric]

[Continue with Pro - $X/mo]
[Remind me later]    [Downgrade to Free]

Soft Upgrade Prompt

Non-blocking suggestion:

[Banner or subtle modal]

You've been using [Product] for 2 weeks!
Teams like yours get X% more [value] with Pro.

[See Pro Features]    [Dismiss]

Team/Seat Upgrade

When adding users:

Invite your team

Your plan: Solo (1 user)
Team plans start at $X/user

• Shared projects
• Collaboration features
• Admin controls

[Upgrade to Team]    [Continue Solo]

Imported: Mobile Paywall Patterns

iOS/Android Conventions

• System-like styling builds trust
• Standard paywall patterns users recognize
• Free trial emphasis common
• Subscription terminology they expect

Mobile-Specific UX

• Full-screen often acceptable
• Swipe to dismiss
• Large tap targets
• Plan selection with clear visual state

App Store Considerations

• Clear pricing display
• Subscription terms visible
• Restore purchases option
• Meet review guidelines

Imported: Timing and Frequency

When to Show

• Best: After value moment, before frustration
• After activation/aha moment
• When hitting genuine limits
• When using adjacent-to-paid features

When NOT to Show

• During onboarding (too early)
• When they're in a flow
• Repeatedly after dismissal
• Before they understand the product

Frequency Rules

• Limit to X per session
• Cool-down after dismiss (days, not hours)
• Escalate urgency appropriately (trial end)
• Track annoyance signals (rage clicks, churn)

Imported: Upgrade Flow Optimization

From Paywall to Payment

• Minimize steps
• Keep them in-context if possible
• Pre-fill known information
• Show security signals

Plan Selection

• Default to recommended plan
• Annual vs. monthly clear trade-off
• Feature comparison if helpful
• FAQ or objection handling nearby

Checkout

• Minimal fields
• Multiple payment methods
• Trial terms clear
• Easy cancellation visible (builds trust)

Post-Upgrade

• Immediate access to features
• Confirmation and receipt
• Guide to new features
• Celebrate the upgrade

Imported: A/B Testing Paywalls

What to Test

• Trigger timing (earlier vs. later)
• Trigger type (feature gate vs. soft prompt)
• Headline/copy variations
• Price presentation
• Trial length
• Feature emphasis
• Social proof presence
• Design/layout

Metrics to Track

• Paywall impression rate
• Click-through to upgrade
• Upgrade completion rate
• Revenue per user
• Churn rate post-upgrade
• Time to upgrade

Imported: Output Format

Paywall Design

For each paywall:

• Trigger: When it appears
• Context: What user was doing
• Type: Feature gate, limit, trial, etc.
• Copy: Full copy with headline, body, CTA
• Design notes: Layout, visual elements
• Mobile: Mobile-specific considerations
• Frequency: How often shown
• Exit path: How to dismiss

Upgrade Flow

• Step-by-step screens
• Copy for each step
• Decision points
• Success state

Metrics Plan

What to measure and expected benchmarks

Imported: Common Patterns by Business Model

Freemium SaaS

• Generous free tier to build habit
• Feature gates for power features
• Usage limits for volume
• Soft prompts for heavy free users

Free Trial

• Trial countdown prominent
• Value summary at expiration
• Grace period or easy restart
• Win-back for expired trials

Usage-Based

• Clear usage tracking
• Alerts at thresholds (75%, 100%)
• Easy to add more without plan change
• Volume discounts visible

Per-Seat

• Friction at invitation
• Team feature highlights
• Volume pricing clear
• Admin value proposition

Imported: Anti-Patterns to Avoid

Dark Patterns

• Hiding the close button
• Confusing plan selection
• Buried downgrade option
• Misleading urgency
• Guilt-trip copy

Conversion Killers

• Asking before value delivered
• Too frequent prompts
• Blocking critical flows
• Unclear pricing
• Complicated upgrade process

Trust Destroyers

• Surprise charges
• Hard-to-cancel subscriptions
• Bait and switch
• Data hostage tactics

Imported: Experiment Ideas

Trigger & Timing Experiments

When to Show

• Test trigger timing: after aha moment vs. at feature attempt
• Early trial reminder (7 days) vs. late reminder (1 day before)
• Show after X actions completed vs. after X days
• Test soft prompts at different engagement thresholds
• Trigger based on usage patterns vs. time-based only

Trigger Type

• Hard gate (can't proceed) vs. soft gate (preview + prompt)
• Feature lock vs. usage limit as primary trigger
• In-context modal vs. dedicated upgrade page
• Banner reminder vs. modal prompt
• Exit-intent on free plan pages

Paywall Design Experiments

Layout & Format

• Full-screen paywall vs. modal overlay
• Minimal paywall (CTA-focused) vs. feature-rich paywall
• Single plan display vs. plan comparison
• Image/preview included vs. text-only
• Vertical layout vs. horizontal layout on desktop

Value Presentation

• Feature list vs. benefit statements
• Show what they'll lose (loss aversion) vs. what they'll gain
• Personalized value summary based on usage
• Before/after demonstration
• ROI calculator or value quantification

Visual Elements

• Add product screenshots or previews
• Include short demo video or GIF
• Test illustration vs. product imagery
• Animated vs. static paywall
• Progress visualization (what they've accomplished)

Pricing Presentation Experiments

Price Display

• Show monthly vs. annual vs. both with toggle
• Highlight savings for annual ($ amount vs. % off)
• Price per day framing ("Less than a coffee")
• Show price after trial vs. emphasize "Start Free"
• Display price prominently vs. de-emphasize until click

Plan Options

• Single recommended plan vs. multiple tiers
• Add "Most Popular" badge to target plan
• Test number of visible plans (2 vs. 3)
• Show enterprise/custom tier vs. hide it
• Include one-time purchase option alongside subscription

Discounts & Offers

• First month/year discount for conversion
• Limited-time upgrade offer with countdown
• Loyalty discount based on free usage duration
• Bundle discount for annual commitment
• Referral discount for social proof

Copy & Messaging Experiments

Headlines

• Benefit-focused ("Unlock unlimited projects") vs. feature-focused ("Get Pro features")
• Question format ("Ready to do more?") vs. statement format
• Urgency-based ("Don't lose your work") vs. value-based
• Personalized headline with user's name or usage data
• Social proof headline ("Join 10,000+ Pro users")

CTAs

• "Start Free Trial" vs. "Upgrade Now" vs. "Continue with Pro"
• First person ("Start My Trial") vs. second person ("Start Your Trial")
• Value-specific ("Unlock Unlimited") vs. generic ("Upgrade")
• Add urgency ("Upgrade Today") vs. no pressure
• Include price in CTA vs. separate price display

Objection Handling

• Add money-back guarantee messaging
• Show "Cancel anytime" prominently
• Include FAQ on paywall
• Address specific objections based on feature gated
• Add chat/support option on paywall

Trial & Conversion Experiments

Trial Structure

• 7-day vs. 14-day vs. 30-day trial length
• Credit card required vs. not required for trial
• Full-access trial vs. limited feature trial
• Trial extension offer for engaged users
• Second trial offer for expired/churned users

Trial Expiration

• Countdown timer visibility (always vs. near end)
• Email reminders: frequency and timing
• Grace period after expiration vs. immediate downgrade
• "Last chance" offer with discount
• Pause option vs. immediate cancellation

Upgrade Path

• One-click upgrade from paywall vs. separate checkout
• Pre-filled payment info for returning users
• Multiple payment methods offered
• Quarterly plan option alongside monthly/annual
• Team invite flow for solo-to-team conversion

Personalization Experiments

Usage-Based

• Personalize paywall copy based on features used
• Highlight most-used premium features
• Show usage stats ("You've created 50 projects")
• Recommend plan based on behavior patterns
• Dynamic feature emphasis based on user segment

Segment-Specific

• Different paywall for power users vs. casual users
• B2B vs. B2C messaging variations
• Industry-specific value propositions
• Role-based feature highlighting
• Traffic source-based messaging

Frequency & UX Experiments

Frequency Capping

• Test number of prompts per session
• Cool-down period after dismiss (hours vs. days)
• Escalating urgency over time vs. consistent messaging
• Once per feature vs. consolidated prompts
• Re-show rules after major engagement

Dismiss Behavior

• "Maybe later" vs. "No thanks" vs. "Remind me tomorrow"
• Ask reason for declining
• Offer alternative (lower tier, annual discount)
• Exit survey on dismiss
• Friendly vs. neutral decline copy

Imported: Questions to Ask

If you need more context:

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?

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.