Something Inc.LoginSchedule a free consultation
STRATEGY

Your cold email sounds like AI wrote it. The data says so too

You know the tell within three seconds when you're on the receiving end. The grading data on 231,818 real emails says you're sending that exact tell right now.

TTTyler TruffiManaging Partner · AUG 18, 2026 · 9 MIN READ

You can spot it in someone else's inbox in about three seconds. The line that was clearly built from a LinkedIn scrape and dropped into a merge field. The compliment that's technically about your company but says nothing a person who actually looked at your site would say. You know the tell instantly when you're the one reading it. The uncomfortable question is whether you'd catch it in your own sent folder just as fast.

The three-second tell

Experienced buyers have gotten fast at this, faster than most senders have gotten at hiding it. A line that was generated from a scraped data point with no human judgment applied reads differently than a line written by someone who actually looked at the account, even when both lines are grammatically identical and technically accurate. The tell isn't a typo or an obviously wrong fact. It's a kind of flatness: information without a point of view attached to it, personalization that proves a tool ran, not that a person noticed.

That gap between technically-personalized and actually-relevant is the entire subject of this piece, because it turns out to be measurable, not just a feeling experienced buyers report. Lavender, the AI email-coaching platform built by Will Allred and William Ballance, grades cold emails in real time against a model trained on millions of real sends and their actual reply outcomes, and their updated benchmark report, current as of February 4, 2026, puts real numbers on exactly what separates a send that works from one that only looks like it should.

What the grading data actually shows

Across 231,818 cold emails graded on Lavender's A-through-F scale, emails that earned an A grade improved reply rates from a 3.4% baseline to 4.3%, a 27% lift. That's the aggregate number. The more useful number sits one layer down: personalized emails, versus a straight template with a name and company merged in, saw reply rates increase somewhere between 50% and 250%, depending on the department being targeted and how deep the personalization actually went. There is also a regulatory angle for anyone mailing into Europe: what the EU AI Act means for disclosing AI-written cold email.

3.4% → 4.3%
reply rate lift, template-grade to A-grade emails (Lavender, 231,818 emails)
50% to 250%
reply-rate increase, personalized vs. templated, by department
79%
reply-rate lift for A-grade emails sent to finance, the highest of any persona tracked

A 27% aggregate lift undersells the story, because it's an average across a huge range of outcomes, and the range is where the actual lesson lives. Some sends barely move at all when polished from template quality to A grade. If copy is not the constraint, compare the cold email vs LinkedIn outreach numbers. Others, aimed at the right department with the right depth of research behind them, see reply rates that are two to three times higher than the templated version they replaced. Averaging those together produces a number that looks modest and hides a distribution that isn't.

Why you can't see it in your own copy

THE BLIND SPOTWriting a personalized-sounding email and writing an actually relevant one feel identical from the inside. Both involve typing specific-sounding details into a message. Only one of them required knowing something true about the buyer first.

This is the mechanism behind why so many senders genuinely believe their outreach is personalized when the reply data says otherwise. Mentioning a company's name, industry, or a recent press release is personalization in the mechanical sense; it proves a tool or a person did some lookup work. It is not personalization in the sense that moves a reply rate, which requires the detail to connect to something the recipient actually cares about, not just something true about them. A sentence that says "I saw you raised a Series B" is a fact. A sentence that says why the specific thing that changes after a Series B is relevant to what you're selling is a point of view, and only the second one reads as though a person was actually thinking about this specific account.

The tools generating a lot of today's outbound volume are extremely good at the first kind and structurally incapable of the second, because the second requires a judgment call about relevance that no scraped data point makes on its own. That's the same distinction we've made about why AI outbound tools keep underdelivering on ROI: the technology handles retrieval and drafting well, and still needs a person to supply the one ingredient that actually predicts a reply. If the worry about AI-drafted outbound is legal rather than tonal, note that Article 50 of the EU AI Act does not require the disclosure footer vendors are selling.

The department gap nobody talks about

