You're probably sending your cold emails at the wrong time. Not because you're stupid - but because conventional wisdom about "best times to send" is too vague to actually act on.

Most advice says "send Tuesday-Thursday between 9-11am." That's true enough. But it doesn't tell you whether 9:15am performs better than 10:45am. It doesn't account for your specific industry, your list composition, or whether your recipients are EST, CST, or scattered across time zones. It doesn't help you figure out if morning sends matter more than you think, or if you're wasting effort optimizing something that barely moves the needle.

Cold email send time testing is one of the most under-tested variables in B2B outreach - partly because it's harder to test than subject lines, partly because people assume it doesn't matter that much. Both assumptions are wrong.

Why Send Time Actually Matters (More Than You Think)

Here's the reality: your prospect gets 40-80 emails a day. Most of those land in a crowded inbox. The ones that land when they're actually checking email - focused, not in meetings, not buried in Slack - get opened. The ones that land during their commute or after hours get deleted.

We've tested this across 200+ campaigns across service businesses and agencies. The difference between sending at 9am and sending at 3pm on the same day is usually 12-18% in open rate. That's meaningful. On a 500-person list, that's 60-90 extra opens from a single variable.

But here's what actually matters: you have to test this on your specific audience, not rely on industry averages.

The Framework: How to Actually Test Send Times

Cold email testing is usually treated as "change one subject line, measure the result." Send time testing requires a different approach because you need enough volume to see statistical significance, and you need to isolate the variable.

Here's the exact system:

Step 1: Split Your List into Time Zone Blocks

Before you test anything, separate your list by recipient time zone. Don't send the same time to everyone. A 10am EST send is a 7am PST send - totally different reception.

In your cold email platform (or a simple spreadsheet before import), tag prospects by their company HQ location or infer it from their email domain. If you're selling to service businesses in specific verticals, most of your list is probably concentrated in 2-3 time zones anyway.

Step 2: Pick 2-3 Send Times to Test

Don't test 8am vs 9am vs 10am vs 11am vs noon. You'll never reach significance. Pick meaningful gaps: 9am, 12pm, and 3pm. Or 8am and 2pm. Test 2-3 times max per campaign.

Send each variant to roughly the same segment size. If you're sending 300 emails, split it: 100 at 9am, 100 at 12pm, 100 at 3pm - all on the same day (usually Tuesday or Wednesday).

Step 3: Track Opens and Replies Separately

This matters. Some send times get higher open rates but fewer replies. Others get lower opens but better quality engagement. You're optimizing for replies (or calendar books, or whatever your goal is), not just opens.

At minimum, track:

Step 4: Run Minimum 3 Tests to Confirm the Pattern

One test with 100 people per variant is interesting data. Three tests with 100 people per variant is a pattern. If 9am outperforms 3pm in test 1, underperforms in test 2, and wins again in test 3, you have something. If 9am wins in all three, that's your answer for that list.

Real Numbers: What We Actually See

These aren't hypotheticals. These are actual results from service businesses and agencies running cold email:

Test 1 - B2B SaaS Sales (Tech Industry List)

Winner: 9am by 3 percentage points on reply rate. Not huge, but on a 1000-person list, that's 30 extra replies.

Test 2 - Agency Services (Mixed Time Zones)

Winner: 2pm when sent to the prospect's local time zone. Early morning seemed too aggressive. They opened it mid-afternoon when they had breathing room.

The pattern we see most often: morning sends (8-10am) beat afternoon sends (2-4pm) by a small margin, but that margin shrinks if you're selling to senior decision-makers (C-suite, execs) versus individual contributors. Execs reply more to afternoon sends - they're less drowning in email by 2pm.

How to Set Up the Test in Your Platform

Most platforms (Apollo, Instantly, Lemlist, etc.) have built-in scheduling. Here's how to do it cleanly:

Create three separate sequences, identical except for send time. Send Variant A to list segment 1 at 9am. Send Variant B to list segment 2 at 12pm. Send Variant C to list segment 3 at 3pm. Make sure the day is the same (Tuesday or Wednesday work best).

Use your platform's reporting to pull open and reply data by send time. If your platform doesn't separate reporting by send time, use UTM tags or custom tracking (tag variant A emails with "send-9am" in the email metadata).

For follow-up sends, test at the same time as your initial send. Consistency matters - if your follow-up goes out at a different time, you're testing two variables at once.

When Send Time Testing Doesn't Matter (And When It Does)

Be honest about your list size. If you're testing on 50 people per variant, the noise is too high. You need at least 75-100 per variant to see real patterns. Under that, you're just guessing.

Send time matters more if:

Send time matters less if:

One More Thing: Day + Time Combination Testing

Most people test time-of-day in isolation. But day + time matters. A Tuesday 9am send performs differently than a Wednesday 9am send. If you want to get granular, test both.

The simplified version: test Tuesday and Wednesday at your best time from the previous test. Wednesday morning is usually slightly better than Tuesday (people are more settled in, less buried), but it depends on your industry.

The Gap Between Knowing This and Running It

Reading this, you now know how to test send times. But there's a meaningful gap between knowing the framework and having it running smoothly at scale - especially if you're running multiple campaigns simultaneously.

You have to manage list segmentation by time zone, create multiple variants in your platform, track results separately, run analysis across tests, and adjust future sends based on data. If you're also managing copy, list quality, infrastructure, and reply handling, send time testing becomes one more thing competing for attention.

Some teams do it themselves. Others bring in a partner who runs the testing, handles the tracking, and gives them the answer. Both work - it's about your bandwidth and how quickly you want the data.

Related Guides