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. Every visitor who doesn't convert has a reason. Discover those reasons through research, then systematically eliminate them with evidence and proof. This evidence-based approach consistently outperforms "best practices", intuition, competitor copying, and expert opinion.

Scoring

Goal: 10/10. Score any landing page, funnel, or conversion flow against the seven Quick Diagnostic rows below: award ~1.4 points per row answered "yes" (7 rows = 9.8, capped at 10). Bands: 9-10 = single clear action, research-grounded O/CO table, value prop legible in 5 seconds, proof at every friction point, funnel mapped, path free of UX blockers; 5-6 = guessed objections, generic best-practices copy, proof buried in FAQs; <=3 = competing CTAs, no funnel map, claims with no proof. Report the current score and the specific diagnostic rows failing.

The CRO Frameworks

1. The CRO Process

Core concept: A systematic 9-step process moving from defining success metrics through research and experimentation to scaling wins across the business.

Why it works: Random optimization skips research. The process forces you to understand visitors before changing anything, so every change rests on evidence, not opinion.

Key insights:

• Define success metrics aligned with business KPIs before touching any page
• Map the entire funnel to find "blocked arteries" (high-traffic underperforming paths) and "missing links" (absent funnel stages)
• Research visitors in three dimensions: who they are, what blocks them (UX problems), what stops them (objections)
• Gather market intelligence from competitors, reviews, and other industries
• Prioritize ideas with ICE scoring; design bold experiments, not "meek tweaks"
• Run experiments with statistical rigor (95% confidence minimum, full business cycles), then scale wins across the business

Product applications:

Copy patterns:

• "What's preventing you from [action] today?" (exit survey to discover objections)
• "Here's what [X] customers found..." (counter-objection with social proof)

See funnel-analysis.md (references/funnel-analysis.md) when mapping the funnel -- step-by-step mapping, blocked-artery/missing-link diagnosis, industry funnel benchmarks, and impact-based prioritization.

2. Customer Research & Objections

Core concept: Visitors fail to convert for specific, discoverable reasons. Exit surveys, chat logs, support tickets, sales calls, and reviews reveal the "voice of the customer" and their real objections.

Why it works: Teams' guesses about why visitors leave are almost always wrong. Research uncovers objections no one anticipated, and the customer's own language out-persuades any copywriter's invention.

Key insights:

• Primary sources (exit surveys, live chat, tickets, sales calls) give direct visitor language; secondary sources (reviews, social media, competitors) reveal industry-wide objections
• The "Big 5" universal objections: Trust, Price, Fit, Timing, Effort
• Quantitative research (analytics, heatmaps) shows WHERE problems are; qualitative (surveys, interviews) shows WHY
• Non-converter surveys should ask ONE question for maximum response; post-purchase surveys ("What almost stopped you from buying?") reveal the objections that matter most

Product applications:

Copy patterns:

• Use exact customer language in headlines and body copy -- it outperforms 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)

Ethical boundary: Anonymize data, get consent for recordings, and don't survey so aggressively that you degrade the experience.

See RESEARCH.md (references/RESEARCH.md) when planning research -- ready-to-use survey questions per channel, recommended tools, and how to turn raw responses into a ranked objection list.

3. Persuasion Assets

Core concept: Every company sits on overlooked proof -- undisplayed testimonials, unmentioned awards, hidden credentials, buried guarantees. Inventory these "persuasion assets", acquire missing ones, display them.

Why it works: Visitors decide on evidence, not claims. A modest claim with overwhelming proof beats a bold claim with none.

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)
• "Proof sandwich" structure: Claim (bold promise), then Proof (evidence), then Reinforcement (secondary proof)
• Proof hierarchy, strongest first: specific results with context > named testimonials with photos > case studies > statistics > logos > generic testimonials
• Place proof at points of friction, not in FAQs; specific numbers beat round ones ("47,832 customers" beats "About 50,000")

Product applications:

Copy patterns:

• "Here's how we did it for [Company X]..." (case study proof)
• "[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 (references/PERSUASION.md) when auditing or acquiring proof -- the full five-category asset checklist and psychological triggers. See COPYWRITING.md (references/COPYWRITING.md) when writing the proof copy itself -- headline formulas, benefit-led phrasing, and proof-element wording.

4. The O/CO Framework

Core concept: The Objection/Counter-Objection table is the core CRE technique: map every visitor objection to a specific, evidence-backed counter-objection.

Why it works: The table forces every counter to be placed where its objection arises in the reading flow, so a concern is answered the instant the visitor feels it -- not pages later, by which point they have already left.

Key insights:

