Email warm-up: what actually works, what's a waste of money
Every outbound tool advertises 'automated warm-up' as a solved problem. It isn't. Warm-up is a 4–8 week discipline - schedule, volume ramp, reply simulation, seed inbox mix - and skipping any step means new domains start their life in the spam folder and stay there.
You'll recognise this if…
Root causes, in order of impact
Volume ramped too fast
Providers score sudden volume increases as spammer behaviour. Doubling daily send in week two burns the domain.
Single-provider warm-up pool
If every warm-up email lands in Gmail, Outlook filters have no signal - deliverability to enterprise inboxes stays terrible.
No real conversation depth
Warm-up replies that are one line and never threaded look automated to filters. Real threads with 3+ turns move the needle.
Cold and warm-up on same domain
Some setups pause warm-up when cold campaigns start. Keep warm-up running at 20–30% of daily volume forever.
Deliverability by warm-up length
% primary-inbox placement after week 1 of cold campaign
Before vs after
Before - the status quo
- ✗New domain sending 50 cold emails on day one
- ✗Auto warm-up on, no monitoring
- ✗Reply rate under 1%, opens under 20%
- ✗Domain gets flagged in week 3, whole campaign paused
After - with one accountable operator
- ✓6-week ramp: 5→10→15→20→25→30/day
- ✓Mixed provider warm-up pool (Gmail + Outlook + Yahoo)
- ✓20% of daily volume stays on warm-up permanently
- ✓Reply rate 3–6% on the same list, campaign stays live
The playbook
- 1
Week 1: 5–10 warm-up sends/day only
Zero cold outreach. Confirm SPF/DKIM/DMARC. Verify inbox lands with 5 test seeds.
- 2
Week 2–3: add 5–10 warm-up sends/week
Monitor spam-folder rate on Google Postmaster daily. If red, drop volume by 30%.
- 3
Week 4: start cold at 5/day
Warm-up continues at 20+/day. Cold volume never exceeds 40% of total send.
- 4
Week 5–8: ramp cold to target
Add 5 cold sends per week to a ceiling of 30/day per inbox.
- 5
Ongoing: keep warm-up at 20–30% of send
Never turn it off. The signal decays fast if you do.
One accountable operator, not a stack of vendors
- I run warm-up as a calendar, not a tool subscription - every domain has a written ramp with dates.
- Cross-provider seed inboxes I've built over years of live campaigns.
- One dashboard covering all your domains at once, reviewed weekly.
FAQs
Can I skip warm-up if I use a paid infrastructure provider?
No. Dedicated IPs and premium ESPs help, but new domains still need reputation with Google and Microsoft - that only comes from time and volume patterns.
Is 4 weeks enough?
For lower-volume programs, yes. For anything above 300 sends/day/domain, budget 6–8 weeks. Rushed warm-up costs more than a slow one.
Do I need to keep paying for warm-up after launch?
Yes. Keep 20–30% of daily volume as warm-up. Turning it off in month two is the single most common reason established programs lose deliverability.
Related pain points
Cold email deliverability is broken - here's how to actually fix it
You're sending 500–2,000 cold emails a week, opens look 'fine' on paper, and reply volume is a fraction of what your tool's benchmarks promised. The problem is almost never the message - it's that Google and Microsoft never showed it. Deliverability is a compounding, invisible tax on every outbound program, and most teams only notice it once the pipeline has already dried up.
DeliverabilityWhy cold emails go to spam - 11 reasons ranked by impact
Cold email lands in spam for a specific, diagnosable reason - never mystery. The problem is teams treat 'spam' as one thing when it's actually 11 different failure modes stacked. Fix the wrong one and nothing changes. Rank them by impact and fix them in order.
OutboundCold email best practices for 2026 - what changed, what still works
Every 'best practices' article from 2022 is now actively harmful. Google's sender rules, AI-generated inbox fatigue, and Microsoft's tightening in 2024–2025 quietly killed the tactics that used to work. The teams still growing pipeline through cold email in 2026 are running a very specific, much narrower playbook.
Diagnose your version in 30 minutes
Every situation is a little different. Book a call - we'll map your specific version of this pain point and I'll tell you the shortest path to a fix.