Unclassified

19 — Product Narrative

Status: CANONICAL · Commercial OS
Owner: Product Marketing
Last verified: 2026-07-21

Purpose

The single story of the product — told as a day in a user's life, then as a system. Every demo (40), tour page (53), and onboarding sequence (45) is a rendering of this narrative.

Target audience: Everyone who explains the product; the reference for what the product means.

1. The Narrative in One Line

One workspace where your work already knows its context, your Twin has prepared the hard parts, and you decide.

2. The Day (the canonical user story — Maya, CSM, 8:55am)

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.

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).

She 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.

It's 9:20am. The reconstruction ritual didn't happen. The next piece of work started where the last one ended.

3. The System (the same story, structurally)

Workspace            one place; tools stay connected, work stops being scattered
  → Shared Workbench   role-composed surface: her accounts, her focus, her authority
    → Human + Twin      same bench, same context; Twin prepares/proposes, Maya decides
      → Capability Execution   approved actions run across connected tools, audited
        → Organizational Continuity   truth, memory, and outcomes persist in the Spine

Component deep-stories: 22 Spine · 23 Workspace · 24 Workbench · 25 Twin · 26 Capability · 27 Governance · 21 Platform.

4. Narrative Rules

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.
The three beats are fixed: what changed → what needs you → what's prepared. Every workbench, demo, and screenshot honors this order.
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.
The Twin never steals the scene. It prepares and proposes; Maya's decision is the resolution of every beat.
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.
End on continuity. The story's last line is always some form of: tomorrow starts where today ended.

5. Renderings (where this narrative appears, adapted)

Surface	Rendering
Homepage hero + tour	Compressed Day + three beats (53 Website Copy)
First demo	The Day performed live with prospect's tool names (40 Demo Script)
Onboarding	User's own first Day reproduced by day 1 (45 Onboarding)
Sales deck	Beats as the demo agenda; system diagram for technical stakeholders
Investor deck	The Day in 60 seconds, then the moat stack (67)

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).