Skip to content

Incentive compensation management for SDR teams

Incentive compensation built into the operation: each booking creates one commission row, enforced by the database, and the same rows produce the invoice.

Updated 9 October 2026ForOperations and finance leads who own the payout
cancellation approved · compensationHarbor Group · 6 Oct
Invoice sentComm. paidClient sideSDR side
nono—Commission cancelled
yesnoCredit on next invoiceCommission cancelled
noyes—Work owed (open)
yesyesCredit on next invoiceWork owed (open)
money never moves backwardthis booking: row 2
Illustrative example — sample data, not a customer screenshot.

What this gets you

Commission computed from the booking itself, not from an exported spreadsheet

Exactly one commission row per booking, enforced by a unique database constraint

A retried job or redelivered message cannot double-pay — the database refuses it

Approve → pay lifecycle, so "has this been paid" is a stored fact

Cancellations and no-shows resolved by a stored policy, applied identically every month

The same billable set produces both the payout and the client invoice

Most ICM tools get their data from somewhere else

ICM platforms model compensation well, but the data arrives from elsewhere. Someone exports activity from a CRM, maps it to plan rules, loads it and fixes the gaps by hand. An agency also has money moving in two directions: you pay an SDR and invoice a client for the same meeting, and nothing checks that the two agree.

Commission comes from the work itself

Dialbrew is where the work happens, so commission is a by-product of it.

  1. 1

    Lead reserved

    The lead is pinned to one SDR while they work it.

  2. 2

    Calls and SMS logged

    Every touch lands on the lead’s timeline.

  3. 3

    Meeting booked

    Pushed to the client’s HubSpot or Pipedrive.

  4. 4

    Outcome recorded

    Held, no-show or no-show-with-reschedule.

  5. 5

    Commission row

    Exactly one per booking, priced from the client’s product.

Each product carries a customer price and an SDR commission, each with its own currency. One booking prices both the invoice and the payout, so the two cannot drift.

One row per booking, enforced by the database

A UNIQUE (booking_id) constraint makes a duplicate commission impossible, not just unlikely. Background jobs retry and queues redeliver; the second insert is rejected.

Rows move pending → approved → paid, with reverting available. The sync that keeps commission in line with booking outcomes never touches a row that is already approved or paid.

Cancellations: money never moves backward

When a cancellation is approved, the matrix in the example above checks whether the client was already invoiced and whether the SDR was already paid. A billed client gets a credit on the next invoice. An unpaid commission is cancelled; a paid one becomes open work owed by the SDR. The rule is stored, so it resolves the same way in March and November.

When a commission row or billing record is created, the price is copied onto it. Raising a client’s price next quarter does not change last quarter’s payouts or invoices.

Dialbrew vs a dedicated ICM platform

DialbrewDedicated ICM platform
Creates the commission data from bookingsImports it
Client invoice from the same meetingsNot the category focus
Multi-tier, territory and quota modellingCore focus
Complex accelerator structuresCore focus

Category-level comparison. Dedicated platforms such as Everstage, CaptivateIQ and Xactly are better for large-scale plan modelling.

When this fits

Several clients, several SDRs and a commission model that differs by client, with someone spending real time each month turning meetings into both a payout and an invoice. With one client and one scheme, a spreadsheet is fine. Dialbrew also does not run payroll: it hands your payroll process a correct, single number.

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