Cold Call Opener

Cold Call Opener

Draft what a rep says between "hello" and the prospect's first real response. The opener ends the moment the prospect engages or brushes off - everything after that belongs to a neighboring skill (see References). The published evidence on opener wording comes almost entirely from two Gong datasets that contradict each other, plus Cognism's funnel data. This skill reports each source honestly instead of blending them into a fake industry benchmark.

Interview

Ask before drafting anything. One question per message; offer multiple-choice answers when possible. Skip any question the user already answered.

• B2B or B2C? (If both, draft separate openers - the pain framing and the legal scrubbing differ.)
• Who picks up: title and seniority? (IC / manager / director-VP / executive / business owner / consumer.)
• What does the product do, in one plain sentence a stranger would understand? Refuse feature lists; one sentence.
• What pain do you believe this person has, in their words?
• Where did that pain hypothesis come from: a verified signal (job posting, funding, tool change, something they said or submitted) or an educated guess? This decides the wording, not just the confidence.
• Desired outcome of the call: booked meeting / qualification / referral to the right person / (B2C) quote, appointment, or sign-up?
• List temperature: fully cold, warm-ish (prior touch, inbound form), or a re-attempt?
• If a re-attempt: what happened on the previous attempts?
• How does the rep naturally talk: direct, warm, understated, high-energy? (Or paste two sentences of how they actually speak.)
• Which market/jurisdiction is being called: US / UK / EU member state (which one) / France / other? For B2C this drives mandatory scrubbing - see references/consumer-calling-constraints.md.
• By what date must this opener be booking meetings? (Inside two weeks promotes the cheapest pattern and caps the test at one variable; a quarter or more makes the research-heavy pattern affordable.)
• One-off win or compounding asset: a script for one campaign push, or the team's default opener for the year? (One-off promotes direct reason-for-call; compounding promotes permission-based, whose rehearsal cost is paid once and collected on every call after.)
• Effort ceiling: rehearsal hours per rep, months of phone tenure behind them, and minutes of pre-call research affordable per account. (Near-zero research minutes removes context-first/peer-proof from the menu for this run; a first-week rep promotes direct reason-for-call to first.)

Opener anatomy

Four components, one length budget. The whole opener runs 5-30 seconds of rep speech, then stops.

Stay short for two reasons:

• Chris Beall's framing: a cold caller has roughly seven seconds to establish trust, since curiosity, not value, is what avoids triggering reactance.
• Jason Bay's observation, quoted in Cognism's 2025 report: only 10% of cold calls make it past 2 minutes. An opener that eats 45 seconds has already spent a third of the median call before the prospect says a word.

1. Identification (~3-5s). Full name plus company. Honest, unhurried, no fake familiarity.
2. Reason-for-call (~5s). One sentence naming why this person, today. Gong credits John Barrows with the test: if the rep cannot finish "the reason for my call is...", do not make the call.
3. Pain hypothesis (~10s). One spoken sentence the prospect recognizes as their own problem. Rules in Pain-hypothesis line below.
4. Ask / transition (~5s). Exactly one ask, matched to the desired outcome from the interview. Then stop talking.

Working cap: about 75 words, a self-set bar rather than a published one. Verify with a read-aloud timer, not a word counter alone.

Workflow

1. Run the Interview; collect every answer first.
2. If you can browse the web, verify the pain signal (job posting, funding news, public statement); otherwise ask the user for the evidence. Never invent a signal. For turning raw signals into angles, see mbfinotti/sales-skills@sales-outreach-personalization.
3. Enter brainstorming mode: propose 2-3 candidate angles (each = one opener pattern + one pain framing). Score every candidate on the three axes Choosing the pattern uses:

• Measured value.
• Rep effort (rehearsal, live composure, how it fails in unskilled hands).
• Conversations needed before it can be judged.

Recommend one and name the axis that decided it. Ask questions one at a time. Draft nothing until the user picks an angle.

1. Pick the pattern with the ranking in Choosing the pattern; open references/opener-patterns-and-evidence.md only for the full evidence trail behind a rate or an attribution.
2. Draft 2-3 variants. Each variant isolates exactly one variable (pattern, pain wording, or ask) against the others; a variant that changes two things teaches nothing.
3. Write delivery notes per variant (Delivery below).
4. Run your preferred humanizer skill over every variant, then read each aloud with a timer. A cold call opener is speech; raw first-draft model output is never the final deliverable.
5. Score every variant against the Self-check gate; iterate until all items pass.
6. Hand off the artifact in Expected output, including the test plan.
7. If your harness has persistent memory, memorize the approved persona, pain hypothesis, product sentence, and - once tested - the winning opener; later runs then skip the interview.

Choosing the pattern

Rank patterns by what they return per unit of rep effort, and say the ranking out loud instead of letting row order imply it. Effort here is rehearsal time, live composure, and how badly the pattern fails in an unskilled rep's hands - a pattern that is strong for a veteran and damaging for a new rep is high-effort, not high-value. Full evidence, attributions, and the Gong 2018/2024 contradictions sit in references/opener-patterns-and-evidence.md.

The axes disagree, so each gets its own line:

• efficiency: permission-based > direct reason-for-call > context-first/peer-proof > pattern interrupt
• value: context-first/peer-proof == permission-based > direct reason-for-call
• effort: pattern interrupt > context-first/peer-proof > permission-based > direct reason-for-call

That == is a real tie, not a way of avoiding the call. Gong's 2024 study separates those two by 0.06 percentage points and publishes no per-opener sample size, so nothing in the data can order them. They split on effort instead.

No compliance-cost axis belongs on this menu. Consent and scrubbing duty attaches to the list and the jurisdiction, identically for every pattern (see references/consumer-calling-constraints.md).

1. Permission-based - the default rung.

• Value: ~11% of connected calls produced a held meeting in Gong's 2024 study, roughly 5x that study's worst-scoring opener.
• Effort: about an hour of rehearsal, paid once and collected on every call after. The rep names the interruption without flinching, then actually stops talking.
• Fails softly: rushed, it sounds like an apology, which costs that call and nothing else.
• Guessed pain routes here, with the pain line hedged (see Pain-hypothesis line). A guess asserted as fact hands over the top-five brush-off "I don't have the problem you're describing" (Cognism 2025).

1. Direct "reason for my call" - the cheapest, and the only one that composes.

• Value: about double baseline in Gong's 2018 study, the smallest measured lift on this menu. Gong describes it as pairable with any other opener, so it never fully loses a round.
• Effort: minutes. One sentence, tested by John Barrows' rule: if the rep cannot finish "the reason for my call is...", do not make the call.