Cost per meeting is total outbound program spend, tools plus labor, divided by meetings booked in a given period, used to compare channels or vendors on a shared basis instead of comparing subscription prices alone.
Cost per meeting is a simple ratio: everything spent running an outbound program, divided by how many meetings it produced. The number is easy to state and easy to get wrong, because most teams only put tool subscriptions into the numerator and leave out the layer that usually costs the most.
A working outbound stack runs four cost layers: data and enrichment, sending infrastructure, deliverability and verification, and orchestration and labor, the person who designs the waterfall logic, decides what counts as a bad match, and rebuilds the system when a vendor changes an API. Every tool-vendor cost breakdown stops at the first three, because none of them sell the fourth. But in a real comparison across in-house, solo, and agency setups, the labor line is routinely the largest one in the budget, not the smallest: one breakdown found an in-house GTM engineer's salary dwarfing the monthly tool spend sitting next to it by more than ten times over.
That's why a stack that costs a few hundred dollars a month in subscriptions and quietly eats fifteen hours of someone's week isn't actually a cheap stack once cost per meeting includes the labor. The tool bill and the true cost are two different numbers, and only one of them predicts whether the program is actually worth running.
Write down the labor hours even when the person doing the work isn't billing separately for it. A stack that looks inexpensive on a subscription page can carry a real cost per meeting once someone's unpaid time gets valued at what that time is actually worth.
Teams compare cost per meeting across vendors or channels using only the subscription price, which is comparing a fraction of each program's real cost. The labor layer, orchestration, monitoring, and rebuilding the logic when something breaks, usually outweighs the tool spend by a wide margin, and leaving it out of the comparison favors whichever option happens to hide its labor cost best, not whichever option is actually cheaper.
Tell us how your motion runs today. We'll show you what we'd engineer.
Contact us