Lesson 8 of 10 · ⭐ Gap priority

Live Demo & Technical Storytelling

A prospect escalates live on a screen-share, or the golden path breaks two minutes in. What you say next matters more than what you'd planned to say.

Structuring a walkthrough

Three beats cover almost every good technical demo, in this order.

What: state the problem this solves in one sentence. Why: say why it matters to this specific audience, not audiences in general. Show: take the shortest path to proving it works, cutting anything that doesn't serve those first two beats.

When the demo breaks live

Something will eventually fail mid-walkthrough. These three habits are what separate a recoverable moment from a lost room.

Have a recorded fallback

Record a backup video of the golden path before you present live — never let the first time something runs live be in front of the customer.

Narrate while you debug

If something breaks, describe what you're checking out loud instead of going silent. Silence reads as "lost"; narration reads as "still in control."

Know your escape hatch

Have a pre-built example or staging account ready to jump to if the primary path is broken.

Handling unscripted Q&A

You will get a question you don't have the answer to. The response matters more than the answer.

Acknowledge the question directly, answer the part you actually know, and commit to a specific follow-up for the rest — a named time, not "I'll look into it." A confident guess that turns out wrong costs more credibility than an honest "let me confirm and get back to you by end of day."

Exercises

Read the annotated demo script below, then work through both exercises.

[Open] "Today I'll show how a webhook retry actually recovers from
a dropped delivery — this is the exact flow your team hit last week."

[Show] Trigger a test event, point at the dashboard, and call out the
retry count and backoff interval as they update live.

[If it breaks] "Interesting — let's look at why," then open the logs
panel on screen instead of going quiet. Narrate what you're checking.

[Unscripted question] "Good question — I don't have the exact number
on retry limits for the Enterprise tier. Let me confirm and send that
to you by end of day."

[Close] Restate the one thing you want them to remember, in one sentence.

Concept check

Answer in your head first, then click a question to reveal the answer.

Scenario checklist

Work through the sample demo script and check each item off. Progress is saved in your browser.

Write a one-sentence statement of the problem this demo solvesIdentify the shortest path to showing it working, cutting anything non-essentialPrepare a fallback (recording or backup environment) before presenting liveDecide what you will say out loud if the demo breaks mid-walkthroughDraft a response for a question you might not know the answer to

Go deeper

These primers are a starting point. Read the primary sources to build real fluency.

Emily McManus: How to give a good basic tech demoA short, concrete guide from a TED editor who has coached hundreds of technical talks TEDx Speaker Guide (official)Structure, scripting, and delivery guidance — built for technical and non-technical speakers alike Storylane: An ultimate guide to giving a great product demoA broader walkthrough of demo structure, pacing, and audience framing

Training Notes

What building this project taught me.

This is a flagged gap-priority module

Live demo delivery was one of the self-identified gaps from Tom's job-hunting skills scan — it's a soft skill, but a specifically technical one: the thing that breaks live is usually the thing you understand best, which is exactly what makes narrating through it credible.

This lesson has no code to run

Unlike the other TSE Onboarding lessons, there's no request/response or CLI output to reproduce here. The "exercises" below are about drafting language, not verifying a technical result.