Skip to content

bereach-ai/linkedin-prospecting-skills / skills/cold-email

cold-email

Verified

Writes cold emails and follow-ups for people in a BeReach list: finds work emails, one sequence per persona, drafts the user sends. Use for any cold email or email outreach.

FileKindSize
SKILL.mdskill md8.5 KB
references/artifacts.mdmarkdown7.6 KB
references/deliverability.mdmarkdown3.1 KB
references/frameworks.mdmarkdown12.7 KB
references/legal.mdmarkdown3.5 KB
references/sequence.mdmarkdown2.2 KB

references/frameworks.md

View on GitHub
# Frameworks

How to use this library:
1. No study shows one framework beats another. What is measured is the parts: about them, their problem, short, one easy ask. "Nothing proven" never justifies keeping a part that fails: each part earns its place by what it does for the reader.
2. A framework only orders those parts. The default is the expert shape below, written in the user's voice; frameworks upgrade every part of the user's own emails that fails it, pro or novice (a reply count never keeps a failing part).

Evidence levels: **Measured** (a study with a method and a sample), **Survey** (self-reported), **Practice** (named practitioners, nobody measured it), **Vendor claim** (a sending tool's own data, observational), **Untraced** (repeated, no source found).

## Summary

| Framework | Author | Feeds | Evidence |
|---|---|---|---|
| Default: about them, who writes, one yes/no question | The parts the data supports | Every email 1, in the user's voice | Vendor claim |
| Trigger / 4T | Josh Braun | Email 1 with a dated event | Practice |
| PAS, gently | Untraced; Schwartz 1966, Kennedy 1990 | Email 1 on a clear role pain | Practice |
| BAB | Untraced | A follow-up carrying a real result | Untraced |
| 3Ps | Untraced | Email 1 on a real achievement of theirs | Untraced |
| QVC | Untraced | Email 1 opening on a sharp question | Untraced |
| Referral ask | Aaron Ross and Marylou Tyler, Predictable Revenue, 2011 | A senior person, owner unknown | Practice |
| Premise, Hook, CTA | Becc Holland, Flip the Script | The personal line, reused across the sequence | Practice |
| Value offer | Gong, executive data, 2026 | The ask to a busy executive | Vendor claim |
| Interest ask | Gong Labs, 304,174 emails | The yes/no question that ends every email | Vendor claim |
| Specificity | John Caples; David Ogilvy | The `{why now}` line, any number | Practice |
| "But you are free" | Gueguen and Pascual 2000; Carpenter 2013 | The way out in the last email | Measured (small, uncertain) |
| AIDA, as a check | C. P. Russell 1921 (acronym) | Self-check only, never a template | Measured (against) |
| Sender rules, law | Google, Yahoo, Microsoft; FTC, CNIL, ICO | `deliverability.md`, `legal.md` | Practice (official rules and law) |

## Default: about them, who writes, one yes/no question

Three lines, in the user's voice.

1. **About them:** a dated fact from their brief (the default when it holds one), else the persona's
   premise, true for all of them, with the problem it points to in their words.
2. **Who writes:** name + trade noun, one clause (never hidden on whose behalf, CNIL).
3. **One yes/no question:** naming the offer from the user's trade. Never a meeting, never a vague wish.

> Subject: hiring two SDRs
>
> Saw you opened two SDR roles last week. New reps usually spend their first month building lists by hand
> instead of calling, and the first quarter's pipeline shows it. I'm Sam, I build prospect lists for sales
> teams, sorted by territory and checked by hand. Want a free list of fifty accounts for one of the new
> reps' territories, ready before their first day?

Evidence: Vendor claim. Short (50 to 90 words), relevant, interest ask: every large sending dataset agrees; none compares frameworks.

## Which shape when

| You know | Use | Shape |
|---|---|---|
| A dated event (new role, hiring, funding, a post) | **Trigger / 4T** (Josh Braun) | Trigger, a question that makes them think, one yes/no question (the peer, from a real customer only, waits for a follow-up) |
| A clear pain the role has, no personal fact | **PAS**, gently | Problem, why it costs them, how it is solved. Never "agitate" hard. |
| An easy before and after | **BAB** | Today, what it looks like solved, how you bridge it |
| A real achievement of theirs | **3Ps** | Specific praise (not flattery), the outcome they want, a small ask |
| A sharp question they will want to answer | **QVC** | Question, value, call to action |
| A senior person, unsure who owns the topic | **Referral ask** (Aaron Ross) | Two lines: what it is about, are you the right person for it? |
| A strong premise from research | **Premise, Hook, CTA** (Becc Holland) | Premise 100% about them, hook to the problem, small ask. Reuse the same premise in every follow-up. |
| A busy executive | **Value offer** | Offer something useful (a benchmark, an estimate or audit of their own case) instead of a meeting |

## The frameworks

Examples use one invented seller: field calibration software for water networks, writing to a network manager.

### Trigger / 4T (Josh Braun, taught in his courses and posts; the template circulated from about 2021)
- What it says: Trigger (or Truth: a plain fact about their world), Think (a question that makes them rethink), Third-party (how a peer handles it: from a real customer the user gave, and only in a follow-up, never email 1), Talk (one yes/no question).
- On email: email 1 when a row carries a dated `whyNow`; the trigger is the personal line, the Talk is the yes/no question.
- Example: "Your utility just opened a tender for 4,000 new meters. Who checks they stay accurate after year two? I'm Sam, I build field calibration software for water networks. Want the field checklist?"
- Use when / not when: a fact under 6 months; not without one (never fake a trigger).
- Evidence: Practice. Sources disagree whether the first T is Truth or Trigger.

### PAS, Problem, Agitate, Solve (no traceable inventor; the same moves in Eugene Schwartz, *Breakthrough Advertising*, 1966; popularised by Dan Kennedy, *The Ultimate Sales Letter*, 1990)
- What it says: name a problem the reader has, make it felt, present the fix.
- On email: email 1 for a persona with a known pain and no personal fact; "agitate" is one clause of cost, never more.
- Example: "Meters on old sector lines drift, and the loss shows up as unbilled water. I'm Sam, I build field calibration software for network managers. Want the 1-page check for your oldest sector?"
- Use when / not when: a problem-aware reader; not one who does not feel the problem yet.
- Evidence: Practice. Making the threat bigger moves little; showing the fix works moves more (O'Keefe and Hoeken 2021).

### BAB, Before, After, Bridge (no traceable inventor)
- What it says: their world now, their world solved, how to get from one to the other.
- On email: a follow-up that carries a real result of the user's customer.
- Example: "Before: two technicians a week on meter checks. After, at a utility your size: one day a month. The bridge was calibrating in the field. Want their setup on one page?"
- Use when / not when: a real "after" exists; never with an invented one.
- Evidence: Untraced. Its ingredients (vividness, the fix works) are measured as small gains.

### 3Ps, Praise, Picture, Push (no traceable origin; practitioner template)
- What it says: specific sincere praise, the outcome they want, a small ask.
- On email: email 1 when they did something real and recent (a published network plan, a talk).
- Example: "Your talk on cutting non-revenue water by sector was the clearest I have heard. If field checks took a day instead of a week, the next sector would come sooner. I'm Sam, I build field calibration software. Want our sector checklist?"
- Use when / not when: a real thing to praise; never generic flattery ("loved your post").
- Evidence: Untraced. Relevance beats compliments in practitioner advice.

### QVC, Question, Value, Call to action (no traceable origin; practitioner template)
- What it says: open on a question about their situation, give one piece of value, ask.
- On email: email 1 when one question will make them want to answer.
- Example: "How do you know which sector meters drifted since last spring? I'm Sam, I build field calibration software that finds them in one pass. Want the method on one page?"
- Use when / not when: a sharp, specific question; not a rhetorical one ("Do you want to save money?").
- Evidence: Untraced. Opening on a question is not a lever by itself (measured, small).

### Referral ask (Aaron Ross and Marylou Tyler, *Predictable Revenue*, 2011, Cold Calling 2.0)
- What it says: a short plain email to a senior person asking who handles the topic.
- On email: email 1 to a director when the owner of the problem is unknown.
- Example: "Your network is replacing meters this year, and someone will own their accuracy. I'm Sam, I build field calibration software for water networks. Are you the one who looks after meter accuracy?"
- Use when / not when: senior readers, unclear owner; not when the right person is already in the list.
- Evidence: Practice. Results quoted online are vendor retellings.

### Premise, Hook, CTA (Becc Holland, Flip the Script, training and podcast interviews; year not traced)
- What it says: a premise 100% about them (why you, why now) from research, a hook to the problem, a small ask; one premise reused across the sequence; no real premise, fall back to persona relevance.
- On email: the `{why now}` line and its reuse in every follow-up.
- Example: premise "You are merging two water boards' networks this year"; every follow-up refers back to the merger.
- Use when / not when: a real premise from the brief; never a faked one.
- Evidence: Practice.

### Value offer (Gong, "Do execs really reply to cold email?", executive sales cycles, 2026)
- What it says: executives reply more to an offer of value (Gong's example: a peer benchmark) than to a meeting request.
- On email: the ask names an object the reader keeps, from the user's own trade.
- Example: "Want a drift estimate for your own network?"
- Use when / not when: senior readers; the object must exist before the send.
- Evidence: Vendor claim. Gong's own customer data.

### Interest ask (Gong Labs, cold email call-to-action study, 304,174 emails)
- What it says: a meeting booked (Gong's measure) for 30% of interest asks, 15% of specific-time asks, 13% of open-ended asks; in live deals the order flips.
- Example: "Worth a look for your northern sector?"
- Use when / not when: cold emails; a specific time only once they are engaged.
- Evidence: Vendor claim. Observational, one vendor. Gong's phrasing names no object; ours always does.

| Ask | Example | Meetings |
|---|---|---|
| Interest | "Worth a look?" | 30% |
| Specific time | "Tuesday at 4?" | 15% |
| Open-ended | "Time next week?" | 13% |

### Specificity (John Caples, *Tested Advertising Methods*, 1932 onward; David Ogilvy, *Ogilvy on Advertising*, 1983 (be specific))
- What it says: exact, checkable facts beat general claims.
- On email: the personal line names one checkable, dated fact; any figure comes from the user.
- Example: "opened a tender for 4,000 meters in September" over "is growing fast".
- Use when / not when: every line; never a precise number nobody gave.
- Evidence: Practice.

### "But you are free" (Gueguen and Pascual, 2000; Carpenter, meta-analysis, Communication Studies, 2013)
- What it says: telling the reader they are free to say no raised compliance in many studies.
- On email: the last email offers the way out (never a lever on email 1); every follow-up carries the plain opt-out line.
- Example: "Not a priority this year? Reply no and I will stop."
- Evidence: Measured, small and uncertain: a 2023 preregistered re-analysis (Fillon, Souchet, Pascual, Girandola, Meta-Psychology) found no effect in the low-bias studies.

### AIDA, as a check (acronym in C. P. Russell, *Printers' Ink*, 1921; usually credited to E. St. Elmo Lewis, 1898, a date a 2024 history paper could not confirm)
- What it says: Attention, Interest, Desire, Action.
- On email: only a check that email 1 has a reason to read, a reason to care and one ask; never the template.
- Example: draft with no ask: fails the Action check.
- Evidence: Measured, against: a review of 250+ studies found little support for a fixed sequence (Vakratsas and Ambler 1999).

## Deliverability and law (by name; the rules live elsewhere)

- Deliverability, in `deliverability.md`: Google email sender guidelines (2024), Yahoo sender requirements (2024), Microsoft Outlook.com high-volume sender rules (2025), SPF, DKIM and DMARC, one-click unsubscribe (RFC 8058), M3AAWG Sender Best Common Practices.
- Law, in `legal.md`: CAN-SPAM Act (United States, FTC compliance guide), GDPR legitimate interest (article 6.1.f, EDPB Guidelines 1/2024), CNIL rules on B2B prospecting (France), PECR (United Kingdom, ICO), UWG section 7 (Germany).

## Personal line rules

- Relevance beats compliments. "You are hiring SDRs" beats "Loved your post".
- One premise for the whole sequence; the fresh brief before a follow-up only checks for a reply or a newer fact.
- No real fact? Use the persona's problem. Never fake one.
- The line names something checkable and recent (its date in the review); the tense follows the date:
  "just" under 1 month, 1 to 6 months "in <month>" or "recently", over 6 months not used.

## French

- Same shape, same length. French runs longer: cut a sentence rather than squeeze.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall