SDR Metrics: The Numbers That Show Whether Outbound Is Working

SDR metrics should tell you where outbound is working and where it breaks. A large activity total cannot answer that question on its own. Build a diagnostic chain from prospect-facing activity to engagement, completed meetings, accepted opportunities, and pipeline. Then define every rate with a numerator, denominator, cohort, time window, source, and attribution rule.

This approach gives sales leaders a useful decision: fix the first weak stage in the chain. If execution is low, inspect capacity and workflow. If activity is high but replies or live conversations are weak, inspect the list, channel, offer, and message before asking for more volume.

The SDR Metrics Hierarchy

A sales metric is any quantifiable measure of performance. A metric becomes a KPI when the team chooses it to track progress toward a defined goal, according to Salesforce's sales KPI guide. That choice should follow the decision a manager needs to make.

We organize SDR measurement into four layers:

1. Activity and execution covers prospects worked, outbound attempts, delivered emails, live call connections, and time to first touch.
2. Engagement and conversion covers replies, positive replies, and movement between defined stages.
3. Meetings and handoff quality covers booked, completed, canceled, rescheduled, no-show, sales-accepted, and converted-to-opportunity outcomes.
4. Opportunities and pipeline covers opportunities created, raw pipeline, weighted pipeline, coverage, and closed outcomes.

The layers keep the scorecard diagnostic. A meeting shortfall might begin with low execution, weak contact data, poor engagement, calendar attrition, or a qualification dispute. One top-line number hides those causes.

These are operating definitions, not universal standards. Document them before reporting so a label such as "conversion rate" cannot quietly change from one dashboard to another.

Activity Metrics Diagnose Execution

Count each category of prospect-facing action separately. Useful fields include outbound call attempts, live connections, emails delivered, prospects worked, human replies, and time to first touch. A total activity field may include work that never reached a buyer.

HubSpot's sales analytics documentation illustrates the problem. Its completed-activities report can include calls, meetings, tasks, emails, and notes. Meetings and tasks that are not marked complete are excluded. That definition is useful inside HubSpot, but it does not make the total equivalent to outbound touches.

Call records need the same care. HubSpot's activity property documentation separates call direction, status, outcome, and connected count. Connected count refers to calls that reached a live recipient. A completed outbound call attempt therefore belongs in a different field from a live conversation.

For email, we track delivered recipients, replies, positive replies, and prospects contacted. Our operating formulas are:

• One-to-one email reply rate equals recipients who replied / successfully delivered recipients.
• Positive reply rate equals positive replies / total human replies.
• Leads to positive equals prospects with a positive reply / prospects contacted.

Positive-reply classification needs a written rule. A referral, a request to reconnect later, and a direct meeting request may all deserve separate labels even if the scorecard rolls them into one positive category.

High activity with weak connections points toward data, timing, or channel fit. Connections with weak replies point toward targeting, offer, or message. Low activity points toward capacity, workflow, or execution. Our broader outbound services connect these inputs, but the scorecard still needs to show which input changed.

Conversion Rates Need Comparable Cohorts

Every conversion rate divides one population by another. The populations must describe the same group or the result can move for reasons unrelated to current SDR performance.

Consider stage-to-stage conversion:

Cohort records entering the next stage / eligible cohort records entering the prior stage x 100

A fixed-entry cohort groups records by when they entered the prior stage, then follows that group through a defined observation window. Period-event reporting counts events that occurred during a calendar period, even if the underlying records entered months apart. Both views can answer useful questions. They should not share one label or appear as direct comparisons.

For example, suppose a team counts opportunities created in October but divides them by meetings completed in October. Some October opportunities may come from September meetings, while some late-October meetings may convert in November. That period-based formula mixes populations. A fixed cohort instead follows the meetings completed in a chosen period and reports how many became opportunities within the agreed window.

