Skip to content

Sales performance management for SDR teams

Performance rollups per rep and client project, bookings-per-hour rates, money per hour and work-time variance, measured against real working days.

Updated 9 October 2026ForTeam leads and operations managers measuring output
performance · this month4 SDRs
ClientAll projectsNorthgate LtdKestrel LtdHarbor Group
SDRCallsConv.Booked / heldMeetings per hour
Ricky Roma4129614 / 120.42
Shelley Levene388819 / 60.27
Dave Moss3558811 / 100.36
Jordan Belfort301647 / 50.22
hours net of holidays + absences33 held of 41 booked
Illustrative example — sample data, not a customer screenshot.

What this gets you

Performance rollups pre-aggregated per rep and per rep-per-client-project

Bookings-per-hour rates that stay conservative on small samples

Money produced per hour spent, per rep and per client

Work-time variance: expected hours against hours actually logged

Show rate measured at the grain where the cause lives

Three common errors in SDR performance numbers

Most SDR dashboards use the right metrics with the wrong denominators. The errors are systematic, so the same reps and the same months look wrong every time.

Typical dashboard

  • Weekdays as the denominator, so December looks like a collapse
  • Booked meetings counted as delivered, though show rates differ by rep and client
  • Two bookings in three hours planned as 0.67 meetings per hour
  • Hours taken from self-reported timesheets

In Dialbrew

  • Working days = weekdays minus public holidays, then absences and part-time schedules
  • Held, no-show and no-show-with-reschedule recorded as separate outcomes
  • Bayesian rates that stay conservative until there is enough history
  • Active hours accrued in the app, pausing on idle and hidden tabs

What each SDR is measured on

Rollups are pre-aggregated per SDR, and per SDR per client project, for daily, weekly and monthly periods. Filter by client or by SDR and the same numbers recompute for that slice.

Activity

Calls made and connected, connect rate and conversion rate.

Meetings

Booked, held, no-show, disqualified and rejected, plus no-show rate.

Meetings per hour

A per SDR, per client rate from a Bayesian estimate, with manager overrides kept as a separate layer.

Money per hour

Revenue produced against hours spent, per SDR and per client project.

Work-time variance

Expected hours against hours logged, so drift shows while you can still act.

Hours

Scheduled, observed active and absence hours on every rollup.

A manager override never overwrites the computed rate. It is stored on top, visible as an override, and the model value stays available to revert to.

Money per hour usually decides whether a client is worth keeping. A client with a hard-to-reach market and a low show rate can lose money while its revenue line looks healthy.

Built to resist gaming

Any metric tied to pay gets optimised. Two guards are structural: pay on held meetings, not booked ones, and take hours and outcomes from the system, not from self-report.

On benchmarks

Your own trailing numbers, split by client, are a better benchmark than any industry figure. They already account for your market, list quality and qualification bar.

The platform is built towards a six-week capacity forecast within ±15%. That is a design target, not a measured guarantee.

Book a walkthrough

Put every client on one floor

A walkthrough on your own roster, clients and commission model — from an imported list to a sent invoice. Judged on your operation, not a demo dataset.

One booked meeting pays for an SDR's seat for the month.

EU-hosted · eu-central-1 · integrates the CRM, calendar and telephony you already run