cro-methodology
A systematic, research-based framework for identifying why visitors don't convert and creating data-backed experiments to improve results.
Install
mkdir -p .claude/skills/cro-methodology && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19545" && unzip -o skill.zip -d .claude/skills/cro-methodology && rm skill.zipInstalls to .claude/skills/cro-methodology
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isn''t converting", "conversion rate", "A/B test", "why visitors leave", or "objection handling". Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.Key capabilities
- →Audit landing pages for conversion friction
- →Map user funnels to identify blocked arteries
- →Design evidence-based A/B tests
- →Create objection-handling copy
- →Calculate required sample sizes for tests
How it works
The methodology uses a 9-step process to research visitor behavior and objections, then systematically eliminates friction points through evidence-based experimentation.
Inputs & outputs
When to use cro-methodology
- →Audit a low-converting landing page
- →Design an evidence-based A/B test
- →Map user funnels for friction points
- →Create objection-handling copy
- →Evaluate page design against conversion principles
About this skill
CRO Methodology
Scientific, customer-centric approach to conversion rate optimization based on the CRE Methodology(TM). Extraordinary improvements come from understanding WHY visitors don't convert, not from copying competitors or applying generic tips.
Core Principle
Don't guess -- discover. The methodology rejects "best practices" and "magic buttons" in favor of evidence-based optimization. Most websites underperform not because of bad design, but because no one has systematically researched why visitors leave without converting.
The foundation: Every visitor who doesn't convert has a reason. Your job is to discover those reasons through research, then systematically eliminate them with evidence and proof. This customer-centric approach consistently outperforms intuition, competitor copying, and "expert" opinions.
Scoring
Goal: 10/10. When reviewing or creating landing pages, funnels, or conversion flows, rate them 0-10 based on adherence to the principles below. A 10/10 means full alignment with all guidelines; lower scores indicate gaps to address. Always provide the current score and specific improvements needed to reach 10/10.
The CRO Frameworks
1. The CRO Process
Core concept: A systematic 9-step process for optimizing conversion rates, moving from defining success metrics through research, experimentation, and scaling wins across the business.
Why it works: Random optimization efforts fail because they skip the critical research steps. The CRE process forces you to understand visitors before changing anything, ensuring changes are based on evidence rather than opinion.
Key insights:
- Define success metrics aligned with business KPIs before touching any page
- Map the entire conversion funnel to find "blocked arteries" (high-traffic underperforming paths) and "missing links" (absent funnel stages)
- Understand visitors in three dimensions: who they are (types and intentions), what blocks them (UX problems), and what stops them (objections)
- Gather market intelligence from competitors, reviews, and other industries
- Prioritize ideas using ICE scoring (Impact, Confidence, Ease) before testing
- Create bold experimental designs based on research, not "meek tweaks"
- Run experiments with proper statistical rigor (95% confidence minimum, full business cycles)
- Scale wins across landing pages, ad copy, email sequences, and offline materials
Product applications:
| Context | CRO Process Step | Example |
|---|---|---|
| Landing page audit | Steps 1-3: Define goals, map funnel, research visitors | Identify that 70% of traffic bounces because value prop is unclear |
| Checkout optimization | Step 2: Map funnel for blocked arteries | Discover shipping cost shock causes 40% cart abandonment |
| New feature launch | Steps 6-8: Strategize, design, experiment | A/B test two positioning approaches before full rollout |
| Email sequence | Step 9: Scale wins | Apply winning objection-handling copy from landing page to drip emails |
| Competitor response | Step 4: Market intelligence | Transfer proven strategies from adjacent industries |
Copy patterns:
- "What's preventing you from [action] today?" (exit survey question to discover objections)
- "Here's what [X] customers found..." (counter-objection with social proof)
- Document hypothesis: "If we [change X], then [metric Y] will improve because [reason from research]"
- Always calculate required sample size BEFORE starting any test
Ethical boundary: Never manipulate test results or cherry-pick data. Report all tests, including failures, and wait for genuine statistical significance.
See: testing-methodology.md for detailed ICE scoring, A/B vs. multivariate guidance, and statistical rigor.
2. Customer Research & Objections
Core concept: Visitors don't convert for specific, discoverable reasons. Research methods -- exit surveys, chat logs, support tickets, sales calls, reviews -- reveal the "voice of the customer" and their real objections.
Why it works: Companies guess why visitors leave, but guesses are almost always wrong. Direct research consistently uncovers objections that teams never anticipated, and the language customers use is more persuasive than any copywriter's invention.
Key insights:
- Primary sources (exit surveys, live chat logs, support tickets, sales call recordings) give you direct visitor language
- Secondary sources (reviews, social media, competitor analysis) reveal industry-wide objections
- Objections fall into two categories: explicit ("too expensive") and implicit ("I'm not sure I'll follow through")
- The "Big 5" universal objections are Trust, Price, Fit, Timing, and Effort
- Post-purchase surveys ("What almost stopped you from buying?") reveal the objections that matter most
- Non-converter surveys should ask ONE question for maximum response rate
- Quantitative research (analytics, heatmaps) shows WHERE problems are; qualitative research (surveys, interviews) shows WHY
Product applications:
| Context | Research Method | Example |
|---|---|---|
| Exit intent | On-site survey (Hotjar, Qualaroo) | "What's preventing you from signing up today?" |
| Post-purchase | Email survey within 7 days | "What almost stopped you from buying?" |
| Objection mining | Support ticket analysis | Search for "but", "however", "worried about" patterns |
| Voice of customer | Sales call recordings | Capture exact language customers use to describe problems |
| Competitive gaps | Review mining (yours and competitors') | Negative reviews = unaddressed objections |
Copy patterns:
- Use exact customer language in headlines and body copy (more persuasive than polished marketing copy)
- "What's the one thing we could change to make you [action]?"
- "How would you describe [product] to a friend?" (reveals positioning in customer terms)
- Ask open-ended questions for discovery; save multiple choice for validation
Ethical boundary: Respect customer privacy in research. Anonymize data, get consent for recordings, and don't survey so aggressively that you degrade the user experience.
See: RESEARCH.md for tools, survey questions, and data analysis methods.
3. Persuasion Assets
Core concept: Every company has overlooked proof elements -- testimonials not displayed, awards not mentioned, statistics not highlighted, guarantees not prominent, team credentials hidden. These are "persuasion assets" that must be inventoried, acquired, and displayed.
Why it works: Visitors make decisions based on evidence and proof, not claims. A bold claim without proof is just noise. A modest claim with overwhelming proof is irresistible. Most companies sit on goldmines of proof they never use.
Key insights:
- Audit five categories: Credentials & Authority, Social Proof, Risk Reversal, Data & Specificity, Process & Methodology
- Create a "wish list" for missing assets and actively acquire them (request testimonials, apply for awards, compile statistics)
- The "proof sandwich" structure: Claim (bold promise) then Proof (evidence) then Reinforcement (secondary proof)
- Hierarchy of proof from strongest to weakest: specific results with context, named testimonials with photos, case studies, statistics, logos/badges, generic testimonials
- Place proof at points of friction, not hidden in FAQs
- Specific numbers beat round numbers ("47,832 customers" beats "About 50,000")
Product applications:
| Context | Persuasion Asset | Example |
|---|---|---|
| Landing page header | Logo bar + rating | "Trusted by 10,000+ companies" with 5 recognizable logos |
| Pricing page | Risk reversal | "30-day money-back guarantee, no questions asked" |
| Product page | Specific testimonial | Photo + name + company + "Increased conversion by 47% in 3 weeks" |
| Checkout flow | Trust badges near forms | Security certification, payment logos, guarantee seal |
| About page | Team credentials | Years of experience, certifications, publications, patents |
Copy patterns:
- "Here's how we did it for [Company X]..." (case study proof)
- "And here's what their CEO says about working with us..." (testimonial reinforcement)
- "[Specific number] businesses trust us" (not "thousands of customers")
- Lead with benefits, not features: "Never delete another photo" beats "256GB storage"
Ethical boundary: Never fabricate testimonials, inflate statistics, or display fake trust badges. All proof must be genuine and verifiable.
See: PERSUASION.md for the full persuasion assets checklist and psychological triggers.
4. The O/CO Framework
Core concept: The Objection/Counter-Objection (O/CO) table is the core CRE technique. Create a two-column table mapping every visitor objection to specific, evidence-backed counter-objections.
Why it works: Visitors arrive with objections. If the page doesn't address them, visitors leave. The O/CO framework ensures no objection goes unanswered, and counter-objections are placed exactly where objections naturally arise during the reading flow.
Key insights:
- Don't guess objections -- research them from surveys, chat logs, support tickets, and sales calls
- Implicit objections (ones visitors won't admit) require "CO Only" approach: address the objection without stating it
- Place counter-objections at the point of friction (credit card objection near payment form), not buried in FAQ
- Address primary objections above the fold, secondary objections in the flow
- Use multiple formats for the same counter-objection: text, video, testimonial, data
- Canned support responses are goldmines of tested counter-objections
Product applications:
| Context | Objection Type | O/CO Example |
|---|---|---|
| **Tr |
Content truncated.
When not to use it
- →When seeking overall marketing strategy
- →When addressing general usability issues
Limitations
- →Never manipulate test results
- →Never cherry-pick data
How it compares
It replaces intuition and generic best practices with a customer-centric research framework that identifies why visitors leave.
Compared to similar skills
cro-methodology side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| cro-methodology (this skill) | 0 | 4mo | No flags | Intermediate |
| page-cro | 0 | 4mo | No flags | Advanced |
| google-analytics | 43 | 6mo | Review | Intermediate |
| app-store-optimization | 19 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by christophacham
View all by christophacham →You might also like
page-cro
foolhardy45
Analyze and optimize individual pages for conversion performance.
google-analytics
davila7
Analyze Google Analytics data, review website performance metrics, identify traffic patterns, and suggest data-driven improvements. Use when the user asks about analytics, website metrics, traffic analysis, conversion rates, user behavior, or performance optimization.
app-store-optimization
davila7
Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store
analytics-tracking
davila7
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.
developing-in-lightdash
lightdash
Build, configure, and deploy Lightdash analytics projects. Supports both dbt projects with embedded Lightdash metadata and pure Lightdash YAML projects without dbt. Create metrics, dimensions, charts, and dashboards using the Lightdash CLI.
seo-cannibalization-detector
sickn33
Analyzes multiple provided pages to identify keyword overlap and potential cannibalization issues. Suggests differentiation strategies. Use PROACTIVELY when reviewing similar content.