Stage skips also need a rule. A CRM may allow a record to move from meeting completed directly to qualified opportunity. Decide whether reports infer passage through the skipped stage, exclude the record from that stage's conversion, or report skips separately. HubSpot's funnel reporting can include stage skips, so the account's report settings matter.

Compare campaigns only after matching source, segment, stage rules, attribution, and observation window. Segment by campaign or rep when the resulting groups remain large enough to interpret. We do not prescribe a universal minimum because sales cycles and event volume differ by business.

Meeting Metrics Separate Booked From Held

A booked meeting records calendar creation. It says little about attendance or qualification. Track the meeting through its outcome and handoff:

• Booking rate equals meetings booked / the named eligible denominator.
• Completion rate equals completed meetings / meetings due in the cohort.
• No-show rate equals no-show meetings / meetings due in the cohort.
• Sales-accepted rate equals meetings accepted as qualified / completed meetings.
• Meeting-to-opportunity conversion equals outbound-sourced opportunities created / completed qualified meetings.

The booking-rate denominator changes the question. Meetings booked per prospect contacted measures end-to-end list efficiency. Using positive replies as the denominator measures reply handling and scheduling. A denominator of live conversations measures call conversion. Keep the denominator in the metric name or dashboard note.

HubSpot provides separate outcome fields for completed, canceled, no-show, and rescheduled meetings. Connected scheduling tools may use different properties, so normalize those values before combining records. A rescheduled meeting should not become both a completed meeting and a no-show because two systems wrote different states.

Sales acceptance also needs an agreed rubric. Specify the required account fit, contact role, stated problem, and next step. The metric then reveals whether targeting and qualification produce meetings the sales team can work, rather than measuring how many calendar slots SDRs filled.

Pipeline Metrics Connect SDR Work to Commercial Progress

Pipeline is the seller's staged view of active deals, as explained in Salesforce's pipeline guide. Pipeline value is potential revenue. It is not realized revenue or proof that the SDR alone caused a closed deal.

Start with opportunities created under a documented acceptance and attribution rule. Then keep three pipeline views distinct:

1. Raw pipeline generated is the sum of deal amounts for outbound-sourced opportunities created in the period.
2. Weighted pipeline is the sum of each deal amount multiplied by its configured probability.
3. Pipeline coverage is relevant open pipeline expected to close in the target period / the revenue target for that same period.

HubSpot's deal property documentation defines weighted amount as deal amount multiplied by deal probability. That probability follows the stage setting unless a user overrides it. Weighted pipeline therefore reflects CRM configuration. It is a planning view, not a promise about future revenue.

Coverage requires matching horizons, currencies, pipelines, and close-date rules. The Salesforce guide describes coverage relative to sales targets but does not establish one healthy multiple for every company. Use your own stage history and sales cycle to interpret the result.

Closed-won outcomes provide a lagging quality check once the cohort has had time to mature. Calculate opportunity win rate with closed-won opportunities over all opportunities closed won or lost. Leaving unresolved open opportunities in that denominator makes the rate depend on how many deals are still in progress.

Build an SDR Scorecard You Can Audit

A weekly scorecard should show the chain in order, from prospects worked through accepted pipeline. For each metric, record the formula, cohort start, observation window, source or channel, owner, CRM field or report, current result, prior comparable result, and action triggered.

Use comparisons to locate the first material change. Stable delivered volume with falling replies points to targeting or message. When positive replies hold but completed meetings fall, inspect scheduling, reminders, and calendar outcomes. A drop in sales acceptance while completed meetings stay level calls for a review of the qualification rubric and handoff. Accepted opportunities can stay level while pipeline value changes because deal sizing or stage configuration moved.

That sequence keeps the review tied to a decision. It also prevents managers from responding to every downstream miss with a volume target. For broader coaching, team design, and cadence guidance, use our sales resources. Keep this scorecard focused on definitions, comparability, and the next operating action.

Ready to See Where Outbound Is Breaking?

We build and run the managed outbound system, then report the chain from execution through qualified meetings and pipeline with definitions your team can audit.

Book your free discovery call →