Inspect what the payment unit rewards
A per-meeting model makes a count easy to invoice, but the definition matters: booked or held, relevant role or any contact, qualified or merely interested. A retainer can also reward activity without quality if responsibilities are vague. Do not assume one pricing form solves incentives automatically.
Require evidence criteria and a review mechanism. Compare replacement, rejection and dispute handling in the agreement without inventing a universal rule. Add your AEs' time and missing work to the cost comparison. A cheap appointment can be expensive if it consumes repeated unqualified discovery.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Invoice unit | Precisely defined meeting or scoped capacity | Understand what the provider is paid to produce |
| Quality standard | Fit, buyer context and accepted handoff evidence | Prevent counts from replacing commercial usefulness |
| Downstream responsibility | No-show, follow-up, rejection and learning owner | Include the work that happens after booking |
Work through the decision
Illustrative comparison: a pay-per-meeting provider charges for held calls meeting defined fit conditions, while a retainer provider includes research and ongoing coaching. Neither automatically owns closing. Compare the same target cohort and receiving-team work.
Ask both what happens when the buyer is relevant but has no active decision. The answer should preserve the conversation in its true state rather than inflate pipeline. Consider how rejected evidence changes the next cohort, not only whether the invoice offers a replacement.
Replacement meetings become the entire quality system
Replacing a weak call can settle a billing question while leaving targeting broken. Require rejection reasons and a learning loop. Repeated replacement without diagnosis can consume both buyer attention and AE capacity.
A concrete next step
Ask each provider to calculate the cost and handling of three hypothetical outcomes: accepted call, poor-fit call and relevant call with no active project. Compare definitions before prices.
Sources and research notes
- GitLab sales development handbookCompany operating handbook
- Bessemer: 10 laws of cloudInvestor operating guidance
Primary sources reviewed October 6, 2026. The operating recommendations and worked scenarios are Daavid’s analysis. Illustrative numbers are assumptions, not measured client results. Company marks identify sources and prior experience; they do not imply a customer relationship or endorsement.
Schematic