Cold Email Personalization Frameworks: PASO, PAS, BAB, and When to Use Each

Updated July 2026 · 15 min read · By Marwene Amor

Frameworks are having a moment in cold email circles. PASO, PAS, BAB, AIDA, everyone's got an acronym and a swipe file, and the promise is always the same: follow this structure and your emails will convert. I want to push back on that a little, because the framework is the easy part, and treating it as the whole answer is why so many "well-structured" cold emails still get ignored.

Here's the thing a framework can't do. It can't make your email relevant. It gives you a clean skeleton to hang a message on, which is actually useful, but if the message itself could have been sent to a thousand people, the cleanest PASO structure in the world won't save it. So this guide covers both halves, plainly: the frameworks worth knowing and when each fits, and the personalization that decides whether any of them actually work. Structure and substance. You need both, and most advice only sells you the first.

If you want the sending side of this, the subject lines guide and the follow-up cadence guide cover what surrounds the body. This one is about the body itself.

What a framework is actually for

Let's be precise about the job a framework does, because it's narrower than people claim. A copywriting framework is a sequence that keeps your email logical and tight: it stops you rambling, makes sure you name a reason for writing before you ask for anything, and gives the reader a clear path from "why is this in my inbox" to "here's what to do next." That's valuable. Unstructured cold emails wander, bury the point, and lose the reader.

But notice what that job doesn't include. A framework doesn't generate relevance, doesn't do your research, and doesn't know anything about the person you're emailing. It's an empty container. Fill it with something specific and true about the prospect and it sings; fill it with generic pain and a generic pitch and you've just organized your spam more neatly. Hold that distinction the whole way through this guide, because it's the difference between frameworks helping you and frameworks fooling you.

This is also why swipe files disappoint people. You copy a framework that worked for someone else, drop in your product, and it falls flat, because what made their email work wasn't the structure you copied, it was the relevance you couldn't. The structure travels; the substance doesn't. Treat every framework you read as a template to fill with your own research, never as a finished email to lightly edit. The moment you're editing someone else's words instead of writing your own relevant ones, you've lost the only thing that was ever going to make the email land for your prospect.

The frameworks worth knowing

Four structures cover almost everything useful in cold email. Here's each one, what it's for, and where it fits, so you can pick by situation rather than by whichever acronym is trending this week.

PAS: Problem, Agitate, Solution

The classic, and still the workhorse. Name a problem the prospect has, briefly agitate it by touching on what it costs them, then present your solution. It works because it's problem-led, and a relevant problem is the fastest way to earn a stranger's attention. The risk is the agitate step: lean on it too hard and you sound like a late-night infomercial twisting the knife. In cold email, agitation should be a light touch, a single clause acknowledging the cost, not a paragraph of manufactured anxiety.

PASO: Problem, Agitate, Solution, Outcome

PAS with a fourth beat, and the one that's been getting attention lately for good reason. You add an explicit outcome: after the solution, you state the concrete result the prospect would get. The reason it suits cold email is that busy buyers care less about your solution's features and more about the payoff, so ending on a specific outcome ("teams doing this book roughly a third more demos") answers the "so what" that PAS sometimes leaves hanging. Same caution applies: keep the agitate step subtle, and make the outcome specific and believable rather than a grand promise, because an inflated outcome reads as hype and kills trust.

BAB: Before, After, Bridge

A different entry point. Instead of leading with pain, you paint the "before" (where they are now), the "after" (where they could be), and the bridge (how you get them there). BAB shines when the desirable end state is easier to picture than the problem is to name, or when the problem is a bit abstract. It's a more positive, aspirational structure, which can feel less pushy than PAS for certain audiences. The trap is vagueness: a fuzzy "before" and a dreamy "after" read as fluff, so both need to be concrete and grounded in the prospect's real situation.

AIDA: Attention, Interest, Desire, Action

The old marketing standby, and the one I reach for least in pure cold email. AIDA asks for attention, builds interest, stokes desire, then calls for action, which is a lot of steps for a stranger's inbox and works better on a slightly warmer audience or a longer format. In cold outreach it tends to produce emails that are too long and too salesy, because "build desire" invites you to lay it on. It has its place on a warm re-engagement or a landing page, but for a first cold touch, PAS or PASO usually beats it on brevity alone.

Framework	Best when	Main risk
PAS	The prospect feels a clear, nameable pain	Over-agitating into infomercial territory
PASO	You can state a specific, believable outcome	Inflated outcomes that read as hype
BAB	The win is easier to picture than the pain	Vague before/after that reads as fluff
AIDA	Warmer audience, longer format	Too long and too salesy for a first touch

