Reply rate is the wrong north star

Reply rate is easy to measure and easy to game. That's the problem with it.

For a firm selling engagements worth hundreds of thousands, a reply that goes nowhere is worth nothing. A single reply from the right CFO telling you you're wrong and naming the real issue is worth a quarter.

How reply rate misleads

Teams that chase reply rate learn to write for replies. Provocative subject lines. Questions designed to get a quick no thanks. Breakup emails. Volume, so the denominator gets big enough to make the numerator look healthy.

And it works, on the metric. Replies go up. Unsubscribes, polite declines and confused one-liners all count. The dashboard looks fine.

Pipeline doesn't move.

The deeper problem is who you're reaching. Reply rate treats every contact the same. A reply from a junior analyst who'll never sit on the buying committee counts the same as one from the economic buyer. In services, where three or four people decide, that's a broken unit.

What to measure instead

Measure first meetings with someone on the buying committee. The economic buyer, the champion, the technical lead. Not anyone with a pulse.

Measure corrections. When a senior buyer writes back to tell you your hypothesis was off and names the real problem, that's the best outcome of a first touch. It means you were close enough to be worth correcting. Track how often it happens.

And measure accounts, not contacts. At how many target accounts have you engaged two or more members of the committee? That number tells you whether you're building deals or collecting conversations.

A scenario

Say two reps sell for the same 100 person cloud consultancy.

The first sends a high volume of short, punchy emails and gets plenty of replies. They're mostly no, some asking for information, a few turning into calls with mid-level managers.

The second sends far fewer. Each one follows research on the account and names a specific hypothesis for a specific person. Replies are rarer. But a CTO writes back to say the migration isn't the issue, the team's skills are. A VP of finance forwards the note to the CIO with a line saying it's worth a look. Two accounts now have multiple committee members engaged.

On reply rate, the first rep wins. On pipeline, the second rep wins by a mile.

Why teams default to it

It's fast. You know the reply rate in a day. Meetings and committee coverage take weeks to show.

It's comparable. Every tool reports it, every peer quotes it.

And it feels like progress. A full inbox feels better than a quiet one. But a quiet inbox with three right replies beats a busy one full of wrong ones.

Change the conversation in reviews

Stop asking reps about reply rate in pipeline reviews. Ask them who on the committee they've reached at each top account. Ask what the buyer said the problem was. Ask how long it took to get from the signal to the first meeting. The post on time to first meeting as a metric covers that one.

Behavior follows what you ask about. If the weekly question is how many replies, reps will write for replies. If it's who did you talk to and what did they tell you, they'll do the research.

The one thing reply data is good for

Reply rate isn't useless. It's a decent smoke alarm. If it drops to near zero, something's broken. Deliverability, targeting, or a message that's lost all specificity.

Use it as a check, not a goal. The goal is a meeting with someone who can buy, about a problem they actually have.

Teams that make that switch send less and learn more. Every correction from a buyer sharpens the next hypothesis. Every committee meeting builds a deal instead of a log entry. For why volume breaks for big deals, read why volume outbound breaks for $250K deals.