39 — Demo Guide
Status: CANONICAL · Commercial OS
Owner: Founder (sales)
Last verified: 2026-07-21
Purpose
The principles and preparation system behind every demo. The word-for-word performance lives in 40 Demo Script; this guide is why the demo is built that way, how to prepare it, and how to adapt it without breaking it.
Target audience: Anyone demoing — founder, AE #1, SE-of-the-future.
1. Demo Philosophy
The demo is the Day, performed. We don't tour features; we re-enact the prospect's own morning with the pain removed (19 Product Narrative). The prospect should recognize themselves in the first 90 seconds and see their tools by name throughout.
Three laws:
- Outcome before mechanism. Show the assembled morning before explaining the Spine. Wonder first, architecture second.
- The approval is the climax, not the caveat. Every demo builds to: Twin proposes → human approves → real execution → audit trail. That beat is the differentiation (27 Governance Story).
- Show the refusal. Once per demo, show what the system will not do (unapproved write failing closed, the Twin staying silent without evidence). Nobody else dares demo their product refusing — it's our most credible 10 seconds.
2. The Fixed Beat Structure (15 minutes — 40 implements)
| Beat | Min | Job |
|---|---|---|
| 1. Their morning, named | 0–2 | Recognition: their tools, their H hours, their wound story from discovery |
| 2. The workbench opens | 2–5 | The three beats live: what changed / what needs you / what's prepared |
| 3. Evidence under everything | 5–7 | Provenance panel; the signal's evidence chain |
| 4. Work with the Twin | 7–11 | Ask → Assign → Approve on one real item; the climax |
| 5. The refusal + the trail | 11–13 | Fail-closed moment + audit view + TruthLayer gate |
| 6. The ask | 13–15 | ROI napkin recalled; POV proposed with criteria |
Adaptation rules: beats never reorder; beat 3 deepens for P3/P4 audiences, compresses for P1; beat 6 becomes an exec-readout close when P5 is present. Cutting a beat = not doing the demo; reschedule instead.
3. Preparation System
Personalization map (from discovery, 15 min prep): their tool names → connector set shown · their wound story → the demo's signal scenario (usage-drop/renewal pattern mirroring it) · their H/C/N → beat 6 napkin · their skeptic → assigned a direct question in beat 4 ("[Name], you approve this — what would you check first?").
Demo environment: the standing demo tenant (Meridian Corp + realistic account set) with connectors matching their stack where possible; rehearsed data states (the signal must fire; the evidence must resolve; the refusal must refuse). Never demo on hope — verify the environment 30 minutes before, every time (checklist below).
Pre-demo checklist: □ tenant loads < 5s □ signal scenario fires □ provenance panel resolves □ approval → execution → audit path works □ refusal beat works □ tool names updated □ screen clean (notifications off, tabs closed — we sell the end of tab chaos; do not demo from tab chaos).
4. Delivery Discipline
- Talk ratio: ≤ 60% us. Questions land at beats 2, 4, 5 ("what would your team do with this signal?").
- Silence discipline: after the approval executes — stop talking for 3 seconds. Let the receipt land.
- Honest edges: if asked about something unbuilt: "Not yet — here's what's real today, here's the roadmap posture" (69). One overclaim costs the category's whole trust story.
- Failure protocol: if the environment breaks, name it, switch to the recorded backup (kept current — see §5), and offer a live re-run. Composure is a governance demo.
5. Demo Assets Register
| Asset | Owner | Freshness |
|---|---|---|
| Standing demo tenant + scenario states | Founder | Verified weekly + pre-demo |
| Backup recording (current release, 12 min) | Founder | Re-record each T1/T2 launch (20 §3) |
| Persona depth modules (P3 provenance deep-dive; P4 governance deep-dive) | Founder | Quarterly |
| Post-demo recap template | Sales | Standing (37 Play 3) |
KPIs: demo → POV conversion ≥ 40%; checklist compliance 100%; "that's my morning" moment occurrence (call recordings); refusal-beat shown rate 100% (74).
Related: 40 Demo Script · 19 Product Narrative · 38 Discovery · 37 Playbook