The part that actually matters: personalization

Now the half that decides everything. You can run any of those frameworks perfectly and still get ignored, because the framework organizes your message but doesn't make it relevant. Relevance comes from personalization, and personalization in 2026 has a much higher bar than it used to.

Surface personalization is dead, or close to it. Dropping in a first name, mentioning the company name, "I loved your work at {company}," these are so automated now that buyers read them as exactly what they are: merge fields. They don't signal that a human looked; they signal that a tool ran. Real personalization proves attention. It references something specific and current: a role they're hiring for, a product they just launched, a market they just entered, a problem their particular situation clearly implies. That's the stuff that's hard to fake at scale, which is precisely why it still works when the easy tricks have stopped. It's also why auto-generated AI personalization tends to fall flat, a topic we cover in our guide on AI cold email.

So the personalization goes into the problem step of your framework. That's the spot that pays off most. When your "P" in PAS is a problem this specific prospect visibly has, the whole email feels written for them even if the rest is a solid template. When your "P" is a generic industry pain, no framework hides that it's a blast.

Personalizing at scale without hand-writing every email

Here's the tension every operator hits: real personalization takes research time, and research time doesn't scale. Hand-writing a deeply personal email to a thousand prospects isn't a strategy, it's a way to send forty emails and burn out. So how do you get relevance at volume? Two moves.

First, personalize through segmentation. If you segment tightly enough, one actually specific problem statement fits a whole segment. "Companies that just raised a Series A and are hiring their first three SDRs" share a real, specific problem you can name once and send to all of them, and it'll feel personalized because it's true for each. Tight segments turn one piece of research into relevance for a hundred prospects. This is the single biggest win, and it's why targeting is upstream of copywriting: get the segment right and the personalization gets easy.

Second, personalize one line per prospect where the payoff justifies it. On top of the segment-level relevance, add a single custom line, an observation about that specific prospect, for the accounts worth the extra minute. High-value prospects earn a hand-written opener; the long tail rides on segment-level relevance alone. Match the research depth to the deal value, exactly as you'd match your whole stack to it, which the stack framework gets into. Tools like lemlist lean into this with dynamic variables and snippets, and the trade-offs between personalization-depth and volume are covered in the lemlist vs Smartlead vs Instantly comparison.

A worked example

Let's build one email so the abstract turns concrete. Say I'm selling an onboarding tool to SaaS companies, and my segment is "Series A SaaS that just hired a Head of Customer Success." I'll use PASO, lightly.

Problem (personalized): "Congrats on bringing on a Head of CS, usually a sign onboarding is about to get a hard look." That's the segment-level relevance doing the work; it's true for everyone in the segment and it proves I know their moment. Agitate (light): "The tricky part is that the first 30 days set churn, and a new CS lead rarely has the tooling to see where accounts stall." One clause on the cost, no knife-twisting. Solution: "We give new CS teams that visibility in week one." Outcome: "Most cut early churn noticeably in a quarter." Then a soft ask. Total: under 90 words, structured by PASO, but carried by the opening relevance. Swap the framework for BAB and it'd still work, because the thing making it land is the specific, true observation up top, not the acronym.

How to find the personalization detail fast

The whole thing hinges on finding a real, specific detail about the prospect, and the fear is that this takes forever. It doesn't, if you know where to look and you time-box it. The goal isn't a deep dossier; it's one true, usable observation, and you can usually get there in a minute or two per prospect.

The richest sources are the obvious ones. The prospect's company careers page tells you what they're hiring for, which implies what they're scaling and where the strain is. Their recent LinkedIn activity or company posts show what they're publicly focused on this quarter. A recent funding announcement or product launch signals a moment of change, and change is where problems live. Even their website's positioning shift or a new page hints at a direction. Any one of these gives you a "they're clearly doing X" observation that beats a merge field.

The discipline is the time box. Give yourself ninety seconds per prospect at the long-tail end, and if you don't find a usable detail in that window, fall back to your segment-level relevance rather than forcing a weak one. A weak, generic "observation" is worse than none, because it reads as trying too hard. Save the deep research, the ten-minute dig into a prospect's podcast appearance or their conference talk, for the high-value accounts where the deal justifies it. Match the minutes to the money, and personalization stops feeling like a tax on your time. Over a few weeks you'll also build a mental library of the signals that map to real problems in your market, and the whole process gets faster.

The mistakes people make with frameworks

A few patterns worth dodging, since they show up constantly.

