Sales development metrics that matter (and the ones to delete)

Most SDR dashboards measure activity. The ones worth building measure economics. Dial counts and email volume tell you a rep is busy. Cost per SQL and pipeline created per rep tell you whether outbound is working. Here are the sales development metrics that actually predict pipeline in 2026, and the vanity metrics that should be deleted.

The four metrics every SDR org must track

1. Meetings held per rep per month. Not booked. Held. No-shows are a quality signal, not a coincidence.

2. Meeting-to-SQL conversion. The AE controls this rate. Anything below 55 percent points to an ICP or SDR quality problem, not an AE problem.

3. Cost per SQL (fully loaded). Fully loaded rep cost plus tools plus management overhead divided by SQLs. This is the single number that tells you whether the motion clears CAC.

4. Pipeline created per rep per quarter. ARR entered into stages the CRO counts as real pipeline. Ties SDR output to the number the board cares about.

The three leading indicators

Leading indicators show you where next month is going before it arrives. The three that correlate best with pipeline in B2B SaaS: conversations per rep per day (dial + LinkedIn + reply threads), positive reply rate on cold email, and connection accept rate on LinkedIn. When any of these drop for two consecutive weeks, meetings will drop the following month.

Benchmarks you can use in 2026

• Meetings held per SDR per month: 10 to 14 in mid-market, 6 to 9 in enterprise.
• Meeting to SQL: 60 to 75 percent in a healthy motion.
• SQL to opportunity: 70 to 85 percent.
• Opportunity to closed-won: 15 to 25 percent for outbound-sourced.
• Cost per SQL: $800 to $2,500 fully loaded in mid-market, higher in enterprise.
• Positive reply rate on cold email: 0.5 to 1.5 percent of sends.

Vanity metrics to stop reporting

Dials placed, emails sent, LinkedIn requests sent, and "activities logged" are inputs. They belong in coaching conversations, not in board decks. A team that hits activity targets and misses meeting targets has a motion problem or a targeting problem; the activity number cannot fix it and often distracts from the fix.

The cost per meeting question

Cost per meeting is a useful proxy but it lies without quality adjustment. Always normalize to cost per SQL or cost per opportunity. A $300 meeting that converts is cheaper than a $90 meeting that does not. See our 2026 cost per meeting benchmarks for the ranges by vertical.

Pipeline coverage: the CRO's metric

The CRO wants to know: does outbound produce enough pipeline to cover the quarter's quota with a healthy multiple? 3x to 4x is baseline in mid-market SaaS. Below 3x, the AE team will miss regardless of close rate. This is where SDR output ties directly to the P&L. Full walkthrough in our pipeline coverage formula piece.

Segment your metrics by source

SDR-sourced pipeline, marketing-sourced pipeline, and AE-sourced pipeline all convert at different rates. Blending them into a single "pipeline created" number hides where the motion is actually working. Report by source and by rep tenure (0-3 months, 3-9 months, 9+) or you will diagnose the wrong problem.

Rep tenure changes the numbers

A rep in month two producing 4 meetings is on pace. A rep in month nine producing 4 meetings is a performance conversation. Blending them into "team average" masks both. Any serious dashboard segments by tenure.

The show-rate audit

No-show rates above 25 percent point to a booking problem, not a buyer problem. Common causes: booking too far out, no confirmation email cadence, meetings not calendar-blocked for the buyer, AE not sending a value email between book and meet. Fix this before you blame the sequence.

AE feedback loop

AEs must submit a written accept-or-reject decision on every meeting within 24 hours. Reject reasons feed a monthly review. Without this loop, SDRs and AEs drift into different definitions of quality and pipeline reporting becomes political. This is one of the largest untracked drivers of SDR attrition.

Deliverability metrics belong on the SDR dashboard

Bounce rate, spam rate, domain reputation, and mailbox rotation should be visible to the SDR manager weekly. When deliverability degrades, meeting output follows within two weeks. See our deliverability infrastructure guide for the metrics that matter and how to monitor them.

Weekly, monthly, quarterly cadence

• Weekly: conversations, reply rate, meetings booked, meetings held, deliverability health.
• Monthly: meeting to SQL, cost per SQL, SQL to opportunity, AE-rejected meetings and reasons.
• Quarterly: pipeline coverage, opportunity to closed-won, CAC payback on outbound-sourced ARR.

Common mistakes

1. Measuring dials and emails as the primary KPIs.
2. Not tracking meetings held, only booked.
3. Blending SDR-sourced and marketing-sourced pipeline in one number.
4. Ignoring AE reject rate and reason data.
5. No deliverability visibility until reply rates already collapsed.

The dashboard we build for clients

A working SDR dashboard fits on one screen: this week's conversations, meetings held month to date vs target, cost per SQL month to date vs target, pipeline created quarter to date vs target, deliverability health, and top three rejected-meeting reasons. Everything else is a coaching tab, not a board tab. If you want a version scoped to your motion, see sales operations as a service.

The closing take

Measure economics, not activity. Segment by source and tenure. Watch leading indicators weekly. Fix the AE feedback loop. If your dashboard cannot answer "does outbound clear CAC," rebuild it. And if you want us to run the motion and the reporting for you, book a 20-minute pipeline review.