Cold Outreach Coaching Conversation Guide

Before the 1:1 — What to Pull

For the review period (typically trailing 2–4 weeks), pull:

• Sends
• Open rate
• Reply rate
• Positive-reply rate
• Meetings booked
• Unsubscribe / spam-complaint rate

Compare each to the team benchmark or median, not an arbitrary target. Reference ranges (typical, not universal — your list quality and ICP will move these):

Identify the ONE metric most out of line. That's today's topic — don't try to fix everything in one conversation.

Opening the Conversation

"Before I share what I'm seeing in the numbers, I want to hear it from you first — walk me through the last couple weeks of outreach. What do you feel good about? What's been harder than you expected?"

This order matters: it surfaces whether the gap is awareness (they don't see the problem) or execution (they see it but haven't fixed it) before you anchor them to your read of the data.

Diagnostic Question Sets by Symptom

Symptom: Low open rate (otherwise normal)

• "What's your subject line approach right now — are you testing variations or reusing the same ones?"
• "What time of day and day of week are most of these going out?"
• "How fresh is this list — when was it last verified?"
• "Who's it coming from — a name they'd recognize, or a generic address?"

Symptom: Opens are fine, reply rate is low

• "When you read your own email back, would a busy person reply in 10 seconds or less?"
• "What's the one thing you're asking them to do — is there more than one ask in there?"
• "How much of this message is about them versus about us?"
• "Where did the personalization come from — something you found, or a mail-merge field?"

Symptom: Replies coming, but mostly negative/no

• "Who are you sending to — is there a pattern in title or company size in the 'not interested' replies?"
• "What's the trigger or reason you're reaching out to this list right now?"
• "If you had to guess — do they actually have this problem, or are we assuming they do?"

Symptom: Positive replies aren't converting to booked meetings

• "How fast are you responding once someone replies positively?"
• "What does your reply to a 'sure, tell me more' actually say — are you making the scheduling one click, or asking them to do the work?"
• "Is there a qualifying question getting lost between the positive reply and the calendar invite?"

Symptom: High unsubscribe or spam-complaint rate

• "How many times is this list hearing from us in a month, across every sequence they might be in?"
• "Is there any chance this list includes people who've already told us no?"
• Note: this symptom is often an infrastructure/list-hygiene issue, not a coaching issue — escalate if the rep's own process looks sound.

The "Why" Ladder

Don't stop at the first answer. Ask "why" up to three times to get from symptom to root cause.

"Reply rate is low." → Why? "My messages are pretty generic." → Why? "I don't have time to research each account." → Why? "I don't have a fast, repeatable way to find a relevant detail." Root gap: needs a faster research method — not a lecture on "personalize more."

Naming the Underlying Skill

Once you've found the root cause, name it plainly and connect it forward:

"What I'm seeing is a research-speed gap, not an effort gap — you're doing the work, but the method takes too long to sustain at volume. That's a specific, learnable skill: fast account triage. Let's build you a 5-minute research routine you can run before every send."

Commitment & Practice Plan

• "What's the one thing you'll change in your next 10 sends?"
• "How will we both know it worked — what number moves?"
• "What do you need from me to make that stick — a template, a review of your first 3 attempts, something else?"
• "When should we check back in on this specifically?"

Escalation Flags — Not a Coaching Problem

• Deliverability/domain reputation (mass bounces, spam-folder placement) → route to whoever owns sending infrastructure
• Compliance risk (no opt-out, no sender ID, purchased list in a regulated region) → route to compliance/legal immediately, don't coach around it
• Tooling gaps (no working sequencer, no verified list) → that's a resourcing problem — name it as such to your own leadership

One-Page Flow Summary

1. Pull data, find the ONE outlier metric
2. Open with self-diagnosis
3. Run the matching diagnostic question set
4. Ladder "why" 2–3x to find the root skill gap
5. Name the skill plainly
6. Get a specific commitment + how you'll both know it worked
7. Escalate infrastructure/compliance issues instead of coaching around them