Objection-Proof Cold Email Framework (PAS-R)
The four-part Problem–Agitate–Solve–Reply structure behind first-touch emails that read like a specific observation about the recipient, not a template with their name pasted in.
What's inside
- The 4-part PAS-R structure with word-count guidance per part
- Subject line formulas (and 4 banned subject lines)
- Full worked example: VP Sales persona
- Full worked example: RevOps persona
- Fill-in-the-brackets master template
- Why each part works (the mechanism behind it)
- 6 common mistakes that break the framework
- A pre-send test: the 'would a stranger reply' check
Most first-touch cold emails fail for one of two reasons: they open with a generic problem statement anyone could have written, or they ask for too much too soon (a 30-minute demo from a total stranger). PAS-R fixes both by building toward a reply, not a meeting, on touch one.
P — Problem. Name a specific problem this persona has, in their language, tied to something real about their account. One sentence.
A — Agitate. Make the cost of leaving it unsolved concrete — quantified if you can put a number on it. One to two sentences.
S — Solve. Bridge to what becomes possible, framed as a capability, not a feature list. One to two sentences. No product jargon.
R — Reply ask. A single, low-friction question designed to get a one-line reply, not book a meeting. One sentence.
Target length: 80–120 words total. If it's longer, you're explaining instead of asking.
Subject line formulas
- Specific trigger: "Quick one on [specific trigger — a hire, a launch, a post]"
- Peer reference: "How [similar company type] handled [problem]"
- Curiosity + number: "[Number]% of [persona]s hit this — you too?"
Never use: "Quick question", "Following up", "Touching base", "Checking in" — all four signal template and get archived on sight.
Master template
Subject: [subject line formula] P: [Specific problem, in their language, tied to something true about their account or role] A: [Cost of leaving it unsolved — quantified where possible; who notices, and when] S: [What becomes possible — capability, not feature; plain language] R: [One low-friction question that invites a one-line reply]
Worked example 1 — VP Sales persona
Subject: Quick one on your Q3 headcount post Saw you're adding 6 AEs this quarter — most VPs I talk to in that spot tell me ramp time is what actually eats the quarter, not the hiring itself. If ramp runs the usual 4–6 months, that's roughly two full quarters of quota those 6 reps aren't hitting — right when the board's asking why growth didn't show up faster. We help sales orgs cut ramp time by grading new reps against the exact skill gaps their best reps closed first, instead of a generic 30-60-90. Most see new reps hit full quota 6–8 weeks sooner. Worth 15 minutes to see if it'd move the needle for your Q3 class — or is ramp not actually the bottleneck for you right now?
Worked example 2 — RevOps persona
Subject: The gap between forecast and coaching Most RevOps leads I talk to have a clean forecast model and a messy "why did this rep miss" model — the two don't talk to each other. That gap usually means coaching decisions get made on gut feel, and the reps who need help most keep missing quarter after quarter until someone notices the pattern by accident. We connect skill data to forecast data, so you can see which specific competency gap is costing which specific deals — before the quarter closes, not in the post-mortem. Is that gap between forecast and coaching something you're actively trying to close right now, or is it lower on the list?
Why each part works
- Problem earns the read — it proves you did homework before you typed anything.
- Agitate creates urgency without pressure tactics — it's math, not manipulation, and it's specific to their situation.
- Solve avoids feature-dumping; it answers "what changes for me" instead of "what does your product do."
- Reply ask lowers the bar to respond to almost zero — a one-line reply is easier to send than ignoring an email that asked a direct question.
6 mistakes that break PAS-R
- Turning Problem into a generic industry statement instead of an account-specific one.
- Skipping Agitate and jumping straight to your product — kills urgency.
- Listing 3+ features under Solve instead of one capability.
- Asking for a meeting instead of a reply on touch one.
- Writing more than 2 sentences per section — length signals template.
- Using the same PAS-R email for every persona instead of rewriting Problem and Agitate per role.
Pre-send test
Read the finished email once, then ask: would a stranger who has never met me reply to this with more than "not interested"? If the honest answer is no, the Reply ask is either too big, too vague, or the Problem line didn't earn enough trust to justify it.
How to use it
Draft each of the four parts as one to two sentences using the master template, swap in the two worked examples as tone references, then run the finished email through the pre-send test before it goes out.