• Research objections from surveys, chat logs, tickets, and sales calls -- don't guess
• Implicit objections (ones visitors won't admit) require "CO Only": counter without stating the objection
• Place counter-objections at the point of friction (credit-card objection near the payment form), not buried in FAQ
• Address primary objections above the fold; repeat the same counter in multiple formats (text, video, testimonial, data)
• Canned support responses are goldmines of tested counter-objections

Product applications:

Copy patterns:

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

Ethical boundary: A counter-objection must resolve the concern with real evidence, not dismiss a legitimate worry as unfounded.

See OBJECTIONS.md (references/OBJECTIONS.md) when building the O/CO table -- per-category counter-objection technique catalogs, CO-Only patterns for implicit objections, and how to mine objections from support logs.

5. Hypothesis Design

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

Why it works: A hypothesis forces you to articulate WHY a change should work, grounding it in customer research. ICE scoring stops teams wasting traffic on low-impact tweaks.

Key insights:

• Format: "If we [change X], then [metric Y] will improve because [reason based on research]"
• Define primary (decides winner), secondary (monitoring), and guardrail (must not decrease) metrics before testing
• ICE, 1-10 each: Impact (could this double conversion?), Confidence (how strong is the research?), Ease (how easy to implement?); prioritize by the average
• The 10x screen: if a change couldn't 10x results, deprioritize it. Worth testing: complete redesign, new value proposition, fundamentally different offer. Not worth testing: button color, font size, image swap

Worked example: "Customer language from surveys will lift signups because visitors see their own words" scores I:8, C:9, E:10 = 9.0 -- a top-priority test. A button-color swap scores ~I:2, C:2, E:10 = 4.7 and gets skipped despite being trivial to build.

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. Document after: raw numbers, confidence interval, learnings, next steps

See testing-methodology.md (references/testing-methodology.md) when prioritizing or scoring a backlog -- per-axis ICE scoring rubrics, a worked prioritization table, and the weighted-ICE variant.

6. A/B Testing Methodology

Core concept: Run controlled experiments comparing page versions with proper statistical rigor, so results reflect reality rather than random noise.

Why it works: Without rigor you can't distinguish real improvements from random variation -- peeking, undersized samples, and ignored practical significance all manufacture false winners.

Key insights:

• Calculate required sample size BEFORE starting (baseline rate, minimum detectable effect, 80% power, 95% significance)
• Run at least one full business cycle (1-2 weeks), covering weekdays AND weekends
• Never peek at results and stop early -- it dramatically inflates false positives
• Practical significance matters: a statistically significant 0.1% lift isn't worth implementation complexity
• Use multivariate only with 100k+ monthly visitors on a proven winning page
• Promote winners to the new control; a failed test that teaches you something beats a win you don't understand

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]"
• Document learnings: Test, Hypothesis, Result, Learning, Applicable to

Reporting rule: Decide sample size and duration up front, then report whatever the pre-set test returns -- never stop early on a peeked "winner," rerun a test until it yields the answer you want, or bury an inconclusive result. (This is the one honest-reporting constraint for the whole methodology.)

Common Mistakes

Quick Diagnostic

Audit any landing page or conversion flow:

Further Reading

For the complete CRE Methodology(TM), detailed case studies, and advanced techniques:

• "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 cofounders of Conversion Rate Experts, the agency whose CRE Methodology has doubled the sales of many leading websites -- clients include Google, Apple, Amazon, Facebook, and Dropbox -- and earned a Queen's Award for Enterprise (Innovation). Blanks holds a PhD and led usability teams at Hewlett-Packard; Jesson's background is direct-response marketing. Their book Making Websites Win distills the methodology into a repeatable, evidence-based process.

---

Supporting file: references/COPYWRITING.md

Persuasive Copywriting for CRO

Evidence-based copywriting principles. Write as much as it takes to communicate your entire sales message—but not one word more.

Headlines

The headline's job: Get visitors to read the next line.

Headline Formulas That Work

Problem-agitate-solve: "Tired of [problem]? [Solution] lets you [benefit]."

Specificity wins: Bad: "Improve your conversion rate" Good: "How we increased conversions by 363%"

News angle: "[X] facts about [topic] you were never told"

How-to: "How to [achieve result] without [common pain]"

Question: "What's stopping your website from converting?"

Headline Testing Priority

1. Value proposition clarity
2. Specific numbers/results
3. Audience targeting
4. Urgency/timeliness
5. Emotional hook

Body Copy Principles

Length

Write as much as it takes to:

• Communicate the complete sales message
• Address all major objections
• Provide sufficient proof

Long copy works when visitors are:

• Unfamiliar with product category
• Making a high-commitment decision
• Comparing alternatives

Short copy works when:

• Brand is well-known
• Product is simple/commoditized
• Visitors are already convinced

Structure

Lead with benefits, not features Feature: "256GB storage" Benefit: "Never delete another photo"

