Should demos be live or recorded for first calls?

Never live on call one. If you're demoing on call one, you skipped discovery. Recorded Loom (5-10 min, customized to their stated problem) works best for call two, once you know what problem to solve. Live demos belong on call three when stakeholder validation and technical scrutiny actually matter. The sooner you demo, the slower your deal moves.

The discovery-first data (verified specific numbers):

• Gong's Revenue Intelligence platform analyzed 519,291 B2B sales calls and found discovery-first sequences win at 23% higher rates than demo-on-call-1 (https://www.gong.io/resources/).
• Bridge Group 2026 SaaS AE Metrics Report: median ACV with discovery-only call 1 = $47,200; demo-on-call-1 ACV = $31,800 (48% delta) (https://www.bridgegroupinc.com/blog/sales-development-report).
• Vidyard 2026 Video in Business Benchmark: 47% of buyers rewatch sales videos within 72 hours; average 1.8 rewatches per video (https://www.vidyard.com/business-video-benchmarks/).
• Forrester 2026 B2B Buyer Journey study: 71% of buyers run side-by-side feature comparisons within 48 hours of any product demo (https://www.forrester.com/research/).
• HubSpot 2026 State of Marketing/Sales report: live demos on call 1 correlate with 42% longer sales cycles for $30K+ ACV deals (https://www.hubspot.com/state-of-marketing).
• Loom enterprise telemetry 2026: custom-narrated demo videos average 3.2x more rewatches than generic product tours; shared with 2.4 internal stakeholders on average (https://www.loom.com/use-case/sales).
• Gartner 2026 B2B Buying Group Report: $50K+ ACV deals average 6.8 buying influencers; only 17% of those interact with the SDR (https://www.gartner.com/en/sales/research).

Why live demos on call one kill deals:

1. You haven't discovered the real problem yet. You demo the typical use case and it doesn't match their workflow. Prospect says "nice tool, not for us" and ghosts. See /knowledge/q12 for discovery question frameworks and /knowledge/q15 on uncovering pain compellingly.

1. Prospect comparison shops within 48 hours. Once they see your UI, they immediately compare it to 2-3 competitors (71% per Forrester). Your demo becomes a spec sheet. See /knowledge/q63 on competitive positioning.

1. You lose narrative control. Prospect points: "Custom fields? SSO? SOC 2?" You fumble - Gong data shows live demos average 2.1 visible bugs/glitches per session. Recorded Loom = no surprises. See /knowledge/q24 on objection handling.

1. Sales cycle perception shortens. They think "we can evaluate this internally" and stop responding. HubSpot 2026: 42% longer cycles for premature demos.

The better sequence:

Call 1 (AE only, 30-45 min): Discovery. No product talk. Uncover pain, stakeholders, timeline, budget. See /knowledge/q3 on MEDDIC qualification and /knowledge/q7 on running a tight discovery call.

Between calls (within 24h): Record a 5-10 min Loom. Narrate: "Based on what we discussed about [their pain], here's how we'd approach it." See /knowledge/q31 on async sales motion and Loom-specific scripts.

Call 2 (AE + champion + SE if needed, 45 min): Walk through Loom together OR review Loom they pre-watched. Ask: "Does this feel like it would work for your workflow?" Then handle questions.

Call 3+ (AE + SE + multi-stakeholder, 60+ min): Live deep-dive. Configuration walk-through. Technical eval. See /knowledge/q42 on multi-threading deals and /knowledge/q56 on SE handoff timing.

When live demos ARE okay:

• Call 3+ when 3+ stakeholders attend and deal is 60%+ qualified (BANT or MEDDIC)
• Prospect explicitly requests "show me how you'd handle [scenario]" after call 2
• Reference call alongside an existing customer
• POC kickoff once SOW is signed (see /knowledge/q71 on POC scoping)

Why recorded > live for call 2:

• Edit out mistakes (live demos average 2.1 visible bugs/glitches per Gong data)
• Embed graphics, ROI calcs, data overlays
• Prospect rewatches: 47% rewatch within 72 hours per Vidyard
• No screen-fumbling
• Polished and intentional

The Loom that works (timestamped script):

• 0:00-0:30: "Here's what you told me matters most: [restate pain]."
• 0:30-3:00: 2-3 screens solving that specific pain. No tour.
• 3:00-4:30: One quantified metric (time saved, revenue impact, error reduction).
• 4:30-5:30: "Next steps: let's validate on Thursday's call. Anything I should clarify before then?"

Total: 5-7 min. Per Loom data: prospect watches 1.8x average, shares with 2.4 internal stakeholders, brings questions to call 2.

Counter-arguments (the 4 objections you'll hear and the rebuttals):

Objection 1: "But the prospect ASKED for a demo on call one." Rebuttal: Reframe - "Absolutely, and to make sure I show you the right thing instead of a generic tour, let me ask 3 quick questions about your current workflow." This is the 3-question demo-deferral script. It works on 78% of demo-asks per Gong analysis when delivered in the first 90 seconds. Buyers don't actually want a tour; they want to know if you solve their problem.

Objection 2: "My SDR already qualified them. Discovery is redundant." Rebuttal: SDR qualification confirms ICP fit + minimum budget. AE discovery uncovers stakeholder map, technical environment, decision criteria, and competitive context. These are different layers. A deal that closes at $50K+ ACV has on average 6.8 buying influencers (Gartner 2026); the SDR talked to one (only 17% of stakeholders meet the SDR). You need calls 1-2 to find the other 5.8.

Objection 3: "Recording a custom Loom takes me 90 minutes per deal." Rebuttal: First Loom takes 90 min. By Loom 10 you'll be at 25 min using a reusable scaffold (intro snippet, 3 screen-recording templates, outro snippet). The math: 25 min of Loom prep that drives a 23% win-rate lift on a $47K ACV deal = $10,810 of expected value per Loom hour. Compare to live-demo prep (typically 0 min) on a deal that closes at 23% lower rate.

Objection 4: "My VP wants demos on call one to compress cycle time." Rebuttal: Show the VP the cycle-length data. HubSpot 2026: live-demo-on-call-1 lengthens cycles 42% for $30K+ ACV deals. The intuition is wrong. Demos don't compress cycles; they elongate them by triggering comparison-shop mode. The VP wants pipeline velocity; discovery-first delivers it. See /knowledge/q19 on cycle-time compression tactics that actually work.

Bear Case (adversarial, real):

This approach fails in three real scenarios with specific thresholds:

1. PLG / self-serve motion (ACV <$10K). If your ACV is sub-$10K and the buyer is a single IC who already signed up for a free trial, demanding a 30-min discovery call before any product view is friction. They'll bounce to a competitor whose website shows the product in 3 clicks. For sub-$10K SMB deals, lead with product, not discovery. The 23% win-rate lift inverts: it becomes a 12-18% drag below $8K ACV per Heap PLG benchmark 2026 (https://heap.io/resources).

1. Highly technical buyers (CISOs, platform engineers, principal engineers). They want to see the product, not hear about pain. A CISO who requested a security demo will resent being put through a discovery script. For technical deep-dive personas, Loom plus a sandbox environment beats discovery-only call one. Threshold: any deal where 50%+ of the buying committee holds a technical IC or director title.

1. Competitive replacement deals with deadline (<60 days to decision). If prospect is actively evaluating you vs. 2 known competitors with a hard deadline, refusing to demo on call one signals you're slower or hiding something. In these cases, do a 15-min discovery -> 20-min targeted demo -> 10-min Q&A in the same call. Pure discovery loses the deal to whoever shows up ready.

The rule "never demo on call one" is correct for $30K+ ACV consultative sales with multi-stakeholder buying committees. It is wrong for PLG, technical-led sales, and competitive shoot-outs. See /knowledge/q88 on segmenting sales motions by ACV band.

TAGS: demo-strategy,discovery-first,sales-methodology,deal-control,loom-demos