TARGET DEPARTMENTA-GRADE REPLY-RATE LIFTWHAT THAT IMPLIES
Finance79% lift, highest of any personaFinance buyers reward specificity most; generic pitches get filtered hardest here
OperationsReply rate climbs to 5.4%, a 58% liftProcess-literate buyers respond to messages that show you understand their actual workflow
Engineering / productReply rate reaches 5.2%Technical buyers reward accuracy and penalize vague claims fast

Notice the pattern across all three rows: the departments with the biggest gap between templated and personalized outreach are exactly the ones trained to spot a claim that doesn't hold up under two seconds of scrutiny. Finance people read a lot of numbers for a living and can tell when one doesn't add up. Engineers can tell when a technical claim is hand-wavy. These are not soft, feelings-based buyers who respond to a friendly tone. They're the buyers most likely to notice, immediately, when a message was assembled rather than written, and the reply-rate data shows they act on that noticing by not replying.

1The detail has to change the message, not just decorate itIf you could delete the personalized line and the rest of the email would still make sense unchanged, it wasn't real personalization. It was a fact bolted onto a template.
2Specificity beats volume of detailOne sharp, relevant observation about the account outperforms three generic ones. Piling on scraped facts doesn't compound the effect; it just makes the assembly more obvious.
3Match research depth to department, not just to deal sizeThe data suggests finance and technical buyers punish shallow personalization harder than other departments do. Calibrate research effort to who's reading, not only to how big the account is.

The illustrative case: same list, two openers

It's easier to see the gap side by side than in the abstract. Picture two versions of a cold email opener sent to the same VP of Finance at a mid-market manufacturing company, both technically referencing something true about the account. The templated version reads: "I noticed [Company] recently expanded its operations, and I wanted to reach out about how we help finance teams like yours streamline reporting." Every word is accurate. It could also have been sent to four hundred other finance leaders with a find-and-replace on the company name, and nothing about the sentence would need to change to fit any of them.

The personalized version starts from the same underlying fact, the expansion, but does something the first one doesn't: it connects the fact to a specific, plausible consequence for that specific role. Something closer to: "A facility expansion usually means your close process picks up two or three new cost centers overnight, and most finance teams don't touch their reconciliation workflow until that backlog is already painful." That sentence would read as wrong, or at least oddly specific, if sent to a company that hadn't just expanded. It only works for this account, which is the entire test. The first opener survives being sent to anyone. The second one doesn't, and that's exactly why it's the one the data says earns the reply.

Fixing it without slowing down

The instinctive fix, slow down and hand-write every email, doesn't scale and isn't actually what the data recommends, because the constraint was never speed. Plenty of fast-written emails pass this test, and plenty of slow, heavily-researched ones still fail it, because research and relevance aren't the same activity even though they feel like it from the sender's side. The instinctive alternative, let a tool draft everything from enrichment data, is the mistake that produces the flatness in the first place. The workable middle is closer to what real-time grading tools like Lavender are built for: draft fast, using whatever research and automation tooling makes sense for your volume, then run every send through a check for whether the personalized line would survive being read by someone who knows the account is being AI-assisted. If the sentence only works because the reader doesn't know how it was produced, it needs a rewrite before it goes out, not a defense of the process that produced it.

This is also a sequencing problem as much as a copy problem. A message can be perfectly personalized on send one and completely generic by send four, because most sequences front-load the research into the opener and coast on cadence after that. We've written about how the interval between follow-ups affects deliverability independent of content quality, and the same discipline applies to personalization depth: a sequence that's sharp on message one and templated on messages two through five is training the recipient to recognize, by message three, that the personalization was a one-time performance rather than an ongoing signal that someone is paying attention.

There's a team-level version of this problem too, worth naming separately. A single rep can hold this standard in their head for a dozen sends a week. A team running hundreds of sends a day across multiple reps needs the standard written down and checked, not assumed, because "does this line survive being sent to anyone" is exactly the kind of judgment call that erodes quietly under volume pressure. The rep who wrote sharp, specific openers in month one starts reaching for the same three safe phrasings by month four, not from laziness, but because volume makes the fast, safe choice more attractive every single day it isn't explicitly checked against.