Use specific numbers Weak: "Thousands of customers" Strong: "47,832 businesses trust us"

Write for scanners

• Subheadings that tell the story alone
• Bold key phrases
• Bullet points for multiple items
• Short paragraphs (2-4 sentences)

Voice

Clarity over cleverness No reader is too sophisticated for simple sentences.

Active voice Bad: "Your conversion rate will be improved" Good: "We'll improve your conversion rate"

"You" focus Count "you" vs. "we" in your copy. Visitors care about themselves.

Circle adjectives and adverbs Replace vague modifiers with specific facts: Bad: "incredibly fast delivery" Good: "delivery in 2 hours or less"

Proof Elements

Hierarchy of proof (strongest to weakest)

1. Specific results with context "Increased revenue by $2.4M in 6 months"

2. Named testimonials with photos Real people, real companies, specific outcomes

3. Case studies Problem → Solution → Results format

4. Statistics and data Industry benchmarks, research findings

5. Logos and badges Client logos, media mentions, certifications

6. Generic testimonials Unnamed quotes (weakest form)

Testimonial Best Practices

Include specifics: Bad: "Great product!" Good: "Increased our conversion rate from 2.1% to 4.7% in 3 weeks"

Address objections: Choose testimonials that counter specific fears

Match the audience: B2B visitors want testimonials from similar companies/roles

Use photos: Real photos > stock photos > no photos

Calls-to-Action

CTA Copy

Benefit-oriented: Bad: "Submit" Good: "Get my free report"

Reduce perceived commitment: "Start free trial" vs. "Sign up" "See pricing" vs. "Buy now"

Match button to promise: If page promises "10 ways to improve X", CTA should be: "Show me the 10 ways" not "Learn more"

CTA Placement

• Above the fold (for aware visitors)
• After each major section
• At moment of peak interest
• Sticky/floating for long pages

CTA Testing Ideas

1. Benefit vs. action language
2. Commitment level (free vs. buy)
3. Urgency elements
4. Size and color (test AFTER copy)
5. Number of CTAs per page

Common Copywriting Mistakes

1. Features without benefits Always answer "So what?"

2. Vague claims "Best in class" → "Rated #1 by [source]"

3. Talking about yourself Reframe everything around the visitor

4. Burying the lead Put most important information first

5. Assuming knowledge Explain industry jargon

6. Missing objections Address hesitations head-on

7. Weak proof Generic testimonials, no specifics

8. Unclear next step Always make the action obvious

---

Supporting file: references/OBJECTIONS.md

Objection/Counter-Objection (O/CO) Framework

The core CRE technique for increasing conversions. Don't guess objections—research them. Then systematically counter each one.

The O/CO Table

Create a two-column table:

How to Discover Objections

Primary Sources (Direct from visitors)

Exit surveys (Qualaroo, Hotjar, etc.)

• "What's preventing you from signing up today?"
• "What questions do you still have?"
• "What would make this decision easier?"

Live chat logs

• Search for patterns in "but", "however", "worried about"
• Note recurring hesitations

Support tickets

• Pre-purchase questions reveal objections
• "Canned responses" are goldmines of tested counter-objections

Sales call recordings

• What objections do salespeople hear repeatedly?
• What counter-arguments work?

"Refer a friend" messages

• How do customers describe you to friends?
• What do they emphasize? What do they downplay?

Secondary Sources

