Cro Optimization

CRO Optimization

Purpose

Analyze a landing page and deliver a comprehensive CRO audit with specific, actionable recommendations to maximize conversions.

---

Execution Logic

Check $ARGUMENTS first to determine execution mode:

If $ARGUMENTS is empty or not provided:

Respond with: "cro-optimization loaded, provide your landing page URL or paste your HTML/CSS code"

Then wait for the user to provide their landing page in the next message.

If $ARGUMENTS contains content:

Proceed immediately to Task Execution (skip the "loaded" message).

---

Task Execution

When landing page is available (either from initial $ARGUMENTS or follow-up message):

1. MANDATORY: Read Reference Files FIRST

BLOCKING REQUIREMENT — DO NOT SKIP THIS STEP

Before doing ANYTHING else, you MUST use the Read tool to read ALL three reference files:

Read: ./references/cro_principles.md
Read: ./references/landing_page_patterns.md
Read: ./references/element_audit_framework.md

What you will find:

• cro_principles.md: 13 core CRO principles with detection criteria and fix patterns
• landing_page_patterns.md: Real patterns from high-converting pages (ClickUp, Notion, Stripe, Apple, etc.) organized by category
• element_audit_framework.md: Systematic framework for auditing HTML elements, CTAs, forms, and visual hierarchy

DO NOT PROCEED to Step 2 until you have read all files and have the principles, patterns, and audit framework loaded in context.

2. Check for Business Context

Check if FOUNDER_CONTEXT.md exists in the project root.

• If it exists: Read it and use the business context to personalize recommendations (industry, target audience, product type, competitors).
• If it doesn't exist: Proceed with analysis based on page content alone.

3. Fetch and Extract Landing Page

If user provided a URL:

• Use WebFetch to retrieve the landing page content
• Extract and catalog key elements (see Element Extraction below)

If user provided HTML/CSS directly:

• Analyze the provided code directly
• Note any missing context (live styling, images, etc.)

4. Element Extraction

Extract and catalog these elements from the page:

Typography:

• H1 (should be exactly one)
• H2s (section headers)
• Body text samples
• CTA button copy

Visual Structure:

• Above-the-fold content
• Section sequence
• Image/visual placement
• Color scheme and contrast

Conversion Elements:

• Primary CTA (copy, placement, design)
• Secondary CTAs
• Forms (field count, labels)
• Trust signals (logos, testimonials, badges)
• Social proof (metrics, reviews, case studies)

Technical:

• Mobile responsiveness indicators
• Load speed concerns (large images, etc.)

5. Audit Against CRO Principles

For each of the 13 principles in cro_principles.md: 1. Check if the page violates the principle 2. Note specific violations with evidence 3. Determine severity (High/Medium/Low) 4. Draft specific recommendations

Prioritize by impact:

• High: Above-fold clarity, CTA effectiveness, major trust gaps
• Medium: Objection handling, visual hierarchy, scannability
• Low: Minor copy tweaks, nice-to-have additions

6. Compare to High-Converting Patterns

Using landing_page_patterns.md: 1. Identify the most relevant category (B2B SaaS, E-commerce, etc.) 2. Compare page structure to proven patterns 3. Note missing elements that top performers include 4. Identify opportunities to adopt successful patterns

7. Generate Recommendations

For each issue found, provide: 1. What to change — specific element and action 2. Why it matters — principle violated and expected impact 3. How to implement — concrete example or rewrite 4. Priority — High/Medium/Low with reasoning

8. Format and Verify

• Structure output according to Output Format section
• Complete Quality Checklist self-verification
• Ensure recommendations are specific and actionable (not generic advice)

---

Writing Rules

Hard constraints. No interpretation.

Core Rules

• Every recommendation must be specific and actionable
• Include before/after examples for copy changes
• Reference the specific principle violated
• Prioritize by conversion impact, not ease of implementation
• Frame changes as testable hypotheses when possible
• Never recommend changes without explaining the "why"

Analysis Rules

