Skip to content

SDR outsourcing — the operating system for the provider

The platform for selling SDR capacity as a service: shared rosters across clients, per-client pricing and commission, honest outcomes and a client portal.

Updated 9 October 2026ForProviders selling SDR capacity, and buyers evaluating one
client portal · Kestrel Ltd · october
Worked byRicky RomaDave MossShelley Levene
MeetingSDROutcomeBilling
Tremont DentalRicky R.heldbillable
Alder ClinicsDave M.heldbillable
Medi NorthRicky R.cancelledcredited
Kingsway CareShelley L.upcomingupcoming
credit applied to next invoicesame data your team sees
Illustrative example — sample data, not a customer screenshot.

What this gets you

One shared rep roster spread across many client projects, with unambiguous attribution

Per-client products carrying a customer price and an SDR commission

Booking outcomes that decide billability and payout from the same record

A client portal that proves delivery without a monthly export

Capacity answers before you sign the next client

For providers and for buyers

If you provide outsourced SDR capacity, Dialbrew runs the operation. If you are buying it, the last section lists what to ask a provider. Most of it is about record-keeping, not headcount.

Three things that make outsourcing hard

Attribution

SDRs are shared across clients. A named roster per client project gives every meeting one client and one SDR.

Two prices per meeting

Each product carries a client price and an SDR commission, so one meeting prices both.

Proof

The client portal shows meetings with outcomes, reports and billing, live.

What triggers the invoice

In a per-meeting model, the billing trigger is the negotiation:

TriggerYou carryClient carries
Meeting bookedNothingAttendance and qualification risk
Meeting heldAttendance riskQualification-fit risk
Accepted as qualifiedAttendance and their judgementLittle
Opportunity createdAll of it, plus their sales processAlmost nothing

Each step down should raise your price per meeting. Meeting held is usually the right place to land. Dialbrew records held, no-show and no-show-with-reschedule as separate outcomes, so that trigger can be enforced.

Agree on no-shows before you sign

  • Prospect no-show: replaced or billed? Capped?
  • Prospect reschedules: the same unit, not a new one.
  • Client’s own salesperson misses a delivered meeting: billable. Say so.
  • Disqualified afterwards: within what window, on what criteria?

Then the internal side: what does the SDR get in each case? Dialbrew stores the cancellation policy, so the same case resolves the same way every month, and the client sees the credit without asking.

Meetings-per-hour rates per SDR per client, against hours net of public holidays and absences, answer “can we take this client in six weeks” before you sign.

If you are the buyer, ask four things

  1. 1

    Can I see my meetings live?

    A monthly PDF is a copy, and copies drift.

  2. 2

    Are no-shows visible?

    With credits applied automatically, not netted off quietly.

  3. 3

    What triggers an invoice?

    Booked, held or accepted, and the rejection window.

  4. 4

    Who worked my account?

    A stored roster answers it. A shared mailbox does not.

A provider running on Dialbrew can answer all four from the system.

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