Lesson 8/10 · 80%
← Course Home
Cold Outreach Masterclass
1 Why Cold Email Fails 2 The Permission Paradox 3 Subject Line Science 4 Personalization at Scale 5The 3-Sentence Body 6Call-to-Action Strategy 7Sequence Design 8A/B Testing Emails 9Objection Handling 10Metrics and Optimization
Lesson 8 of 10

A/B Testing Emails

Gut instinct is a poor guide for email optimization. A/B testing — running controlled experiments on specific variables — is the only way to know what actually works for your audience, your product, and your market.

What to Test First

Test in order of impact: (1) Subject line, (2) Opening sentence, (3) Value proposition, (4) Call to action, (5) Email length. Most teams never get to #5 because the first four are already enough to improve performance dramatically.

A Rigorous Test Setup

Send each variant to a minimum of 100 recipients from the same audience segment. Change only one variable per test. Run the test to completion (all 5 touches) before measuring final reply rate — measuring after Touch 1 misses the replies that come later. Document every test in a shared spreadsheet with: hypothesis, variant A, variant B, sends per variant, open rate, reply rate, winner, and what you'll test next.

Common Testing Mistakes

Testing too many things at once: If you change the subject line, opening, and CTA simultaneously and get a different result, you don't know which change caused it. One variable per test, always.

Declaring a winner too early: With fewer than 50 sends per variant, your results are statistically meaningless. Discipline yourself to wait for proper sample sizes.

Not documenting results: The team that doesn't document test results repeats the same tests indefinitely. A shared swipe file of winning variants is a compounding organizational asset.

Key Takeaways
  • Test in order: subject line → opening sentence → value prop → CTA → length
  • 100+ sends per variant is the minimum for statistically meaningful results
  • One variable per test — testing multiple variables makes results uninterpretable
  • Document every test result in a shared file — it compounds into a team advantage over time
← Sequence Design Objection Handling →