• Audit systematically — don't skip principles
• Note what's working well, not just problems
• Consider the page's apparent target audience
• Account for likely traffic sources
• Distinguish between critical issues and optimizations

Recommendation Rules

• Lead with highest-impact changes
• Group related recommendations together
• Provide specific copy rewrites, not just "make it clearer"
• Include placement suggestions, not just content suggestions
• Consider mobile experience separately

---

Output Format

# CRO Audit Report: [Page Name/URL]

## Executive Summary
[2-3 sentences: Overall assessment, biggest opportunities, expected impact]

---

## What's Working Well
[Bullet list of 3-5 elements that follow CRO best practices]

---

## Critical Issues (Fix First)

### Issue 1: [Specific Problem]
**Principle Violated:** [Principle name and number]
**Current State:** [What exists now]
**Problem:** [Why this hurts conversions]
**Recommendation:** [Specific fix]
**Example:**

BEFORE: [Current copy/element] AFTER: [Recommended copy/element]

**Expected Impact:** [What improvement to expect]

### Issue 2: [Specific Problem]
[Same structure]

---

## High-Impact Optimizations

### Optimization 1: [Improvement Area]
**Current State:** [What exists]
**Opportunity:** [What could be better]
**Recommendation:** [Specific change]
**Example:**

BEFORE: [Current] AFTER: [Recommended]

**Priority:** [High/Medium] — [Reasoning]

[Continue for each optimization]

---

## Section-by-Section Analysis

### Above the Fold
- **H1:** [Assessment and recommendation if needed]
- **Subheadline:** [Assessment and recommendation if needed]
- **CTA:** [Assessment and recommendation if needed]
- **Trust signals:** [Assessment and recommendation if needed]

### [Section Name]
[Analysis and recommendations]

[Continue for each major section]

---

## Quick Wins (Easy Implementations)
1. [Simple change with good impact]
2. [Simple change with good impact]
3. [Simple change with good impact]

---

## Testing Roadmap
1. **Test First:** [Highest impact hypothesis]
2. **Test Second:** [Next priority]
3. **Test Third:** [Following priority]

---

## Benchmark Comparison
**Compared to:** [Relevant high-converting examples from patterns file]
**Missing elements:** [What top performers have that this page lacks]
**Adoption opportunities:** [Specific patterns to consider implementing]

---

References

All three files MUST be read using the Read tool before analysis (see Step 1):

Why all three matter: Principles tell you what's wrong. Patterns show you what good looks like. The audit framework ensures you check everything systematically. Together they produce specific, evidence-based recommendations instead of generic CRO advice.

---

Quality Checklist (Self-Verification)

Before finalizing output, verify ALL of the following:

Pre-Analysis Check

• [ ] I read ./references/cro_principles.md before analyzing
• [ ] I read ./references/landing_page_patterns.md before analyzing
• [ ] I read ./references/element_audit_framework.md before analyzing
• [ ] I have all 13 principles, category patterns, and audit criteria in context

Extraction Check

• [ ] I identified the H1 and assessed its clarity
• [ ] I catalogued all CTAs and their copy
• [ ] I noted social proof elements and placement
• [ ] I evaluated above-the-fold content
• [ ] I assessed the section sequence

Analysis Check

• [ ] Each principle was evaluated against the page
• [ ] Issues cite specific principles violated
• [ ] Recommendations include before/after examples
• [ ] Priority is assigned based on conversion impact
• [ ] I compared to relevant high-converting patterns

Output Check

• [ ] Executive summary captures key findings
• [ ] Critical issues are listed first
• [ ] Every recommendation is specific and actionable
• [ ] Testing roadmap provides clear next steps
• [ ] "What's working well" section is included

If ANY check fails → revise before presenting.

---

Defaults & Assumptions

Use these unless context indicates otherwise:

• Page type: SaaS landing page (most common)
• Traffic temperature: Mixed (cold to warm)
• Primary goal: Signups or demo requests
• Audience: Business decision-makers
• Device split: 60% desktop, 40% mobile
• Conversion definition: Primary CTA click

