You're staring at your draft email wondering: is this too long? Should I cut it down? Will they even read past the first sentence?
Here's the thing - email length isn't actually the problem you think it is. Most people obsess over word count when they should be obsessing over relevance. But there are real constraints, and there's a specific structure that works better than others.
The Actual Length That Works
The sweet spot for a cold email is between 50-125 words. That's not arbitrary - it's based on what gets opened, read, and replied to across thousands of campaigns.
Here's why that range matters:
- Under 50 words: You don't have enough space to establish relevance. You end up with generic nonsense that reads like spam.
- 50-125 words: You can hit three essential pieces - why you're writing, what you noticed about them specifically, and a single clear ask.
- 125-200 words: Still works, but reply rates start dropping. People skim at this length, and you need every line to pull weight.
- Over 200 words: You're fighting against human behavior. Most people won't read it, and you're competing against their inbox noise.
The data is consistent: emails in the 50-125 word range get replied to more often than longer or shorter emails. But - and this is important - only if the content actually matters to the person reading it.
What You Actually Need in Those Words
Length only works if you use it right. You need four components, in this order:
- Opening line (1-2 sentences): This triggers whether they keep reading. It should reference something specific - a recent company move, a problem you know they have, something you noticed about their business.
- The relevance statement (2-3 sentences): Why this matters to them specifically. Not why your solution is good - why their situation makes this relevant right now.
- Social proof or credibility (1 sentence, optional): A quick mention of similar work you've done or a type of result you've helped others achieve.
- The ask (1 sentence): One thing. Not three. One clear next step.
Here's a real example that hits all four and lands around 85 words:
Hi [Name], I noticed [Company] just launched [specific product/service] - that's a big move into a competitive space. We work with software companies in similar situations who struggle with [specific problem]. Most don't have the customer data infrastructure to really understand what's working with new users. We've helped companies like [similar company] reduce their GTM cycle by 30-40% by implementing [specific thing]. Worth a 15-min call to see if it applies here? [Your name]
This is short, specific, and moves the reader toward a decision. It doesn't ramble. It doesn't overcomplicate.
Common Length Mistakes That Kill Reply Rates
Now let's look at what actually breaks emails, even when they're the "right" length:
Mistake 1: Being too vague to stay short. People try to compress a generic pitch into 60 words. It ends up meaningless. Being short only works if you're specific. If you can't be specific in 100 words, the problem isn't length - it's that you don't have a real reason to be emailing this person.
Mistake 2: Including too many details. A 150-word email that includes your background, your company history, three benefits, and two call-to-actions is worse than a 200-word email with one clear point. Length matters less than focus. Cut the noise, not the substance.
Mistake 3: Long opening lines. This kills more emails than anything. Your first sentence should be 10-15 words max. Something specific. Something that makes them think "this person knows something about my business." Long, flowery openers get skipped.
Here's what a bad opening looks like:
Hi [Name], I hope this email finds you well. I'm reaching out because I think what you're doing at [Company] is really impressive and I'd love to explore potential synergies.
This is generic filler. Cut it completely. Compare it to:
Hi [Name], saw your Q3 earnings report mentioned customer churn as a headwind - curious how your team is addressing that.
Same concept. Massive difference in impact. The second one gets read.
Length Varies by Industry and Intent
There are some nuances worth knowing:
For enterprise deals (longer sales cycles): You can push toward 150 words because there's more complexity to explain. But you still need that specificity. More length works only if every line earns it.
For quick-turnaround services (design, marketing, development): Stick closer to 60-85 words. These decisions move fast. Long emails slow things down.
For follow-ups in a sequence: Your first email should be shorter (60-90 words). Subsequent emails can be slightly longer because they're reaching someone already warmed up to you. But still - keep them lean.
The subject line also matters here - a weaker subject line means you need a stronger opening paragraph. Stronger subject line means people are already primed to read, so you can be direct immediately.
Testing Length on Your Own Lists
Theory is useful. Testing is better. Here's how to actually figure out what works for your specific business:
Run a simple test: Send version A (70 words) and version B (120 words) to similar segments of your list. Both should have identical opens, identical topics, identical asks. Just one is tighter, one is more detailed.
Track reply rate on each. Whichever wins, lean into that pattern. Your industry, your audience, your offer - they might prefer different lengths than someone else's.
But start with the 50-125 baseline. Adjust from there based on what actually happens.
The Gap Between Knowing This and Actually Getting It Right
Here's what's tricky: knowing that "50-125 words works" is useless if you don't know what to say in those words. You need the right research, the right angle, the right reason to be emailing this person today. You need your infrastructure set up correctly so emails actually land in inboxes. You need a sequence, not just one email. You need to handle replies when they come in.
Length is one small piece. BEC Growth handles the rest - finding the right people, writing copy that's specific to their situation, managing the infrastructure so it doesn't look like spam, running the full sequence, and handling every reply. Most agencies or in-house teams struggle with consistency here. It's not hard once it's systematized. It's just tedious if you're doing it yourself.