Cold Email Β· Guide

Cold Email Copy Frameworks

Which framework fits each prospect type, how each one is structured, and the four copy patterns that kill reply rates regardless of which framework you use.

Written for operators No vendor influence Practical, not theoretical

TL;DR

Framework selection follows one variable: prospect awareness

Low-awareness targets need problem-led copy that names the pain first. High-awareness or signal-triggered targets need research-specific openers that show you did real work before sending. The framework is a consequence of awareness level, not industry or company size.

Framework Reference

Five cold email copy frameworks at a glance

FrameworkBest forTarget lengthCore structure
PAS (Problem-Agitate-Solution)Cold targets, low awareness, broad ICP3 to 5 sentencesName the pain, sharpen its cost, offer a specific way out
BAB (Before-After-Bridge)Aspirational buyers, expansion-stage companies4 to 6 sentencesCurrent state, better state, the mechanism that connects them
Relevance-Value-CTAHigh-volume sequences, wide market segments2 to 4 sentencesOne relevance hook, one specific value claim, one low-friction ask
BASHO (research-triggered)Named accounts, signal-triggered outreach, enterprise ICP5 to 8 sentencesSpecific research hook, problem connection, one credibility signal, one ask
Credibility-Problem-CTAWarm audiences, referral context, re-engagement3 to 5 sentencesSocial proof first, problem framing second, single direct ask

Short-Form Frameworks

PAS and Relevance-Value-CTA: frameworks for broad outreach

PAS leads with the problem in terms the prospect uses internally, sharpens its cost in sentence two, and offers a specific way out in sentence three. Most implementations fail at sentence three by over-explaining the solution. Keep the ask light: one question, one resource, one call offer.

Relevance-Value-CTA compresses the same logic for high-volume segments. The relevance hook must be specific to the recipient: a company attribute, role-level challenge, or recent event. Generic job-title openers do not qualify. One value claim. One ask.

πŸ’‘
PAS specificity test

Read sentence one aloud. If it fits 500 companies unchanged, the pain is too generic to work as PAS.

Research-Based Frameworks

BASHO and BAB: frameworks for named accounts and high-intent targets

BASHO opens with a specific, verifiable observation about the prospect: a recent hire, product launch, or job posting. That observation connects to the problem your product solves in sentence two. Best for named account lists and signal-triggered sequences where research investment per contact is justified by deal size.

BAB leads with the prospect's current reality, describes a better version in concrete terms, then positions your product as the mechanism closing the gap. Use it for expansion-stage companies aware of a gap but not yet in active pain. BAB requires accurate knowledge of the prospect's current state to describe it in one sentence.

  1. BASHO: 3 opener structures

    Job posting: "You are hiring [role], which usually means [initiative] is already in motion." Funding: "Congrats on [round]. Teams at your stage hit [bottleneck] around [threshold]." Statement: "Saw [name]'s post on [topic]. That friction shows up consistently in [role] teams at [company type]."

  2. BAB: structural pattern

    Before: "[Role] teams at your size typically [current-state friction]." After: "High-performing teams achieve [specific outcome]: [one concrete detail]." Bridge: "[Product] gets there by [one-sentence mechanism]. Worth a 15-minute call?"

⚠️
BASHO needs a signal routing layer at scale

BASHO at volume requires Clay, Apollo alerts, or a similar enrichment workflow to inject research hooks automatically. Without that infrastructure, it stays a manual tactic for high-priority accounts only. See the Cold Email and Buying Signals guide for how signals feed this framework.

What Kills Reply Rates

4 copy patterns that underperform across all frameworks

These failures show up in PAS, BAB, and BASHO equally. They are structural, not stylistic.

Failure 1
Product pitch in sentence two
Naming the product by sentence two collapses the framework before it builds tension. Keep the product name out of the first two sentences and let it appear as a consequence of the problem.
Failure 2
Multi-ask CTA
"Would it make sense to talk?" outperforms any CTA presenting three options. One low-friction ask per email, no exceptions.
Failure 3
Feature-first value sentences
Lead with outcomes, not features. "We use AI to analyze your pipeline" loses to "Teams cut pipeline review time by half."
Failure 4
Paragraph-length openers
An opener longer than two sentences forces the prospect to commit before they have a reason to care. The first sentence must deliver one complete claim on its own.

Recommended Tools

Lavender, lemlist, Apollo: tools for framework execution

Lavender
Scores cold email copy in real time and flags structural failures: long openers, feature-first value claims, multi-ask CTAs. Works inside Gmail and Outlook during the writing process.
See Review
lemlist
Personalization variables and text injection scale BASHO-style openers by feeding signal-specific hooks into a consistent framework template. Built for high-personalization sequences at volume.
See Review
Apollo
Sequence builder supports A/B and A/Z testing at the step level. Run PAS vs Relevance-Value-CTA against the same contact segment to measure reply rate differences directly.
See Review

Common Questions

4 questions on cold email copy frameworks

Q Which cold email copy framework gets the highest reply rates?

No single framework wins. BASHO outperforms PAS on named accounts because the research hook earns attention. PAS outperforms at volume because it requires no per-contact research. Test both against your list before committing to one.

Q How long should a cold email be under each framework?

PAS and Relevance-Value-CTA: 3 to 5 sentences. BAB: 4 to 6 if the before and after states are specific. BASHO: up to 7 to 8, but every sentence must carry distinct information. Any sentence that only transitions between others should be cut.

Q Can I use cold email copy frameworks examples as templates directly?

Frameworks give you the structural skeleton, not the final copy. The specificity that makes any framework work comes from knowing the prospect's context and your product's real outcomes. Paste-and-send use produces generic emails.

Q Should I use the same framework for every step in a sequence?

No. Follow-ups serve a different function: a new angle, a relevant case, or a direct question. Using PAS for every step in a 5-email sequence builds annoyance, not trust. See the Follow-Up Playbook for step structures.

Framework chosen. Now build the CTA that closes it.

The CTA Library covers every cold email ask pattern with structural examples mapped to sequence stage and prospect temperature.