Should you personalise every cold email?
A personal detail that changes the pitch helps. A first-name field in a stock template rarely does. One that misfires hurts more than none.
Want to see it first? Book a demo
The short answer
- A personal touch lifts reply rates only when it changes something real about the pitch. A first name or company name dropped into the same template for everyone does not.
- A personal detail that is wrong, off-topic or plainly machine-made tends to do worse than none. It shows the reader a broken process.
- Deep research on each person won't scale to big volumes without a lot of time or tools. Writing per segment, to a trait a group shares, is the practical middle ground.
- Here's the test of whether a personal touch is doing real work. Would the email change in substance, beyond its looks, if you sent it to someone in a different situation?
Why depth matters more than a merge field
People often treat personalising as yes or no: an email has a merge field or it doesn't. That view misses what decides whether it helps. A first name or company name in a generic template counts as personal on paper. It doesn't change what the email says about the reader's situation, and readers now spot this thin version at a glance.
Real personalising changes the heart of the pitch. It names a true, specific detail about the reader's role, company or recent work that makes your main claim more believable or more relevant. That takes research on top of a data field, and it's why it won't scale cheaply to a list of thousands.
Try this test. Would the email need to say something different in substance if you sent it to someone in a similar role at another company? If not, the personal touch is only on the surface, and it won't move reply rates much either way.
How deep to go, and where each level fits
| Level | Example | Scales to |
|---|---|---|
| Cosmetic (merge fields only) | First name, company name inserted into a fixed template | Any volume, little lift in replies |
| Segment-level | A message angle tailored to a shared trait (industry, role, company size) | Medium volume, real relevance |
| Individual research-based | A specific, true detail unique to that person or company | Small volume, highest relevance per email |
What to do when you trade volume for depth
Writing per segment is a sound default for most outbound. Give each segment its own angle instead of one generic template for the whole list, and skip unique research on every contact. Save deep, one-by-one research for a short list of high-value targets, where the extra work per contact fits the deal size.
It also helps to check a sample of sent emails against the data they pulled from. Was the detail right and current on the day it went out? A field that was right when the record was made can go stale, like an old job title or a company that changed its name. That's the kind of wrong detail that costs you trust, and only a regular spot check catches it, not a one-time review at setup.
Disclosure: SalesCrew is our product. Its AI drafting can build a personal opener from data already in the record, and nothing sends until someone approves it. A person reading the draft still decides if a detail matters to the reader, or is only a field that happens to be right.
Check every AI-written detail before it sends
Questions
- Is a first-name mail merge considered personalization?
- Technically, yes, but not the kind that lifts reply rates. A first name dropped into a generic template is hard to tell apart from no personal touch at all. It doesn't change what the email says about the reader's situation.
- Can AI-generated personalization backfire?
- Yes, if the personal detail is wrong, bland or plainly auto-filled. A field that misfires, with a detail that doesn't match or an odd phrase, reads worse than none at all. It shows the reader a machine getting it wrong.
- How much time should genuine personalization take per email at scale?
- You trade depth for volume. Deep, hand-researched detail won't stretch to thousands of emails without a lot of time or tools. That's why many teams write per segment instead, to a trait a group shares, not a detail unique to each person.