Pricing

Cost per meeting benchmarks by SaaS vertical

Real 2026 cost per booked meeting benchmarks across major B2B SaaS verticals. What is good, what is bad, and how to think about quality.

June 23, 2026 · 6 min read

Cost per booked meeting (CPM) is the cleanest leading indicator of an outbound motion. Here are 2026 benchmarks across major B2B SaaS verticals, with the quality adjustments that make the number honest.

The rule of thumb

Cost per booked meeting that converts to SQL should be under 1 percent of expected ACV. For a $50K ACV product, $500 per SQL is breakeven, $250 is healthy. This rule cuts through the noise of vanity metrics.

2026 benchmarks by vertical

These are observed ranges across managed outbound pods, normalized to fully loaded cost per booked meeting (not per SQL):

  • Vertical SaaS: $180 to $350
  • HR tech: $200 to $400
  • Dev tools / API-first: $250 to $500
  • AI infrastructure: $300 to $700
  • Cybersecurity: $400 to $900
  • Fintech (B2B): $350 to $750
  • Healthcare SaaS: $400 to $1,000 (gatekeeping is heavy)
  • Public sector / govtech: $500 to $1,500

Why some verticals run higher

Three factors push CPM up: heavy gatekeeping (cyber, healthcare, public sector), small ICPs (govtech), and high contact churn (fintech compliance roles). None of these are fixable with a better sequence; they require more sophisticated signals and longer plays.

Why your CPM is trending up

Common causes, in order of frequency:

  1. List saturation - same accounts hit too often, replies drop
  2. Deliverability decay - mailboxes burning out, sends landing in spam
  3. Sequence fatigue - copy that worked 6 weeks ago feels generic now
  4. Signal staleness - the triggers you wired in are no longer firing
  5. ICP drift - you started selling slightly different segments without updating motion

A GTM engineer should rotate signals and refresh sequences every 6 to 8 weeks to keep CPM flat or trending down.

The quality adjustment most teams skip

Always normalize CPM to meetings that convert to SQL. A vendor producing $90 meetings with a 25 percent SQL conversion is at $360 per SQL. A vendor producing $250 meetings with a 70 percent SQL conversion is at $357 per SQL. Same effective cost, very different motion quality.

Reps tend to prefer the second motion: fewer meetings, but the right meetings. They close better and they stay longer.

How to lower CPM honestly

  • Add signal layers (job changes, funding, intent) to cut wasted touches
  • Tighten ICP (better targeting reduces volume needed)
  • Improve deliverability (warmer mailboxes, fewer spam folder sends)
  • Refresh sequence content every 6 to 8 weeks
  • Use AI personalization sparingly (works on first touch only)

How to lower CPM dishonestly (and why not to)

You can drive CPM down by booking lower-quality meetings: looser qualification, "discovery meeting" with anyone who replies, incentive structures that reward booked over booked-and-qualified. The number on the report looks great. The pipeline does not move. Reps lose trust in the function within a quarter.

The CPM-to-CAC bridge

At healthy SQL conversion rates and reasonable win rates, outbound CAC payback should land in 8 to 14 months for B2B SaaS. If CPM looks fine but CAC payback is over 18 months, the issue is downstream (sales cycle, win rates) not in outbound. Do not blame the SDR layer for an AE-stage problem.

What to do this week

Pull your last 90 days of booked meetings. Calculate fully loaded cost per booked meeting. Apply your meeting-to-SQL conversion. Compare to the vertical benchmark above. If you are in the upper third of the range, your motion needs tuning. If you are at or above the top of the range, the motion needs rebuilding.

Want help running the math on your motion? Book a 20-min pipeline review.

FAQ

Frequently asked questions

Related

Keep reading.

Next step

Want this run for you instead?

90-day pilot, month-to-month after. No long contracts.