Reviews (yours and competitors')

• Negative reviews = unaddressed objections
• Positive reviews = effective counter-objections

Social media mentions

• Reddit, Twitter threads about your category
• Forums where your audience discusses alternatives

Competitor analysis

• What objections do competitors address?
• What proof do they emphasize?

Types of Objections

Explicit objections

Easy to address—visitors state them clearly:

• "Too expensive"
• "No free trial"
• "Requires credit card"

Implicit objections

Harder to identify—visitors won't admit them:

• "I'm lazy and don't want to do the work"
• "I'm not sure I'll follow through"
• "This seems too good to be true"

Technique for implicit objections: Use "CO Only" approach—address the objection without stating it.

Bad: "Worried you're too lazy to learn a language?" Good: "Let the audio do the work for you."

The "Big 5" Universal Objections

Most products face some version of:

1. Trust: "Why should I believe you?"
2. Price: "Is it worth the money?"
3. Fit: "Will it work for MY situation?"
4. Timing: "Why should I act now?"
5. Effort: "How hard will this be?"

Counter-Objection Techniques

For Trust objections

• Specific testimonials (with photos, names, results)
• Media logos ("As seen in...")
• Awards and certifications
• Team credentials
• Years in business, customers served
• Money-back guarantee

For Price objections

• ROI calculators
• Cost comparison (vs. alternatives, vs. not solving problem)
• Payment plans
• Price anchoring (show higher-priced option first)
• Emphasize value, not features

For Fit objections

• Case studies from similar situations
• Segmented landing pages
• "Perfect for [specific audience]" messaging
• FAQ addressing edge cases
• Free trial or sample

For Timing objections

• Limited-time offers (genuine scarcity only)
• Cost of delay
• Seasonal relevance
• Urgency-building statistics

For Effort objections

• "Done for you" framing
• Step-by-step breakdown
• Time estimates ("Set up in 5 minutes")
• Onboarding support
• "System" or "process" language

Placement Strategy

Don't hide objections in FAQ. Address them:

• At point of friction: Credit card objection → right below payment form
• In the flow: As objections naturally arise during reading
• Above the fold: For primary objections
• Multiple times: Different formats (text, video, testimonial)

O/CO Audit Questions

1. What are our visitors' top 5 objections?
2. Which are we NOT addressing on the page?
3. Which are we addressing weakly (no proof)?
4. Are counter-objections placed where objections arise?
5. What counter-objections do competitors use that we don't?

---

Supporting file: references/PERSUASION.md

Persuasion Assets & Psychological Triggers

Your website should be a "proof magnet." Identify, acquire, and display persuasive assets.

Persuasion Assets Audit

Credentials & Authority

• Industry awards
• Certifications
• Media mentions (logo bar)
• Speaking engagements
• Published books/research
• Years in business
• Number of customers/users
• Team credentials/bios
• Patents or proprietary technology

Social Proof

• Customer testimonials (with photos, names, results)
• Video testimonials
• Case studies (problem → solution → results)
• Client logos
• User-generated content
• Review aggregator scores (G2, Trustpilot, etc.)
• Social media followers/engagement
• Community size

Risk Reversal

• Money-back guarantee
• Free trial
• Free samples/demos
• Satisfaction guarantee
• Performance guarantee
• Easy cancellation
• No credit card required

Data & Specificity

• Specific results achieved
• ROI calculations
• Before/after comparisons
• Time-to-value metrics
• Industry benchmarks
• Research/survey data

Process & Methodology

• Named methodology/system
• Step-by-step process visualization
• Behind-the-scenes transparency
• Quality control standards
• Security/privacy certifications

Asset Acquisition Wishlist

If you don't have an asset, plan to acquire it:

Psychological Triggers

Scarcity (Use Ethically)

• Limited time offers (genuine deadlines)
• Limited quantity
• Exclusive access
• Seasonal availability

Warning: Fake scarcity destroys trust. Only use real limitations.

Social Proof

• "Join 50,000+ marketers"
• Real-time activity ("John from NYC just signed up")
• Testimonials at decision points
• Expert endorsements

Authority

• Expert positioning
• Media logos
• Certifications visible
• Specific credentials

Reciprocity

• Free valuable content upfront
• Free tools/calculators
• Generous trial periods
• Helpful support

Commitment/Consistency

• Micro-commitments (email before credit card)
• Progress indicators
• "You're almost there" messaging
• Previous choices displayed

Loss Aversion

• Cost of inaction
• "What you're missing"
• Comparison with competitors' customers
• Before/after contrast

The "Proof Sandwich"

Structure for maximum persuasion:

1. Claim: Make a bold, specific promise
2. Proof: Immediately support with evidence
3. Reinforcement: Add secondary proof

Example: "We increase conversion rates by an average of 47%" (claim) "Here's how we did it for Company X..." (proof) "And here's what their CEO says about working with us..." (reinforcement)

Placement Principles

Above the fold

• Main value proposition
• Primary social proof (logo bar, rating)
• Clear CTA

Throughout the page

• Testimonials at objection points
• Data supporting each claim
• Visual proof (screenshots, photos)

Decision points

• Guarantees near payment
• Trust badges near forms
• Testimonials near CTAs

Bottom of page

• Comprehensive FAQ
• Trust indicators
• Alternative contact options

Asset Display Best Practices

Logo bars

• 5-7 recognizable logos
• Similar visual treatment
• Relevant to target audience

Testimonials

• Photo + Name + Company + Title
• Specific results > vague praise
• Match testimonial to objection

Statistics

• Round numbers seem less credible
• "47,832 customers" > "About 50,000"
• Source your data

Guarantees

• Make them prominent, not hidden
• Explain what happens if claimed
• Reduce perceived risk of claiming

---

Supporting file: references/RESEARCH.md

CRO Research Methods & Tools

Don't guess why visitors don't convert. Use these methods to discover the truth.

Research Framework

Quantitative (What is happening)

• Analytics data
• Heatmaps
• Click tracking
• Funnel analysis
• A/B test results

Qualitative (Why it's happening)

• User surveys
• Customer interviews
• Usability testing
• Session recordings
• Support analysis

Both are essential. Quantitative shows WHERE problems are. Qualitative shows WHY they exist.

Analytics Analysis

Key Reports

Funnel Visualization

• Where do visitors drop off?
• Which steps have highest abandonment?
• Do patterns differ by traffic source?

Landing Page Performance

• Bounce rate by page
• Time on page
• Exit rate vs. bounce rate

Traffic Source Analysis

• Conversion rate by source
• Behavior differences by channel
• Quality vs. quantity of traffic

Device/Browser Analysis

• Mobile vs. desktop conversion
• Browser-specific issues
• Page speed by device

Red Flag Metrics

• Bounce rate > 70% on key pages
• Exit rate spikes at specific steps
• Mobile conversion << desktop (check UX)
• High traffic, low conversion pages
• Long time on checkout pages (confusion)

User Surveys

On-Site Surveys (Hotjar, Qualaroo)

Exit intent surveys:

• "What stopped you from [action] today?"
• "What's the one thing we could change to make you [action]?"

Post-purchase surveys:

• "What almost stopped you from buying?"
• "What convinced you to choose us?"
• "How would you describe [product] to a friend?"

Browsing surveys (trigger after X seconds):

• "What brought you here today?"
• "Is there anything you can't find?"

Email Surveys

New customers (within 7 days):

• "What was your biggest hesitation before buying?"
• "What finally convinced you?"
• "What's one thing we could improve?"

Non-converters (abandoned cart):

• "We noticed you didn't complete your order. What stopped you?"
• Keep it to ONE question for higher response rates

Survey Best Practices

1. Ask ONE question (max 2-3)
2. Open-ended > multiple choice for discovery
3. Time triggers thoughtfully
4. Don't annoy—limit frequency
5. Incentivize for longer surveys

Usability Testing

DIY Testing (5-10 users is enough)

Tasks to test:

1. Find [specific product/information]
2. Complete [primary action]
3. Understand [value proposition]
4. Compare [options/plans]

What to observe:

• Where do users hesitate?
• What do they say aloud?
• What do they click expecting something different?
• What frustrates them?

5-Second Test

Show page for 5 seconds, then ask:

• "What is this page about?"
• "What action should you take?"
• "What company is this?"

Tests clarity of value proposition and hierarchy.

First-Click Testing

Give users a task, record where they click first:

• Is it the right element?
• Do different user types behave differently?

Session Recordings (Hotjar, FullStory)

What to Look For

Rage clicks: Rapid clicking = frustration Dead clicks: Clicking non-clickable elements U-turns: Going back immediately Form abandonment: Which fields cause drop-off Scroll depth: How far do visitors read?

Prioritization

Focus on recordings from:

• High-value pages
• High drop-off points
• Specific user segments (buyers vs. non-buyers)

Heatmaps

Click Heatmaps

• What gets clicked (and what doesn't)?
• Are CTAs getting attention?
• Are non-clickable elements being clicked?

Scroll Heatmaps

• How far do visitors scroll?
• What percentage see key content?
• Where do visitors stop reading?

Move Heatmaps

• Where does attention focus?
• What gets ignored?

Heatmap Insights → Actions

Competitive Analysis

What to Analyze

• Value propositions
• Pricing/positioning
• Social proof used
• Objections addressed
• Risk reversal offers
• Onboarding flows
• Email sequences (sign up!)

Competitive O/CO Mining

1. Read competitor reviews (positive and negative)
2. Note objections customers raise
3. Note what competitors claim as strengths
4. Identify gaps in their approach

Customer Interview Guide

Who to Interview

• Recent buyers (why they bought)
• Recent non-buyers (why they didn't)
• Long-term customers (what keeps them)
• Churned customers (why they left)

Key Questions

Pre-purchase:

• "What triggered you to look for a solution?"
• "What alternatives did you consider?"
• "What almost stopped you from buying?"
• "What convinced you to choose us?"

Post-purchase:

• "What result have you achieved?"
• "What's been harder than expected?"
• "What would you tell a friend about us?"

Interview Tips

1. Let them talk (don't lead)
2. Ask "why" repeatedly (5 Whys)
3. Get specific examples
4. Record for quotes (with permission)
5. Look for patterns across interviews

Research Prioritization

1. Start with analytics (quick, free)
2. Add on-site survey (1 question)
3. Review existing support/chat logs
4. Watch 10-20 session recordings
5. Run 5 usability tests
6. Deep-dive interviews (ongoing)

---

Supporting file: references/funnel-analysis.md

Funnel Analysis Framework

Deep methodology for mapping, analyzing, and optimizing conversion funnels.

Table of Contents

1. Funnel Philosophy (#funnel-philosophy)
2. Mapping Your Funnel (#mapping-your-funnel)
3. Blocked Arteries (#blocked-arteries)
4. Missing Links (#missing-links)
5. Industry Funnel Patterns (#industry-funnel-patterns)
6. Funnel Prioritization Framework (#funnel-prioritization-framework)
7. Funnel Visualization (#funnel-visualization)
8. Funnel Optimization Checklist (#funnel-optimization-checklist)
9. Advanced: Multi-Touch Attribution (#advanced-multi-touch-attribution)

---

Funnel Philosophy

A funnel isn't just a visualization—it's a diagnostic tool. Every business has a funnel, whether they've mapped it or not. The question is: where is it leaking?

Core insight: Most businesses focus on the top of the funnel (traffic) when the biggest wins are often in the middle (conversion) or bottom (retention/expansion).

---

Mapping Your Funnel

The Basic Funnel Structure

Awareness → Interest → Consideration → Intent → Evaluation → Purchase → Retention → Advocacy

Simplified Business Models

E-commerce:

Visit → View Product → Add to Cart → Begin Checkout → Complete Purchase → Repeat Purchase

SaaS:

Visit → Signup → Onboard → Activate → Engage → Convert (Paid) → Retain → Expand

Lead Generation:

Visit → Lead Magnet → MQL → SQL → Opportunity → Close → Upsell

Content/Media:

Visit → Read/View → Subscribe → Engage → Share → Become Regular

Identifying All Steps

List every step a customer takes from first touch to desired outcome:

1. Acquisition touchpoints - Where do they first hear about you?
2. Engagement actions - What do they do before converting?
3. Conversion moments - Where do they make commitments?
4. Value realization - When do they get what they came for?
5. Expansion opportunities - How do they become more valuable?

---

Blocked Arteries

A "blocked artery" is a high-traffic path with underperformance—a point where lots of visitors enter but few progress.

How to Find Blocked Arteries

Step 1: Map traffic volume at each stage

Homepage:         10,000 visitors
Product page:     3,000 visitors (30% of traffic)
Add to cart:      600 visitors (20% of product viewers)
Checkout start:   300 visitors (50% of cart adds)
Purchase:         150 visitors (50% of checkout starts)

Step 2: Calculate conversion at each step

Homepage → Product:     30%
Product → Cart:         20% ← Potential blocked artery
Cart → Checkout:        50%
Checkout → Purchase:    50%

Step 3: Compare to benchmarks

Step 4: Prioritize by impact

Impact = Traffic Volume × Conversion Gap

Cart → Checkout: 600 × (0.65 - 0.50) = 90 potential conversions
Checkout → Purchase: 300 × (0.75 - 0.50) = 75 potential conversions

Common Blocked Arteries

---

Missing Links

A "missing link" is an absent or underutilized funnel stage that leaves value on the table.

Common Missing Links

Pre-purchase:

• No retargeting for abandoned visitors
• No email capture before purchase intent
• No comparison tools for researchers
• No social proof at decision points

Purchase:

• No upsell/cross-sell offers
• No subscription/bundle options
• No referral program at purchase
• No installation/setup guidance

Post-purchase:

• No email onboarding sequence
• No check-in at key milestones
• No expansion offers at right time
• No advocacy program for happy customers

Missing Link Audit

Cross-Sell Mapping

Map products that naturally pair together:

---

Industry Funnel Patterns

E-commerce Funnels

Standard:

Visit → Browse → Product → Cart → Checkout → Purchase

Enhanced:

Visit → Browse → Product → Wishlist/Email → Retarget → Cart → Checkout → Upsell → Purchase → Post-purchase email → Review request → Repeat purchase

Key metrics:

• Cart abandonment rate (benchmark: 70%)
• Checkout abandonment rate (benchmark: 25%)
• Repeat purchase rate (benchmark: 25-40%)

SaaS Funnels

Standard:

Visit → Trial/Freemium → Activation → Engagement → Conversion

Enhanced:

Visit → Content → Lead magnet → Nurture → Trial → Onboarding → Activation → Engagement → Conversion → Onboarding (paid) → Expansion → Advocacy

Key metrics:

• Trial-to-paid conversion (benchmark: 3-5% freemium, 15-25% free trial)
• Activation rate (varies by product)
• Expansion revenue % (benchmark: 30%+ of revenue)

Lead Generation Funnels

Standard:

Visit → Form → Lead → Sales contact → Opportunity → Close

Enhanced:

Visit → Lead magnet → Nurture → Scorecard/Quiz → MQL → SDR qualify → Demo → SQL → Proposal → Close → Onboarding → Expansion

Key metrics:

• Lead-to-MQL conversion (benchmark: 20-30%)
• MQL-to-SQL conversion (benchmark: 30-50%)
• SQL-to-close rate (benchmark: 20-40%)

Subscription/Membership Funnels

Standard:

Visit → Free content → Subscribe → Retain

Enhanced:

Visit → Free content → Email opt-in → Free trial → Subscribe → Onboard → Engage → Retain → Annual upgrade → Advocacy

Key metrics:

• Free-to-paid conversion (benchmark: 2-5%)
• Monthly churn rate (benchmark: 3-7%)
• Annual vs. monthly mix (benchmark: 30%+ annual)

---

Funnel Prioritization Framework

Calculate Opportunity Value

For each potential improvement:

Opportunity = (Current Volume) × (Conversion Gap) × (Revenue per Conversion)

Example:

Current: 1,000 visitors, 2% conversion, $100/conversion = $2,000 revenue
Potential: 1,000 visitors, 3% conversion, $100/conversion = $3,000 revenue
Opportunity value: $1,000/month = $12,000/year

Prioritization Matrix

The 80/20 Rule in Funnels

Typically:

• 80% of revenue comes from 20% of the funnel stages
• 80% of drop-off happens at 20% of the steps
• 80% of improvement potential is in 20% of the pages

Focus ruthlessly on the high-impact stages before optimizing everything.

---

Funnel Visualization

Basic Funnel Chart

┌─────────────────────────────────────────┐ 10,000
│            Website Visits               │
├───────────────────────────────┐         │ 3,000 (30%)
│      Product Page Views       │
├─────────────────────┐         │         │ 600 (20%)
│   Add to Cart       │
├───────────────┐     │         │         │ 300 (50%)
│  Checkout     │
├─────────┐     │     │         │         │ 150 (50%)
│ Purchase│
└─────────┘

Leakage Analysis

At each stage, map where users go instead:

Product Page (3,000 visitors)
├─→ Add to Cart: 600 (20%)
├─→ Exit site: 1,500 (50%)
├─→ Browse other products: 600 (20%)
├─→ Check reviews/FAQ: 200 (7%)
└─→ Contact support: 100 (3%)

Insight: 50% exit from product page—that's the primary leak to investigate.

---

Funnel Optimization Checklist

Before Optimizing

• Have you mapped the complete funnel?
• Do you have baseline conversion rates at each stage?
• Have you identified the biggest blocked arteries?
• Have you audited for missing links?
• Do you know your industry benchmarks?
• Have you calculated opportunity values?

During Optimization

• Are you testing bold changes, not tweaks?
• Are you measuring the right metrics?
• Are you waiting for statistical significance?
• Are you documenting learnings?

After Optimization

• Did conversion improve at the target stage?
• Did downstream metrics also improve?
• Did any metrics unexpectedly decrease?
• Can this learning apply to other funnels?

---

Advanced: Multi-Touch Attribution

The Problem

Customers don't convert in a straight line. They might:

1. See a Facebook ad
2. Google your brand
3. Read a blog post
4. Leave
5. Get retargeted
6. Return via email
7. Convert

Which touchpoint gets credit?

Attribution Models

Practical Recommendation

1. Start with last-touch (simplest)
2. Add first-touch to understand acquisition
3. Graduate to position-based for balanced view
4. Only use data-driven with sufficient volume

---

Supporting file: references/testing-methodology.md

CRO Testing Methodology

Deep-dive into experiment design, statistical rigor, and test prioritization from the CRE Methodology.

Table of Contents

1. The Philosophy of Bold Testing (#the-philosophy-of-bold-testing)
2. A/B Testing vs. Multivariate Testing (#ab-testing-vs-multivariate-testing)
3. Statistical Significance (#statistical-significance)
4. ICE Prioritization Framework (#ice-prioritization-framework)
5. Test Documentation (#test-documentation)
6. When Tests Fail (#when-tests-fail)
7. CRO Team Dynamics (#cro-team-dynamics)
8. Testing Platform Comparison (#testing-platform-comparison)

---

The Philosophy of Bold Testing

Why "Meek Tweaks" Fail

Most A/B tests fail because they're too small to detect. Button color changes, minor copy tweaks, and micro-optimizations suffer from:

1. Insufficient sample size - Small changes require massive traffic to reach significance
2. Interaction effects - Minor changes get lost in noise
3. Opportunity cost - Time spent on 2% wins could find 200% wins

Rule: Test big changes that could double conversion, not small changes that might move it 5%.

The 10x Mindset

Before any test, ask: "Could this 10x our results?" If not, is it worth testing?

• Worth testing: Complete page redesign, new value proposition, fundamentally different offer
• Not worth testing: Button color, font size, image swap

---

A/B Testing vs. Multivariate Testing

A/B Testing (Split Testing)

Compare two (or more) complete versions against each other.

When to use:

• You have a hypothesis about a major change
• Traffic is limited
• You're comparing conceptual approaches

Multivariate Testing (MVT)

Test multiple elements simultaneously to find optimal combination.

When to use:

• You have a winning page to optimize further
• High traffic (100k+ monthly visitors)
• Clear, isolated elements to test

Traffic Requirements

A/B Test:

Minimum sample per variant = 250-500 conversions
For 2 variants with 5% conversion: 10,000-20,000 visitors needed

Multivariate Test:

Combinations = (Options for Element 1) × (Options for Element 2) × ...
Example: 3 headlines × 3 images × 2 CTAs = 18 combinations
Each combination needs 250+ conversions = 90,000+ conversions total

Recommendation: Start with A/B tests. Only move to MVT when you have:

• Proven winning page concept
• 100k+ monthly visitors
• Mature testing program

---

Statistical Significance

What It Means

Statistical significance tells you: "How likely is this result due to chance vs. a real effect?"

Industry standard: 95% confidence (p-value < 0.05)

• 95% confident the difference is real
• 5% chance it's random noise

Common Mistakes

1. Peeking and stopping early

Checking results daily and stopping when you see a winner leads to false positives.

• Wrong: "We're at 95% confidence after 3 days—ship it!"
• Right: Pre-determine sample size and test duration; don't stop early

2. Calling tests with insufficient data

3. Ignoring practical significance

A statistically significant 0.1% lift isn't worth implementation complexity.

4. Multiple comparison problem

Testing 20 variants? One will show "significance" by chance alone.

Sample Size Calculation

Before testing, calculate required sample size:

Inputs needed:

• Baseline conversion rate
• Minimum detectable effect (MDE) you care about
• Statistical power (typically 80%)
• Significance level (typically 95%)

Rule of thumb:

For 5% baseline, 20% relative lift detection:
~25,000 visitors per variant needed

For 5% baseline, 50% relative lift detection:
~4,000 visitors per variant needed

Key insight: The smaller the effect you want to detect, the more traffic you need. This is why bold changes are better—they're detectable with less traffic.

Test Duration

Minimum test duration:

• At least 1 full business cycle (typically 1-2 weeks)
• Include weekdays AND weekends
• Account for seasonality

Why?

• Visitor behavior differs by day of week
• Friday buyers differ from Monday researchers
• Monthly cycles affect B2B especially

---

ICE Prioritization Framework

Prioritize test ideas using ICE scores:

Impact (1-10)

"If this wins, how big would the impact be?"

Confidence (1-10)

"How confident are we this will work?"

Ease (1-10)

"How easy is this to implement and test?"

ICE Score Calculation

ICE Score = (Impact + Confidence + Ease) / 3

Or weighted:

ICE Score = (Impact × 2 + Confidence × 1.5 + Ease × 1) / 4.5

Sample Prioritization

---

Test Documentation

Before the Test

Document:

1. Hypothesis: "If we [change X], then [metric Y] will improve because [reason based on research]"
2. Primary metric: One metric that determines winner
3. Secondary metrics: Additional metrics to monitor
4. Guardrail metrics: Metrics that shouldn't decrease
5. Sample size requirement
6. Test duration
7. Traffic allocation

After the Test

Document:

1. Results: Raw numbers, conversion rates, confidence interval
2. Statistical significance: p-value, confidence level
3. Practical significance: Is the lift worth implementing?
4. Learnings: What does this teach us about our customers?
5. Next steps: Ship winner, iterate, or abandon?

Learnings Database

Every test should add to organizational knowledge:

---

When Tests Fail

Types of "Failure"

1. No winner (inconclusive)

• Sample size too small
• Effect size too small to detect
• Test needed to run longer

2. Control wins

• New version is worse
• Hypothesis was wrong
• Still a learning!

3. Technical problems

• Tracking broke
• Experience differed from plan
• Sample contamination

What to Do

1. Document the learning - "We learned customers prefer X"
2. Investigate why - Go back to research
3. Don't give up on the page - The opportunity exists, you just haven't found the solution
4. Try a bolder change - Maybe the change wasn't big enough

Critical insight: A failed test that teaches you something is more valuable than a winning test you don't understand.

---

CRO Team Dynamics

Roles in a CRO Program

Getting Stakeholder Buy-In

Common objections:

Building credibility:

1. Start with quick wins (high-traffic pages, obvious problems)
2. Document and share learnings widely
3. Quantify impact in revenue terms
4. Build testing into the culture, not just a project

Test Velocity

Goal: Increase valid tests per month over time.

---

Testing Platform Comparison

Key Features to Look For

• Visual editor for non-developers
• Robust statistical engine
• Segment targeting
• Integrations (analytics, CDP, etc.)
• Flicker prevention
• Mutually exclusive experiments