# Mid-Demo Disaster Scripts: Eight Failures, Word-for-Word Fixes

> Word-for-word recovery scripts for eight common mid-demo failures, from environment crashes to visible disengagement. Each scenario includes a named failure mode, a one-line diagnosis, and a ready-to-use script with bracketed fill-ins.

Free script/swipe for sales reps. Topic: [Demos & Product Storytelling](https://www.peerlab.ai/library/topic/demos-product-storytelling/). Published by PeerLab in the [Sales Enablement Resource Library](https://www.peerlab.ai/library/). Source: https://www.peerlab.ai/library/mid-demo-disaster-scripts-eight-failures-word-for-word-fixes/

## How to use it

Print or save this before every demo and keep it open in a second tab or on a physical card during the call. When something goes wrong, find the matching failure mode, read the script as written, and adapt only the bracketed sections. Review the debrief note afterwards to close the prevention gap.

## What's inside

- Eight named failure modes, each mapped to a specific mid-demo scenario
- One-line diagnosis for each failure so you can identify what has actually gone wrong under pressure
- Word-for-word recovery script for every scenario, with bracketed fill-ins for context-specific details
- Honest guidance on tone and timing within each script section
- Post-demo debrief note for each failure covering one concrete prevention action
- A quick-reference summary table mapping failure to script opening and prevention action
- "When NOT to use this" note for scenarios where recovery scripts are the wrong tool entirely

This resource picks up where preparation ends. You have already run the tech check, rehearsed the flow, confirmed attendees. Something has gone wrong anyway. The scripts below are for that moment: not principles, not frameworks, just the words.

Each entry follows the same structure: the failure mode, a one-line diagnosis, the recovery script (use it as written, adjust only the brackets), and a debrief note for preventing recurrence.

---

## When NOT to use these scripts

If the demo has gone so far off-course that the prospect has lost confidence in your company, not just the session, a recovery script is not enough. Acknowledge it, stop the demo, and book a reset meeting. Trying to push through with a clever line when trust is broken makes it worse.

---

## Failure 1: Demo Environment Crashes

**Diagnosis:** The sandbox, test instance or screen share has failed and cannot be recovered quickly.

**Recovery script:**

"I'm going to stop trying to fix this live, because that's not a good use of your time. What I'd like to do instead is walk you through [the three things we were about to cover] using the slides I have here, talk through what you'd actually see at each step, and then get you a recorded walkthrough before [end of day / tomorrow morning]. Does that work?"

*Tone note: Say this within 30 seconds of the failure. Silence while you frantically click is worse than any script.*

**Debrief note:** Every demo needs a pre-built slide deck covering the same journey as the live environment. Build it once, keep it current, bring it to every call.

---

## Failure 2: Wrong Stakeholder Turns Up

**Diagnosis:** The person in the room is more senior, more junior, or from a completely different function than you prepared for.

**Recovery script:**

"Before I dive in, I want to make sure this is genuinely useful for you. We had prepared this for [original audience, e.g. the operations team], but I'd rather adapt on the fly than waste your time on the wrong thing. Can I ask: what's your main involvement in this decision, and what would make today worthwhile from your perspective?"

*Tone note: Do not apologise for the mismatch. Reframe it as a choice to adapt rather than a failure to prepare.*

**Debrief note:** Confirm attendees by name and role 24 hours before every demo. If a name changes, ask why.

---

## Failure 3: Prospect Derails with Off-Topic Objections

**Diagnosis:** A prospect is raising objections about pricing, contract terms, or integration concerns mid-demo, pulling the session off its track.

**Recovery script:**

"That's an important question and I don't want to brush past it. Can I do this: let me note it down right now so it doesn't get lost, finish showing you [the section we're in], and then we address it properly at the end when you have the full picture? I find the answer lands better once you've seen [the relevant part of the product]. Is that fair?"

*Tone note: Write the question down visibly. It signals you are taking it seriously, not parking it to avoid it.*

**Debrief note:** Build a formal "questions parking" step into your demo structure. Name it at the start of every demo so it is not a surprise when you use it.

---

## Failure 4: Presenter Loses Their Place

**Diagnosis:** You have lost track of where you are in the demo, what you have covered, or what comes next.

**Recovery script:**

"Bear with me for one second. I want to make sure I'm taking you through this in the right order for your situation rather than just rattling through our standard sequence. We've covered [X and Y]. The two things I want to make sure we get to before we finish are [A and B]. Does that still match what you need from today?"

*Tone note: This reframes a navigation failure as a deliberate check-in. It also gives you a moment to reorient without the prospect noticing.*

**Debrief note:** Use a physical or on-screen demo run sheet with checkboxes. Tick sections as you complete them. Three seconds of glancing at it is invisible.

---

## Failure 5: Hostile Challenge from a Sceptic

**Diagnosis:** One attendee is openly dismissive, challenging your credibility, or making the room uncomfortable.

**Recovery script:**

"I appreciate you being direct, that's more useful to me than polite nodding. Can you tell me specifically what's not landing for you? I'd rather deal with it now than leave you with a concern I haven't addressed. If I can't answer it well, I'll say so."

*Tone note: Do not get defensive and do not enlist the rest of the room against them. A sceptic who feels heard often becomes an internal champion. One who feels attacked becomes a blocker.*

**Debrief note:** Before demos with multiple stakeholders, ask your champion who in the room is likely to push back hardest and on what. Prepare one specific answer for that objection.

---

## Failure 6: Key Feature is Broken in the Sandbox

**Diagnosis:** A specific feature you planned to demonstrate is not working, returning an error, or producing wrong output.

**Recovery script:**

"This isn't behaving as it should in our sandbox environment, and I'm not going to pretend otherwise. What I can do is show you [a screenshot / a recorded clip / the config in our production environment] so you can see exactly how it works when it's set up correctly. I'll also get our [technical team / solutions engineer] to confirm the behaviour in writing after this call. Does that work for you?"

*Tone note: Name the problem clearly. Trying to talk around a broken feature while it is visibly broken destroys credibility faster than admitting it.*

**Debrief note:** Run every feature you plan to demo in the actual sandbox the morning of the call, not the day before.

---

## Failure 7: Time is Cut Without Warning

**Diagnosis:** The prospect announces mid-demo that they have to leave in five minutes, cutting the session short.

**Recovery script:**

"Understood, I'll work with that. Given five minutes, the most valuable thing I can show you is [single most relevant section]. Let me go straight there. The rest I'll send you as a short recorded walkthrough so you can cover it in your own time. Sound good?"

*Tone note: Do not rush through everything. Pick one thing, do it well, and make the follow-up concrete. Rushing produces a bad impression of everything.*

**Debrief note:** At the start of every demo, confirm the time available and name your most important section explicitly. "If we only get through one thing today, it should be X" gives you permission to prioritise if time is cut.

---

## Failure 8: Prospect Visibly Disengages Mid-Flow

**Diagnosis:** The prospect has gone quiet, is looking at their phone, or is giving one-word responses. They are no longer with you.

**Recovery script:**

"Can I stop for a second? I get the sense this isn't quite hitting the mark for you, and I'd rather know now than keep going. What are you actually trying to solve at the moment? I might be showing you the wrong thing entirely."

*Tone note: This is a direct pattern interrupt. It takes confidence to use it. The alternative, pressing on through visible disengagement, wastes both parties' time and ends with a polite "we'll be in touch".*

**Debrief note:** Run a discovery quality check before your next demo. Disengagement mid-demo usually means the demo is not connected tightly enough to a problem the prospect genuinely owns.

---

## Quick Reference

| Failure | Script opening | One prevention action |
|---|---|---|
| Environment crashes | "I'm going to stop trying to fix this live..." | Build a parallel slide deck |
| Wrong stakeholder | "Before I dive in, I want to make sure this is useful for you..." | Confirm names and roles 24 hours before |
| Off-topic objections | "That's an important question, can I note it down..." | Name the parking step at the start |
| Lost your place | "Bear with me for one second..." | Use a physical run sheet with checkboxes |
| Hostile sceptic | "I appreciate you being direct..." | Ask your champion who will push back |
| Broken feature | "This isn't behaving as it should..." | Test every feature the morning of the call |
| Time cut short | "Understood, I'll work with that..." | Confirm time and name your priority section upfront |
| Visible disengagement | "Can I stop for a second?..." | Run a discovery quality check before every demo |