Skip to content
For SDR agenciesBuilt for agencies that book meetings for clients

The platform to manageSDR operations.

Dialbrew is one place to run your SDR team and your clients: lead lists, calls, booked meetings, meeting outcomes, SDR commission and client invoicing.

Book a demoWalk the workflow
7
workflow stages, one record
1
row behind every invoice and payout
0
spreadsheets at month end

Illustrative — example clients and figures, not customer data.

01The problem

Six tools. Six versions of the month.

The work is real. The record of it is scattered across tools that were never designed to agree — and someone reconciles them by hand, every month, for every client.

Today6 systems
  • Prospect listsCSVs + a sheet
  • Calls & SMSdialer / phone system
  • Meetingscalendar
  • Client dealsclient's CRM
  • Rep commissionspreadsheet
  • Client invoiceaccounting tool

Six places, six versions of the month, and a reconciliation someone does by hand. The invoice and the payout are computed separately, so eventually they disagree.

With Dialbrew1 platform
lead → invoice
  1. Leadreserved to Anna M.
  2. Contacted3 calls · 1 SMS · recorded
  3. Bookedpushed to client CRM
  4. Heldoutcome recorded
  5. Commission€100 · approved
  6. Invoicedon INV-2041 · sent
derived from one rowreconciled

One lifecycle, one record. The client invoice and the rep payout arederived from the same booking — which is why they cannot drift apart.

Illustrative. Figures and names are examples, not customer data.

02Built for agencies

One floor. Many clients. Each in its own lane.

An agency is not one sales team — it is several clients’ campaigns run by a shared floor of reps. Every client project carries its own lists, products, DNC, roster, CRM and portal. Switch client, switch scope.

client project · Lumen Software

Products

Discovery meeting€120rep €35
Enterprise meeting€260rep €70

Roster · bookings share

AMAnna M.42%
LKLiisa K.31%

List health

1,840

rows in play

92%

valid E.164

46

DNC suppressed

Bookings flow to

HubSpotGoogle Calendar#lumen-meetingsClient portal

Booked this month

47

Held

38

Show rate

81%

client project · Nordkapp Logistics

Products

Qualified meeting€90rep €25
Site visit€180rep €50

Roster · bookings share

MSMikko S.38%
PNPekka N.29%
AMAnna M.18%

List health

3,120

rows in play

88%

valid E.164

141

DNC suppressed

Bookings flow to

PipedriveOutlook Calendar#nordkapp-sdrClient portal

Booked this month

62

Held

49

Show rate

79%

client project · Vireo Health

Products

Clinic demo€150rep €40

Roster · bookings share

LKLiisa K.44%
JVJussi V.35%

List health

1,240

rows in play

95%

valid E.164

12

DNC suppressed

Bookings flow to

HubSpotOutlook Calendar#vireo-pipelineClient portal

Booked this month

29

Held

25

Show rate

86%

Illustrative example clients. Lists, products, pricing, DNC and reporting are all scoped to the client project they belong to.

03The workflow

Seven stages. One record. Nothing re-entered.

