SDR Metrics: Benchmarks, Red Flags, and What Good Looks

What are SDR metrics?

Most "SDR metrics" articles hand you a list of 15 numbers and call it a day. That is the wrong mental model. A list gives you data. A framework gives you a diagnosis.

The core problem SDR managers face is this: activity metrics and pipeline metrics describe completely different things. A rep who dials 100 times a day but books zero meetings has an activity number and an outcome problem. A rep who books 10 meetings a month but closes none has a qualification problem. Collapsing all of these into one score — or reviewing them on the same cadence — is where most teams lose diagnostic accuracy.

The frame that works: split every metric into one of two buckets.

• LEADING Leading indicators — activity metrics and conversion ratios. These change this week and predict pipeline two to three weeks from now. Coach on these weekly.
• LAGGING Lagging indicators — pipeline sourced, revenue attributed, SQL acceptance rate. These confirm whether the previous four to six weeks of leading work paid off. Review monthly, not weekly.

A manager who only watches pipeline is always coaching three weeks too late. A manager who only watches dials is gaming the wrong lever. You need both, reviewed at different cadences.

The four metric categories below are organized to respect this distinction. Activity and conversion metrics come first — because they are the control surface. Pipeline and efficiency metrics follow — because they are the scorecard.

Activity metrics: the leading indicators

Activity metrics measure what the rep does, not what results from it. They are leading indicators — changes in activity show up in pipeline three to four weeks later. That lag is why you have to review them weekly. If connect rate drops this week and you catch it in 48 hours, you can fix message, list, or call time before the pipeline damage arrives.

Activity metrics also distinguish effort from effectiveness. A rep with 90 dials and a 3% connect rate has a different problem than a rep with 50 dials and a 9% connect rate. Both have a pipeline exposure, but the fix is completely different. The first rep needs better contact data or a different call window. The second rep needs more time on the phone.

Bridge Group data across 365 B2B SaaS companies shows the median SDR makes 10.6 contact attempts per prospect. The revenue-maximizing range is 9–12 attempts. Reps who quit after 2–3 attempts leave more than half the addressable pipeline on the table.

One nuance most articles miss: activity targets are proxies, not goals. If a rep dials 100 times a day and never reaches anyone, the activity is noise. The right framing is to set activity targets as a floor, then coach on the conversion rates above them. The floor keeps reps in the market. The rates determine whether the market pays back.

LinkedIn activity is frequently undertargeted. Reps who run 15–25 LinkedIn touches per day — connection requests with one-line notes, direct messages on signal events, comments on buyer posts — create a third pipeline source independent of phone and email. Teams that ignore LinkedIn are leaving one of the highest-reply-rate channels untouched.

Conversion metrics: where effort becomes outcome

Conversion metrics are ratios. They show whether the activity the rep is doing is producing results. A rep can look great on activity metrics and terrible on conversion metrics — that is almost always a targeting or messaging problem, not a work-ethic problem.

Connect rate and email reply rate are the two conversion metrics that SDRs struggle with most and that are most directly improved by outreach quality. Cold templates sent to static lists average a 2–3% reply rate. Outreach tied to a specific recent event — a new hire, a funding round, a job posting in the buyer's function — averages 8–15% in Gangly rep data. The event is the unlock. Without it, reps are grinding ratios that are structurally capped.

An analysis of 16.5M cold emails put the average reply rate at 5.8% in 2025, down from 6.8% in 2023. Inbox saturation is rising. Reps relying on volume to compensate for low reply rates are running against a structural headwind. The only durable fix is more relevant targeting — which means knowing why you are reaching out before you send.

Meetings held rate is the most under-discussed conversion metric. Most teams track meetings booked but not meetings held. A booked meeting that never happens is a wasted AE slot and a pipeline number that will never close. Below 65% show rate signals that the rep is booking meetings with contacts who agreed just to end the conversation — which means the qualifying questions are too weak or the value proposition is not landing.

The lead-to-SQL conversion metric is where inbound and outbound SDRs diverge most sharply. Inbound high-intent leads convert at 75–80% to meetings. Low-intent leads convert at 5–10%. An outbound SDR reaching cold accounts should expect 10–20% lead-to-SQL. If the number is below 8%, the ICP definition is too broad — reps are working accounts that will never convert.

Pipeline metrics: the lagging indicators leadership watches

Pipeline metrics are the business scoreboard. They answer one question: is this SDR generating enough qualified opportunity to justify the investment? The answer is almost always "yes, if the activity and conversion metrics are healthy" or "no, because the conversion rates are broken." Pipeline metrics do not tell you what is wrong — they tell you that something is wrong. The diagnosis lives upstream.

The most widely cited benchmark comes from Bridge Group's 2024 study of 365 B2B SaaS companies: the median SDR generates approximately $3M in pipeline annually. The range is enormous — from under $750K to over $10M — because pipeline per SDR scales with ACV. A team selling $10K contracts will never hit $3M per SDR with the same headcount as a team selling $100K contracts.

The right way to set a pipeline target: work backward from quota. If the AE closes 25% of pipeline and needs $2M to close to hit quota, the SDR needs to deliver $2M ÷ 0.25 = $8M in sourced pipeline annually. That divides to roughly $667K per month. Knowing that target makes it possible to reverse-engineer the meetings and activities needed to produce it.

