What do you do when a live demo fails?

Name it once and briefly, move to a recorded fallback of the same flow, and keep narrating as though nothing changed. Then send the working version the same day so the last impression is the product working.

What is the worst response to a broken demo?

Retrying in silence. Prospects forgive a fault and remember uncomfortable dead air. Also avoid "it never normally does that" -- unfalsifiable, and it reads as exactly what it is.

Is a recording a downgrade from a live demo?

Not usually. A screenshot deck reads as retreat and describing a feature in words reads as not having it, whereas a recording is the product moving at the right pace -- and for anything slow or fiddly live, it is often the better demo.

← Back to blog

When the Live Demo Breaks

August 25, 2026

Something will break eventually — a slow environment, an error on the one screen that matters, a connection that degrades mid-flow.

What decides how much it costs is not the fault. It is the next ninety seconds.

What to do

Name it once, briefly. "That is our demo environment being slow — one moment." Not an explanation of the architecture.
Move to the fallback. A recording of the same flow, already open. Keep narrating over it as though nothing changed.
Keep the meeting's shape. They came for a conversation about their problem; the screen was a prop for it.
Follow up with the working version the same day, so the last impression is the product working.

What not to do

Do not keep retrying in silence, do not blame the environment at length, and do not promise it "never normally does that" — which is unfalsifiable and reads as exactly what it is.

The most damaging response is minutes of dead air while someone refreshes. Prospects forgive a fault and remember an uncomfortable silence.

Why a recorded fallback beats improvising

The alternatives are a screenshot deck (which reads as retreat) or describing the feature in words (which reads as not having it). A recorded walkthrough is the product, moving, at the right pace.

It also means the fallback is not a downgrade. For a feature that is slow or fiddly live, the recording is often the better demo anyway.

Afterwards

Send the working thing that day, with one line and no apology paragraph. "Here is the reconciliation flow running properly — took nine seconds." Short, specific, and it replaces the memory.

A long apology draws attention to the failure. A working link quietly overwrites it.

Frequently asked questions

What do you do when a live demo fails?: Name it once and briefly, move to a recorded fallback of the same flow, and keep narrating as though nothing changed. Then send the working version the same day so the last impression is the product working.
What is the worst response to a broken demo?: Retrying in silence. Prospects forgive a fault and remember uncomfortable dead air. Also avoid "it never normally does that" -- unfalsifiable, and it reads as exactly what it is.
Is a recording a downgrade from a live demo?: Not usually. A screenshot deck reads as retreat and describing a feature in words reads as not having it, whereas a recording is the product moving at the right pace -- and for anything slow or fiddly live, it is often the better demo.

Keep reading

This is what Demorta does

Click through it — the same kind of demo you can record of your own product.

Try it on your own product

Record your first interactive demo free.

Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.

Start free →