Each stage hands the next its data and leaves a real artefact behind. Scroll the chain from an imported list to a sent invoice.

  1. 01ListAccount manager

    A list lands clean, inside the client it belongs to

    Imported per client project. Numbers normalise to E.164 so duplicates actually collapse, the client’s DNC list removes rows before a rep ever sees them, and a depletion threshold warns you before someone spends a week working nothing.

    import · vireo-q4.csv1,240 rows
    Aalto Clinics+358 9 4241 1100
    Medi Nord+358 40 551 2093
    Aalto Clinics+358 9 4241 1100duplicate
    Kuopio Care+358 17 288 400dnc
    Tampere Dental+358 3 315 6600

    E.164

    normalised

    38

    duplicates

    12

    DNC removed

  2. 02ReserveSDR

    Opening a lead makes it one rep’s, for now

    An expiring soft lock pins the lead to the SDR working it, so two reps never dial the same company. A background job releases stale holds — an abandoned claim does not quietly take a lead out of circulation.

    lead · reserved to youexpires 6d

    Nordkapp Oy

    +358 40 123 4567 · Helsinki

    manufacturingrecent hire52 staff
    Call · 4m 12sanswered
    SMS · follow-up sent
    Note · asked for Q1

  3. 03ContactSDR

    Every touch lands on one timeline

    Calls over VoIP, SMS, email and notes write to a single per-lead timeline. Calls are recorded and transcribed, and the feed streams live, so a team lead watches the work land instead of reading about it tomorrow.

    activity · Kaira Oystreaming
    1. Call · 4m 12srecorded · transcript ready14:02
    2. Email · deck sentopened twice14:09
    3. SMS · confirmationdelivered14:11
    4. Booked · Thu 10:00HubSpot · Outlook · Slack14:12

  4. 04BookSDR

    A booking, distributed to everywhere it needs to be

    One booking fans out to the client’s CRM (HubSpot or Pipedrive), the right calendar and the client’s Slack channel — as durable events, so a restart cannot lose the push.

    bookings · october47 booked · 38 held
    CompanySDROutcomeValue
    Nordkapp OyAnna M.held€100
    Virtanen GroupMikko S.held€100
    Saaristo TechLiisa K.no-show—
    Hämeen MetalliAnna M.held€100
    Koskinen & CoPekka N.pending€100

  5. 05OutcomeTeam lead

    Held, no-show, or reschedule — recorded, not remembered

    Three distinct outcomes, each a stored state. A no-show feeds the compensation matrix, the client’s portal and the rep’s performance rollup, instead of silently vanishing from a total.

    client portal · Nordkapp Oy

    47

    Booked

    38

    Held

    81%

    Show rate

    The client reads the same rows your team does — not a monthly export.

  6. 06CommissionFinance

    One booking, exactly one commission row

    Products carry a customer price and an SDR commission. A unique database constraint means a retried job cannot pay twice. Rows move through approve → pay, and cancellations resolve by policy, not negotiation.

    commission · approve → pay€3,800 pending
    SDRProductStateAmount
    Anna M.Meeting · stdpending€1,400
    Mikko S.Meeting · stdapproved€1,100
    Liisa K.Meeting · entpending€900
    Pekka N.Meeting · stdwithheld€400
    unique per bookingno double-pay

  7. 07InvoiceFinance

    The invoice comes from the same rows as the payout

    Billable bookings roll into a billing record and out to Procountor, with the price frozen at invoice time. The client invoice and the rep payout derive from the same booking — they cannot drift apart.

    INV-2041 · sent
    Nordkapp Oy€4,200.00
    Meeting · standard38 × €100€3,800
    Meeting · enterprise2 × €250€500
    Credit · no-show1 × −€100−€100

    Price frozen at invoice time — reproducible after a re-price.

04Every seat in the agency

Same rows. Five different workdays.

The SDR, the team lead, the account manager, the owner and your client all work from one set of records — each seeing the workflow that is theirs.

SDR’s question

“Who do I call next — and is anyone else already on them?”

  • 1Sees only the client projects they are rostered on
  • 2Opening a lead reserves it, so no colleague dials the same company
  • 3Calls, SMS, email and notes from one screen, with the script beside them
  • 4Books straight into the client’s calendar and CRM
lead · reserved to youexpires 6d

Nordkapp Oy

+358 40 123 4567 · Helsinki

manufacturingrecent hire52 staff
Call · 4m 12sanswered
SMS · follow-up sent
Note · asked for Q1

Team lead’s question

“Can we take on another client in November?”

  • 1Live activity feed per client list — watch the work land
  • 2Bookings-per-hour per rep per project, with manual overrides
  • 3Capacity against working days that subtract public holidays
  • 4Outcomes and no-shows surfaced while there is still time to act
capacity · next 6 weeks
W1
W2
W3
W4
W5
W6
W4 · holidays−3 working days

Account manager’s question

“Is my client getting what they are paying for?”

  • 1Owns the client project: lists, products, DNC and roster
  • 2Pulls new projects straight from the agency’s HubSpot pipeline
  • 3Invites the client’s team into their own portal
  • 4Scheduled reports that deliver themselves
roster · 4 client projects
NordkappAMMSLK3 SDRs
VirtanenAMPN2 SDRs
SaaristoLK1 SDR
HämeenMSPNAMLK4 SDRs

Agency owner’s question

“Will the invoices and the payouts agree this month?”

  • 1One commission row per completed booking, approve → pay
  • 2Cancellations resolved by a stored compensation matrix
  • 3Billing records out to Procountor with the price frozen
  • 4Permission templates for entrepreneur and employee SDRs
commission · approve → pay€3,800 pending
SDRProductStateAmount
Anna M.Meeting · stdpending€1,400
Mikko S.Meeting · stdapproved€1,100
Liisa K.Meeting · entpending€900
Pekka N.Meeting · stdwithheld€400
unique per bookingno double-pay

Your client’s question

“What did we actually get for our money?”

  • 1Logs into their own portal — the same rows your team sees
  • 2Every booking with its outcome: held, no-show or rescheduled
  • 3Billing with the price as it was invoiced
  • 4Can request a cancellation instead of emailing about it
client portal · Nordkapp Oy

47

Booked

38

