A deep read of Connor Murray's 10 Years of Expert Cold Email Advice in 36 Minutes (B2B Sales) (36:09) on the Higher Levels channel. Murray was the #1 SDR at Oracle, then the #1 SDR manager two years running, and now an enterprise AE who still runs this system. He has taught it to thousands of reps.
Why this analysis exists
This is one of the source layers behind the BuildOS cold-email-engagement-first-outreach skill. It supplies the body craft + cadence layer — the three-paragraph structure, assumptive language replacement, and the AB follow-up rhythm. It is the "what you actually type and when you send it" layer of the skill.
Core thesis
Most cold email training falls into two failure camps. Sales-enablement training teaches five-paragraph emails wrapped in acronyms — a great psychology lesson nobody reads. LinkedIn sales gurus swing the pendulum to the opposite extreme: too-short, fake-personalized notes ("fellow eagle," "saw we're both dog dads") that come off as manipulative and copy-paste. Both fail because both ignore the actual psychology of a busy buyer scanning their inbox.
The working system is less is more, simple is better, repeatable structure, high quality at scale. Three paragraphs. Assumptive language. Pre-built lists and persona templates ("coil the spring") so the daily target is 100+ emails in an hour, not 10 hand-crafted emails in a morning. Four-touch cadence (initial + three follow-ups) on a 24–48 hour rhythm — because 70 to 80 percent of booked meetings come from the follow-ups, not the first email.
The framework
1. The three-paragraph body
Most cold emails fall between four and six sentences, three short paragraphs:
- Who I am. Name, company, the team you're part of. One to two sentences. Position yourself as if you're already part of their account team — formal, not cutesy.
- Why I'm relevant. Priorities and challenges this specific persona is likely to care about, plus how your team solves them at a high level. This is the only paragraph where industry/role specificity shows up.
- What I want. Time on their calendar. Not "is this worth a chat" — "I'm looking to set some time for an introduction. What does your availability look like later this week?"
The brain prefers threes. Once an email hits four or five paragraphs, scanners flick away. Murray's rule of thumb: it should fit on one phone screen.
"It's actually proven in psychology that in written word the brain likes threes. Anything more than three paragraphs — once it gets to four or five it's like, 'this is too much.' They're less likely to scan. You scroll down and back up and you're like, you want it to fit on one phone."
2. Assumptive language replacement
The single biggest reply-rate killer is passive language — fluffy openings and interest-based CTAs:
| Passive (kills replies) | Assumptive (gets replies) |
|---|---|
| "I was hoping to set up some time…" | "I'm looking to set up some time…" |
| "If you're interested…" | "Do either of these dates work for you?" |
| "Is this worth a chat?" | "What does your availability look like later this week?" |
| "Is this worth exploring more?" | "I'll send the invite once you share availability." |
| "Warmest regards," | "Thanks in advance," |
Passive language tells the buyer you don't believe the meeting is important. Assumptive language signals you expect the meeting to happen — because they're one of your accounts and you have a job to do.
The goal of every email is a response, not a meeting. Yes, no, or objection. You cannot book from silence; you can book from any reply, including a no. The agent's job is to write language that pulls a reply.
3. Coiling the spring
The reason most reps cap at 10–20 emails a day is that they're trying to research, target, write, and send all inside the same hour. Murray's prep system separates research from sending:
- Filter once. Build buyer lists by job title × department × industry × company size × buying trigger. Don't mix personas inside one list.
- Batch buyers. Each list is one persona (e.g., CFOs in financial services, controllers in banking, VPs of FP&A in retail).
- Template per list. Write a base three-paragraph template that fits that persona's priorities and challenges. The only fields that change per email are first name and company.
He spends two days to a full week up front building lists and templates. Then every morning at 8 a.m. he picks a list, picks a template, and sends 100 emails before doing anything else.
This is the move that takes a rep from 10 emails a day with difficulty to 100 emails a day in an hour. The personalization isn't gone — it has just moved upstream, into the list/template pairing, instead of being done one email at a time.
4. The AB follow-up cadence
Four touches total: one initial + three follow-ups. Sent on alternating days so the buyer sees four emails inside seven to eight days.
- Monday: Initial email to List A
- Tuesday: Initial email to List B
- Wednesday: Follow-up #1 to List A
- Thursday: Follow-up #1 to List B
- Friday: Follow-up #2 to List A
- (And so on.)
Each follow-up is short and redirects the reader back to the original email, not a new ask:
- Benefit-of-the-doubt follow-up. "Hey — just want to make sure you caught my note. Do either of those dates work, or let me know if you have time to speak this week."
- Professional dissatisfaction follow-up. Subject preview reads "Please give me your thoughts on this." This is Murray's highest-reply-rate line of all time, cold call or cold email. The recipient's fight-or-flight reads the preview, scrolls down, and finally reads the original email properly.
- Assumptive breakup. "Is next month a better time to talk about this? Just want to close the loop either way — let me know."
Why every other day, not every Monday? Because a Monday-Monday-Monday cadence reads as automated; the buyer learns "if I wait one more Monday they'll go away." A 24–48 hour rhythm signals you're a real person trying to reach them. After four emails, stop. Anything beyond five touches starts to read as desperate and devalues the sender.
5. The objection response bank
When the assumptive language works, the third common response (after yes/no) is an objection: "we already have a solution," "no budget," "not a priority right now."
Treat objections as the actual unit of work. Build a base template per objection in a swipe file. Pull the base template, add 1–2 lines of context specific to the prospect, send. Most objections can be acknowledged-and-redirected: "Acknowledged on no budget right now — it still makes sense to set up time so when priorities shift we're ready to support."
This is where pre-work compounds. The first time you handle "we already have a solution" you write a thoughtful response. The hundredth time, you pull the template and customize two lines.
6. Two outreach buckets, not one
The base template runs the volume bucket — the wide net you cast across persona × industry lists. It is intentionally not over-personalized so 100 emails a day can ship.
Strategic accounts go in a focused bucket. Same three-paragraph structure, but the first line carries deep context: an earnings-call quote, a 10-K priority, or — the biggest weapon — "I spoke with [name] on your networking team and understand that [specific gap] is a focus this year." This signal does not scale to a hundred recipients a day; it scales to a handful, paired with phone, voicemail, and LinkedIn.
The mistake is conflating the two. Hyper-personalizing at volume kills throughput. Spraying templates at strategic accounts wastes the most valuable contacts.
7. Tracking three inputs, not one
Don't optimize "reply rate" as a single number. Track three rates that diagnose three different problems:
- Open rate. Diagnoses subject line and sender reputation. Low open rate → fix subject, fix preview text, fix domain warmup, increase follow-up frequency.
- Reply rate. Diagnoses body craft and CTA. Low reply rate → passive language is leaking back in; replace it with assumptive phrasing.
- Meeting-booked rate (from replies). Diagnoses the "why I'm relevant" paragraph. Low meeting-booked rate → priorities and challenges aren't resonating; re-segment or re-write that middle paragraph.
A 1–2% improvement at each stage can triple pipeline at SDR-team scale.
What this looks like in the wild
Two base templates Murray reads aloud are short enough to use as scaffolds.
Outbound-to-existing-account (financial services, finance buyer):
Hi John, my name's Connor Murray and I'm part of the [Company] financial applications team responsible for supporting [Account]. Given your role I'm looking to introduce our team and get aligned with your priorities going forward.
My team specifically works on priorities related to expense optimization, financial forecasting, and automated financial reporting. We work with clients to deliver real-time visibility into financial data, reduce unnecessary operational expenses, and automate much of the month-end reporting process.
I'm looking to set some time for an introduction as my team will be the main point of contact for any priorities in these areas going forward. What does your availability look like later this week?
Thanks in advance,
Connor
Pure outbound (construction industry, networking buyer):
Hi John, my name is Connor Murray and I'm part of the construction team at [Company]. We work with networking teams in the construction space to improve system reliability and accelerate response times.
My team specifically focuses on priorities related to network management, managed cloud hosting, and mobile device management, and we work with clients to proactively monitor and maintain networks, plan and execute cloud migrations, and streamline the onboarding of mobile devices.
Do you have availability for an introduction this week? Let me know when works best and I will send us an invite. Looking forward to it.
Connor
The two templates are structurally identical. The only thing that changes between volume sends is the company-specific noun and the persona's priority list. That is what "coiling the spring" buys you.
Where Murray's system diverges from the rest of cold-email-internet
- No "fellow eagle" personalization. Fake warmth is worse than no warmth — the buyer recognizes the template instantly.
- No interest-based CTAs. "Worth a chat" is the single phrase he replaces first when coaching reps.
- No 15-touch cadences. Four to five touches max. The 35-follow-ups-and-they-finally-booked LinkedIn anecdote ignores the thousand contacts the rep burned through to find that one.
- No Monday-Monday-Monday automation rhythm. Buyers pattern-match it as automation; reply rates drop.
- No coast after a clean first email. The first email is the bait. 70–80% of meetings come from the follow-up that redirects them back to it.
What this layer contributes to the BuildOS skill
The Murray analysis supplies the body, cadence, and prep system of the skill. It is the "what to type and when to hit send" layer. Two other source layers handle infrastructure/volume math (Aaron Shepherd) and engagement-first / two-touch / micro-targeting math (Austin Schneider at Instantly). Murray's piece is where the agent's actual email draft gets shaped.