If the page type is clearly different (e-commerce, content site, etc.), adjust analysis accordingly.

Document any assumptions made in the Executive Summary.

---

CRO Principles Reference

13 non-negotiable principles for high-converting landing pages. Each principle includes detection criteria and fix patterns.

---

1. Clarity Beats Persuasion

If visitors do not instantly understand what the page is about, nothing else matters.

Requirements

Above the fold must answer in under 5 seconds:

• What is this?
• Who is it for?
• Why should I care?

Detection Criteria

• Headline uses jargon or insider language
• Value proposition requires reading subheadline to understand
• Multiple competing messages above the fold
• Clever wordplay prioritized over clarity

Fix Pattern

BEFORE: "Revolutionize your workflow with AI-powered synergy"
AFTER: "Schedule meetings in 30 seconds. No back-and-forth emails."

Rule: One primary action per page. No clever language before clarity.

---

2. Single Core Desire Per Page

High-converting pages sell one outcome, not many features.

Requirements

• One primary emotional payoff
• Secondary benefits only support the core desire
• Feature lists must connect to outcomes

Detection Criteria

• Multiple equal-weight value propositions
• Feature dump without outcome framing
• "And also..." pattern in copy
• More than 3 benefits above the fold

Fix Pattern

BEFORE: "Project management, time tracking, invoicing, team chat, and file storage"
AFTER: "Ship projects 2x faster. Everything else is built around that."

Rule: Identify the single strongest desire and anchor all copy to it.

---

3. Message Match Everywhere

The page must feel like the inevitable continuation of the click that brought the user there.

Requirements

• Headline mirrors ad, email, or link promise
• No new positioning introduced mid-page
• Consistent vocabulary and framing throughout

Detection Criteria

• Headline differs significantly from traffic source promise
• New benefits introduced that weren't in the ad
• Tone shift between source and landing page
• Different product framing mid-page

Fix Pattern

AD: "Get 10 qualified leads per day"
LANDING PAGE HEADLINE: "10 Qualified Leads Per Day, Guaranteed"

NOT: "The Ultimate Sales Solution for Modern Teams"

Rule: If traffic source is known, enforce exact message match between source and headline.

---

4. Objection Handling, Not Hype

CRO removes friction. It does not add excitement.

Top 5 Universal Objections

1. Does this work for someone like me? 2. Is this worth the money? 3. How hard is it to use? 4. What happens if it fails? 5. Can I trust this company?

Requirements

• List objections before writing copy
• Answer objections proactively, not defensively
• Place social proof next to the objection it resolves

Detection Criteria

• No testimonials addressing specific concerns
• FAQ section missing or generic
• Guarantees/refunds buried in footer
• No "who this is for" section

Fix Pattern

OBJECTION: "Is this worth the money?"
PLACEMENT: ROI calculator or savings estimate near pricing
PROOF: Testimonial with specific financial outcome

OBJECTION: "Does this work for my situation?"
PLACEMENT: "Perfect for..." section with specific use cases
PROOF: Testimonial from similar customer type

Rule: Surface and neutralize objections in copy. Never hide them.

---

5. Visual Hierarchy Drives Behavior

Users scan. Structure decides conversion.

Requirements

• One dominant visual focal point above the fold
• Clear hierarchy: Headline > Subheadline > CTA
• White space as a conversion tool
• Eye flow guides toward CTA

Detection Criteria

• Multiple elements competing for attention
• CTA button same visual weight as other elements
• Cluttered above-the-fold area
• No clear reading path

Fix Pattern

HIERARCHY CHECK:
1. What does the eye hit first? (Should be headline or key visual)
2. Where does it go second? (Should be value prop or subheadline)
3. Where does it go third? (Should be CTA)

If any step leads to a non-converting element, restructure.

Rule: Flag layouts where multiple elements compete for attention.

---

6. Cognitive Load Minimization

Every extra decision reduces conversion.

Requirements

