Script a live product demo with technical fallbacks

Creates a structured live demonstration script with explicit time markers, narration, and glitch contingencies. Ideal for engineers presenting live software to technical audiences.

Prompt

Prompt
Act as a senior technical evangelist. You will write a tight, minute-by-minute live product demo script equipped with contingency plans for live technical failures.

First, ask me these 3 numbered questions and wait for my response:
1. What is the software tool, who is the audience, and what single core workflow will be shown?
2. What is the total allotted demo time in minutes?
3. What are the two most likely failure points during the live run (such as API latency, authentication drops, or test data errors)?

After I reply, build the demo script following these rules:
- Break the flow into 4-6 distinct narrative beats with concrete on-screen actions paired to spoken narration.
- Keep spoken lines direct and free of corporate filler words.
- Provide an explicit "Glitch Contingency" for every beat detailing what to say and show if the feature stalls.

Output format:
Present a Markdown table with columns: [Timestamp, Visual Action on Screen, Spoken Script, Fallback Action if Broken]. Conclude with a checklist of 3 items to verify locally 15 minutes before showtime.

Example output

Example for: a 5-minute CLI deploy tool demo for DevOps engineers

TimestampVisual Action on ScreenSpoken ScriptFallback Action if Broken
00:00 - 01:00Terminal open. Run deployctl init to scaffold staging cluster."Most deployment tools hide state. Watch deployctl build reproducible manifests locally in two seconds."If terminal hangs, switch to pre-recorded terminal capture tab in browser and narrate from it without stopping.
01:01 - 02:30Edit env.yaml to change replicas from 1 to 5, execute deployctl push --sync."We trigger a canary push. Notice how routing updates instantly without waiting for DNS propagation."If network times out, display slide with the architecture diagram and show local dry-run output via --dry-run flag.
02:31 - 04:00Split screen: terminal showing green logs on left, live Grafana dashboard metrics on right."Our traffic shifts across five pods with zero dropped connections during active rollout."If Grafana fails to render, show cached screenshot of the target latency curve from staging.
04:01 - 05:00Run deployctl rollback to demonstrate instantaneous recovery."A bad migration takes one command to reverse cleanly. That is the whole workflow."If CLI crashes, demonstrate the rollback git commit history in GitHub UI.
15 Minutes Before Showtime Checklist
  1. Confirm local mock environment runs without external internet connection.
  2. Keep recorded video backup file open in full-screen on a secondary desktop workspace.
  3. Verify terminal font size is set to at least 18pt for rear-row readability.
Written by AI from this prompt. Your results will vary.

Answer the three setup questions directly in Claude, ChatGPT, or Gemini. To prepare for offline conferences, follow up by asking the model to rewrite the fallback column for scenarios where local Wi-Fi drops completely.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Presentations & Public Speaking