SDR metrics that matter, and the ones that mislead

SDR metrics are the numbers used to judge whether a sales development rep’s work is creating real pipeline. The ones that matter connect activity to outcomes: conversations held, meetings that actually happen, and opportunities the account executive (AE) accepts and moves forward.

It is easy to measure what is simple to count. Dials, emails and tasks completed are all easy to track, so they often become the scoreboard. But a rep can hit every activity target and still create very little pipeline. Good metrics help you see the difference and decide what to change.

Activity metrics vs outcome metrics

Activity metrics count what a rep does. Outcome metrics count what that work produces.

• Activity metrics: calls made, emails sent, social touches, accounts worked, tasks completed.
• Outcome metrics: live conversations, positive replies, meetings booked, meetings held, opportunities created, pipeline accepted by the AE.

You need both. Activity explains why outcomes move. If meetings drop, activity data can show whether the rep made fewer calls, worked the wrong accounts or simply hit a quiet week. But activity on its own is only effort. It says nothing about whether the effort was aimed well.

Leading vs lagging SDR metrics

A leading metric moves early and hints at what will happen later. A lagging metric confirms results after the fact.

• Leading: conversations, positive replies and meetings booked. Best for weekly coaching and quick course correction.
• Lagging: meetings held, opportunities accepted and pipeline that progresses. Best for judging real impact over a month or a quarter.

Leading metrics are useful because you can act on them this week. Lagging metrics are useful because they are harder to game. A healthy review uses leading metrics to steer and lagging metrics to check that the steering worked.

Which SDR metrics are worth tracking?

Conversation rate

Conversation rate is the share of call attempts that turn into a real conversation with the right person. It reflects list quality, timing and contact data more than it reflects talent. A falling conversation rate is often a sign of stale numbers, poor-fit accounts or calls at the wrong time of day, not a rep who has stopped trying.

Meetings held vs booked

A booked meeting is a promise. A held meeting is the outcome. The gap between the two tells you a lot:

• Many no-shows can mean the prospect was pushed into a meeting they did not really want.
• It can also mean weak confirmation habits or too long a wait between booking and the meeting.

Track both, but give more weight to meetings held. A rep who books fewer meetings that nearly all happen may be creating more value than one with a long list of empty calendar slots.

Pipeline quality

Pipeline quality asks whether the meetings an SDR creates turn into opportunities worth pursuing. Useful signs include:

• the AE accepts the opportunity after the first meeting;
• the account fits your ideal customer profile (see how to define ICP fit);
• the opportunity moves to the next stage within a reasonable time;
• the handoff gave the AE enough context to run the meeting well.

That last point is often missed. A strong SDR to AE handoff is part of what makes pipeline quality measurable, because the AE can judge the meeting against what was promised.

SDR metrics that mislead

Some numbers look good on a dashboard but hide the real picture.

• Raw dials. A high dial count can come from a poor list where nobody answers. Dials matter only next to conversation rate.
• Raw emails sent. Sending more generic emails can raise activity while lowering reply quality and hurting deliverability.
• Open rates. Many email clients and privacy features affect open tracking, so opens are a weak sign of interest.
• Meetings booked alone. Without held and accepted counts, this rewards booking anyone who will say yes.
• Tasks completed. Clearing a task list says nothing about whether the right tasks were on it.

The problem is not that these numbers exist. It is reading them alone, or setting targets on them without a matching quality check.

A quick reference for common SDR metrics

Metric	What it tells you	Watch out for
Dials and emails	How much effort went in	Easy to inflate with poor lists or generic messages
Conversation rate	Whether lists, timing and data reach real people	Depends on data quality, not only on the rep
Positive replies	Whether messages feel relevant	Small numbers swing a lot week to week
Meetings booked	Whether conversations turn into next steps	Says nothing about whether the meeting happens
Meetings held	Whether booked meetings were real	Confirmation habits can hide weak interest
Opportunities accepted	Whether meetings create real pipeline	Needs a clear, shared definition with the AE team

A worked example

Two SDRs at a fictional 200-person HR software company book a similar number of meetings in a quarter. The first works long dial lists across the whole territory, and many of her meetings no-show or get rejected by the AE. The second works a shorter list of high-fit accounts with fresh signals, and most of his meetings are held and accepted.

On a dials dashboard, the first rep looks stronger. On held meetings and accepted pipeline, the second rep is clearly creating more value. The useful coaching question for the first rep is not “can you dial more?” but “which accounts and messages led to meetings that held?”

How to review your own numbers

Pick a short set of metrics and look at them the same way each week. A weekly territory review is a natural place to do it.

1. Check leading metrics: conversations, positive replies and meetings booked.
2. Compare meetings held with meetings booked.
3. Look at which signals, accounts and angles produced held meetings.
4. Change one thing next week, such as the list, the call time or the opener.

The rule to remember

Count activity, but judge results. Meetings held and pipeline your AE accepts tell you more than any dial count, and raw activity only means something when you read it next to an outcome.

To aim each day’s activity at the accounts most likely to turn into real meetings, see the daily attack plan.