How to Reduce Cost per Demo with an iMessage Layer
TL;DR
Cost per held demo is ad spend divided by held demos, and the biggest divisor sitting between those two numbers is the share of paid leads that ever reply to your follow-up. That share is a channel property before it is a copy property: email and cold calls leak most of the leads you already bought. Adding an iMessage layer attacks the reply stage directly, and because everything downstream multiplies off it, a reply-rate lift moves cost per demo more than any realistic improvement in cost per lead.
On this page
What is the actual math from ad spend to held demo?
Ad spend buys leads. Share reply to follow-up and become conversations. Share of conversations book demos. Share of booked demos hold. Cost per held demo = spend ÷ (leads × reply % × booking % × hold %).
The stages multiply: 3x improvement at any gate cuts final cost 3x. The cheapest gate to move is the weakest one.
For B2B paid acquisition, the worst gate is reply. Marketing scrutinizes cost per lead, sales scrutinizes booking and show rates. Nobody measures reply. Teams tolerate 90% non-reply because it goes unmeasured.
Where do replies actually leak?
Reply leaks at the channel level. Email lands in triage and gets deferred. Calls from unknown numbers go unanswered. Neither reflects lead interest. Both are channel properties, not lead properties.
SMS gets seen but requires A2P 10DLC registration (weeks of paperwork). Unknown 10-digit numbers get filtered as broadcast noise. Green bubbles read as spam regardless of content.
iMessage lands as blue-bubble threads from people, read within minutes at 98% open rate. It runs 2-3x reply rate of cold email. This reply stage is where your funnel loses most paid leads. Channel is the variable.
Worked example: cost per held demo before the iMessage layer
Every input below is an assumption, chosen to be round and believable rather than measured from any specific account. Run the same arithmetic on your own numbers before believing any of it.
$6,000 spend at $60 cost per lead yields 100 leads. Stack: 4-email + 2-call producing 6% reply (6 conversations). Half book (3 demos). Two-thirds hold (2 held).
Cost per held demo: $6,000 / 2 = $3,000. The 94 non-replies weren't bad leads. They're lost because not replying is the default on email and phone.
| Stage (all inputs assumed) | Rate | Count |
|---|---|---|
| Ad spend | $60 cost per lead (assumption) | $6,000 |
| Leads | 100 | |
| Replies / live conversations | 6% (assumption) | 6 |
| Demos booked | 50% of conversations (assumption) | 3 |
| Demos held | 67% of booked (assumption) | 2 |
| Cost per held demo | $6,000 / 2 | $3,000 |
Worked example: the same funnel with an iMessage layer
Change one gate and one cost line, hold everything else fixed. Leads, ad spend, booking rate and hold rate all stay identical. The iMessage layer only moves replies.
Lead with iMessage sequence, demote email to long-form. Reply rises 6% to 18% (3x, conservatively). At 18%: 100 leads yield 18 conversations, 50% booking gives 9 demos, 67% hold gives 6 held. Reminders reduce no-shows.
| Stage (all inputs assumed) | Before | With iMessage layer |
|---|---|---|
| Ad spend | $6,000 | $6,000 |
| Channel cost | $0 (existing email/phone stack) | $249 (one line, flat) |
| Leads | 100 | 100 |
| Reply rate (assumption) | 6% | 18% (assumed 3x lift) |
| Conversations | 6 | 18 |
| Demos booked at 50% (assumption) | 3 | 9 |
| Demos held at 67% (assumption) | 2 | 6 |
| Cost per held demo | $3,000 | $1,041.50 |
How to run this on your own numbers
Pull four numbers from last quarter: ad spend, leads generated, reply-or-connect, demos held. If your CRM can't produce reply number cleanly, that's finding one: unmeasured gates rarely perform well.
Stress-test: cut lift to 2x and land near $1,500/demo. Stable because cost is flat, not a spend %. Use iMessage ROI calculator and iMessage sequences.
Two traps. Don't spend the lift on volume: blasting it burns the asset. Apply mechanics to last year's non-responses via list reactivation. Reactivating sunk costs beats new spend.
Where Blue Reacher fits
Blue Reacher supplies dedicated iMessage lines with done-for-you setup, unlimited messages (50 opted-in / 30 cold new contacts/day), flat pricing, RCS/SMS fallback, no A2P registration. Native GoHighLevel, REST API/webhooks for others.
The wider case for running sales conversations on this channel lives at iMessage for sales. If SMS remains part of your stack, our A2P 10DLC guide covers the registration path.
Frequently asked questions
What is a good cost per held demo for B2B paid acquisition?
No universal benchmark exists because cost per demo varies by cost per lead and three conversion gates. Measure yourself: ad spend ÷ held demos for last quarter. Identify which gate (reply, booking, hold) is furthest below its ceiling. Usually it's reply.
Why focus on reply rate instead of cost per lead?
$59.99-$99.99/month for sender plus $0 sandbox and $20/mo shared. Add-ons: phone +$15/mo, SMS/RCS +$15/mo, init conversations +$30/mo. Fully loaded: $119.99-$159.99/month. Availability checking separate.
Are the numbers in the worked example real customer results?
$199/month or $1,949/year (~$162.50/mo, 35% off). Includes unlimited iMessages, custom area code, RCS/SMS fallback. $449 activation waived on annual. FaceTime add-on $99/mo. 50 opted-in / 30 cold new contacts/day pacing. $2.51/month above fully loaded LoopMessage, no daily cap.
Does an iMessage layer help with demo no-shows too?
Audience model differs. LoopMessage sells API to developers, pricing by daily volume with hard caps (300 or 1,000), restricts conversations. Blue Reacher sells managed channel to B2B sales teams, pricing by line with unlimited iMessages (50 opted-in / 30 cold new contacts/day, never metered), no caps, builds workflows/sequences/scripts.
How fast can an iMessage layer be live compared to registered SMS?
Days vs weeks. Business SMS requires A2P 10DLC registration before the first send (3-6 weeks). Blue Reacher requires no A2P registration and setup is handled for you, so the layer fires within days. RCS then SMS fallback covers non-iMessage contacts.
Keep reading
More on outbound strategy
ChatGPT Can Send iMessages Now. It Still Cannot Run Outbound.
OpenAI's Apple Messages plugin can read your message history and send a text as you, on one Mac, with an approval tap per message. Sales teams are asking whether that replaces an outreach platform. The answer sits in OpenAI's own documentation and usage policies rather than in anybody's opinion.
Never Put a Link in Your First Text
Your first text to someone who has never messaged you back is not the same object as every message after it. On iPhone the link inside it will not open. On carrier SMS the same link is one of the strongest reasons a message gets filtered before it lands. Both problems disappear the moment the person replies, which makes the reply the only thing the opener should be built to win.
Demo Show Rate Benchmarks 2026: What the Data Actually Says
No independent cross-industry benchmark for B2B demo show rates exists, and anyone quoting one precisely is quoting a vendor. Here is what can honestly be said, the math per point of show rate, and the levers that move it.
Put this on your pipeline
Blue Reacher runs outbound iMessage for B2B sales teams, from your CRM, with setup handled for you.
Book a demo