{"slug":"strategy/product-strategy/19-product-narrative","title":"19 — Product Narrative","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/product-strategy/19-product-narrative.mdx","bytes":5592,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CANONICAL · Commercial OS\nOwner: Product Marketing\nLast verified: 2026-07-21\n\n---\n\n## Purpose\n\nThe single story of the product — told as a day in a user's life, then as a system. Every demo ([40](../07-sales/40-demo-script.md)), tour page ([53](../10-website/53-website-copy.md)), and onboarding sequence ([45](../08-customer-success/45-onboarding-playbook.md)) is a rendering of this narrative.\n\n**Target audience:** Everyone who explains the product; the reference for what the product _means_.\n\n---\n\n## 1. The Narrative in One Line\n\n> One workspace where your work already knows its context, your Twin has prepared the hard parts, and you decide.\n\n## 2. The Day (the canonical user story — Maya, CSM, 8:55am)\n\n**Before IntegrateWise:** Maya opens the CRM, the support desk, the billing tool, email, Slack, the usage dashboard, last quarter's deck, and a spreadsheet of her own making. Eight tabs to answer one question: _what's true about this account today?_ Forty minutes later she has a guess. She pastes half of it into a chatbot to draft the QBR summary; it invents a renewal date; she fixes it by hand. By 11am she has done the job her tools were supposed to do — again. She is the Human API.\n\n**With IntegrateWise:** Maya opens her workbench. It opens on her work, not a feed: **what changed** overnight (a usage dip at Meridian, flagged with the evidence — which systems, which numbers), **what needs her** (renewal in 45 days; the champion who went quiet), and **what's prepared** (her 10am meeting brief, drafted by her Twin from the account's full truth — CRM, tickets, billing, the email thread where budget language shifted).\n\nShe reads the brief. It cites its sources — every claim traceable. She asks her Twin one question — _\"what did we commit to in March?\"_ — and gets the answer from the Spine, not a guess: the commitment, who made it, where it's recorded. She assigns the follow-up: _draft the renewal outreach reflecting the usage dip conversation._ The draft arrives grounded in what was actually said. She edits one sentence and **approves**. The email sends through her connected tools; the action, its evidence, and her approval land in the audit trail; the outcome enters the account's memory — because she approved that too.\n\nIt's 9:20am. The reconstruction ritual didn't happen. **The next piece of work started where the last one ended.**\n\n## 3. The System (the same story, structurally)\n\n```\nWorkspace            one place; tools stay connected, work stops being scattered\n  → Shared Workbench   role-composed surface: her accounts, her focus, her authority\n    → Human + Twin      same bench, same context; Twin prepares/proposes, Maya decides\n      → Capability Execution   approved actions run across connected tools, audited\n        → Organizational Continuity   truth, memory, and outcomes persist in the Spine\n```\n\nComponent deep-stories: [22 Spine](22-adaptive-spine-story.md) · [23 Workspace](23-workspace-story.md) · [24 Workbench](24-shared-workbench-story.md) · [25 Twin](25-twin-story.md) · [26 Capability](26-capability-fabric-story.md) · [27 Governance](27-governance-story.md) · [21 Platform](21-platform-story.md).\n\n## 4. Narrative Rules\n\n1. **Always start with the person, never the architecture.** Maya's 8:55am is the entry point; the stack diagram is the explanation, not the hook.\n2. **The three beats are fixed:** _what changed → what needs you → what's prepared._ Every workbench, demo, and screenshot honors this order.\n3. **Show the approval.** The signature moment of every telling is Maya approving a prepared action and seeing the audit trail. Governance is not a caveat at the end — it's the climax.\n4. **The Twin never steals the scene.** It prepares and proposes; Maya's decision is the resolution of every beat.\n5. **Silence is a feature.** When nothing is grounded, the Twin says nothing. Tell this proudly — it's the anti-hallucination proof and nobody else can claim it.\n6. **End on continuity.** The story's last line is always some form of: _tomorrow starts where today ended._\n\n## 5. Renderings (where this narrative appears, adapted)\n\n| Surface              | Rendering                                                                                                    |\n| -------------------- | ------------------------------------------------------------------------------------------------------------ |\n| Homepage hero + tour | Compressed Day + three beats ([53 Website Copy](../10-website/53-website-copy.md))                           |\n| First demo           | The Day performed live with prospect's tool names ([40 Demo Script](../07-sales/40-demo-script.md))          |\n| Onboarding           | User's own first Day reproduced by day 1 ([45 Onboarding](../08-customer-success/45-onboarding-playbook.md)) |\n| Sales deck           | Beats as the demo agenda; system diagram for technical stakeholders                                          |\n| Investor deck        | The Day in 60 seconds, then the moat stack ([67](../12-corporate/67-investor-narrative.md))                  |\n\n**KPIs:** demo-to-POV conversion (does the Day land?); time-to-first-\"that's my morning\" in discovery calls; onboarding day-1 activation ([75 CS Metrics](../13-operations/75-customer-success-metrics.md)).\n\n---\n\n**Related:** [12 Messaging](../03-positioning-messaging/12-messaging-framework.md) · [24 Workbench Story](24-shared-workbench-story.md) · [40 Demo Script](../07-sales/40-demo-script.md) · [53 Website Copy](../10-website/53-website-copy.md)\n"}