Skip to content

Dialbrew for sales-as-a-service providers

Sell meetings as a product: per-client pricing and SDR commission, outcomes that drive both, Procountor invoicing and a client portal that shows the work.

Updated 9 October 2026ForProviders selling meetings or pipeline as a productised service
products · Kestrel Ltd3 active · 1 archived
ProductClient priceSDR comm.Margin
Qualified meetingdefault€240€70€170
Meeting · enterprise€420€120€300
Demo held€300€90€210
Meeting · 2025 ratearchived€200€60€140
price frozen onto each billing record→ Procountor
Illustrative example — sample data, not a customer screenshot.

What this gets you

Meetings priced as products, per client, with a customer price and a rep commission

Invoices generated from the billable set rather than assembled by hand

A frozen price on each billing record so sent invoices stay reproducible

Credits for no-shows and cancellations applied by a stored policy

Clients able to verify what they are paying for, themselves

Selling meetings needs a precise unit

A sales-as-a-service business sells a unit, usually a qualified meeting, at a price. The unit has to be defined well enough to bill for and to dispute. What if the prospect does not turn up? What if they reschedule twice and then attend? Each of these is a billing question.

Products define the unit

Each client has products. Each product carries a customer price and an SDR commission, and one is the default. Products are archived, never deleted, so an old booking always resolves to the product that priced it.

A completed booking creates exactly one commission row (a unique database constraint) and joins the billable set for the client’s invoice. Both come from the same booking, so the margin is derived, not calculated twice.

Cancellations are decided by a stored policy

Held, no-show and no-show-with-reschedule are separate outcomes. When a cancellation is approved, a compensation matrix decides the client credit and what happens to the SDR’s commission. The same case resolves the same way every month, and the client sees the credit in their portal without asking.

From held meeting to paid invoice

  1. 1

    Meeting held

    The outcome is recorded on the booking.

  2. 2

    Billing record

    Billable bookings roll into a record, with the price frozen on it.

  3. 3

    Sent to Procountor

    Dialbrew creates the invoice and polls it for status.

  4. 4

    Sent or paid

    Only these states count as invoiced, for the portal and the compensation logic alike.

Because the price is frozen on the record, changing a product price next quarter does not change last quarter’s invoices.

The client can check the work

The portal shows their meetings with outcomes, scheduled reports, and billing, including which meetings sit on which invoice at which price. Calls can be recorded and transcribed, so a dispute about what was said has a record.

What Dialbrew does not do

It does not source leads, send email or act as your clients’ CRM. It pushes bookings into theirs.

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