• Minimum viable form fields
• Short sentences, simple language
• Progressive disclosure for complex information
• One choice at a time

Detection Criteria

• Form asks for unnecessary information
• Sentences average over 20 words
• Technical jargon without explanation
• Multiple CTAs with equal prominence

Fix Pattern

FORM REDUCTION:
BEFORE: Name, Email, Phone, Company, Role, Team Size, Budget, Timeline
AFTER: Email (everything else can be asked later)

PROGRESSIVE DISCLOSURE:
BEFORE: 2000-word feature explanation
AFTER: "See how it works" expandable section

Rule: Remove anything that requires thinking unless it directly increases confidence.

---

7. Trust Before CTA

You do not earn clicks. You earn confidence.

Requirements

• Trust signals appear before first CTA
• Specific proof, not vague claims
• Logos, numbers, testimonials, guarantees strategically placed

Detection Criteria

• CTA appears before any social proof
• Vague trust language ("trusted by many")
• No third-party validation (G2, Capterra, awards)
• Testimonials without names, photos, or specifics

Fix Pattern

BEFORE: "Trusted by many companies"
AFTER: "Used by 12,347 teams across 42 countries"

BEFORE: [CTA Button]
AFTER: "Join 50,000+ marketers" + [CTA Button] + "No credit card required"

Rule: No CTA without trust reinforcement immediately before or after it.

---

8. Behavioral Triggers That Work

Psychology applied responsibly. No gimmicks.

Effective Triggers

Detection Criteria

• Generic benefit language ("save time", "grow faster")
• Gain framing when loss framing would be stronger
• Fake scarcity or urgency
• Round numbers instead of specific ones

Fix Pattern

GAIN FRAMING: "Get more done"
LOSS FRAMING: "Stop wasting 2 hours every day on tasks AI can do"

GENERIC: "Increase productivity"
SPECIFIC: "Teams using [Product] complete sprints 37% faster"

Rule: Prefer concrete, loss-framed, and specific language.

---

9. Friction Audit Framework

Every section must justify its existence.

Section Justification Test

Ask of each section: 1. Does this reduce doubt? 2. Does this increase desire? 3. Does this guide action?

If none apply, remove it.

Detection Criteria

• Sections that don't serve conversion goal
• Redundant information across sections
• "Nice to have" content that adds length
• Company history/mission before value proposition

Fix Pattern

AUDIT EACH SECTION:
[Hero] → Increases desire ✓
[Features] → Reduces doubt ✓
[Team Bios] → Does this reduce doubt for THIS product? Often ✗
[Blog Preview] → Guides action to conversion? Usually ✗

REMOVE: Team bios, blog previews, company history (unless they directly address objections)

Rule: Perform section-by-section friction audit. Remove non-converting elements.

---

10. CTA Discipline

CTAs fail because they ask too much, too soon.

CTA Commitment Ladder

Detection Criteria

• High-commitment CTA for cold traffic
• "Sign Up" or "Submit" as CTA copy
• CTA repeated without new information between
• Multiple CTAs with different asks competing

Fix Pattern

BEFORE: "Sign Up" (vague, high commitment)
AFTER: "Start your free trial" (clear, lower commitment)

BEFORE: "Submit" (generic, friction-inducing)
AFTER: "Get my free report" (benefit-focused, specific)

CTA PLACEMENT RULE:
Repeat CTA only AFTER adding new trust/value information

Rule: Match CTA commitment level to user awareness stage.

---

11. Scannability Is Mandatory

If it cannot be skimmed, it will not be read.

Requirements

• Short paragraphs (3 lines max)
• Bullet points over prose for features/benefits
• Section headers tell a story when read alone
• Bold key phrases for scanning

Detection Criteria

• Paragraphs over 4 lines
• No subheadings for 300+ words
• Headers that don't communicate value when read alone
• Wall of text anywhere on page

Fix Pattern

BEFORE: "Our platform provides comprehensive solutions for managing
your entire workflow including task management, time tracking, team
collaboration, file sharing, and reporting capabilities that help
teams of all sizes work more efficiently."

