Frameworks get a bad reputation because people treat them as fill in the blank templates and end up sounding like everyone else. Used well, a framework is just a structure that keeps you focused on the reader instead of your product. The ones we rely on after writing copy across millions of sends share a single principle: lead with the reader's problem, written like a human would actually say it. Here are the frameworks that hold up.
Problem-first beats feature-first
The default instinct is to open by explaining what you do. That is feature-first, and it fails because the reader has no reason to care about your features until they recognize a problem they have. Problem-first copy flips the order. You name a specific pain the reader likely feels, and only then connect it to what you offer.
The test is simple. Read your first two sentences and ask whether they are about the reader or about you. If the answer is you, rewrite them. A buyer skims for relevance to their own situation, and a problem they recognize is the fastest way to earn the next sentence of attention.
The one-line relevance opener
The first line decides whether the rest gets read. Skip the throat clearing like 'I hope this email finds you well' and open with one line that proves this message was meant for this person. That can be a reference to their role, a recent company event, a hiring signal, or a problem specific to their niche.
Relevance is also where good data earns its keep. A generic opener is a generic email, and generic emails get deleted. Sourcing the right signal for the right person is the difference between a line that lands and one that reads like a mail merge. This is why we build enrichment into the system rather than bolting it on later, an approach we describe in our work on buying signals.
PAS, used lightly
Problem, Agitate, Solution is the most useful structure for cold email because it mirrors how a buyer comes to care about something. Name the problem, briefly make the cost of it real, then offer the solution as a path out. The key word is briefly. Heavy agitation feels manipulative and turns people off.
In a cold email, PAS should be compressed almost to the point of being invisible. One line of problem, one line that hints at the cost, one line of solution, then a soft ask. The framework is a guide for what to include, not a license to write four paragraphs. If the reader can feel the structure, you have overcooked it.
- Problem: name it specifically, in their language.
- Agitate: one line on what it costs, no fear mongering.
- Solution: what you do, framed as the way out.
- Ask: one small, low friction next step.
One soft CTA, and write like a human
End with a single, soft call to action. Stacking asks, or demanding a thirty minute meeting from a stranger, kills reply rates. A soft CTA lowers the bar: ask whether the problem is worth a short conversation, or whether they would like to see how it works, or simply whether you have it right. Interest-based asks consistently beat calendar-link demands in cold email.
Above all, write like a human and not a brochure. Short sentences. Plain words. No jargon, no buzzwords, no paragraph of credentials. Read the draft out loud, and if it sounds like marketing, cut until it sounds like a note from a colleague. The frameworks exist to keep you on the reader. The human voice is what makes the reader respond.
Questions, answered.
How long should a cold email be?
Are templates a bad idea?
What is a soft CTA exactly?
Want this built and run for you?
LongRun builds the outbound system, runs it, and hands it over at day 90. Book a strategy call to scope yours.