Let's be honest. If you're using AI to insert a prospect's name, company, and job title into an email template, you're not personalizing — you're just making the spam look more expensive.

The tools got everyone excited. Drop in a LinkedIn URL, let GPT rewrite the same five paragraphs with the company name swapped out, send at scale. Volume went up. Response rates went down. Nobody wants to talk about that second part.

Here's the thing: recipients aren't stupid. They can tell when an email was written for 10,000 people and slightly adjusted for them. That half-second of "oh, they mentioned my company" immediately gives way to "this is the same template sent to everyone on my team." Click. Archive. Gone.

The Real Problem: You're Personalizing the Wrong Layer

Surface-level tokens — company name, industry, title, a reference to their last tweet — those address the who of personalization. They don't address the why should I care. That's the layer that actually gets emails read.

Think about what makes you stop scrolling in your own inbox. It's not seeing your company name. It's seeing someone articulate a problem you've been losing sleep over. That's not a token swap. That's understanding what's actually happening in their world.

Segment by Situation, Not by Persona

The fix is a different mental model. Instead of "persona-based" outreach (which creates massive generic groups like "VPs of Marketing at SaaS companies"), segment by what's happening in their business right now.

Ask yourself: what are the distinct situations my best prospects are in when they actually respond to cold email? Usually two or three clusters emerge:

One cluster just raised funding — they're suddenly under pressure to hire fast, scale infrastructure, show investors growth. Different urgency than a company that's been flat for eighteen months and a new CMO just walked in with a mandate to fix pipeline. Those two groups need completely different angles. Same product. Completely different entry point.

So before you write a single email, map your outreach list into two or three real situations. Not personas. Situations. You'll write better email because you'll actually have something to say.

Write the Opening Line Like You're Starting a Text Message

The first line of a cold email is doing all the work. If it reads like an email opening, it will be read like one — which means it will be evaluated against every other cold email in their inbox.

Write the first line like you're texting a colleague who just told you about a problem. You'd say: "Heard your pipeline's been tight since the reorg — that's usually where things get interesting." You'd never say: "I hope this email finds you well."

Your first line should do three things: show you know something real about their situation, create a tiny bit of tension, and make it feel like a human wrote it. AI can help with the rest of the email. That first line, write it yourself.

Use AI to Handle the Follow-Up Sequence, Not the First Email

Here's a more effective workflow: write two or three strong first emails by hand — one for each situation cluster. Then let AI draft the five-touch follow-up sequence that moves toward a phone call. The sequence doesn't need to be clever. It needs to be well-timed, progressively less demanding, and aware of what you sent before.

AI is actually better at the follow-up grind than the first email, because follow-ups have a clear job: reference the previous message, add something useful or interesting, make the ask slightly smaller. You can generate five solid follow-ups per situation cluster in about twenty minutes. That's leverage. The first email is still on you.

Test One Variable at a Time

If you're going to A/B test, change only one thing per test. Not subject line AND sending time AND body copy at the same time. Pick one: subject line or sending time. Run 200 emails per variant. Wait a week. Look at reply rate, not open rate — opens are vanity, replies are intent.

Most people test too many variables simultaneously and then can't draw any useful conclusions. Pick your biggest assumption about what might be holding response rates back. Test that. Only that. Let the data tell you what to fix next.