{"slug":"business/00-deck-core","title":"00 — Deck Core","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/00-deck-core.mdx","bytes":23722,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CANONICAL · Commercial OS — the shared factual spine for every IntegrateWise deck\nOwner: Founder + Product Marketing\nCreated: 2026-07-31\nPrecedence: [Architecture Lock](../../architecture/ARCHITECTURE_LOCK.md) governs product\nand runtime truth. [00 Current GTM Canon](../09-gtm/00-current-gtm-canon.md) governs\ncategory, positioning, audience, and launch narrative. [30 Pricing\nStrategy](../05-value-pricing/30-pricing-strategy.md) governs every number.\nThis document governs nothing new — it **renders** those sources into deck-ready form.\n\n---\n\n## 1. Why this document exists\n\nTwelve presentation files accumulated between 2026-01-05 and 2026-02-14. All of them\npredate the Architecture Lock freeze (2026-07-17) and the Commercial OS alignment\n(2026-07-29). Each was internally coherent at the time it was made; collectively they\nnow put four incompatible product stories, three pricing models, two currencies, and\ntwo domain names into the world.\n\nThe fix is not to merge twelve decks. It is to hold **one core** — this document — and\nrender **three audience cuts** from it. When canon evolves, this document changes once\nand the three decks are regenerated. Decks are snapshots. The core is the living asset.\n\n**Deck rule:** no deck asserts anything not traceable to a line in this document.\n\n---\n\n## 2. Provenance and drift map\n\nWhat each legacy deck was, and its disposition.\n\n| Deck | Date | Was | Disposition |\n| --------------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `integratewise_ai_os_presentation` | 2026-01-05 | \"AI Workspace\", Control Plane vs Data Plane, Atlas Spine | **Superseded.** \"Atlas Spine\" → Adaptive Spine. Plane model → the Four Planes. |\n| `integratewise_master_deck` | 2026-01-07 | \"One AI Workspace + 16 Expert Agents\", phased agent release Apr 2026 | **Superseded.** The 16-agent taxonomy is retired; capabilities live in the Capability Fabric, not as named agent personas. Contains unshipped design-brief text pasted into slide 7. |\n| `integratewise_complete_platform` | 2026-01-08 | \"Work Today Is Broken\" problem framing | **Harvest problem framing only.** |\n| `The Spine: Connected Intelligence Framework` | Jan 2026 | Organizational resilience framing | **Retire.** Concept absorbed into Adaptive Spine story. |\n| `integratewise_pitch_deck` | Jan 2026 | \"Cognitive Operating System\", Flow A/B, Think/Act/Learn, Views, Topic Boards | **Partially fundamental.** Flow A/B survive in the Architecture Lock. \"Cognitive OS\", \"Views\", \"Topic Boards\" are retired external names — the surface is the **Workbench**. |\n| `integratewise_os_pitch` (×2) | 2026-01-30, 02-01 | \"IntegrateWise OS\", OS Shell, Signal Strip, Situation Feed, Evidence Drawer, Normalizer | **Superseded naming, live UX.** \"OS Shell\" → Workbench. Signal Strip / Situation Feed / Evidence Drawer are good UX references; Normalizer is real but internal (deterministic normalization), not a customer-facing product concept. |\n| `Unified Cognitive Infrastructure` | Jan 2026 | Infrastructure framing, image-only | **Retire.** Category is now Operational Capability Platform. |\n| `The Onboarding Journey` | Jan 2026 | Onboarding narrative, image-only | **Harvest.** Maps to the five-step activation story in GTM Canon §2. |\n| `integratewise-sales-deck` | 2026-02-14 | SMB/prosumer, 12 industries, $29/$79/mo, `integratewise.online` | **Superseded.** Pricing, audience, and domain all conflict with canon. |\n| `integratewise-marketing-deck` | 2026-02-14 | Brand overview, same SMB frame | **Superseded**, same reasons. |\n| `IntegrateWise_Pitch_Deck 2` | ~May 2026 | India seed ₹2–4 Cr, 80%-demoted-AI thesis, Amnesia/Babysitting/Hallucination/Human API, Arjun/Priya/Vikram | **Best narrative craft of the twelve.** Framing and personas are harvested. The ask (₹2–4 Cr) is superseded by $750K–1.2M. |\n\n### Vocabulary ledger\n\n| Retired external term | Current term | Note |\n| ----------------------------------------------------- | ------------------------------------------------------ | --------------------------------------------------------------- |\n| Cognitive Operating System · IntegrateWise OS · AI OS | **The Operational Capability Platform for the AI Era** | Category, per GTM Canon §1 |\n| OS Shell · Views · Topic Boards · Workspace surface | **Workbench** | One surface, RBAC-projected |\n| Atlas Spine | **Adaptive Spine** | |\n| 16 AI Agents (named personas) | **Capabilities** in the Capability Fabric | Agent taxonomy retired |\n| Cognitive Twin · AI assistant · copilot | **Twin** | Silent by default; a capability of the Workbench, never a panel |\n| Normalizer (external) | _(internal only)_ | Deterministic normalization; not a customer concept |\n| Hermes (external) | _(internal only)_ | Governed execution coordinator, not an AI-surface label |\n| IW-Continuity-Bridge | **IntegrateWise** | Never revive as an external product name |\n| `integratewise.online` | **`integratewise.ai`** | |\n| L1 / L2 / L4 / L7 | Workbench / Twin / Continuity / Governance | Never in user-facing material |\n\n---\n\n## 3. The canonical core\n\nAudience-neutral. Every deck draws from here.\n\n### 3.1 Category and promise\n\n| Layer | Canon |\n| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Category | The Operational Capability Platform for the AI Era |\n| Brand doctrine | Operational Continuity. Governed Intelligence. |\n| One-liner | IntegrateWise connects people, AI surfaces, and operational systems through one governed capability fabric, so work can continue with context, control, and accountability. |\n| Customer aspiration | Your AI already knows language. Now let it know your business. |\n| Tagline | Truth you own. AI you rent. Approval in between. |\n\n### 3.2 The problem (harvested framing, canon-grounded)\n\nThe organization is fragmented, and AI made the fragmentation worse rather than better.\nFour failure modes name it in language every professional recognizes without explanation:\n\n| Failure | What it sounds like | Root cause |\n| ----------------- | --------------------------------------------------------- | -------------------------------------------------------------------- |\n| **Amnesia** | \"I told it everything yesterday. Today it knows nothing.\" | No canonical state the AI can stand on; session memory that guesses |\n| **Babysitting** | \"I gave it a task. It did two steps and stopped.\" | No governed execution path — nothing carries an action to completion |\n| **Hallucination** | \"Confident answer. Completely wrong.\" | The AI is reasoning without grounded operational truth |\n| **Human API** | \"I became the bridge between my AI and my software.\" | No capability fabric — the person is the integration layer |\n\nSupporting market context (cite as market context, never as our measurement):\n~80% of AI adopters quietly demoted AI to low-stakes work · 76% of enterprises now\nrequire human oversight of AI · 130+ SaaS apps per business · $47B+\noperational-intelligence market with a trust crisis at its center.\nSources: [06 Market Analysis](../02-category-market/06-market-analysis.md).\n\n### 3.3 The mechanism\n\n```\nAI surfaces + people + applications/data\n ↓\n Universal Capability Fabric\n ↓\n Adaptive Spine + governance + continuity\n ↓\n Role-specific operational Workbenches\n ↓\n Approved, auditable outcomes in connected systems\n```\n\nThis is a market map, not a runtime diagram. The frozen runtime sequence lives in the\nArchitecture Lock and appears only in the internal deck.\n\nEach failure is answered by a specific part of the mechanism — this mapping is the\nspine of every deck:\n\n| Failure | Answered by | Because |\n| ------------- | ----------------------------------- | --------------------------------------------------------------------------------- |\n| Amnesia | **Adaptive Spine** | Canonical operational state the organization owns, with provenance per field |\n| Human API | **Capability Fabric + Workbench** | Capabilities are discoverable and policy-bound; the person stops being the bridge |\n| Hallucination | **Grounded context** | The Twin reasons over Spine truth, not over a prompt |\n| Babysitting | **Governance + governed execution** | Approved intent runs to completion and returns a receipt |\n\n### 3.4 The four controls (the human-control proof)\n\n**Store in Spine · Ask Your Twin · Assign Your Twin · Approve Twin's Action.**\n\nMapped to OODA: Observe / Orient / Decide / Act. These four are the entire user-facing\ncontrol grammar. The Twin is silent by default and prefers silence to low-value\ncommentary. No approval token, no external mutation — this is architecture, not a\nsetting.\n\n### 3.5 Differentiation — five moats\n\n| Moat | Claim | Why incumbents structurally can't follow |\n| ------------------------------------------- | ---------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |\n| **Shared-state collaboration** | Human and Twin work the same surface over the same live state | Copilots are sidecars to a host app; assistants are conversation threads. Neither has shared work-state to collaborate on. |\n| **TruthLayer — approval-gated memory** | AI proposes memory; humans approve; only then is it organizational knowledge | Auto-memory is their engagement engine. Gating it degrades their core metric. |\n| **Adaptive Spine — truth outside the apps** | Canonical state independent of any SaaS vendor | A vendor whose business _is_ the silo cannot sell truth above the silo without cannibalizing itself. |\n| **Governance as architecture** | Propose → approve → execute → audit is the physics | Agent vendors sell autonomy. Retrofitting mandatory human gates reverses their pitch. |\n| **Compounding continuity** | Every approved fact enriches the Spine; value compounds with tenure | Session-based tools reset by design; continuity requires the other four first. |\n\nSource: [17 Differentiation](../03-positioning-messaging/17-differentiation.md).\n\n### 3.6 Business model\n\nPer-seat. **A seat is a human + Twin pair** — the Twin is never priced separately,\nbecause pricing the AI as an add-on would contradict the category.\n\n| | Starter $19 | Growth $59 | Command $119 | Enterprise |\n| ----------- | ------------------------ | ----------------------------------------- | ------------------------------------------------------------ | ---------------------- |\n| Positioning | See your truth | Work with your Twin | Govern the work | Continuity at scale |\n| Workbenches | 1 department | 3 departments | Unlimited | Unlimited + custom |\n| Twin | Workbench + signals only | Observes · explains · prepares · suggests | Full grammar incl. propose + governed execution + TruthLayer | + policy customization |\n| Governance | Audit log | Approvals + audit | Full lifecycle + export | + SSO/SCIM, DPA, SLA |\n\nPer seat / month, annual billing; monthly +20%. India ₹499 / ₹1,499 / ₹2,999 and\nUAE/GCC $12 / $39 / $79 activate with those market launches. Deal math: 15 × Growth\n≈ $10.6K ACV · 20 × Command ≈ $28.6K ACV · Enterprise 100+ ≈ $150K+ ACV.\nGross margin 97%+ (COGS $0.55–2.10/seat).\nSource: [30 Pricing Strategy](../05-value-pricing/30-pricing-strategy.md).\n\n### 3.7 GTM motion\n\n**Category-led, activation-assisted, proof-gated.** Create demand for the category →\nqualify a concrete cross-system problem with executive, operator, and control champions\n→ activate a bounded ecosystem and role-appropriate Workbenches → demonstrate\nevidence → proposal → approval → execution → receipt → expand across capabilities,\nWorkbenches, and connected systems.\n\nCustomer Success is **one proof path among twelve Workbenches** — never the category,\nthe homepage, or the only buyer. (This resolves the conflict with [67 Investor\nNarrative](../12-corporate/67-investor-narrative.md) §7, which still describes a CS\nwedge; GTM Canon §1 explicitly supersedes it and §7 should be updated.)\n\nNorth-star metric: **time to first approved governed outcome** for an activated\norganization.\n\n### 3.8 Stage and the ask\n\nStage as of 2026-07-31: **pre-launch, design-partner program**. Technical rollout is\nrecorded No-Go pending npm authorization, warning-free Wrangler configuration, and\nstrict test/production isolation. Public T1 launch is No-Go pending the commercial\nproof gate.\nSource: [Go-Live and GTM Plan](../../operations/GO_LIVE_AND_GTM_PLAN.md) §3.\n\nSeed **$750K–1.2M**: 45% engineering (spine hardening, connectors, SOC 2), 25% GTM,\n15% infrastructure, 10% ops, 5% reserve. Buys: launch, 25 customers, ~$1M ARR\nrun-rate trajectory, Series A metrics. _(Supersedes the ₹2–4 Cr figure in the legacy\npitch deck.)_\n\n---\n\n## 4. Claims register\n\nDecision of 2026-07-31: **evidence-gated posture.** A deck states the stage honestly;\nthe architecture and the working approval gate are the proof.\n\n| May state | Must not state (until evidenced) |\n| ---------------------------------------------------------------------- | -------------------------------------------------- |\n| The frozen architecture, the four controls, the governance gate | \"70+ connectors\" or any connector count |\n| That the Twin structurally cannot act without approval | \"sub-200ms Entity360\" as a live benchmark |\n| Design-partner outcomes as `[n]` placeholders the founder fills at use | Customer logos, certifications, SOC 2 |\n| Pre-launch / design-partner stage | General availability |\n| Named connected systems that are currently supported | \"100+ integrations\", \"12 industries supported\" |\n| That the demo _is_ the traction at this stage | \"one click\", \"total continuity\", \"zero downtime\" |\n| Market context with its source named | Market statistics presented as our own measurement |\n\nEvery `[n]` and `[x%]` placeholder in the decks is deliberate. Fill at use; do not\nguess.\n\n---\n\n## 5. The three cuts\n\nSame core. Different question answered. No conflation of product philosophy, user\nexperience, architecture, and marketing.\n\n| | **Investor** | **Design partner** | **Internal / architecture** |\n| ------------------ | --------------------------------------------------------- | --------------------------------------------------- | ------------------------------------------------------- |\n| Question | Why is this a category, and why can't incumbents take it? | What changes for my team, and what do I have to do? | What are we actually building, and what must not drift? |\n| Opens on | The four failures + the demotion thesis | The operator's Monday morning | The kernel terms and frozen laws |\n| Mechanism shown as | Market map + moat logic | Activation sequence + the four controls | Runtime sequence + four planes + flows |\n| Numbers | Pricing, deal math, margin, ask | Per-seat pricing for their tier only | None |\n| Proof | Architecture + approval gate + `[n]` design partners | A bounded first governed outcome | Release gates and evidence record |\n| Excludes | Runtime internals, L-layers | Moat logic, cap table, architecture internals | All marketing language |\n| Length | 14 slides | 12 slides | 13 slides |\n\n---\n\n## 6. Regenerating the decks\n\nThe three `.pptx` files in this directory are build artifacts, not sources. When\ncanon changes, edit this document and the matching generator, then rebuild:\n\n```bash\ncd docs/commercial/decks/build\nnpm install pptxgenjs # first run only\nnode build-investor.js && node build-partner.js && node build-internal.js\n```\n\n`theme.js` holds the shared palette, typography, and layout primitives — change it\nonce and all three decks stay visually consistent. Generators write to the current\ndirectory; move the output up one level.\n\n### Open follow-ups\n\n1. **[67 Investor Narrative](../12-corporate/67-investor-narrative.md) §7** still\n describes a Customer Success wedge that [GTM Canon](../09-gtm/00-current-gtm-canon.md)\n §1 supersedes. Update §7 or annotate it as historical.\n2. **[67](../12-corporate/67-investor-narrative.md) §3** asserts \"70+ connectors,\n sub-200ms Entity360, live today.\" The Go-Live record does not currently evidence\n these. Either evidence them or soften the claim; the decks omit them meanwhile.\n3. **`integratewise.online`** appears in the February collateral and, presumably,\n in live properties. Confirm redirect or retirement in favour of `integratewise.ai`.\n\n---\n\n**Related:** [00 Current GTM Canon](../09-gtm/00-current-gtm-canon.md) ·\n[17 Differentiation](../03-positioning-messaging/17-differentiation.md) ·\n[30 Pricing Strategy](../05-value-pricing/30-pricing-strategy.md) ·\n[67 Investor Narrative](../12-corporate/67-investor-narrative.md) ·\n[Architecture Lock](../../architecture/ARCHITECTURE_LOCK.md)\n"}