Cold email sequence that actually gets replies

# Cold Email Sequence: DevOps Automation Platform → Engineering Managers **Target:** Engineering managers at mid-market SaaS companies (200-2000 employees) **Product:** CI/CD automation platform that cuts deployment time by 70% **Sequence length:** 5 emails over 17 days --- ## Email 1: The Pattern Interrupt **Subject:** Your team shipped 3x last quarter — here's why **Alt A:** I timed your deploy pipeline (yikes) **Alt B:** 47 minutes per deploy is a choice **Body:** Hi [first_name], I looked at [company]'s public GitHub — your team averages 12 deploys/week. Impressive velocity. But your CI pipeline runs suggest each deploy takes ~47 minutes end-to-end. That's 9.4 hours/week your engineers spend waiting. We helped [similar_company]'s team cut that to 14 minutes. Their deploy frequency doubled in 3 weeks. Worth a 15-minute call to see if the same approach fits [company]? [Your name] **CTA:** "Reply with your calendar link" (not a scheduling tool — too impersonal for E1) **Principle:** Specificity creates credibility. Real numbers from their public data prove you did homework. **Timing:** Tuesday 8:30am local time (highest open rates for B2B) --- ## Email 2: The Case Study **Subject:** How [similar_company] went from 45-min deploys to 14-min **Alt A:** [similar_company]'s CTO called this "embarrassingly easy" **Alt B:** The deploy bottleneck nobody talks about **Body:** Hi [first_name], Quick follow-up. Here's what happened when [similar_company] (similar size to [company], also [tech_stack]): **Before:** 42-minute CI pipelines, 8 deploys/week, 2 rollbacks/month **After:** 14-minute pipelines, 22 deploys/week, 0 rollbacks in 90 days The biggest win wasn't speed — it was confidence. Their engineers started shipping Friday afternoon again because rollbacks became instant. Here's the 2-minute case study: [link] No pressure — just thought the parallels were interesting. [Your name] **CTA:** Read the case study (soft — builds trust before asking for time) **Principle:** Social proof from a peer company. "Similar size, similar stack" makes it feel achievable. **Timing:** Thursday 9:00am (2-3 days after E1) --- ## Email 3: The Gift **Subject:** Free audit: your CI pipeline in 30 seconds **Alt A:** I built something for your pipeline **Alt B:** 3 quick wins for [company]'s deploy speed **Body:** Hi [first_name], I put together a quick analysis of [company]'s CI setup based on your public repos. No strings attached — just thought it might be useful. **3 things I noticed:** 1. Your test suite runs sequentially — parallelizing the 4 independent test groups would save ~18 minutes alone 2. Docker layer caching is missing on your build step — easy 5-minute fix 3. Your artifact upload happens before tests pass — moving it after would prevent 30% of wasted build minutes Happy to walk through these or just take them and run. Either way, hope it helps. [Your name] **CTA:** None (intentionally). Give value freely. This builds reciprocity for E4. **Principle:** Reciprocity + demonstrated expertise. You've already helped them — now they feel obligated. **Timing:** Monday 10:00am (4 days after E2) --- ## Email 4: The Direct Ask **Subject:** Quick question, [first_name] **Alt A:** 15 minutes this week? **Alt B:** Can I show you the parallelization fix? **Body:** Hi [first_name], I've shared some ideas about [company]'s CI pipeline over the past couple weeks. Curious if any resonated. If you're open to it, I'd love to do a live 15-minute pipeline audit on a call. I'll share my screen, analyze your actual config, and give you a prioritized list of optimizations — whether you use our platform or not. Here are a few times that work: [2-3 specific slots] If the timing doesn't work, just reply with what does. No worries if it's not a priority right now — I'll stop following up. [Your name] **CTA:** Pick a specific time slot (reducing decision friction vs. "whenever works") **Principle:** Loss aversion ("I'll stop following up") + commitment device (specific time slots reduce the "I'll think about it" loop). **Timing:** Wednesday 8:00am (3 days after E3) --- ## Email 5: The Breakup **Subject:** Should I close your file? **Alt A:** Not the right time? **Alt B:** Last one from me, [first_name] **Body:** Hi [first_name], I've reached out a few times and haven't heard back — totally respect that you're busy. I'll assume the timing isn't right and close out my notes on [company]. If things change down the road, here's where to find me: [calendar link] One parting thought: the parallelization fix from my earlier email (running your 4 test groups concurrently) is a 10-minute config change that would save your team ~6 hours/week. No tool needed — just a YAML change. Here's the exact config: [link to blog post] All the best with [company]'s next release. [Your name] **CTA:** Calendar link (passive) + free resource (active value delivery) **Principle:** Scarcity + the Zeigarnik effect. "Closing the file" creates urgency. Many breakup emails get the highest reply rates because the prospect feels the option slipping away. **Timing:** Monday 9:00am (5 days after E4) --- ## Sequence Performance Benchmarks | Metric | Industry Avg | This Sequence Target | |--------|-------------|---------------------| | Open rate | 22% | 38-42% | | Reply rate | 2-3% | 8-12% | | Meeting booked | 0.5-1% | 3-5% | | Best performing email | Usually E1 | Usually E3 or E5 | ## Key Principles Summary 1. **Research over templates** — mentioning their actual GitHub data beats any template 2. **Give before you ask** — E3 provides real value with zero ask 3. **Specificity beats superlatives** — "47 minutes" beats "too long" 4. **One CTA per email** — never give two choices 5. **Short > long** — every email is under 100 words of body copy