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:

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:

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:

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:

Copy patterns:

• Bad (stating implicit objection): "Worried you're too lazy to learn a language?"
• Good (CO Only): "Let the audio do the work for you."
• "What's preventing you from signing up today?" (survey to discover objections)
• "What almost stopped you from buying?" (post-purchase survey to validate O/CO table)

Ethical boundary: Address real objections with honest counter-objections. Never dismiss legitimate concerns or use deception to overcome valid hesitations.

See: OBJECTIONS.md for the full O/CO framework, research methods, and counter-objection techniques.

5. Hypothesis Design

Core concept: Every experiment needs a documented hypothesis linking a specific change to an expected outcome with a reason grounded in research. Prioritize using ICE scoring (Impact, Confidence, Ease).

Why it works: Without a hypothesis, you're just changing things randomly. The hypothesis forces you to articulate WHY a change should work, which means it must be grounded in customer research. ICE scoring prevents teams from wasting time on low-impact "meek tweaks."

Key insights:

• Hypothesis format: "If we [change X], then [metric Y] will improve because [reason based on research]"
• Define primary metric (determines winner), secondary metrics (additional monitoring), and guardrail metrics (must not decrease)
• ICE scores: Impact (1-10: could this double conversion?), Confidence (1-10: is research backing strong?), Ease (1-10: how easy to implement?)
• Make BOLD changes, not "meek tweaks" -- small changes rarely reach statistical significance and waste resources
• Before testing, ask: "Could this 10x our results?" If not, reconsider priority
• Worth testing: complete page redesign, new value proposition, fundamentally different offer
• Not worth testing: button color, font size, image swap

Product applications:

Copy patterns:

• "Based on our research, visitors' #1 objection is [X]. This test addresses it by [Y]."
• Document before: hypothesis, primary metric, sample size, duration, traffic allocation
• Document after: raw numbers, confidence interval, practical significance, learnings, next steps
• Every test adds to organizational knowledge regardless of outcome

Ethical boundary: Report all test results honestly, including failures. Never cherry-pick data or run tests until you get the result you want.

See: testing-methodology.md for ICE scoring tables and detailed prioritization.

6. A/B Testing Methodology

Core concept: Run controlled experiments comparing page versions to determine which performs better, using proper statistical rigor to ensure results are real, not random noise.

Why it works: Without controlled experiments, it is impossible to distinguish real improvements from random variation. Proper A/B testing methodology prevents the most common errors: peeking and stopping early, insufficient sample size, ignoring practical significance, and the multiple comparison problem.

Key insights:

• Calculate required sample size BEFORE starting (inputs: baseline rate, minimum detectable effect, 80% power, 95% significance)
• Run for at least one full business cycle (1-2 weeks) including weekdays AND weekends
• Never peek at results and stop early -- this inflates false positive rates dramatically
• 95% confidence minimum (p-value less than 0.05) before calling a winner
• A statistically significant 0.1% lift isn't worth implementation complexity (practical significance matters)
• Start with A/B tests; only move to multivariate when you have 100k+ monthly visitors and a proven winning page
• A failed test that teaches you something is more valuable than a winning test you don't understand
• Promote winners to new control and iterate

Product applications:

Copy patterns:

• "We increased [metric] by [X]% with [Y]% confidence over [Z] weeks"
• "Test showed no significant difference, teaching us that [insight about customers]"
• "Control outperformed challenger, suggesting visitors prefer [existing approach] because [reason]"
• Always document learnings: Test, Hypothesis, Result, Learning, Applicable to

Ethical boundary: Never manipulate statistical methods to manufacture significance. Report confidence intervals honestly and acknowledge when results are inconclusive.

See: testing-methodology.md for statistical significance, sample size calculations, and platform comparison.

Common Mistakes

Quick Diagnostic

Audit any landing page or conversion flow:

Quick-Start Checklist

When optimizing any page:

1. What is the ONE action visitors should take?
2. Who are the visitors? What stage of buying journey?
3. What are their top 3-5 objections? (Don't guess -- research)
4. What proof/counter-objections address each?
5. Is the value proposition crystal clear in 5 seconds?
6. Are there UX blockers? (speed, mobile, forms)
7. What persuasion assets are missing or hidden?

Reference Files

• OBJECTIONS.md: O/CO framework, research methods, counter-objection techniques
• COPYWRITING.md: Headlines, proof elements, persuasive writing
• PERSUASION.md: Persuasion assets checklist, psychological triggers
• RESEARCH.md: Tools, survey questions, data analysis
• testing-methodology.md: A/B testing, statistical significance, ICE prioritization, multivariate testing
• funnel-analysis.md: Blocked arteries, missing links, industry funnels, cross-sell mapping

Further Reading

This skill is based on the CRE Methodology(TM) developed by Conversion Rate Experts. For the complete methodology, detailed case studies, and advanced techniques, read the original book:

• "Making Websites Win: Apply the Customer-Centric Methodology That Has Doubled the Sales of Many Leading Websites" by Dr. Karl Blanks and Ben Jesson

About the Author

Dr. Karl Blanks and Ben Jesson are the cofounders of Conversion Rate Experts (CRE), the world's leading agency specializing in conversion rate optimization. Their clients have included Google, Apple, Amazon, Facebook, Dropbox, and many other technology leaders. CRE's methodology has been recognized with a Queen's Award for Enterprise (Innovation), the UK's highest business honor. Blanks holds a PhD in user experience and previously managed teams of usability researchers at Hewlett-Packard. Jesson's background is in direct-response marketing and web development. Together they developed the CRE Methodology, which has been applied across hundreds of websites and consistently delivered significant conversion improvements. Their book Making Websites Win distills this methodology into a systematic, repeatable process for evidence-based website optimization.

Overview

Audit websites and landing pages for conversion issues and design evidence-based A/B tests.

Prerequisites

• Access to the testing environment or API
• Required CLI tools installed and authenticated
• Familiarity with testing concepts and terminology

Instructions

1. Assess the current state of the testing configuration
2. Identify the specific requirements and constraints
3. Apply the recommended patterns from this skill
4. Validate the changes against expected behavior
5. Document the configuration for team reference

Output

• Configuration files or code changes applied to the project
• Validation report confirming correct implementation
• Summary of changes made and their rationale

See testing implementation details for output format specifications.

Error Handling

Examples

Basic usage: Apply cro methodology to a standard project setup with default configuration options.

Advanced scenario: Customize cro methodology for production environments with multiple constraints and team-specific requirements.

Resources

• Official testing documentation
• Community best practices and patterns
• Related skills in this plugin pack