How Receipts-Backed Billing Works

The Problem Receipts Solve

Appointment setting runs on claims. The vendor claims the prospect was qualified, claims the meeting was confirmed, claims the no-show was really a reschedule. In most of the category, those claims are backed by nothing a buyer can open and read, which is why invoice disputes in this industry turn into he-said-she-said and why buyer communities treat the whole category with suspicion.

The 2025 trust collapse at 11x showed where claims-without-evidence lead at scale. TechCrunch documented the a16z-backed AI SDR startup displaying logos of companies that were not customers; ZoomInfo, one of the companies shown, confirmed it had only run a short trial, said it had not authorized its logo, and threatened legal action. The story became the cautionary tale for the entire outbound industry: when your claims are the product, unverifiable claims are a liability with a fuse.

What a Receipt Actually Contains

For a billed meeting, the receipt has three parts:

• The conversation transcript. Every message exchanged with the prospect, verbatim. In our system that is the full SMS thread the Human + AI SDRs held, from first touch to booking. The transcript proves what the prospect was told and what they said back, which kills the two most common dispute types (wrong expectations, phantom interest) before they start.
• The qualification answers. The prospect's responses mapped against your signed criteria doc: fit, authority, situation. Not "they qualified," but the actual answers that passed the bars.
• The confirmation log. Timestamps for the initial booking agreement and the reconfirmation as the meeting approached. This is the record that separates a billable double-confirmed meeting from a calendar entry.

Together the three parts make every invoice line auditable: who this is, why they cleared your bar, when they agreed, and when they confirmed again.

Why Vendors Resist It, and Why We Built Around It

Evidence has a cost. Logging every conversation and mapping answers to criteria takes systems, and systems constrain shortcuts. A vendor reselling tired data or booking soft meetings cannot produce receipts, because the receipts would show the shortcut. That is precisely what makes the request diagnostic: asking for per-meeting evidence sorts the category faster than any pricing question.

We run the entire delivery system in-house, built from scratch on the VA Horizon Private CRM, which is the unglamorous reason we can hand over receipts at all: we control every layer that generates them. The billing loop is simple: a meeting bills only when its transcript, qualification answers, and double-confirmation log exist; the weekly statement lists each meeting with its evidence; disputes are settled by reading, not arguing.

What to Ask Any Vendor

Three requests, before signing: show me a redacted example receipt for a real billed meeting; show me where the evidence lives when I want to audit a charge; and put in writing that a meeting without complete evidence does not bill. A vendor with a real evidence system answers all three in minutes. A vendor without one will explain why trust should be enough. After 11x, it is not.

Sources

The external data in this guide draws on the sources below. Figures described in the text as estimates or industry triangulations are directional and are not attributed to a single dataset.

• TechCrunch, 11x has been claiming customers it does not have (2025-03-24)
• SalesHive, case studies (the anonymized-but-quantified evidence pattern)
• Belkins, case studies (named-logo-with-consent evidence pattern)

FAQ