Reply rate vs meeting rate in outbound GTM

Optimize for meetings booked and held, not polite reply rate.

A 12% reply rate with almost no held meetings is not a Convert win. It is a signal that your notes are easy to answer and hard to buy from. Ehrenberg-Bass / LinkedIn B2B Institute: about 95% of buyers are out of market. Out-of-market people are great at polite replies. They are terrible at revenue.

Optimize for meetings booked and held, not polite replies. Reply rate without meeting rate hides domain burn and wasted Convert cycles.

What is the verdict in one line?

Meeting rate is the primary outbound metric in Convert and Grow. Reply rate is a diagnostic, not a scoreboard.

If you need a hierarchy: held meetings > booked meetings > positive replies that name a next step > soft replies > raw reply rate > open rate. Anything that climbs the wrong end of that list while the top stays flat is theater. Same law as meetings, not theater and vanity metrics that kill GTM teams.

Why do vanity replies feel good and still fail?

Because they look like progress in a weekly screenshot.

Soft replies ("interesting, send more," "not now," "looping my teammate") inflate reply rate. They also consume research time, follow-up slots, and optimism. Salesforce still puts about 27% of reps at quota. Teams that celebrate reply spikes while meetings stay flat are often in the miss majority with nicer Slack charts.

Worse: high-volume soft-reply craft can accelerate domain burn. You trained the inbox ecosystem that your domain sends mail people engage lightly and never convert. Deliverability does not care that the replies were friendly.

What metrics should you actually watch?

Keep the set small enough that Grow can govern it.

1. Meetings booked from signal sends (primary leading)
2. Meetings held (primary lagging for quality)
3. Positive next-step rate (reply that names a time, a stakeholder, or a clear no)
4. Account multi-thread depth on opportunities (are you stuck on one champion?)
5. Domain health (bounces, spam complaints, placement checks)
6. Reply rate only as a diagnostic when meeting rate moves the wrong way

For the measurement method, use meetings from signal sends. Attribute to the weekly signal list, not to "outbound" as a blob.

What failure modes show up when reply rate leads?

• Copy optimized to be agreeable instead of specific
• CTAs that ask for a thought instead of a meeting path
• Sequences that farm curiosity from the 95% out of market
• SDRs rewarded on replies while AEs inherit empty calendars
• Scaling send volume after a reply spike without a meeting spike
• Ignoring hold rate: booked meetings that melt are not Convert success

How do you fix the scoreboard this week?

1. Put held meetings at the top of the outbound dashboard.
2. Tag replies as next-step, soft, or no. Stop reporting a single reply %.
3. Spot-check ten soft replies. Ask if a proof asset or a clearer ask would have filtered earlier.
4. Cap weekly sends to the signal review list. Volume without windows raises replies from the wrong people.
5. If reply rate rises and meetings do not, freeze copy experiments that chase agreeableness. Rewrite for a clear meeting path.

Would you rather a 15% reply rate and two held meetings, or a 4% reply rate and eight held meetings from the same send budget?

Adapt or fail. Grow scales what books and holds meetings. Reply rate is a clue. It is not the goal.

Start Signals, Convert, Grow

FAQ

Is reply rate useless?

No. It is a diagnostic. Use it to spot deliverability issues or dead copy. Do not use it as the KPI that decides bonuses or scale.

What is a "good" meeting rate?

I will not invent a benchmark. Define meeting rate as held meetings divided by accounts (or people) contacted from your capped signal list in a period. Track your own baseline for two weeks, then improve that number. Sourced industry averages are noisy across ICPs.

Should positive replies count if they are not meetings yet?

Count them as a pipeline stage, not as the win. A positive reply that books a time becomes a meeting metric. A positive reply that stalls stays a diagnostic.

How does this fit Signals, Convert, Grow?

Signals caps who you contact. Convert writes for a meeting path. Grow refuses to scale vanity reply craft. The scoreboard has to match that order or you will scale the wrong loop.