{"slug":"strategy/business-strategy/40-demo-script","title":"40 — Demo Script","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/business-strategy/40-demo-script.mdx","bytes":7144,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CANONICAL · Commercial OS\nOwner: Founder (sales)\nLast verified: 2026-07-21\nPerformance notes: [BRACKETS] = personalize from discovery. _(italics)_ = stage directions. Beats fixed per [39 Demo Guide §2](39-demo-guide.md).\n\n---\n\n## Purpose\n\nThe word-for-word 15-minute demo. Deliver it enough times that you can leave it — but the beats, the climax, and the refusal never move.\n\n---\n\n### Beat 1 — Their Morning, Named (0:00–2:00)\n\n> \"Before I show anything — [NAME], you told me something I wrote down word for word: _'[PAIN SENTENCE from discovery]'._ And the morning behind it: [CRM], then [SUPPORT TOOL], then [BILLING], then [CHAT] — [TOOL COUNT] tools to answer one question: _what's true about this account today?_ About [H] hours a day of that, per person.\n>\n> And the AI part — your team tried it. Now it writes emails. Not because the models are bad — because the AI forgot what they told it, stopped halfway, and made things up.\n>\n> For the next 12 minutes I'm going to show you the same morning with all of that gone. One rule for me: everything I show you is real product, live. If you ask about something we haven't built, I'll say 'not yet.'\"\n\n_(Screen share opens on the workbench — already loaded. No app tour, no settings, no slides.)_\n\n### Beat 2 — The Workbench Opens (2:00–5:00)\n\n> \"This is a Customer Success workbench. Not a dashboard — watch what it opens on. Three things, every morning:\n>\n> **What changed.** Overnight, across every connected tool: [scroll] — Meridian Corp's product usage dropped 42% over three weeks. Notice nothing's asking you to go check four systems — the checking already happened.\n>\n> **What needs you.** Meridian's renewal is in 45 days. And their champion — [contact] — hasn't replied in 19 days. Those two facts live in different tools in your world. Here they're the same story.\n>\n> **What's prepared.** Your 10 o'clock meeting brief — already drafted. We'll come back to who wrote it and how you'd trust it.\n>\n> [NAME], honest question — this morning view versus your [TOOL COUNT]-tab version: what's the first thing your team would do with it?\"\n\n_(Let them answer. This is the \"that's my morning\" moment — don't step on it.)_\n\n### Beat 3 — Evidence Under Everything (5:00–7:00)\n\n> \"Here's the part that makes this different from every AI tool your team demoted. Click the usage-drop signal — **evidence.** Which systems, which numbers, when: usage from [ANALYTICS], the support escalation from [SUPPORT TOOL], the renewal date from [CRM], and this line from an email thread — _'budget review next quarter.'_ Four tools, one story, every claim with a source.\n>\n> Click any fact — _(open provenance panel)_ — source system, timestamp, confidence. Your organization's truth, assembled, with receipts. We call where this lives the Spine — your operational truth, in your tenant, exportable any day you want. No AI wrote any of this. AI is not allowed to write truth here. That's architecture, not policy.\"\n\n_(P3/P4 in the room: 60 extra seconds on entity resolution + tenant isolation. Else move.)_\n\n### Beat 4 — Work With the Twin (7:00–11:00) — THE CLIMAX\n\n> \"Now the part your team stopped believing in. Every person here has a Twin — theirs, scoped to their role, working on the same bench. Not a chatbot in a sidebar. Watch the difference.\n>\n> **Ask:** _(type: 'What did we commit to Meridian in the March QBR?')_ — answer, with the commitment, who made it, where it's recorded. It didn't guess — it read your Spine. If it had nothing, it would say nothing. Silence is a feature.\n>\n> **Assign:** _(click: 'Draft renewal outreach reflecting the usage conversation')_ — the Twin's drafting from the actual account story: the usage dip, the March commitment, [CONTACT]'s last thread. Not a template with a name plugged in.\n>\n> And now the moment that changes AI from a toy to a colleague. The draft's ready. Does it send? **No.** _(pause)_ It's a proposal. Evidence attached, reasoning shown. [SKEPTIC NAME] — you're approving this. What would you check first?\"\n\n_(Take their answer seriously — click into whatever they name. Then:)_\n\n> \"You'd edit this line — _(edit it)_ — and **approve.** _(click)_ Now it executes — through your actual [EMAIL/CRM], the systems you already trust. And there's the receipt: proposed, evidence, approved by you, executed, result. _(3 seconds of silence — let the receipt land.)_\n>\n> **The Twin prepares. The human approves.** Every time. That's the whole philosophy in one click.\"\n\n### Beat 5 — The Refusal + The Trail (11:00–13:00)\n\n> \"Two more things nobody else will show you.\n>\n> First — what it _won't_ do. _(attempt an action without approval path / show a memory-write proposal)_ — the AI wants to remember 'Meridian is at risk of churn.' It cannot write that. It can only propose it. _(show the TruthLayer queue)_ You approve it, it becomes organizational memory. You reject it, it never existed. Every AI you've used auto-writes its memory — it guesses about your business. Here, your organization's memory contains only what a human verified. **Every AI remembers. Only IntegrateWise remembers the truth.**\n>\n> Second — the audit trail. _(scroll it, slowly)_ Every proposal, approval, execution. I know it's boring. **Boring is the point.** This is the tab your security team reads, and it's why they'll say yes.\"\n\n### Beat 6 — The Ask (13:00–15:00)\n\n> \"Remember the napkin from our first call: [H] hours × [N] people × $[C] — about $[MONTHLY VALUE] a month in reconstruction work. What you just watched removes most of it — and you saw _how_, not just that it does.\n>\n> Here's the step I'd propose. Thirty days, up to ten of your people, your real tools — [THEIR STACK]. We agree on three success criteria up front — I'd suggest: morning prep under 10 minutes, your next QBR prepped in under 30, and at least one catch like the Meridian signal on a real account of yours. Day 28, we look at the numbers together and you decide. If the criteria aren't met, you'll know exactly why, from me first.\n>\n> What would you want the third criterion to be?\"\n\n_(The close is a question that starts the POV scoping — [37 Play 4](37-sales-playbook.md) takes it from here.)_\n\n---\n\n## Variants\n\n- **8-minute exec version (P5 present):** Beats 1→2→4(compressed to Assign+Approve)→6, with the continuity line added: \"Month 12: institutional memory that leaves with people no longer matters.\"\n- **Technical deep-dive (P3/P4 follow-up, 30 min):** Beats 3+5 expanded — entity resolution, boundary contract, fail-closed demo, export walkthrough. Script: [21 Platform Story](../04-product-marketing/21-platform-story.md) + [42 Security FAQ](42-security-faq.md).\n\n**KPIs:** [39 Demo Guide](39-demo-guide.md) owns demo metrics. Script-fidelity spot checks on recordings — beats present, climax landed, refusal shown.\n\n---\n\n**Related:** [39 Demo Guide](39-demo-guide.md) · [19 Product Narrative](../04-product-marketing/19-product-narrative.md) · [38 Discovery](38-discovery-guide.md) · [37 Playbook](37-sales-playbook.md)\n"}