Enterprise Cold Email Cadence — Playbook
Enterprise Cold Email Cadence the playbook · templates · examples · benchmarks
Enterprise Sales Outbound SDR Cold Email Cadence Design
Cold email has a bad reputation because most cold email is bad. Spray-and-pray templates, fake personalisation, aggressive CTAs sent to the wrong people. That’s not what this playbook teaches.
This is the enterprise cold email playbook — what actually works when you’re reaching out to VPs, Directors, and C-level executives at companies that have never heard of you. The emails are short. The personalisation is real. The ask is small. And the cadence is designed around how busy enterprise buyers actually behave: they don’t ignore you because they’re not interested — they ignore you because they’re drowning in 200 emails a day and yours didn’t earn a second glance.
Who this is for: SDRs, AEs doing their own prospecting, founders doing outbound for the first time, and sales leaders designing cadences for their team.
══════════════ PART I: FOUNDATIONS ══════════════
Part I Foundations Before writing a single email, you need to understand why cold email works in enterprise, how it differs from SMB outbound, and what makes the difference between an email that gets a reply and one that gets archived.
01 Why Cold Email Still Works in Enterprise
Enterprise buyers don’t respond to ads. They don’t fill out forms. They don’t attend webinars for products they’ve never heard of. The only way to reach a VP of Engineering at a Series C company or a CTO at a Fortune 500 is to show up in their inbox with something relevant.
Cold email works in enterprise because of three structural truths:
- Enterprise buyers are unreachable by other channels. They have ad blockers, they don’t Google for solutions, and their assistants filter inbound calls. Email is the one channel where you can reach them directly.
- Enterprise decisions start with awareness. Nobody buys a $100K+ solution from a cold email. But they do take a 15-minute call from a cold email — and that call starts a 6-month enterprise sales cycle. The email is the door-opener, not the close.
- Personalisation at enterprise scale is feasible. You’re not emailing 10,000 SMBs. You’re emailing 200–500 target accounts with 2–3 contacts each. At that volume, genuine personalisation is possible and expected.
The goal of a cold email is not to sell. It is to earn a 15-minute conversation. That’s it. Every word should serve that single objective.
02 Enterprise vs SMB — Different Game, Different Rules
| Dimension | SMB Outbound | Enterprise Outbound |
|---|---|---|
| Volume | 200–500 emails/day per SDR | 30–60 emails/day per SDR |
| Personalisation | Template with merge | Researched. Specific to their company, role, and situation. |
| Research time | 30 seconds per prospect | 5–15 minutes per prospect |
| Email length | 3–5 sentences | 4–7 sentences. Slightly longer because context matters more. |
| CTA | “Book a demo” / calendly link | “Worth a 15-min conversation?” Never a Calendly link cold. |
| Cadence length | 5–7 touches over 14 days | 8–12 touches over 18–28 days |
| Channels | Email + maybe LinkedIn | Email + LinkedIn + Phone + mutual intros |
| Thread strategy | New email each time | Reply to own thread (stays in same conversation) |
| Expected reply rate | 3–8% | 8–20% (lower volume, higher quality) |
| Meeting book rate | 1–3% of emails | 3–8% of prospects contacted |
The enterprise math: 50 well-researched prospects per week × 8% meeting rate = 4 meetings/week = 16 enterprise meetings/month. At $50K+ ACV, that’s enough pipeline to hit quota. Quality > quantity.
03 Anatomy of a Great Enterprise Cold Email
Every high-performing cold email has exactly five components. Miss any one and the email fails:
The Five Components
| # | Component | Purpose | Length |
|---|---|---|---|
| 1 | Subject Line | Get the email opened. That’s it. | 3–6 words |
| 2 | Opening Line | Prove this isn’t a mass blast. Show you did research. | 1 sentence |
| 3 | Problem / Observation | Name a pain they have. Make them nod. | 1–2 sentences |
| 4 | Value Prop / Proof | What you do and why it matters. Ideally with a number. | 1–2 sentences |
| 5 | CTA | One clear, low-commitment ask. | 1 sentence |
Good vs Bad — Side by Side
BAD
Quick question about your data stack
Hi John,
I’m reaching out because I think our platform could be a great fit for your team. We help companies like yours streamline their data operations and improve efficiency by up to 40%.
We work with over 500 companies including [logos]. Our platform offers real-time analytics, automated pipelines, and enterprise-grade security.
Would you be open to a 30-minute demo this week?
Best,
Sarah
GOOD
re: Snowflake costs
Hi John,
Noticed your team posted a dbt role last week — looks like you’re scaling the analytics layer on top of Snowflake.
Curious if compute costs are becoming a conversation yet. We helped Ramp’s data team cut their Snowflake bill by 35% without changing any queries — just smarter scheduling and warehouse sizing.
Worth a 15-min call to see if it’s relevant?
Sarah
Why the good one works: (1) Subject looks like a reply, not a pitch. (2) Opening references a specific thing they did (job posting). (3) Problem is named precisely (Snowflake costs). (4) Proof is a named company + specific number (Ramp, 35%). (5) CTA is small (“15 min”) and non-committal (“see if it’s relevant”). Total length: 4 sentences.
The Rules
- Under 100 words. Enterprise execs read on mobile. If they have to scroll, they won’t read.
- No “I” as the first word. Start with them, not you. “I’m reaching out because…” = instant delete.
- No attachments. Triggers spam filters. Feels salesy.
- No HTML formatting. Plain text looks like a real email from a real person. HTML templates look like marketing.
- One CTA only. “Want to chat or see a case study or check our website?” = decision paralysis = no reply.
- No Calendly links in email 1. Too presumptuous. Earn the right to share your calendar.
- Sign off with first name only. “Best regards, Sarah Johnson, Account Executive, Acme Corp” = corporate robot. “Sarah” = human.
══════════════ PART II: THE CADENCE ══════════════
Part II The 18-Day Enterprise Cadence This is the sequence that works. Four emails, two LinkedIn touches, one phone call, spread over 18 days. Each touch has a different purpose. Each email can stand alone — because enterprise buyers often read email 3 without seeing emails 1 and 2.
04 The 18-Day Sequence — Overview
| Day | Channel | Touch | Purpose | Tone |
|---|---|---|---|---|
| 1 | Email 1: The Opener | Earn attention. Prove relevance. | Curious, specific | |
| 2 | Connect + short note | Multi-channel presence. No pitch. | Warm, brief | |
| 5 | Email 2: The Value Drop | Share a relevant insight or resource | Helpful, not salesy | |
| 8 | Phone | Cold call (30-sec hook) | Voice creates familiarity. Reference emails. | Direct, human |
| 10 | Email 3: The Case Study | Social proof from a similar company | Peer validation | |
| 13 | Engage with their content | Build familiarity. Thoughtful comment. | Genuine interest | |
| 18 | Email 4: The Breakup | Create urgency through scarcity of your attention | Respectful, final |
Thread strategy: Emails 2, 3, and 4 should be replies to email 1 (same thread). This keeps the conversation in one place, makes it look like an ongoing dialogue, and increases the chance they scroll up and read earlier messages. Never start a new subject line for follow-ups.
05 Email 1: The Opener
Goal: Get a reply. Nothing else. The opener is the most important email — it determines whether the rest of the sequence gets read.
Template A — The Trigger-Based Opener
Best when you have a specific trigger: job posting, funding round, product launch, conference talk, LinkedIn post.
To: ** · Day 1
Hi ,
We helped .
Worth a 15-min call to see if it’s relevant for ?
Example: Targeting a VP Engineering after a funding round
To: Priya Sharma · Day 1 congrats on the Series B
Hi Priya,
Saw the $40M round last week — congrats. Based on your job postings, looks like the eng team is about to double.
Scaling from 30 to 60 engineers usually breaks the dev environment — builds slow down, CI queues back up, and onboarding takes 2x longer than it should. We helped Vercel’s team cut CI time by 60% during their scaling phase without changing their toolchain.
Worth a quick call to see if it’s relevant?
Sarah
Why this works: The trigger (funding) is public and real. The observation (team doubling) shows research. The problem (CI slowing down) is specific and plausible. The proof (Vercel, 60%) is named and quantified. The CTA is one sentence, low-commitment.
Template B — The Observation Opener
Best when there’s no obvious trigger. You lead with an insight about their business.
To: Marcus Chen · Day 1 quick thought on
Hi Marcus,
I was looking at — noticed you’re using Segment for event tracking but your pricing page doesn’t mention usage-based tiers. Curious if that’s intentional or if the billing infrastructure hasn’t caught up yet.
We built the metering layer for Resend and Neon so they could launch usage-based pricing in weeks instead of months.
Is this on your radar at all?
Sarah
Why this works: The opening line proves she actually looked at their product (not a mass email). The observation is insightful, not generic. The question (“intentional or hasn’t caught up?”) is non-threatening and opens a real conversation.
06 Email 2: The Value Drop
Goal: Provide value without asking for anything. This email builds credibility. It says: “I understand your world.”
Day 5. Reply to email 1 thread. No new subject line.
To: Priya Sharma · Day 5 · Reply to thread Re: congrats on the Series B
Hi Priya,
No response needed — just thought this might be useful. We published a short analysis of how 15 Series B companies handled eng scaling without blowing up their build times:
The tl;dr: the teams that invested in build infrastructure before hitting 50 engineers saved an average of 3 months of productivity debt later.
Happy to chat whenever timing makes sense.
Sarah
Why this works: “No response needed” removes pressure. The content is relevant to their exact situation (scaling eng team post-Series B). The tl;dr shows she’s not wasting their time. The CTA is soft and non-urgent. The value drop rule: The content you share must be genuinely useful even if they never buy from you. If it’s a thinly-veiled product brochure, it fails. Blog posts, benchmarks, frameworks, industry data, teardowns — anything that helps them do their job better.
07 Email 3: The Case Study
Goal: Social proof. “Someone like you had this problem and we solved it.” Enterprise buyers are risk-averse — they need to see that someone similar has already made the bet.
Day 10. Reply to same thread.
To: Priya Sharma · Day 10 · Reply to thread Re: congrats on the Series B
Hi Priya,
Quick one — just wrapped a case study with a team in a similar spot to yours (Series B, 40→80 eng, monorepo on GitHub Actions):
• Build times: 22 min → 7 min
• CI costs: down 45%
• Onboarding: new eng productive in 2 days vs 2 weeks
Happy to share the details if useful. Either way, hope the scaling is going well.
Sarah
Why this works: The case study is described in the email body (not behind a link they won’t click). Three bullet points with specific numbers. The closing (“either way, hope the scaling is going well”) is human, not transactional. It gives them an easy out while keeping the door open.
08 Email 4: The Breakup
Goal: Create gentle urgency by signalling that this is the last outreach. Counterintuitively, breakup emails often get the highest reply rate — because the prospect realises the window is closing.
Day 18. Reply to same thread.
To: Priya Sharma · Day 18 · Reply to thread Re: congrats on the Series B
Hi Priya,
I’ll keep this short — I know build infrastructure isn’t always top of the priority list when you’re heads-down on hiring and shipping.
If it ever becomes relevant, I’m here. No hard feelings either way.
Sarah
Why this works: It’s 3 sentences. It acknowledges their reality (“heads-down on hiring and shipping”). It doesn’t guilt-trip or pressure. It leaves the door open permanently. The contrast with the typical “FINAL ATTEMPT!!!”-style breakup emails makes it stand out. The psychology: Breakup emails work because of loss aversion. The prospect has been aware of your emails for 18 days. This final “I’m going away” creates a micro-moment of “wait, should I respond before this person stops trying?” Reply rates on email 4 are typically 2–3x higher than emails 2 and 3.
09 Multi-Channel Touches
Day 2: LinkedIn Connection
LinkedIn · Connection Request
Hi Priya — I sent a note about build infrastructure for scaling teams. No pitch here, just thought it’d be good to connect. Congrats again on the round.
Keep it under 300 characters. Reference the email so they connect the dots. Do NOT pitch in the connection request.
Day 8: Phone Call (30-Second Hook)
If you get through:
“Hi Priya, this is Sarah from [Company]. I sent you a couple of emails about build infrastructure — I know you’re scaling the eng team post-Series B. I’ll be quick: we helped Vercel cut their CI time by 60% during a similar growth phase. Is that something worth a 15-minute conversation, or is this not a priority right now?”
If voicemail: leave a 20-second message referencing the emails. Don’t pitch. “Hi Priya, Sarah from [X]. Sent a couple emails about build times — just putting a voice to the name. No need to call back. I’ll follow up by email.”
Day 13: LinkedIn Content Engagement
Find a post they’ve written or shared. Leave a thoughtful comment (not “Great post!”). Add a genuine insight or question. This creates familiarity without being salesy. When they see your next email, you’re no longer a stranger — you’re “that person who left the smart comment on my post.”
══════════════ PART III: TEMPLATES ══════════════
Part III Templates & Examples Steal these. Adapt them. The templates below are organised by subject line patterns, opening lines by buyer persona, and complete 4-email sequences for three different ICP types.
10 Subject Lines That Work
The subject line has one job: get the email opened. Enterprise open rates live or die here. Rules: lowercase, short, looks like a reply or internal email — not a marketing blast.
| Pattern | Example | Why it works | Open Rate |
| — | — | — | — |
| Lowercase casual | quick thought | Looks like an internal email | 55–70% |
| Reference their company | ` + data costs | Specific = relevant = opened | 50–65% |
| **Fake reply** | re: your team | Looks like ongoing thread | 60–75% |
| **Name + question** | , quick q | Personal, intriguing | 50–60% |
| **Mutual connection** | suggested I reach out | Trust transfer | 65–80% |
| **Specific pain** | Snowflake costs getting out of hand?` | If relevant, impossible to ignore | 45–60% |
Subject Lines to Avoid
| Pattern | Example | Why it fails |
|---|---|---|
| Corporate formal | Introduction: Acme Platform Solutions |
Screams mass email. Instant archive. |
| All caps urgency | DON'T MISS THIS OPPORTUNITY |
Spam filter + trust destroyed. |
| Long and vague | How leading enterprises are transforming their data operations in 2026 |
Marketing copy, not a human email. |
| Clickbait question | Want to 10x your revenue? |
Nobody believes this. Insulting. |
11 Opening Lines by Persona
The opening line must prove you’re not sending a mass email. It should reference something specific to them that you could only know if you did research.
| Persona | Where to Research | Opening Line Examples |
|---|---|---|
| VP Engineering | GitHub, tech blog, job postings, conference talks | “Saw your talk at QCon about migrating to Kubernetes — curious if observability became a bottleneck after the migration.” “Noticed you’re hiring 3 platform engineers — sounds like the infra layer is getting serious investment.” |
| CTO | LinkedIn posts, podcast appearances, company blog | “Your post about build-vs-buy for auth resonated — we see the same debate with most Series B CTOs.” “Noticed switched from Heroku to AWS last quarter — curious how the migration is going.” |
| VP Sales / CRO | LinkedIn, G2 reviews of their product, job postings for AEs | “Saw you’re hiring 5 AEs in EMEA — sounds like the European expansion is serious.” “Your team’s win rate on G2 is impressive — curious if pipeline coverage is keeping up with the close rate.” |
| CFO / VP Finance | Annual reports, earnings calls, funding announcements | “With the Series C closed, I imagine forecasting just got a lot more scrutiny from the board.” “Noticed your team posted a FP&A role — sounds like the financial planning stack is getting an upgrade.” |
| CMO / VP Marketing | Website, blog, social channels, SEMrush/Ahrefs data | “Your content strategy is strong — the comparison pages rank on page 1 for most competitor terms.” “Noticed your paid spend on LinkedIn seems to have scaled up this quarter — curious if CAC is holding.” |
12 Full Sequences — Three ICPs
Sequence A: Selling Dev Tools to VP Engineering
Day 1 · Email 1 ci build times Hi Alex,
Noticed your team is running ~200 PRs/week on the monorepo (public GitHub activity). At that volume, CI bottlenecks usually start costing 30–60 min/day per engineer in wait time.
We helped Linear’s team cut that to under 5 min/PR without migrating off GitHub Actions. Happy to share how if useful.
Sarah
Day 5 · Email 2 (reply) Re: ci build times Hi Alex,
No reply needed — thought this benchmark might be useful: we analysed build times across 80 monorepos (10–500 engineers). The median is 18 min. Top quartile is under 6 min. The difference isn’t hardware — it’s caching and parallelisation strategy.
Here’s the data: [link]
Sarah
Day 10 · Email 3 (reply) Re: ci build times Hi Alex,
Last one on this — just published a case study with a team running a similar setup (TS monorepo, ~150 engineers, GitHub Actions):
• P95 build time: 24 min → 4 min
• CI spend: reduced 52%
• Developer NPS on CI: 34 → 78
Happy to walk through the setup if any of this resonates.
Sarah
Day 18 · Email 4 (reply) Re: ci build times Hi Alex,
I’ll assume the timing isn’t right — totally understand. If CI ever becomes a pain point, I’m easy to find.
Good luck with the monorepo. 200 PRs/week is no joke.
Sarah
Sequence B: Selling to VP Sales / CRO
Day 1 · Email 1 pipeline Hi James,
Saw you’re hiring 4 mid-market AEs — exciting growth. Curious: are the existing reps consistently hitting quota, or is the hire to fix a capacity gap?
Asking because we see a common pattern: teams add reps before fixing win rate, and the new reps inherit the same funnel problems. We helped Lattice increase win rate from 18% to 31% before they scaled the team — ended up needing fewer reps than planned.
Worth comparing notes?
Sarah
Day 5 · Email 2 (reply) Re: pipeline Hi James,
Thought this might be useful — we pulled data from 120 mid-market SaaS sales teams on the correlation between pipeline coverage and quota attainment. The tl;dr: teams with 4x+ coverage hit quota 73% of the time. Teams with 2–3x hit it 31% of the time.
Link to the breakdown: [link]
Sarah
Day 10 · Email 3 (reply) Re: pipeline Hi James,
Quick proof point — Lattice’s mid-market team before/after:
• Win rate: 18% → 31%
• Average deal cycle: 68 days → 41 days
• Quota attainment (team avg): 62% → 89%
The main change: better discovery process + deal scoring that killed dead opps earlier. Happy to share the specifics.
Sarah
Day 18 · Email 4 (reply) Re: pipeline Hi James,
Sounds like timing may not be right. Totally get it — scaling a sales team is all-consuming.
If win rate or pipeline coverage ever becomes a focus area, happy to share what we’ve seen work. Good luck with the new AE hires.
Sarah
Sequence C: Selling to CFO / VP Finance
Day 1 · Email 1 cloud spend Hi Rachel,
Congrats on the Series C. With $60M raised, I’d imagine the board is starting to ask harder questions about unit economics — especially cloud infrastructure costs as a % of revenue.
We helped a fintech at a similar stage find $1.2M/yr in wasted AWS spend that wasn’t visible in their existing cost dashboards. Took 2 weeks to identify, zero engineering effort.
Worth a 15-min look to see if something similar exists at ?
Sarah
Day 5 · Email 2 (reply) Re: cloud spend Hi Rachel,
Sharing this in case it’s useful — we published a benchmark: median SaaS company spends 18–24% of revenue on cloud at Series B, dropping to 12–16% by Series D. Companies that actively manage it get to 10–12%.
The gap between “unmanaged” and “managed” is typically 6–8 points of gross margin — worth $2–5M/yr at your scale.
Data here: [link]
Sarah
Day 10 · Email 3 (reply) Re: cloud spend Hi Rachel,
One more data point — a fintech CFO at your stage shared this after working with us:
• Cloud as % of revenue: 22% → 14%
• Gross margin impact: +8 points
• Annual savings: $1.2M
• Engineering time required: zero
Happy to connect you directly if that would be more credible than hearing it from me.
Sarah
Day 18 · Email 4 (reply) Re: cloud spend Hi Rachel,
I’ll assume cloud costs aren’t the top priority right now. Totally fair.
If it ever moves up the list (usually happens when the board asks about gross margin path), I’m an email away.
Sarah
══════════════ PART IV: OPERATIONS ══════════════
Part IV Operations Great emails with bad deliverability reach nobody. This part covers the metrics to track, how to stay out of spam, the tooling stack, and the mistakes that get your domain blacklisted.
13 Metrics & Benchmarks
| Metric | What it measures | Target (Enterprise) | If below target |
|---|---|---|---|
| Open Rate | % of delivered emails opened | 50–70% | Subject line problem. Test new patterns. |
| Reply Rate | % of opens that reply (positive + negative) | 8–20% | Email body problem. Not relevant or too salesy. |
| Positive Reply Rate | % of replies that are interested / open to a call | 3–8% | ICP targeting problem. Right message, wrong people. |
| Meeting Book Rate | % of prospects contacted who book a meeting | 3–8% | CTA problem or follow-up too slow. |
| Bounce Rate | % of emails that bounce | < 3% | Data quality problem. Verify emails before sending. |
| Unsubscribe Rate | % who unsubscribe | < 1% | Sending to wrong people or too frequently. |
| Spam Complaint Rate | % who mark as spam | < 0.1% | Critical. Above 0.3% = domain reputation damaged. |
The funnel math: 50 prospects/week × 60% open × 15% reply × 50% positive × 80% show up = ~1.8 meetings/week from email alone. Add phone + LinkedIn = 3–4 meetings/week. At enterprise ACV ($50K+), that’s $600K–$800K quarterly pipeline per SDR.
14 Deliverability — Getting to the Inbox
None of this matters if your emails land in spam. Deliverability is infrastructure, not content.
The Checklist
| Item | What it is | Priority |
|---|---|---|
| SPF record | DNS record authorising your email servers to send on behalf of your domain | Critical |
| DKIM signing | Cryptographic signature proving the email wasn’t tampered with | Critical |
| DMARC policy | Instructs receiving servers what to do with emails that fail SPF/DKIM | Critical |
| Separate sending domain | Use outreach.yourcompany.com, not yourcompany.com. Protects primary domain reputation. |
High |
| Domain warmup | New domains start with 10–20 emails/day, increase by 5–10/day over 2–4 weeks | High |
| Email verification | Verify every email address before sending. Bounces destroy reputation. | High |
| Plain text only | No HTML, no images, no tracking pixels (or minimal). Plain text = higher deliverability. | Medium |
| Volume limits | Max 50–80 emails/day per sending address. Rotate across 3–5 inboxes. | Medium |
| Unsubscribe link | Required by CAN-SPAM and increasingly enforced by Google/Microsoft | Critical |
The domain death spiral: Send 500 cold emails from your primary domain → 5% bounce → spam complaints → Google downgrades your domain → your CEO’s emails to investors start landing in spam → company-wide email crisis. Always use a separate sending domain.
15 Tools & Stack
| Category | Tools | What it does | Monthly Cost |
|---|---|---|---|
| Sequencing | Instantly, Smartlead, Apollo, Outreach, Salesloft | Automate multi-step cadences. A/B test. Track opens/replies. | $50–$150/seat |
| Email Verification | ZeroBounce, NeverBounce, MillionVerifier | Verify emails before sending. Remove bounces. | $30–$100 |
| Lead Data | Apollo, ZoomInfo, Clay, Lusha, RocketReach | Find verified emails, phone numbers, firmographic data | $50–$500/seat |
| Domain Warmup | Instantly (built-in), Warmbox, Lemwarm | Gradually build sending reputation on new domains | $15–$50/inbox |
| Enrichment | Clay, Clearbit, Builtwith, SimilarWeb | Technographic + firmographic data for personalisation | $100–$500 |
| CRM | HubSpot, Salesforce, Pipedrive, Close | Track deals, log emails, manage pipeline | $0–$150/seat |
| LinkedIn Automation | Expandi, Phantombuster, HeyReach | Automate connection requests, profile views, messages | $50–$100 |
Minimum viable stack for a solo founder or first SDR: Apollo (free tier for leads + sequencing) + Instantly ($30/mo for sending + warmup) + HubSpot CRM (free). Total: ~$30/mo. You can run a professional enterprise outbound program for the cost of a coffee subscription.
16 What Not to Do
The fastest way to learn what works is to understand what fails. These are the most common enterprise cold email mistakes, ranked by how much damage they do:
| Mistake | Why it fails | What to do instead |
|---|---|---|
| Sending from primary domain | One spam complaint wave can destroy your entire company’s email deliverability | Always use a separate sending domain |
| “I” as the first word | “I’m reaching out because…” tells the reader this is about you, not them. Instant archive. | Start with them. Their company. Their problem. Their trigger. |
| Feature dumping | “We offer real-time analytics, AI-powered insights, and enterprise security…” Nobody cares about features in a cold email. | Name their problem. Show one result. That’s it. |
| Fake personalisation | “I love what is doing in the space!” = clearly a mail merge. Insulting. | Reference something specific you could only know from research. |
| Too long | Anything over 150 words requires scrolling on mobile. Scrolling = not reading = no reply. | Under 100 words. 4–6 sentences. Period. |
| Multiple CTAs | “Want to book a call, see a demo, or check out our case studies?” = choice paralysis. | One CTA. One question. Make it easy to say yes. |
| Calendly in email 1 | Presumptuous. You haven’t earned the right to ask them to schedule around you. | Ask “is this worth a conversation?” Let them say yes first, then send the link. |
| HTML templates | Looks like a marketing email, not a personal email. Lower deliverability. | Plain text. No images. No fancy formatting. Like a real email. |
| Sending on Monday morning | Monday 9am = inbox is already overflowing from the weekend. | Tuesday–Thursday, 8–10am or 4–6pm in the prospect’s timezone. |
| No unsubscribe | Legally required (CAN-SPAM). Google/Microsoft increasingly filter emails without it. | Add a simple one-line unsubscribe at the bottom. |
The best cold email you’ll ever write is the one where the prospect replies “how did you know we were thinking about this?” That means your research, timing, and problem identification were all right. That’s the bar. Everything else is noise.
The Cold Email Checklist
Subject < 6 words lowercase, looks like a real email
Under 100 words if they have to scroll, they won’t read
First line = them never start with “I”
One specific problem not a feature list
One proof point named company + number
One CTA “worth a 15-min call?”
Plain text no HTML, no images, no tracking pixels
Separate domain never send from primary domain
The goal is not to sell. The goal is to earn a 15-minute conversation.