◆   Field Dispatch Series — Revenue Operations   ◆   Downloaded, Not Hired   ◆

SDR Productivity: What to Measure and What to Stop

The SDR team is the most heavily measured function in most sales organisations. Calls per day, emails sent, LinkedIn messages, sequences enrolled, follow-up touches — the dashboards are full of numbers. The problem is that most of these numbers measure effort, not output. Measuring effort is what you do when you don't trust your people or don't understand what actually produces results. Either way, it produces the wrong behaviour: SDRs who optimise for metrics rather than for quality, and pipelines stuffed with meetings that will never become opportunities.

The activity-metric trap is seductive because the data is easy to collect. Your sequencing tool logs every email and call. Your CRM records every task. A manager can build a dashboard in a morning that shows who is working hard. What that dashboard cannot show is whether the work is any good — and in SDR functions, the quality of the work is almost entirely what determines the output.

Why Activity Metrics Are Misleading

Activity metrics create a specific failure mode. When SDRs are measured on calls per day, they make more calls — to poorly qualified accounts, at suboptimal times, with recycled talk tracks. When they are measured on emails sent, they send more emails — generic, lightly personalised, destined for the spam folder. The volume goes up. The conversion rate goes down. The meeting-held-to-opportunity rate collapses. And because the dashboards are full of green numbers, management doesn't see the problem until the pipeline is hollow.

The deeper issue is that activity metrics don't capture the variable that matters most: the quality of the account being targeted and the quality of the message being delivered. An SDR who sends 20 carefully researched, precisely targeted emails to ideal-fit accounts will almost always outperform one who sends 100 templated emails to a mixed list. The second SDR looks more productive on every activity dashboard. In reality, they are generating noise.

What Actually Predicts SDR Output

Four metrics — tracked carefully and interpreted together — give you a genuine picture of SDR productivity. They are sequence quality, ICP precision, call connect rate, and meeting-held-to-opportunity rate.

Sequence Quality

A sequence is not a set of templates. It is a series of value propositions delivered in the right order to the right person at the right time. Sequence quality is measured by reply rate and positive reply rate. Total reply rate tells you whether the message is getting through. Positive reply rate — replies that lead to a conversation rather than an opt-out — tells you whether the message is resonating.

If reply rate is below 5%, the message is irrelevant or the targeting is wrong. If positive reply rate is low relative to total reply rate, the message is generating interest but not sufficient clarity on the value proposition to move someone to act. Both problems are fixable, but only if you are measuring the right thing. Most teams are not.

ICP Precision

What percentage of the accounts an SDR is working match your Ideal Customer Profile? This is a pre-activity metric — it measures the quality of the input before any outreach happens. SDRs who are working low-ICP-fit accounts will have poor conversion rates regardless of how good their sequencing is. The account is the constraint, not the effort.

ICP precision should be tracked per SDR and per team. High variation in ICP precision between SDRs is a data quality problem or a list-building process problem. Low ICP precision across the whole team is an ICP definition problem — see the post on How to Build an ICP That Sales Will Actually Use.

Call Connect Rate

Connect rate — the percentage of calls that result in a live conversation — is a leading indicator of both targeting and timing. A connect rate below 5% on cold calls suggests either the wrong contacts are being called, the wrong times are being used, or both. Industry benchmarks vary by segment, but most SDR teams should be targeting a connect rate between 8% and 15% on well-targeted lists with intelligent timing.

Connect rate also tells you about list quality. If an SDR is calling direct lines sourced from accurate data, their connect rate will be significantly higher than one calling main switchboard numbers from a stale list. This is measurable and manageable, but only if you are tracking it at the individual SDR level rather than burying it in team-level averages.

Meeting-Held-to-Opportunity Rate

This is the most important metric in the SDR function and the one most often ignored. It measures what percentage of held meetings get accepted by the account executive as a qualified opportunity. An SDR who books 20 meetings per month but only 6 are accepted as real opportunities is not performing at the level their booking rate suggests. They are producing volume, not pipeline.

