If you've ever bought an outbound course, you've been taught AIDA, PAS, and Challenger as if they were universal solvents. They're not. Each one wins under specific conditions and loses elsewhere.
Below is what 14,000 cold emails across our pilot teams say about which framework wins where.
AIDA — Attention, Interest, Desire, Action#
The original. Borrowed from print advertising in the 1890s, somehow still recommended for cold email in 2026.
Structure:
- A: Hook — get them to keep reading
- I: Build interest — relevant context
- D: Build desire — outcome they want
- A: Specific ask — usually a meeting
Reply rate in our dataset: 4.1%
When it wins: When your buyer is a senior exec who reads the first sentence to triage. AIDA's punchy Attention line gets past the inbox glance. The Desire section, when written well, hooks them on outcome, not feature.
When it loses: When the buyer is technical or skeptical. AIDA's structure feels manipulative to anyone who's seen it before — and at this point, in the median tech-adjacent role, they've all seen it.
PAS — Problem, Agitation, Solution#
The cold-email favorite of the last decade. Still the most-taught framework. Probably the most overused.
Structure:
- P: State the problem they have
- A: Make them feel it (cost, frustration, embarrassment)
- S: Position your solution
Reply rate in our dataset: 3.4%
When it wins: When you can name a problem they've already named themselves — usually because they posted about it. PAS without that prior signal feels presumptuous; with it, it feels like you're agreeing with them.
When it loses: When you're describing a problem they don't yet recognise. Agitation only works if the agitation lands; if the prospect doesn't believe they have the problem you describe, they bounce.
Challenger — Lead with insight that reframes their thinking#
The framework Brent Adamson taught a generation of enterprise reps. Built for complex sales, mis-applied to cold email constantly.
Structure:
- Lead with a non-obvious insight
- Reframe the prospect's thinking on a problem
- Earn the right to a conversation by being a smarter peer
Reply rate in our dataset: 6.8%
When it wins: When you genuinely have an insight. "73% of teams using the playbook you described publicly are seeing 30% drop in reply rates by week 6" — if true, that's irresistible. The prospect has to engage to find out if you're right.
When it loses: When the insight is fake or obvious. Most reps don't have insights, they have product talking points. Repackaging a feature as an insight reads as condescending and tanks reply rates.
The honest hierarchy#
Across our dataset:
| Framework | Reply rate | Best fit |
|---|---|---|
| Challenger (with real insight) | 6.8% | High-context buyers, technical roles |
| AIDA | 4.1% | Time-poor execs, large enterprises |
| PAS (with confirmed signal) | 3.4% | Buyers who've publicly named the problem |
| Generic / no framework | 2.1% | (Don't) |
The single biggest factor isn't which framework you pick. It's whether the email reads as if it was written to them or at them.
The one we actually use#
We don't pick a framework upfront. We pick a hook, then let the framework follow:
- Recent post / activity → reflects what they care about → shape an AIDA-style attention line.
- Public statement of a problem → use PAS, mirror their language back.
- Public claim that's incomplete or wrong → use Challenger, offer the missing piece.
- No signal at all → don't send. The prospect's not ready, you're guessing.
That fourth bullet is the one most teams resist and it's the one that moves the metric most. The 3% reply-rate floor is half bad copy, half sending to the wrong people. You can't out-write a list of cold strangers who haven't signalled they care.
Stop optimising the framework#
Three things that move reply rate further than swapping framework:
- Cut the email to half its current length, ruthlessly.
- Make the ask smaller: not a meeting, not a call, just "worth comparing notes?"
- Send fewer, better-researched emails: 50 well-researched outperforms 500 templated, every time we measure.
Frameworks are scaffolding. The pillar underneath is whether you actually know who you're writing to.
OREE picks the framework based on the signal it surfaces — Challenger when there's a public insight to challenge, AIDA when the buyer is exec-level with no public posts, PAS when they've named the problem themselves. The signal drives the frame. Try it on a real prospect.
Written by
Ben Hewitt
Founder, OREE
Ran Momentum Outbound for three years before founding OREE. Writes about the SDR motion and what good outbound actually looks like in 2026.