AUDIT
Audit your last 20 sent emails coldRead them as if you were the recipient with no context. If you can't tell which lines took research and which were templated, your recipients probably can't either, and that's the actual problem to fix first.
Grade before you send, not after you analyze repliesWaiting for reply-rate data to tell you a sequence isn't working costs weeks. Real-time grading catches the flatness before the email leaves the draft.
Weight research effort by department sensitivityPut your best personalization work against finance and technical buyers specifically. The data says that's where shallow research costs you the most replies.

Do this next: pull ten of your last month's sent emails to finance or technical buyers specifically, the two personas this data says punish flatness hardest, and delete every line that would still make sense if you swapped in a different company's name. What's left is your actual personalization rate, not the one you assumed you were running. If reply rates have been sliding regardless, it's worth ruling out the broader is cold email actually dead question before assuming the channel itself is the problem; more often the channel is fine and the copy running through it isn't. Our cold email team builds sequencing and research workflows around exactly this distinction, because the fix was never writing more. It was writing fewer, sharper lines that couldn't have been sent to anyone else.

See where you are cited today

A free snapshot audit of your rankings and AI citations before we ever talk.

TT
Tyler TruffiMANAGING PARTNER, SOMETHING INC.

Tyler leads work at the intersection of SEO and generative engines at Something Inc., helping B2B brands get ranked and cited across every major AI engine.

Keep reading

All insights →
STRATEGYYour AI SDR Reply Rate Has No DenominatorTwo of the most widely read accounts of AI in sales development landed within days of each other, and they point in opposite directions. Jason Lemkin's six-month write-up at SaaStr reports an outbound agent sending 19,847 messages at a 6.7 percent overall response rate, roughly 3,000 a month against the 75 to 285 a month its human reps managed. Atlassian's Teamwork Lab, publishing November 9, 2026 after interviewing eight sales development reps, reports a blanket internal rule that no AI-written message reaches a customer without human review, and one rep who abandoned AI for outbound email entirely and booked ten meetings in a week writing like a person texting a friend. The reflex is to pick a side. The better move is to notice that neither account defines the denominator under its reply rate, and that SaaStr's own campaign figures do not reconcile against either obvious candidate. Volume changes what a reply rate means. Here is how to read one, which denominator to hold your program to, and when adding sends stops paying.TYLER TRUFFI · 12 MINSTRATEGYYour November Bounce Data Is ContaminatedOn November 5, 2026, senders began getting hard rejections from Outlook.com, Hotmail, Live and MSN addresses, carrying the error 550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records. Plenty of those senders had passing SPF and DKIM. Plenty were nowhere near the 5,000 messages a day that Microsoft's published bulk sender rule actually covers. On November 10 Microsoft's incident report said a spam enforcement rule update had caused messages to be incorrectly marked and blocked, and by November 11 a spokesperson said the bug was fixed. No postmaster notice went out while it was happening, and the bounce text pointed at SPF when a missing DMARC record was the trigger. For outbound teams the damage is not the week of blocked sends. It is that six days of Microsoft bounce data is now unusable as a reputation signal, and the standard response to a bounce spike, cut volume and rebuild domains, is the wrong move if the spike was never yours. Here is how to read those bounces, what to quarantine, and why the botched rollout still points one direction.TYLER TRUFFI · 11 MINSTRATEGYReverse DNS Is The Cold Email Gate You Do Not ControlSpamhaus updated its Sender Guidelines in October 2026 and says that starting in November 2026 it is gradually rolling out a requirement for every sending IP to have a valid HELO, a reverse DNS (PTR) record and a matching A record. Nothing in that sentence is new advice. What is new is enforcement, and the listing zones behind it are CSS and XBL, which are the ones that take an IP out of the inbox rather than into the spam folder. The awkward part for outbound teams is ownership: SPF, DKIM and DMARC are published in DNS you control, while a PTR record can only be set by whoever controls the IP. Most cold email programmes spent 2026 moving onto private and dedicated sending infrastructure to escape bulk-sender limits, and in doing so handed the one record they cannot publish themselves to a vendor they have never audited. Here is how to find out whose problem it is, by sending setup, and what to fix this week.JOSH BERNSTEIN · 11 MIN
Free consultation

Let us be the last SEO agency you ever work with

A 30 minute call and a free audit of your SEO and GEO position. You keep the findings either way.