A healthy meeting-held-to-opportunity rate should be above 60% for a well-run SDR function targeting good-fit accounts. Below 50% is a serious signal that something is wrong — either with ICP precision, with the qualification criteria being applied, or with the handover process between SDR and AE. Track this metric by SDR and by the AE receiving the meetings, because the problem sometimes lives on both sides of the handover.

THE FRAMEWORK

The full interrogation framework is Dispatch #007 — SDR Qualification Framework. 38 questions across four sections that expose where your outbound qualification motion is creating pipeline noise instead of pipeline quality. $97. Instant download.

See the full framework →

Building a Productivity Framework That Improves Over Time

The goal is not to replace activity tracking with a single output metric. It is to build a layered framework that connects activity to quality to outcomes, so you can diagnose problems at the right level and improve the system iteratively.

The framework works like this. Start at the output: meeting-held-to-opportunity rate. If it is low, work backwards. Are meetings being held? If yes, the problem is qualification. Are meetings being booked? If yes, the problem is in the handover or in the AE's acceptance criteria. Is outreach getting replies? If yes, the problem is in the conversation and discovery. Is outreach being sent to the right accounts? If no, the problem is ICP precision upstream of everything else.

Each metric in the chain points to a specific intervention. Low ICP precision requires better list-building processes or a clearer ICP definition. Low connect rate requires better data or smarter calling times. Low positive reply rate requires sequence testing and message improvement. Low meeting-held-to-opportunity rate requires tighter qualification criteria and better SDR training on discovery. None of these interventions are made visible by tracking calls per day.

Run a weekly review with SDR managers that starts at the output metric and works backwards. Do this consistently and you will see improvement in every leading indicator within a quarter. The team learns which behaviours actually drive results and starts to self-direct toward them. That is a productivity framework. Daily call minimums are not.

The Pipeline Quality Problem That Volume-Measured SDR Teams Create

There is a downstream cost to activity-driven SDR management that does not show up in the SDR metrics but shows up clearly in the sales metrics. When SDRs are incentivised to book meetings rather than book qualified meetings, account executives spend a significant portion of their time on first calls that should never have been booked. This increases average sales cycle length, lowers conversion rates at early stages, and creates the false appearance of a full pipeline that is actually full of junk.

The AE who gets three low-quality meetings from an SDR will start to distrust SDR-sourced pipeline. They will mentally downgrade those opportunities in their forecasting. They will deprioritise follow-up. The relationship between SDR and AE degrades, handover quality gets worse, and the pipeline quality problem compounds. You can see this dynamic clearly in pipeline coverage ratio analysis — teams with high coverage ratios but low conversion rates almost always have a qualification problem rooted in SDR output quality.

The fix is to align SDR and AE incentives around the same outcome: qualified opportunities, not meetings. This might mean SDRs are partly compensated on opportunity-to-pipeline conversion rather than solely on meetings booked. It definitely means the definition of a qualified meeting needs to be explicit, written down, and consistently applied. See the post on pipeline qualification for the criteria that distinguish real opportunities from polite conversations.

Also track SDR productivity in the context of MQL-to-SQL conversion — if marketing-sourced leads are converting at a significantly higher rate than SDR-sourced opportunities, it tells you something about the relative quality of outbound targeting versus inbound intent. Both numbers should be moving up over time.

An SDR team measured on calls per day will give you calls per day. An SDR team measured on qualified pipeline will give you a business.

SDR productivity is a system problem, not a motivation problem. The SDRs who are making 80 calls a day to poorly qualified accounts are not lazy — they are rational actors responding to the incentives they have been given. Change the metrics, change the incentives, build the diagnostic framework that connects activity to quality to outcome, and you change what the team optimises for. That is the lever. Pull it.

DISPATCH #007

SDR Qualification Framework

38 questions that expose where your outbound qualification motion is generating pipeline noise instead of pipeline quality. $97. Instant download.

Download the Framework — $97 See the framework →
Other Field Notes