Why a vendor's meetings-booked total is easy to inflate and how to audit it row by row
Meetings booked in deal origination: what the number actually counts.

A vendor sends a monthly report with one number circled: meetings booked, up again this month. It is the single easiest figure in an origination report to inflate, by accident or on purpose, because "a meeting got booked" can mean five different things depending on whether you count reschedules, cancellations, and repeat bookings by the same person. Meetings booked in deal origination only means something once you can trace the total back to individual rows and say what each one actually was. We rebuilt our own counting method after catching our own number wrong, and this is the waterfall we now use, published with the mistake left in rather than quietly fixed.
This is written for PE principals, M&A advisors, search fund principals, and corporate development leaders who receive a meetings-booked number from an origination vendor, in-house team, or SDR partner and want to know what to ask before trusting it. If you are deciding whether that number should even be the headline metric, deal origination vanity metrics covers the broader question of which numbers predict a closed deal and which only look good in a report. If you are building the questions list for a vendor conversation, this sits alongside nine questions to ask before you sign.
What does "meetings booked in deal origination" actually mean on a report?
It means a calendar event was booked and attributed to an origination effort, but that single sentence hides several decisions a vendor makes before the total ever reaches you: whether a reschedule counts twice, whether a cancelled booking still counts, and whether a repeat booking by the same person within a few weeks counts as a second meeting. Over a recent 90-day window across Danish Lead Co. / DealSource Systems' own operating platform, 1,564 raw booking rows came in across the calendars connected to the system. Only 1,018 of those rows passed a defined counting method. The other 546 were not deleted from the data. They were sorted into categories that explain why a raw row count and a defensible meetings-booked number are never the same thing.
Why do reschedules and cancellations inflate a meetings-booked count?
Because every reschedule and every cancelled-then-rebooked meeting creates a second row in the underlying booking data for the same actual conversation, and a vendor counting raw rows instead of counted meetings reports that second row as new volume. The table below is the actual reconciliation for the same 90-day window: what the 1,564 raw rows became once reschedules, repeats, cancellations and excluded event types were separated out.
| Category | Rows | Share of 1,564 |
|---|---|---|
| Counted meetings booked | 1,018 | 65.1% |
| Recent bookings, not yet processed | 21 | 1.3% |
| Repeat bookings and reschedules | 137 | 8.8% |
| Cancelled | 259 | 16.6% |
| Excluded event types (internal calls, onboarding, podcast recordings) | 129 | 8.2% |
A vendor who reports 1,564 instead of 1,018 is not lying with a fabricated number. They are reporting a raw row count and calling it meetings booked, which overstates the real total by more than 50%. Of the 259 cancelled rows, 209 were first bookings rather than reschedules of something already counted, and 82 of those were never rebooked at all, meaning the meeting that was "booked" never actually happened and never will.
The five-point audit for a meetings-booked number
- 1. Ask for the raw row count and the counted total, both. If a vendor can only produce one number, they are not tracking the difference between a raw booking event and a counted meeting, which is the gap the table above exists to close.
- 2. Ask what share is matched to a specific campaign. Of our own 1,018 counted meetings, only 82 are matched to one named campaign. The rest are real, counted meetings, but describing all 1,018 as "attributed to a campaign" would overstate what the data actually supports.
- 3. Ask how concentrated the total is by account. In our own 90-day window, one account accounted for 69% of the total. Dividing a reported meetings-booked figure by a client or campaign count to imply a per-client average is meaningless once one relationship can carry most of the book.
- 4. Ask for the positive-reply-to-meeting rate, not just the meeting count. Of 3,119 qualified positive replies in the same window, 525 converted to a booked meeting, a rate of 17%. That is a floor, since a meeting booked under a different address or on a calendar outside the tracked set would be missed, but it is the honest number, not a round figure picked to sound good.
- 5. Ask whether a show rate or no-show rate is attached, and how it is tracked. If the answer is a specific percentage with no description of how attendance is recorded, treat it as unverified. We cover why in the next section.
Should a meetings-booked number include a show rate?
Only if attendance is actually tracked, and for most origination programmes it is not, because a meeting is marked attended or missed only when the host does it manually in their own calendar tool, and in practice almost no host does. We know this because we got it wrong first. Every weekly data pull up to and including the run on 2026-09-21 counted every non-cancelled booking row, reschedules and repeat bookings included, and reported between 624 and 1,055 "meetings booked from outbound" depending on the week, alongside a 0.0% show rate. Both figures were wrong: the meeting count was inflated by uncounted repeats, and the 0.0% show rate was not a real finding, it was the artifact of attendance never being marked at all. We retracted both rather than keep publishing a number that looked precise and was not, which is the same discipline deal origination conversion rate argues for applying to every stage of a funnel, not just the parts that make a report look clean.
Why does account concentration matter more than the total?
Because a single large account can make an origination programme's aggregate numbers describe one relationship rather than the whole book, and a buyer evaluating a vendor on the total alone has no way to see that. At 69% concentration in one account, a reported "1,018 meetings booked across the platform" is substantially a story about one client's result, not a representative base rate a new client should expect. This is the same blind spot covered in LP due diligence on deal sourcing, where a vendor's aggregate pitch deck numbers deserve the same row-level question an LP would ask a fund about a single outsized deal driving its whole return.
How should I use a meetings-booked number when evaluating a vendor?
Use it as a starting question, not a verdict, and ask for the breakdown behind it before comparing it to any other vendor's total. A number with a visible waterfall, a disclosed concentration, and an honest floor on attribution is more trustworthy at 1,018 than an unverifiable raw count at 1,564, even though the smaller number looks worse on a slide. The same standard applies to our own published results, including a healthcare investment bank client who held 14 owner conversations in the first three weeks and 133 within 90 days, a figure that holds up under the same row-by-row scrutiny this article describes because it comes from a named, countable engagement rather than a blended platform total. See how the origination engine works or the solutions built for private equity firms evaluating a partner on these terms.
If you would rather have this run for you, DealSource Systems does off-market deal sourcing for lower middle market private equity: owners reached directly before they run a process, for a flat $4,000 a month.
Key Terms Glossary
Frequently asked questions
What counts as meetings booked in deal origination?
A counted meeting is a calendar booking that is a first-time booking by that person or company within a defined window, was not later cancelled, and is not an excluded internal event type such as an onboarding call. A reschedule of an already-counted meeting does not create a second count.
Why do reschedules inflate a meetings-booked total?
Because a reschedule generates a new row in the underlying booking data for the same conversation, and a vendor counting raw rows instead of applying a counting method reports that second row as new volume on top of the original.
Should a vendor's meetings-booked number equal its positive replies?
No. In our own data, 3,119 qualified positive replies produced 525 booked meetings, a 17% conversion rate, and that is a floor rather than a ceiling since some bookings happen on calendars or under addresses the tracking cannot see.
Is a 17% positive-reply-to-meeting rate good or bad?
It is a baseline from one platform's aggregate data across a 90-day window, not a universal benchmark, and the right comparison is the same rate measured consistently over time for the same programme rather than against another firm's unverified figure.
Why is account concentration a red flag in a vendor's reported results?
Because a high concentration, such as one account making up 69% of a total, means the aggregate figure mostly describes one relationship's outcome rather than a representative result a new client should expect to see.
Can a deal origination vendor report a show rate or no-show rate?
Only if attendance is actually tracked in a system of record, which requires a host to mark every meeting attended or missed. Most calendar-booking workflows never do this, so an unexplained show-rate figure should be treated as unverified rather than taken at face value.
What should I ask a deal origination vendor before trusting their meetings-booked number?
Ask for the raw row count alongside the counted total, the share matched to a specific campaign, the account concentration, the positive-reply-to-meeting conversion rate, and how attendance is tracked if a show rate is quoted. A vendor who can answer all five with real numbers is describing a measured programme rather than a marketing total.