Skip to content

What SDR operations is, and why it is not sales engagement

A working definition of SDR operations, the five things it has to get right, and the specific failure modes that show up when it is run out of a spreadsheet.

Updated 1 October 20267 min readTypeGuide
bookings · october47 booked · 38 held
CompanySDROutcomeValue
Northgate LtdAnna M.held€100
Vantage GroupMike S.held€100
Seaside TechLisa K.no-show—
Hamilton MetalsAnna M.held€100
Carter & CoPaul N.pending€100
Illustrative example — sample data, not a customer screenshot.

Most sales development tooling is built for engagement — designing a sequence, sending the touches, measuring which message performs. SDR operations is a different discipline: running the function. Supplying it, staffing it, measuring it honestly, paying for it, and proving it to whoever is funding it.

A team can have excellent engagement and broken operations. The symptom is always the same: a reconciliation at the end of every month that somebody does by hand.

The five jobs of SDR operations

Supply

Reps have clean lists to work, without collisions or silently empty lists.

Staffing

Who works which client, what capacity that is, and what fits six weeks out.

Record

What was done to each prospect, by whom, with what result — and it survives turnover.

Money

What each rep earned and each client owes, derived from the same facts.

Proof

A credible, current view for the client paying for the meetings.

Engagement platforms address none of these directly. That is a scope boundary, not a criticism.

Where spreadsheet-run operations break

FailureWhat happensThe fix
Supply runs on guessworkTwo reps call one company; a rep works an empty list for a weekExpiring lead reservations and per-list depletion alerts
The record is a copyClient report and invoice disagree; the client cannot checkClients read the same data, scoped to them
Outcomes collapse into "booked"Performance is overstated by the no-show gapTrack held, no-show and no-show with reschedule
Two sources of truthCommission and billing sheets drift apartDerive both from one billable set
Capacity ignores the calendarDecember forecast looks like MarchWeekdays minus holidays and absences, times a stable rate

Supply: collisions and depletion

Collision is two reps contacting the same company for the same client. On a shared list it is certain without a lock, and to the prospect it looks disorganised. The fix is a reservation that expires — a permanent assignment turns the list into a graveyard of leads nobody revisits.

Depletion is quieter and more expensive. A rep on a list that has run dry produces nothing, activity just drops, and it can go a week before anyone asks. Per-list depletion alerts pay for themselves immediately.

Client reports built from exports drift

An exported report is a copy, and copies drift. The client has no way to check, so when report and invoice disagree a reporting task becomes a trust problem. The fix is that the client reads the same data you do, scoped by tenancy — which also ends every conversation that starts with reconciling two documents.

A booking is not a delivered meeting

Counting bookings overstates performance, and not uniformly — show rates differ between reps and between clients. Track three states:

  • Held — delivered.
  • No-show — the prospect did not attend.
  • No-show with reschedule — the meeting may still be delivered, and the commercial consequence differs.

Two reps with the same booking count and different show rates are not performing equally. A forecast built on bookings alone is wrong by exactly that gap.

Commission and invoices from the same meetings

A booked meeting is revenue at one number and cost at another. If commission and client billing live in separate sheets, they will disagree — usually in a month already invoiced. The robust fix is derivation: the same billable set produces the invoice and the commission rows, and “billed” is defined exactly once.

  • Idempotency. Jobs retry and queues redeliver. Without a unique constraint tying one commission row to one booking, a retry can double-pay. That belongs in the database, not in application logic.
  • Frozen prices. A sent invoice must stay reproducible. If billing looks the price up live, next quarter’s price change rewrites history.

Capacity needs real working hours

Capacity is a rate times available hours, and both halves are usually wrong. Bookings divided by hours collapses on small samples — three hours of history on a new client is not a rate. An estimate that starts from a prior and moves toward the observed value keeps early forecasts conservative, with manager overrides as a visible separate layer.

Available hours, done properly

  1. 1

    Weekdays

    The starting point most forecasts stop at.

  2. 2

    Minus public holidays

    For the country the account operates in.

  3. 3

    Minus absences

    Vacation, sick leave and part-time schedules.

  4. 4

    Times a stable rate

    Bookings per hour that does not swing on small samples.

Skip the holidays and a December forecast is identical to March — and you conclude the team underperformed when the denominator was wrong.

When to move off the spreadsheet

Not every team needs a platform. A spreadsheet is better for exploration, costs nothing, and handles bespoke arrangements a product would refuse. Two signals mark the threshold:

  1. Someone spends a day a month reconciling.
  2. A rep or a client disputed a number and you could not immediately prove it.

Below that, keep the spreadsheet. Above it, the cost is no longer the tool but the reconciliation — and operations deserves a system rather than a discipline.

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