← All articles

What's an honest cold calling conversion rate?

A rate means nothing without a definition. Dials, pick-ups, conversations, demos: here's what to track.

We get the question at every demo: what’s a good conversion rate in phone prospecting?

There’s no useful answer until you’ve said what you’re talking about. The same list, the same team and the same week can produce a rate of 2% or 30% depending on what you put in the numerator and the denominator. That’s why the numbers going around are useless.

The rates you hear everywhere

You’ve probably run into these figures: “2% conversion in cold calling”, “1 meeting per 100 calls”, “20% conversion rate”.

They’re not wrong. They just don’t measure the same thing.

The first often counts dials, including the ones that led nowhere. The second sometimes counts meetings held, sometimes meetings booked, which isn’t the same number three weeks apart. The third usually starts from conversations actually engaged, which excludes the vast majority of attempts.

When someone quotes you a rate without specifying these points, you can’t do anything with it.

The definitions that change everything

A prospecting session produces a cascade of stages, and each one can serve as the basis for a rate.

The dial. The dialer launched an attempt. It says nothing about what happened next.

The pick-up. Something answered. A voicemail picks up too: if your tool files voicemails under pick-ups, your rate is mechanically inflated.

The conversation. A person answered and the exchange lasted. This is where the definition really gets decided. From what duration do you count a conversation? Ten seconds, where the prospect says they’re not interested? Thirty? A minute?

The meeting booked. A date is in the calendar.

The meeting held. The person showed up. Between the two sits the no-show, and it’s not marginal.

A conversion rate is a ratio between two of those five stages. There are about ten possible combinations, and they give results that have nothing to do with each other.

What an industry benchmark is worth

Not much, unless it states its method.

A benchmark built on American SaaS teams calling enriched direct mobiles will tell you nothing if you’re calling the switchboards of French industrial SMEs. The pick-up rate isn’t the same, the person who answers isn’t the same, and neither is the decision cycle.

Even within one industry, the gap between two teams often comes down to the list rather than the script. A list enriched three months ago and a list bought last year don’t produce the same numbers with the same SDRs.

Use benchmarks to check you’re within a plausible order of magnitude. Not to set a team target.

Why comparison backfires

The problem isn’t that comparisons are imprecise. It’s what they set off.

A manager who finds out their team is “below market” adjusts. Often, they adjust what’s easiest to adjust: the definition. You start counting meetings booked instead of held, ten-second conversations instead of thirty-second ones. The number goes back up, and the measurement has stopped serving any purpose.

The other effect is quieter. When the target is a rate, the team learns to protect the denominator. You call fewer difficult accounts, you pull the lists that drag the average down, you keep the contacts that are already warm. The rate goes up, the pipeline goes down.

The three numbers to track

If you had to keep only three, take these.

The number of conversations per SDR per day. It’s the only volume that counts, because it’s the only moment when something actually happens. In a classic setup, most calling time produces no conversation: ringing, voicemails and wrong numbers absorb the day. That’s the number a parallel dialer moves, and it’s also the first to degrade when the list ages.

The conversation-to-meeting-booked rate. It measures what your pitch is worth once someone is on the line. You work on it with call recordings, not with a spreadsheet.

The no-show rate. The most ignored, and often the one that explains the gap between flattering reports and a disappointing pipeline.

These three numbers are read together. Lots of conversations with few meetings is a pitch or targeting problem. Few conversations with a good conversion rate is a volume or list problem. A good meeting-booked rate with lots of no-shows is a qualification problem.

What we suggest doing this week

Write the definition of each stage on one page. One line per stage, with the exact threshold: from how many seconds a conversation counts, at what point a meeting gets recorded, how a no-show gets marked.

Then check that your tool and your CRM actually apply those definitions. That’s often where the surprise comes: statuses synced automatically don’t always match what the team thinks it’s counting. The reports are only worth the statuses that feed them.

Then, and only then, compare your weeks against each other. It’s the only benchmark that really concerns you.

Frequently asked questions

What’s the average conversion rate in B2B cold calling?

There’s no usable average, because published figures don’t measure the same thing. A rate calculated on dials and a rate calculated on engaged conversations can differ by a factor of ten on the same data. Ask for the definition before keeping any figure.

From what duration does a conversation count?

There’s no standard. Many teams settle on thirty seconds, because below that you usually haven’t gotten past the opening line. The threshold matters less than setting it once and never touching it again.

Should you count meetings booked or meetings held?

Track both, and manage on meetings held. Booked meetings measure the SDR’s work; held meetings measure what reaches the pipeline. The gap between the two is information in itself.

How do you know if your rate is dropping because of the list or the team?

Look at the pick-up rate separately from the conversion rate. A falling pick-up rate with a stable conversion rate points to the list or your numbers’ reputation. The reverse points to the pitch.

Read next

See the difference in a week

Connect your CRM, run a first session, compare with the week before.