AFTER:
**Everything your team needs:**
- Task management that actually gets used
- Time tracking without the spreadsheets
- Collaboration that doesn't require another meeting

Rule: Optimize for skimming first, deep reading second.

---

12. Conversion Momentum

Each section should make the next action feel easier.

Momentum Building Pattern

1. Start with low-risk agreement (acknowledge their problem) 2. Build confidence gradually (proof, then more proof) 3. End with urgency that feels earned (after value is established)

Detection Criteria

• Page starts with hard sell
• Urgency appears before value is established
• No confidence-building between sections
• Abrupt transition to CTA

Fix Pattern

MOMENTUM SEQUENCE:
1. "Tired of [problem]?" (Agreement - low risk)
2. "Here's why it happens" (Education - builds trust)
3. "Here's the fix" (Solution - increases desire)
4. "Here's proof it works" (Testimonials - reduces doubt)
5. "Here's what you get" (Offer - clarifies value)
6. "Join 10,000+ who fixed this" (CTA - feels earned)

Rule: Each section should logically prepare the user for the next step.

---

13. Data Over Opinions

CRO is empirical, not aesthetic.

Requirements

• Recommendations should be testable
• Avoid absolute claims
• Provide hypotheses, not certainties
• Track and measure impact

Framing Pattern

ABSOLUTE: "This headline will convert better"
HYPOTHESIS: "Test this headline against current. Expected: 15-20% lift based on clarity improvement"

ABSOLUTE: "Remove this section"
HYPOTHESIS: "This section may cause friction. Test removal against control"

Rule: Frame changes as testable hypotheses. Provide expected impact and reasoning.

---

Quick Reference: Principle Violations by Symptom

Element Audit Framework

Systematic framework for analyzing and optimizing landing page elements. Use this to audit HTML/CSS structure and provide specific recommendations.

---

Element Extraction Checklist

When analyzing a landing page, extract and evaluate these elements:

Typography Elements

Visual Elements

Interactive Elements

---

H1 Audit Criteria

Clarity Test

Score each criterion (0-2 points):

• [ ] Answers "What is this?" (0-2)
• [ ] Answers "Who is it for?" (0-2)
• [ ] Answers "Why should I care?" (0-2)
• [ ] Uses simple language (no jargon) (0-2)
• [ ] Under 10 words (0-2)

Score interpretation:

• 8-10: Strong H1
• 5-7: Needs refinement
• 0-4: Rewrite required

H1 Patterns That Convert

Outcome-focused:

"[Achieve outcome] without [pain point]"
Example: "Ship projects faster without the chaos"

Problem-solution:

"Stop [problem]. Start [solution]."
Example: "Stop losing deals. Start closing them."

Quantified benefit:

"[Specific number] [outcome] in [timeframe]"
Example: "10 qualified leads per day in 30 days"

Replacement:

"[Product category] that actually [works/delivers]"
Example: "A CRM that salespeople actually use"

H1 Anti-Patterns to Flag

---

CTA Audit Criteria

Button Copy Evaluation

Strong CTA patterns:

[Action verb] + [What they get]
- "Get your free report"
- "Start my free trial"
- "See how it works"
- "Claim your discount"

Weak CTA patterns to flag:

- "Submit" (generic, no value)
- "Sign Up" (commitment, no benefit)
- "Learn More" (vague, low intent)
- "Click Here" (meaningless)
- "Get Started" (okay, but could be stronger)

CTA Placement Checklist

• [ ] Visible above the fold
• [ ] Appears after trust signal
• [ ] Repeated after new value information
• [ ] Not competing with other CTAs
• [ ] Sufficient contrast from background
• [ ] Adequate whitespace around it

CTA Commitment Ladder

Match CTA to user awareness:

---

Form Audit Criteria

Field Necessity Test

For each field, ask: 1. Do we need this to deliver value? (Yes/No) 2. Can we get this later? (Yes/No) 3. Does this increase or decrease trust? (Increase/Decrease/Neutral)

