Skip to content

SDR commission models that survive a cancellation

The common ways to pay SDRs, what each incentivises, and how to write a compensation policy that resolves no-shows and cancellations consistently.

Updated 1 October 20267 min readTypePlaybook
commission · approve → pay€3,800 pending
SDRProductStateAmount
Anna M.Meeting · stdpending€1,400
Mike S.Meeting · stdapproved€1,100
Lisa K.Meeting · entpending€900
Paul N.Meeting · stdwithheld€400
unique per bookingno double-pay
Illustrative example — sample data, not a customer screenshot.

Most arguments about SDR pay are not about the rate. They are about the edge cases — the meeting that no-showed, the one that rescheduled twice, the one the client cancelled the day before, the one already invoiced when it fell apart. A model that does not answer those in advance gets renegotiated every month.

This is a structural guide, not a benchmark. We do not quote market rates: they vary by market, seniority and deal size, and a number invented on a vendor page is worse than no number. To run your own numbers through a pay model, use the SDR commission calculator.

Five common SDR commission structures

Per booking

A flat amount per meeting booked. Simple and motivating, but it pays on a promise and rewards volume whether or not the meeting holds.

Per held meeting

The same, gated on attendance. Aligns the rep with the client, but the rep carries attendance risk, so the rate is usually higher.

Tiered or accelerated

The rate rises past a threshold. Pushes top performers, but a hard tier invites a bad booking just below it. Softer accelerators reduce that.

Base plus variable

A salary plus one of the variable models. Standard for employed reps and often legally necessary; often the wrong shape for contractors.

Percentage of client price

Scales with the value of the work when clients pay very different amounts per meeting. Reps can infer your margins from it.

What triggers payment matters most

Pick one trigger and write it down:

TriggerPays onRep carries
Booking createdA promiseNo outcome risk
Meeting heldA delivered unitAttendance risk
Client invoicedYour billing cycleAttendance + your process risk
Client paidCash collectedAttendance + your process + client credit risk

A later trigger lowers your risk and raises the rep’s, and they will price that in. Paying on client paid makes the rep an unsecured creditor of your customer. Meeting held is the usual middle ground: it aligns incentives without making the rep carry risks they cannot see.

Write the compensation matrix as a table

Most operations keep this in somebody’s head. Write it over the scenarios that actually occur — who initiated, how much notice, whether a reschedule was requested, whether it was already invoiced — and give each row two answers: what the client is credited and what the rep keeps. Those are separate decisions. Crediting the client and still paying the rep is often right when the failure was not the rep’s doing; a rep who loses income to a client’s cancellation learns to distrust the system.

ScenarioClient creditedRep keeps
Prospect no-show, no rescheduleYesPolicy decision — usually yes, if qualification was sound
Prospect no-show, reschedule requestedNo (meeting pending)Yes, pending the rescheduled outcome
Client cancelled, short noticeNoYes
Client cancelled, long noticePartial or fullPolicy decision
Disqualified afterwards as unqualifiedYesNo
Already invoiced when cancelledCredit note next cycleYes

A sketch of the shape. The exact answers are yours — decide them once and apply them identically every month.

Show credits to clients and reps

A credit the client sees appear by itself is a non-event. A credit they have to notice and ask for is a renewal risk, and the suspicion outlasts the amount. The same holds internally: a rep who can see why a commission row was reduced, against a stated policy, argues far less than one who just receives a smaller payment.

Three implementation details that prevent disputes

  1. 1

    One row per booking

    Enforced by a database unique constraint, not application logic. Retries and redelivered jobs cannot create a duplicate.

  2. 2

    An explicit lifecycle

    Pending, approved, paid — with reversion possible. "Has this been paid" is a stored state, not a recollection.

  3. 3

    Frozen prices

    Copy the price onto each commission and billing row when it is created, so next quarter’s price change cannot rewrite last quarter’s pay.

The test of a good commission model

Hand the policy to someone who has never closed your books. If they produce the same numbers you would, the model works. If not, the policy is still in someone’s head, and you are one holiday away from an inconsistent month.

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