Held

81%

Show rate

The client reads the same rows your team does — not a monthly export.

05A week on the floor

The moments that usually break a spreadsheet

Monday’s new lists to Friday’s month end. Drag through the week.

Mon08:30

Two new client lists land

Imported into each client’s own project. Numbers normalised, duplicates collapsed, the client’s DNC applied before anyone dials.

Lead management
Tue11:15

Liisa moves from Lumen to Vireo

Change the roster, not a spreadsheet. Her reservations release on schedule and Vireo’s leads open to her immediately.

Rosters
Wed10:05

A no-show at Nordkapp

Recorded as no-show with reschedule requested. The client sees it in their portal; the compensation matrix decides the credit.

Outcomes
Thu15:40

Can we sign a fourth client?

Capacity from bookings-per-hour per rep, against working days with public holidays subtracted — six weeks out.

Capacity
Fri16:00

Month end, in an hour

Commission approved and paid from one row per booking. Invoices out to Procountor from the same rows. Nothing to reconcile.

Commission & billing

06The mechanics

The parts of SDR operations nobody demos

Reservations, hygiene, outcomes, credits, holidays — the unglamorous mechanics that decide whether the month reconciles.

Reservation

Two reps never dial the same company

Opening a lead locks it to one SDR with an expiry. Stale holds release themselves.

List hygiene

Bad rows leave before anyone dials them

Commission

Cannot double-pay

A unique constraint on the booking: one row, ever.

Outcomes

Recorded, not remembered

Each outcome drives credit, payout and the client’s portal.

Capacity

A forecast that knows it is December

Working days subtract public holidays, not just weekends.

Client portal

Your client reads the same rows your team does

Not a monthly export. Bookings, outcomes and billing, live, in a portal your client logs into — with scheduled reports that deliver themselves.

Client reporting
Every module, end to end

07Integrations

It assumes you already have a stack

Dialbrew is the operations layer, not a replacement for your CRM, calendar, telephony or accounting. In an agency there is not one CRM — there is yours, and then one per client.

All integrations
HubSpotPipedriveGoogle CalendarOutlookProcountorSlackTwilioSalesforgeSharePointPostHogSentry

What it is built to achieve

Targets, stated as targets

The objectives the system was designed around — not customer results. We would rather show you the mechanism than quote a number we cannot evidence.

0

manual SDR reports

0

billing & commission errors, by construction

48h

to surface unproductive work

6 wk

capacity forecast horizon

Design objectives, not measured customer outcomes. No testimonials or case-study figures appear on this site until real ones exist.

Questions

Straight answers

If yours is not here, ask it in the demo — we would rather answer it than sell around it.

What exactly does Dialbrew replace?
The spreadsheet in the middle. Most SDR agencies run lists in CSVs, calls in a dialer, meetings in a calendar, the client’s deals in the client’s CRM, commission in a spreadsheet and invoicing in an accounting tool — then reconcile by hand. Dialbrew owns the lifecycle that connects them: lists, reservation, activity, booking outcomes, commission and the client invoice. It integrates the rest rather than replacing it.
Why is it built for agencies specifically?
Because an agency is not one sales team. It is several clients’ campaigns run by one shared floor of reps, and every client has its own lists, pricing, DNC, CRM and expectations. Dialbrew makes the client project the unit everything hangs off, so a rep can work three clients in a day without anything leaking between them — and each client gets their own portal.
Is this a sales engagement platform like Outreach or Salesloft?
No. Those tools optimise the touches — which message, which step, which cadence. Dialbrew runs the operation around them: who is rostered on which client, what capacity that represents, which bookings held, what each rep earned, and what each client gets invoiced. If you already run a sequencer, keep it.
Is it a phone system like Aircall or Dialpad?
No, and the distinction matters. Dialbrew has real calling — VoIP numbers per rep, inbound routing, recording, transcription, scripts — but it has no IVR, queues or org-wide telephony. A phone system gives you the call; it does not give you the commission on the meeting the call produced.
How does commission actually get calculated?
Each client has products, and each product carries both a customer price and an SDR commission. A completed booking generates exactly one commission row, enforced by a unique constraint on the booking — so a retried background job or a redelivered queue message cannot double-pay. Rows then move through approve and pay, and cancellations resolve via a stored compensation matrix.
Where is the data hosted?
AWS eu-central-1 (Frankfurt). Product analytics run on PostHog EU cloud with anonymous profiles disabled, and error monitoring is in the EU region. GDPR retention and right-to-be-forgotten procedures are documented alongside the implementation. We do not hold SOC 2 or ISO 27001 and will not imply otherwise.

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.

Book a demoSee how it works

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