Founders ask us what outbound costs, and the honest answer is that the sticker price is the least interesting part. The number that matters is cost per meeting, and it is not fixed. It starts high while the system is being built and warmed, then falls as domains age, data improves, and messaging gets dialed in. If you only look at month one, you will draw the wrong conclusion. Here is the full cost stack, how cost per meeting moves over a pilot, and why owning the system beats renting meetings one at a time.
The real cost stack
Most outbound budgets get quoted as a single agency fee, which hides the moving parts. A real outbound system has several line items, and understanding them is how you judge whether a quote is reasonable or padded.
- Sending domains: dedicated domains separate from your primary, so a deliverability problem never touches your corporate mail.
- Mailboxes: multiple inboxes per domain, warmed before they send a single cold message.
- Data and enrichment: the cost of building accurate, targeted lists, which is where Clay does the heavy lifting.
- Tooling: the sending platform plus the automation layer that ties it together, in our case self-hosted n8n.
- The fee: the human work of strategy, copy, list building, and running the system day to day.
A LongRun pilot runs roughly 2,000 to 2,500 dollars a month and bundles most of this together. The point is not the exact figure, it is that you can see what you are paying for instead of a black box.
Why cost per meeting falls over time
In month one, your spend buys infrastructure that has not produced anything yet. Domains are warming, the first list is being tested, and the messaging is a hypothesis. Cost per meeting in that window looks ugly because the denominator is small.
By month two and three, the system compounds. Warmed domains hit the inbox reliably, the data gets sharper as you learn which segments respond, and the copy is rewritten around the replies you actually received. The same monthly spend now produces more meetings, so cost per meeting drops, often sharply. This is why judging outbound on its first thirty days is a mistake. You are looking at the build cost, not the run-rate economics.
Owning the system versus paying per meeting
Pay-per-meeting vendors quote a clean number, say a few hundred dollars a meeting, and it sounds simple. The catch is that you never own anything. The domains, the data, the playbook, and the relationships all belong to the vendor. The day you stop paying, the pipeline stops, and you have nothing to bring in-house.
An owned system inverts that. Your cost per meeting starts higher but trends down as the asset matures, and at the end you hold the domains, the mailboxes, the Clay tables, and the workflows. You can keep running it, hire someone to run it, or hand it to your existing team. We dig into that tradeoff in detail in our comparison of an owned system versus paying per meeting. The short version: per-meeting pricing is a rental, and you are paying a premium to never build equity.
How to actually calculate it
Take your total monthly outbound spend, every line item above included, and divide by meetings that actually happened, not meetings booked. Then track it month over month so you see the trend, not a single snapshot. Tie meetings and resulting pipeline back to your CRM so you can extend the math all the way to closed revenue.
The honest version of this calculation is the foundation of any outbound decision. If you want help modeling it against your deal size and sales cycle, our breakdown of outbound ROI shows how cost per meeting rolls up into return on the whole program.
Questions, answered.
What is a reasonable cost per meeting for B2B outbound?
Is paying per meeting ever the right choice?
Why is the first month so much more expensive per meeting?
Want this built and run for you?
LongRun builds the outbound system, runs it, and hands it over at day 90. Book a strategy call to scope yours.