If answers are No, Yes, Decrease → Remove the field

Field Count Benchmarks

Form Friction Reducers

• [ ] "No credit card required" near submit
• [ ] Privacy assurance near email field
• [ ] Social login option (Google, LinkedIn)
• [ ] Progress indicator for multi-step
• [ ] Inline validation (not just on submit)

---

Social Proof Audit

Types by Strength

Testimonial Quality Checklist

• [ ] Real name (not just initials)
• [ ] Real photo (not stock)
• [ ] Role/company
• [ ] Specific outcome or metric
• [ ] Addresses a likely objection
• [ ] Length appropriate (2-4 sentences)

Social Proof Placement Rules

1. Logo bar: Immediately after hero 2. Testimonials: Next to features they validate 3. Metrics: Near CTAs to reduce risk perception 4. Ratings: Trust section or footer 5. Case studies: Mid-page, after features

---

Trust Signal Audit

Trust Element Checklist

• [ ] Security badges (SSL, payment security)
• [ ] Compliance certifications (SOC 2, GDPR, HIPAA)
• [ ] Third-party ratings/reviews
• [ ] Money-back guarantee
• [ ] Customer count or metrics
• [ ] Partner/integration logos
• [ ] Press/media logos
• [ ] Industry awards

Trust Signal Placement

---

Visual Hierarchy Audit

Eye Flow Test

Trace the natural eye path on the page: 1. Where does the eye land first? 2. Where does it go second? 3. Where does it go third?

Ideal flow: Headline → Value prop → CTA

Hierarchy Violations to Flag

• [ ] Multiple elements with same visual weight
• [ ] CTA less prominent than decorative elements
• [ ] Important info in low-contrast areas
• [ ] No clear focal point above the fold
• [ ] Text competing with busy background

Color Contrast Checks

• [ ] CTA button stands out from background
• [ ] Text readable on all backgrounds
• [ ] Links distinguishable from body text
• [ ] Form fields clearly defined

---

Mobile Audit Checklist

Above Fold (Mobile)

• [ ] H1 visible without scrolling
• [ ] CTA visible without scrolling
• [ ] Text readable without zooming
• [ ] Touch targets 44px minimum
• [ ] No horizontal scroll required

Mobile-Specific Issues

---

Page Speed Impact

Critical Metrics

Common Speed Issues to Flag

• [ ] Uncompressed images
• [ ] No lazy loading
• [ ] Render-blocking scripts
• [ ] Too many fonts
• [ ] No image CDN
• [ ] Large JavaScript bundles

---

Output Format for Element Audit

When auditing elements, structure findings as:

## [Element Type] Audit

### Current State
[Description of current implementation]

### Issues Found
1. [Specific issue] - [Principle violated]
2. [Specific issue] - [Principle violated]

### Recommendations
1. [Specific change] - [Expected impact]
2. [Specific change] - [Expected impact]

### Priority
[High/Medium/Low] - [Reasoning]

High-Converting Landing Page Patterns

Real patterns extracted from top-performing landing pages across categories. Use these as benchmarks and inspiration.

---

Category: B2B SaaS - Productivity

ClickUp Pattern

What works:

• Headline directly addresses core problem: "Replace all your software"
• Dual CTAs with friction reducer: "Get started. It's FREE" + "Free forever. No credit card"
• ROI quantification prominent: "384% ROI, $3.9M revenue gains, 92,400 hours saved"
• Competitor comparison pages linked (vs. Monday, Notion, Asana)
• Enterprise trust badges near final CTA: SOC 2, ISO 27001, GDPR, HIPAA

Key elements:

ABOVE FOLD:
- Problem/solution headline
- "Free forever" friction reducer
- No form - direct to app signup

TRUST STACK:
- "10 million+ teams"
- "Backed by 100+ awards"
- Forrester ROI report link

CTA STRATEGY:
- Primary: "Get started. It's FREE"
- Section-specific: "Explore solution →"
- Feature deep-dives: "Learn More"

Notion Pattern

