Files
marketingskills/skills/paywalls/references/experiments.md
T
Corey Haines 30f9b9a729 feat: v2.0 skill renames and CRO consolidation (#291)
* feat: v2.0 skill renames and CRO consolidation

BREAKING CHANGE: Users must reinstall skills after this update.

## Skill Renames (16)
- ab-test-setup → ab-testing
- analytics-tracking → analytics
- aso-audit → aso
- competitor-alternatives → competitors
- email-sequence → emails
- free-tool-strategy → free-tools
- launch-strategy → launch
- onboarding-cro → onboarding
- paywall-upgrade-cro → paywalls
- popup-cro → popups
- pricing-strategy → pricing
- product-marketing-context → product-marketing
- referral-program → referrals
- schema-markup → schema
- signup-flow-cro → signup
- social-content → social

## Consolidations (1)
- page-cro + form-cro → cro (form content in references/form.md)

## Why 2.0?
- Shorter, cleaner skill names
- Consistent naming (no -strategy, -setup, -cro suffixes)
- All cross-references updated across 100+ files

Total skills: 40

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(v2.0): update evals for renamed skills, fix validate script, clear warnings

- Update 32 evals.json files to reference new skill names (page-cro → cro,
  product-marketing-context → product-marketing, etc.) — these were missed
  in the initial v2.0 rename pass since only SKILL.md and marketplace.json
  were updated.
- Fix validate-skills.sh: replace GNU-only `head -n -1` with portable awk
  so frontmatter extraction works on macOS.
- Move Copy Editing Checklist (56 lines) to references/checklist.md to
  bring copy-editing SKILL.md under the 500-line limit (508 → 457).
- Add "see X" pointers to marketing-psychology description for skill
  discovery (cro, pricing, copywriting).
- Update skill-request.yml issue template placeholder (page-cro → cro).

All 40 skills now pass validation with zero warnings.

* fix(v2.0): add evals for 8 missing skills, strip stale frontmatter from cro/form.md

Adds 48 new eval cases (6 per skill) for skills that previously had no evals:
aso, co-marketing, community-marketing, competitor-profiling, directory-submissions,
image, lead-magnets, video. All 40 skills now have eval coverage (251 total cases).

Strips leftover frontmatter from skills/cro/references/form.md — it was inherited
from the old form-cro SKILL.md before consolidation. Reference files don't need
frontmatter.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): rename paid-ads → ads

One more v2.0 simplification — drops the redundant 'paid-' qualifier. Updates
the skill directory, SKILL.md frontmatter, evals.json, README skill table, the
v2.0 rename table in VERSIONS.md (now 17 renames), and all cross-references in
related skills (ad-creative, aso, competitor-profiling, customer-research,
lead-magnets, marketing-ideas) plus the tools/integrations guides.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): bump SKILL.md frontmatter version to 2.0.0 for all 40 skills

VERSIONS.md was already updated to 2.0.0 but the metadata.version field inside
each SKILL.md was still on 1.x. That mismatch would have caused the update-check
flow to perpetually report 'update available' since it compares VERSIONS.md
against local SKILL.md metadata versions.

Caught by codex review (P1).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): add legacy product-marketing-context.md filename fallback

Before this fix, users upgrading from v1.x who had a `product-marketing-context.md`
file would lose automatic context loading — every skill only checked the new
`product-marketing.md` filename. Now all 40 skills also accept the legacy
filename (in either `.agents/` or `.claude/`), and the README migration command
covers both legacy and current filenames.

Caught by codex review (P1 + P2).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): re-sort README skills table alphabetically, fix ads box width

The skills table had a few entries out of alphabetical order from the renames
(co-marketing was after cold-email, ads was at the renamed position).
Re-sorted alphabetically per sync-skills.js. Also padded the 'ads' cell in the
ASCII flow diagram to keep the box width consistent.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): document folder cleanup on upgrade, stop sync-skills from re-adding skills array

README upgrade guide now includes:
- A clear cleanup step for stale v1.x skill folders (renamed + consolidated) so
  users don't end up with both old and new folders side-by-side after upgrading
- The full v1 to v2 rename map for reference
- Existing product-marketing-context.md migration steps (preserved)

sync-skills.js no longer (re-)introduces a `skills` array on marketplace.json --
Claude Code's plugin schema discovers skills via the `skills/` directory, and the
explicit array was failing validation. The script now refreshes the description
count and strips the stale array if present.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-05-13 22:05:15 -07:00

5.3 KiB

Paywall Experiment Ideas

Comprehensive list of A/B tests and experiments for paywall optimization.

Contents

  • Trigger & Timing Experiments (When to Show, Trigger Type)
  • Paywall Design Experiments (Layout & Format, Value Presentation, Visual Elements)
  • Pricing Presentation Experiments (Price Display, Plan Options, Discounts & Offers)
  • Copy & Messaging Experiments (Headlines, CTAs, Objection Handling)
  • Trial & Conversion Experiments (Trial Structure, Trial Expiration, Upgrade Path)
  • Personalization Experiments (Usage-Based, Segment-Specific)
  • Frequency & UX Experiments (Frequency Capping, Dismiss Behavior)

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