7 Cold Email Copywriting Frameworks, With an Example Email for Each

The rule every framework has to fit

I write cold email for B2B clients, and the framework is the last thing I decide, after the list and the offer. My rule for a first email: 30 to 40 words, one concrete problem, one concrete offer and one question at the end. Every example below sticks to it, and every example was written for this article, not taken from a real campaign.

The data points the same way. Instantly's 2026 benchmark, built on its users' sends from January to December 2025, found the best campaigns keep first emails under 80 words, and it tells senders to "lead with the problem, not your solution". It also found 58% of replies come from the first step, so the first email is where structure matters most.

What the report doesn't do is name or rank any framework, and I haven't found a published test that compares them head to head. So pick by situation, not by a leaderboard.

The 7 frameworks at a glance

Problem first: PAS and BAB

PAS: problem, agitate, solution

Name a problem the reader has, make it real with one consequence, then say what you do about it. In a long sales letter the agitate part runs for paragraphs. In cold email it's one sentence with one real consequence. Pile on adjectives and it reads like a guilt trip.

Example email (written for this article):

"Hi Marta, at subscription companies your size, failed card payments often sit unchased for weeks. By then the customer has quietly churned. We retry and chase them automatically. Want the three-email recovery sequence we use?"

Use it when there's no trigger, most companies on the list share the same problem and you can describe it the way they would. It's a good default for cold segments.

BAB: before, after, bridge

Describe where they are now, then where they could be, then how you get them there. It skips the lecture about the problem and goes straight to the better state.

Example email (written for this article):

"Hi Jonas, your German pages are translations of the English ones, so they target phrases German buyers rarely search for. Picture pages written around what they do type. We rewrite them that way. Want one sample page?"

Use it when they already know they have the problem: they've posted about it, hired for it or use a tool you replace. Explaining the pain to someone who lives with it every day wastes your 40 words.

Trigger or praise first: AIDA and PPP

AIDA: attention, interest, desire, action

AIDA comes from advertising around 1900, where you have to win attention before anything else. In cold email the reader has already opened the message, so the attention line only earns its place if it's a real, recent event at their company. Then one line on the problem that event creates, one on what you offer and then the ask.

Example email (written for this article):

"Hi Laura, congrats on the Series B. Bigger deals usually bring bigger security questionnaires, and they land on your engineers. We fill them from your existing docs in a day. Want us to do your next one as a test?"

Use it when something happened in the last few weeks: a funding round, a new office, a key hire, a launch. Without a real trigger, skip AIDA, because a made-up attention line reads like every other cold email.

PPP: praise, picture, push

Open with an honest, specific comment on something they did, paint the result you could help with, then ask. The praise has to be about one thing only they did. "Love what you're building" reads as automated even when it isn't.

Example email (written for this article):

"Hi Tom, your post on ungating your pricing page was the best case for it I've read. Picture the same idea on your demo form, which still asks for nine fields. Want a two-minute video on cutting it to three?"

Use it when they've recently published a post, a podcast or a talk that connects to your offer. If you haven't read or heard the thing, don't praise it.

Question first: QVC and the four-line email

QVC: question, value, call to action

Open with a question about how they handle something today, give one line on what you do about it, then ask. The opening question does some of the qualifying: the answer tells you which problem they actually have.

Example email (written for this article):

"Hi Ana, before Hannover Messe, who books your reps' meetings, or do they fill the calendar at the booth? We start outreach to your target accounts four weeks out, so reps arrive with meetings set. Want the plan we'd use?"

Use it when you know the area they struggle in but not the exact problem, or your list mixes companies that handle it in different ways.

The four-line email: observation, question, pitch, ask

I've written this one up in full in the four-line cold email framework. The short version: an observation that proves you looked, a question that makes the problem feel present, one sentence on what you do and for whom and an ask small enough to say yes to. It's close to AIDA, but the question turns it into a conversation instead of a pitch.

Example email (written for this article):

"Hi Lukas, you've posted three SDR roles this month. Where will their first lead lists come from? We build verified account lists for new SDR teams before day one. Want 50 accounts for one rep to test?"

Use it when you have a trigger for every company in the segment. If you can't find one, the segment probably needs splitting.

Value first: PVP

A PVP, or permissionless value proposition, gives the reader something useful before you ask for anything, usually an insight you built from public data. The test: would this person pay $100 for what you just told them? If not, it's personalisation dressed up. I go deeper in the PVP test.

Example email (written for this article):

"Hi Petra, four of your competitors posted Salesforce admin roles in Kraków this month, the same city you're hiring in. You're bidding for the same people. Want the list with the salary ranges they posted?"

Use it when the account is worth an hour of research and you can find data that's useful on its own. It's the most work per email of the seven, so keep it for your best accounts.

How to pick a framework for each segment

Go through these in order and stop at the first yes:

1. Did something happen at the company in the last few weeks? Use the four-line email, or AIDA if the event itself is the hook.
2. Did the person publish something that connects to your offer? PPP.
3. Is it a top account worth an hour of research? PVP.
4. Do they already know they have the problem? BAB. If they probably haven't put a name on it yet, PAS.
5. Not sure which problem they have? QVC, and let the answer tell you.

Decide this per segment before you write, not once for the whole list. One framework across every segment fits some of them and misses the rest.

When the framework isn't the problem

If replies are flat, the framework is rarely the reason. Check in this order: the list (right companies, right people?), the offer (small, useful, easy to say yes to?) and deliverability (are you reaching the inbox?). Only then look at the copy.

To test one framework against another, split one segment in half. Keep the list, subject line and send times the same and change only the body. Compare positive replies rather than all replies. Give it enough sends before you call a winner. I lay out the setup in my cold outbound testing framework.

FAQ