What works:

• Headline clarity: "One workspace. Zero busywork"
• Dual-path CTAs: "Get Notion free" (self-serve) + "Request a demo" (enterprise)
• Early logo bar with recognizable brands (Figma, OpenAI, Vercel)
• Quantified proof: "Over 100M users worldwide", "#1 knowledge base 3 years (G2)"
• Cost calculator comparing alternative tools

Key elements:

ABOVE FOLD:
- Benefit-driven headline (outcome, not feature)
- Two CTAs serving different user intents
- No form on homepage

SOCIAL PROOF LAYERS:
1. Logo bar (immediate credibility)
2. Statistics (scale proof)
3. Video testimonials (emotional proof)
4. Case studies (deep proof)

OBJECTION HANDLING:
- "Is it worth switching?" → Cost calculator
- "Can it replace my tools?" → "Solve problems with one tool" testimonial

Linear Pattern

What works:

• Developer-focused design: clean, dark theme, technical aesthetic
• Dual value props: "Purpose-built for planning and building products"
• Integration signals: MCP with Claude/Cursor (AI-native positioning)
• Multiple product screenshots showing actual interface

Key elements:

POSITIONING:
- "Purpose-built for product development"
- "Designed to move fast"
- "Crafted to perfection"

DEVELOPER TRUST:
- Git workflow integration prominent
- API/developer documentation linked
- 100+ integrations mentioned

---

Category: B2B SaaS - Sales/Outreach

Instantly.ai Pattern

What works:

• Outcome-focused headline: "Find, Contact & Close Your Ideal Clients"
• Aggressive friction reduction: "No credit card required" + "Free leads included"
• Early testimonials with specific results: "2-5 meetings every day"
• Quantified social proof: 4.8 rating from 3,838 reviews, 40,000+ customers

Key elements:

ABOVE FOLD:
- Action verb headline (Find, Contact, Close)
- Dual CTAs: "START FOR FREE" + "Book a demo"
- Trust badges immediately visible

PROOF STRATEGY:
- G2-style ratings: 9.7/10 for support
- Specific outcome claims: "16 appointments"
- "Wall of Love" testimonial section

OBJECTION HANDLING:
- Cost → Free tier, no credit card
- Complexity → "Super easy to use" testimonial
- Results → Specific meeting metrics
- Support → 9.7/10 rating emphasized

Breakcold Pattern

What works:

• AI-native positioning: "The AI-Native CRM that Automates the Boring Part"
• Pain-point headline addressing tedium
• Modern design signals premium positioning
• Live chat (Crisp) for immediate support

Key elements:

POSITIONING:
- "Automates the boring part" = outcome-focused
- AI-native = modern/cutting-edge signal

DESIGN APPROACH:
- Premium typography (Inter, Manrope, Satoshi)
- Design-forward = enterprise-ready signal

---

Category: B2B SaaS - Scheduling

Calendly Pattern

What works:

