Demo Operations Guide

Use this guide to select the right script, prepare the environment, and recover quickly if anything goes wrong live.

Demo Script Selection Matrix

Audience	Duration	Script	Synthetic docs to load	Key scenario
C-suite (COO, CFO, CTO)	15 min	exec-overview-15min.md	acme-corp, pre-extracted	scenario-01
Loan operations team	45 min	ops-team-deep-dive-45min.md	acme-corp, betabank, gamma	scenario-01 + scenario-02
Credit analysts	30 min	credit-analyst-demo-30min.md	acme-corp, gamma	scenario-03 + scenario-04
IT / Security team	30 min	it-security-briefing-30min.md	Any (architecture focus)	n/a
Pilot kickoff	60 min	pilot-kickoff-demo-60min.md	All five docs	All four scenarios

Pre-Demo Checklist

1. Verify demo environment is running and accessible.
2. Load the correct synthetic documents for the chosen script.
3. Verify pre-extracted results are visible in the UI.
4. Reset covenant alerts to default state.
5. Clear any previous demo Q&A history.
6. Test screen share and audio.
7. Have backup screenshots from demo-environment/screenshots/ ready.

Reset Procedure

Use demo-environment/reset-instructions.md between every run to ensure consistent outcomes.

Common Pitfalls and Recovery Tactics

Network or session instability

• Signal: upload stalls, page fails to load, or live widgets lag.
• Recovery:
  1. Narrate what should happen next in one sentence.
  2. Switch immediately to prepared screenshots in demo-environment/screenshots/.
  3. Continue the story using the same flow and expected outputs.

Slow extraction response

• Signal: processing exceeds the expected demo pace.
• Recovery:
  1. Keep the audience engaged by explaining the extraction output schema and confidence workflow.
  2. Move to pre-extracted results already loaded in the environment.
  3. Return to the live processing screen later only if timing allows.

Audience attention drop

• Signal: fewer questions, cameras off, or discussion shifts to unrelated topics.
• Recovery:
  1. Ask a direct role-specific question (for example: "Where does manual re-keying hurt most today?").
  2. Jump to the next value moment instead of continuing feature-by-feature.
  3. Close with one concrete pilot next step and owner.