SDR-sourced pipeline as a percentage of total new business revenue is a team-level diagnostic. The benchmark is 30–45% for companies with dedicated SDR functions (Crunchbase research). If SDR-sourced pipeline is below 25%, the function is underperforming relative to its cost. If it is above 55%, the team may be overstaffed relative to marketing demand generation.

Average deal size sourced by SDR versus average deal size closed by AEs is a quality control metric. If SDRs are booking meetings with $20K accounts and AEs are closing $80K accounts, there is a targeting misalignment. Either the ICP definition is not shared between functions, or the SDR is optimizing for meetings booked rather than meetings that will close.

For a deeper look at how SDR compensation is tied to pipeline metrics and quota design, read the SDR compensation guide.

Efficiency metrics: quality per unit of effort

Efficiency metrics sit at the intersection of activity and pipeline. They measure whether the rep's effort is generating outcomes at a sustainable ratio. A rep who books 20 meetings per month but converts zero to opportunities is inefficient in a way activity metrics will not catch. A rep who books 6 meetings but converts 5 to opportunities is highly efficient even if the raw activity numbers look low.

Qualified meetings per SDR per month is the single efficiency metric most managers should anchor to. It is specific enough to be actionable, and it is a direct input into pipeline. At a 50% meeting-to-opportunity conversion rate, 10 qualified meetings per month generates 5 new opportunities. At an $80K average deal size, that is $400K in pipeline per SDR per month — well within the benchmark range.

SDR ramp time is an efficiency metric that most companies track informally. The benchmark for B2B SaaS is 3–4 months to full quota contribution. Companies with ramp times over 5 months almost always have an onboarding problem — not a rep quality problem. The rep is capable; the playbook is missing or the tooling is unclear.

SQL-to-opportunity conversion (sometimes called SAL acceptance rate) is the most direct measure of SDR-AE alignment. If AEs are rejecting more than 40% of meetings the SDR books, the qualification criteria are not shared. The fix is not to push the SDR harder — it is to sit the SDR and AE in the same room and define what "qualified" means in writing.

The Signal Ratio Framework: Gangly's approach to SDR metrics

Most SDR metrics dashboards track what happened. The Signal Ratio Framework measures what is about to happen. It is built on a single observation: the two SDR metrics that are most predictive of pipeline — connect rate and email reply rate — improve most dramatically when reps reach out in response to a real trigger event rather than a static list.

The framework adds one metric to the standard SDR dashboard: signal-sourced reply rate — the reply rate on outreach that is directly triggered by a detected buying signal, measured separately from cold outreach. This split matters because it isolates what is working.

Gangly internal data from Q1 2026 shows that reps who act on a signal within 24 hours book 3.4× more meetings than reps who batch signal processing into a weekly cadence. By day 7, four to six competing reps have typically reached the same buyer. By day 14, the signal is stale.

The four-step process:

1. 1

   Detect the signal.

   Pull job changes, funding events, hiring data, and executive moves from LinkedIn alerts, Crunchbase, and your CRM's closed-lost bucket. Do this before 9 a.m., every day.

2. 2

   Score the account.

   Apply the five-factor score: recency (×3), role match (×2), intent depth (×2), ICP fit (×2), prior relationship (×1). Work accounts scoring 80+ same day. See how this scoring approach works in the B2B buying signals guide.

3. 3

   Send the signal-led sequence.

   First line names the event. Second line bridges to the pain. Third line is a 15-second ask. Email + call + LinkedIn, same day, for accounts scoring 80+.

4. 4

   Measure signal-sourced reply rate separately.

   Tag every outreach that is tied to a signal. Track reply rate on signal-tagged outreach versus cold-list outreach. The gap tells you how much your signals are worth.

Gangly's Signal Detection module runs this scan automatically before the rep's day starts — ranking accounts by signal score, attaching the specific trigger event, and drafting the first outreach line. The rep reviews, edits, and sends. What previously took 45 minutes of manual tab-switching takes under five minutes. For the full outbound motion, see the outbound sales playbook.

Red flags: when a metric tells you something is broken

Numbers in isolation do not diagnose problems. A red flag is useful only when you know whether it signals a rep coaching issue, a systemic workflow issue, or a data and targeting issue. The three root causes have completely different fixes.

The most common mistake: treating a data or workflow problem as a rep motivation problem. A low connect rate is not fixed by encouraging the rep to try harder. It is fixed by cleaning the list, testing a different call window, and verifying caller ID status. Coaching without diagnosis wastes both the manager's time and the rep's confidence.

How to measure SDR performance week by week

Performance measurement works best as a two-layer review cadence. Weekly reviews cover the leading indicators. Monthly reviews cover the lagging indicators. Merging them into a single monthly review means you are always three to four weeks behind on problems that were fixable in 48 hours.

For coaching conversations, always start with the metric furthest upstream. If pipeline is low, look at meetings held. If meetings held is low, look at meetings booked. If meetings booked is low, look at connect rate and reply rate. If connect rate is low, look at activity volume and contact data quality. The problem lives one level up from where the symptom appears.

One metric that is rarely tracked but highly predictive: pipeline velocity per SDR. Velocity is the product of deal count, average deal size, win rate, and sales cycle length. An SDR who sources 5 deals at $100K that close in 60 days at 25% creates more velocity than an SDR who sources 10 deals at $40K that take 120 days to close at 15%. Track the inputs, not just the counts.

For the full picture of what SDR productivity looks like across a team, the sales productivity statistics post covers benchmarks from 1,000+ reps across funnel stages. For a deeper look at the role itself, read the complete SDR role guide.