• Free positioning prominent in title
• Integration signals (Chrome, Firefox, Safari, Google Play)
• Clean, professional color scheme (#0B3558, #006BFF)
• Progressive disclosure - explore without commitment

Key elements:

TRUST SIGNALS:
- Browser/platform integrations
- GDPR/privacy compliance signals
- Professional but approachable design

FRICTION REDUCTION:
- "Free" in page title
- Expandable sections for details
- No aggressive form capture

---

Category: E-commerce Platform

Shopify Pattern

What works:

• Dynamic headline rotation creates engagement
• Massive social proof: "$1,000,000,000,000 in sales on Shopify"
• Conversion claim: "Shopify Checkout converts 15% higher"
• Scale range: solo sellers to enterprise (Mattel, Gymshark)
• Capital offering addresses cash flow objection

Key elements:

HEADLINE STRATEGY:
- Rotating aspirational headlines
- "Dream big, build fast, grow far"

PROOF AT SCALE:
- Trillion-dollar GMV
- "150M+ high-intent shoppers"
- "4000+ world-class developers"

OBJECTION HANDLING:
- Scalability → Examples from solo to enterprise
- Cost/cash → "$5B loaned, 0% equity" capital program
- Complexity → "13,000+ commerce apps"

---

Category: B2B - Fintech/Payments

Stripe Pattern

What works:

• Scale proof in hero: "Global GDP running on Stripe"
• Infrastructure-level positioning: "Financial infrastructure to grow your revenue"
• Dual conversion paths: Self-serve signup + Enterprise sales
• Google OAuth removes signup friction

Key elements:

TRUST METRICS:
- "99.999% historical uptime"
- "$1.4T payments volume in 2024"
- "135+ currencies supported"
- "200M+ active subscriptions"

LOGO STRATEGY:
- Enterprise: Amazon, Shopify, Uber
- Startups: Figma, OpenAI, Anthropic
- Both audiences see themselves

CASE STUDIES:
- Hertz: "160 countries, 11K+ locations"
- URBN: "$5B revenue consolidated"
- ElevenLabs: "$3B AI audio leader"

---

Category: Design/No-Code Tools

Webflow Pattern

What works:

• AI-native positioning: "Smarter sites start here"
• Multiple creation pathways: AI builder, templates, blank
• Persona selector in navigation: Marketer/Designer/Developer/Agency
• Figma integration addresses designer workflow

Key elements:

ABOVE FOLD:
- Innovation signal: AI-native
- Speed promise: "faster than ever"
- Outcome focus: "drive real results"

PERSONA TARGETING:
- Explicit role selector
- Role-specific solution pages
- Addresses different entry points

CREATION PATHWAYS:
1. AI builder (fastest)
2. Templates (guided)
3. Blank (full control)

---

Category: Consumer Tech

Apple Pattern

What works:

• Product-first, minimal copy
• Achievement-based proof: "4 Oscar Nominations"
• Consistent "Learn more" + "Buy/Shop" CTA pattern
• Authority assumed, not argued

Key elements:

DESIGN PHILOSOPHY:
- Image-first, copy-second
- Single-sentence value props
- No aggressive persuasion

CTA PATTERN:
- "Learn more" (exploration)
- "Buy" / "Shop" (transaction)
- Never pushy, always available

TRUST APPROACH:
- Brand reputation does the work
- Awards and achievements (not testimonials)
- Entertainment partnerships as proof

---

Pattern Matrix: What to Use When

---

Above-the-Fold Checklist

Based on patterns from all analyzed pages:

Must Have

• [ ] Clear headline answering "what is this?"
• [ ] Value proposition or subheadline with benefit
• [ ] Primary CTA visible without scrolling
• [ ] Trust signal or friction reducer near CTA

High Impact

• [ ] Specific number or metric in headline/subheadline
• [ ] "Free" or "No credit card" if applicable
• [ ] Product visual or screenshot
• [ ] Secondary CTA for different intent (demo vs. signup)

Avoid

• [ ] Jargon or insider language
• [ ] Multiple competing headlines
• [ ] Form fields above the fold (unless very short)
• [ ] Generic stock photography
• [ ] Autoplay video with sound

---

Section Sequence Template

Based on highest-converting patterns:

1. HERO
   - Headline (problem/outcome focused)
   - Subheadline (who it's for + key benefit)
   - Primary CTA + friction reducer
   - Product visual

2. SOCIAL PROOF BAR
   - Customer logos (5-8)
   - OR key metric ("Used by X teams")

3. PROBLEM/SOLUTION
   - Articulate the pain
   - Position your solution
   - Visual demonstration

4. FEATURES/BENEFITS
   - 3-4 key capabilities
   - Each tied to outcome
   - Screenshots or demos

5. TRUST SECTION
   - Testimonials with specifics
   - Case study snippets
   - Awards/ratings

6. OBJECTION HANDLING
   - FAQ or direct answers
   - Guarantee/risk reversal
   - Security/compliance (if relevant)

7. FINAL CTA
   - Restate key benefit
   - Trust reinforcement
   - Clear action