Treating the framework as the strategy. People memorize PASO, apply it to generic pain, and wonder why it flops. The framework was never the strategy; the relevance is. Structure a boring message and you get a well-structured boring message.

Writing a paragraph per step. Frameworks tempt you to fully develop each beat, which bloats a cold email into a wall of text that reads as a pitch. Compress each step to a sentence or a clause. Short is not optional.

Over-agitating. The agitate step is where enthusiastic operators go wrong, manufacturing pain the prospect doesn't feel until the email reads as manipulative. A light touch on a real cost beats a heavy hand on an invented one.

Faking personalization to fill the problem step. Slotting a company name into a template problem isn't relevance, and buyers see through it. If you can't name a real, specific problem for the segment, your targeting is too broad, fix that before you touch the copy.

Where copy sits in the whole system

Keep this in proportion, because copy is one input among several. Your list and targeting decide whether you're even talking to the right people. Your deliverability decides whether the email arrives at all, which the deliverability checklist covers. Your subject line gets the open. Your framework and personalization, this guide, get the reply. And your follow-ups catch the majority who don't reply the first time. A brilliant PASO email on a bad list, sent from a cooked domain, still fails. Frameworks are worth learning, but they're the polish on top of targeting and deliverability, not a substitute for either. Get those right first, then let a clean, relevant, well-structured email do its job.

Frequently asked questions

What is the PASO framework in cold email?

PASO stands for Problem, Agitate, Solution, Outcome. You open by naming a problem the prospect has, briefly agitate it by pointing at the cost of leaving it unsolved, present your solution, and close on the concrete outcome they'd get. It's a tightening of the older PAS formula with an explicit outcome step, which suits cold email because busy buyers want the payoff. Used lightly it structures a short, relevant email; overused it reads like a sales script, so the agitation step in particular should stay subtle.

Which copywriting framework is best for cold email?

There isn't one best framework; there's a best fit for the situation. PAS and PASO work when the prospect feels a clear pain you can name. BAB works when the win is easier to picture than the pain is to state. AIDA suits a warmer audience that will read a few lines. For most cold outreach, a light PAS or PASO on a actually relevant problem is the safest default. The framework matters less than whether the problem you name is real and specific to that prospect.

How do you personalize cold email at scale?

By personalizing the variable that matters, not every word. The personalization that pays off most is the opening problem or observation, tied to something real about the prospect's company or role, while the rest stays a solid template. Trying to hand-write every email doesn't scale, and swapping in a first name isn't personalization. The workable middle is to segment tightly so one relevant problem statement fits a whole segment, then personalize one specific line per prospect where the payoff justifies the research time.

Is a framework or personalization more important in cold email?

Personalization, by a wide margin. A framework is just a structure that keeps your email clear and short; it does nothing if the content is generic. A relevant, specific email with a loose structure beats a perfectly structured email that could have gone to anyone. Use the framework as scaffolding to organize a actually relevant message, not as a substitute for having something relevant to say.

Does personalization still work in cold email in 2026?

Yes, but the bar has risen. Surface personalization like inserting a first name or company name is now so common from automated tools that buyers discount it. What still works is personalization that proves a human looked: referencing a specific initiative, a role they're hiring for, a product they shipped, or a problem their situation implies. That kind of relevance is harder to fake at scale, which is why it still earns replies while merge-field tricks have stopped.

How long should a cold email using a framework be?

Short. Whichever framework you use, the whole email should run roughly 50 to 125 words and fit on a phone screen without scrolling. Frameworks like PASO can tempt you to write a full paragraph per step, which bloats the email into a pitch. Compress each step to a sentence or a clause. A busy buyer decides whether to reply in seconds, so the framework's job is to make a short email land, not to license a long one.

Bottom line

Frameworks are useful scaffolding and nothing more. PAS and PASO for problem-led emails, BAB when the after is easier to picture than the before, AIDA for warmer or longer formats, all of them kept to a sentence per step and the whole email under about 125 words. But the framework is the easy 20 percent. The other 80 is personalization: naming a real, specific problem for a tightly chosen segment, adding a custom line where the deal justifies it, and never mistaking a merge field for relevance. Get the targeting and the relevance right, pour them into whichever framework fits, and keep it short. That's cold email copy that earns replies.

Pair this with the subject lines guide to get the open, the cadence guide to catch the non-repliers, and the stack framework if you're still assembling the tools behind it all.

Related Reviews & Guides

Other deep dives on EmailToolsHub that pair well with this one.

Browse all reviews →