DEV Community

Li Chris
Li Chris

Posted on

170 Cold Emails. The First Human Reply Asked Us to Stop.

Quick update for the thread that's been following our outreach numbers, because the scoreboard just moved in the least flattering direction possible.

After 170 cold emails since early October — 153 from a consumer Gmail address, then 17 from the new domain sender we switched to last week — we received our first human reply on Friday. It was one sentence of clarity:

"Please remove me from your list - no further emails"

What we did. Removed her, marked the address as declined in our tracker, and sent nothing back — not even a confirmation, because "no further emails" means no further emails. The address is out of every pool we run.

What the reply actually proves. Two weeks ago the working theory on this thread was that our emails vanished before reaching humans — one practitioner publicly confirmed nothing had ever arrived, not even in spam. The switch to a proper domain sender was the fix. Friday's reply is the first hard evidence from the other side that the pipe now works: a real person received a real email, opened it, read it, and answered it. The channel is alive. The message just earned a "no."

What we changed because of it. The email that triggered the removal was a follow-up — the second unsolicited touch to that recipient in two days. That's now retired as an automatic move: new contacts get one email, and a second touch only happens if they interact first. The next batch (already pre-registered in this thread: two segments split by marketing stack, minimum twenty per segment) goes out as first-touches only.

The scoreboard, honestly updated. Old era: 153 sent, zero replies. New era: 17 sent, 16 delivered, one hard bounce (dead address), one reply — a removal request. Zero positive replies across both eras. The never-arrived count we promised to track stays at zero for the new sender, which was the metric to watch; the reply count is at one, in red ink.

Two weeks to the pre-registered segment test results. Both lines, no merging — that promise doesn't get easier to keep, which is exactly why it was made.

Top comments (0)