00 — Deck Core
Status: CANONICAL · Commercial OS — the shared factual spine for every IntegrateWise deck
Owner: Founder + Product Marketing
Created: 2026-07-31
Precedence: Architecture Lock governs product
and runtime truth. 00 Current GTM Canon governs
category, positioning, audience, and launch narrative. 30 Pricing
Strategy governs every number.
This document governs nothing new — it renders those sources into deck-ready form.
1. Why this document exists
Twelve presentation files accumulated between 2026-01-05 and 2026-02-14. All of them
predate the Architecture Lock freeze (2026-07-17) and the Commercial OS alignment
(2026-07-29). Each was internally coherent at the time it was made; collectively they
now put four incompatible product stories, three pricing models, two currencies, and
two domain names into the world.
The fix is not to merge twelve decks. It is to hold one core — this document — and
render three audience cuts from it. When canon evolves, this document changes once
and the three decks are regenerated. Decks are snapshots. The core is the living asset.
Deck rule: no deck asserts anything not traceable to a line in this document.
2. Provenance and drift map
What each legacy deck was, and its disposition.
| Deck | Date | Was | Disposition |
|---|---|---|---|
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. |
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. |
integratewise_complete_platform | 2026-01-08 | "Work Today Is Broken" problem framing | Harvest problem framing only. |
The Spine: Connected Intelligence Framework | Jan 2026 | Organizational resilience framing | Retire. Concept absorbed into Adaptive Spine story. |
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. |
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. |
Unified Cognitive Infrastructure | Jan 2026 | Infrastructure framing, image-only | Retire. Category is now Operational Capability Platform. |
The Onboarding Journey | Jan 2026 | Onboarding narrative, image-only | Harvest. Maps to the five-step activation story in GTM Canon §2. |
integratewise-sales-deck | 2026-02-14 | SMB/prosumer, 12 industries, $29/$79/mo, integratewise.online | Superseded. Pricing, audience, and domain all conflict with canon. |
integratewise-marketing-deck | 2026-02-14 | Brand overview, same SMB frame | Superseded, same reasons. |
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. |
Vocabulary ledger
| Retired external term | Current term | Note |
|---|---|---|
| Cognitive Operating System · IntegrateWise OS · AI OS | The Operational Capability Platform for the AI Era | Category, per GTM Canon §1 |
| OS Shell · Views · Topic Boards · Workspace surface | Workbench | One surface, RBAC-projected |
| Atlas Spine | Adaptive Spine | |
| 16 AI Agents (named personas) | Capabilities in the Capability Fabric | Agent taxonomy retired |
| Cognitive Twin · AI assistant · copilot | Twin | Silent by default; a capability of the Workbench, never a panel |
| Normalizer (external) | (internal only) | Deterministic normalization; not a customer concept |
| Hermes (external) | (internal only) | Governed execution coordinator, not an AI-surface label |
| IW-Continuity-Bridge | IntegrateWise | Never revive as an external product name |
integratewise.online | integratewise.ai | |
| L1 / L2 / L4 / L7 | Workbench / Twin / Continuity / Governance | Never in user-facing material |
3. The canonical core
Audience-neutral. Every deck draws from here.
3.1 Category and promise
| Layer | Canon |
|---|---|
| Category | The Operational Capability Platform for the AI Era |
| Brand doctrine | Operational Continuity. Governed Intelligence. |
| One-liner | IntegrateWise connects people, AI surfaces, and operational systems through one governed capability fabric, so work can continue with context, control, and accountability. |
| Customer aspiration | Your AI already knows language. Now let it know your business. |
| Tagline | Truth you own. AI you rent. Approval in between. |
3.2 The problem (harvested framing, canon-grounded)
The organization is fragmented, and AI made the fragmentation worse rather than better.
Four failure modes name it in language every professional recognizes without explanation:
| Failure | What it sounds like | Root cause |
|---|---|---|
| Amnesia | "I told it everything yesterday. Today it knows nothing." | No canonical state the AI can stand on; session memory that guesses |
| Babysitting | "I gave it a task. It did two steps and stopped." | No governed execution path — nothing carries an action to completion |
| Hallucination | "Confident answer. Completely wrong." | The AI is reasoning without grounded operational truth |
| Human API | "I became the bridge between my AI and my software." | No capability fabric — the person is the integration layer |
Supporting market context (cite as market context, never as our measurement):
~80% of AI adopters quietly demoted AI to low-stakes work · 76% of enterprises now
require human oversight of AI · 130+ SaaS apps per business · $47B+
operational-intelligence market with a trust crisis at its center.
Sources: 06 Market Analysis.
3.3 The mechanism
AI surfaces + people + applications/data
↓
Universal Capability Fabric
↓
Adaptive Spine + governance + continuity
↓
Role-specific operational Workbenches
↓
Approved, auditable outcomes in connected systems
This is a market map, not a runtime diagram. The frozen runtime sequence lives in the
Architecture Lock and appears only in the internal deck.
Each failure is answered by a specific part of the mechanism — this mapping is the
spine of every deck:
| Failure | Answered by | Because |
|---|---|---|
| Amnesia | Adaptive Spine | Canonical operational state the organization owns, with provenance per field |
| Human API | Capability Fabric + Workbench | Capabilities are discoverable and policy-bound; the person stops being the bridge |
| Hallucination | Grounded context | The Twin reasons over Spine truth, not over a prompt |
| Babysitting | Governance + governed execution | Approved intent runs to completion and returns a receipt |
3.4 The four controls (the human-control proof)
Store in Spine · Ask Your Twin · Assign Your Twin · Approve Twin's Action.
Mapped to OODA: Observe / Orient / Decide / Act. These four are the entire user-facing
control grammar. The Twin is silent by default and prefers silence to low-value
commentary. No approval token, no external mutation — this is architecture, not a
setting.
3.5 Differentiation — five moats
| Moat | Claim | Why incumbents structurally can't follow |
|---|---|---|
| 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. |
| 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. |
| 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. |
| Governance as architecture | Propose → approve → execute → audit is the physics | Agent vendors sell autonomy. Retrofitting mandatory human gates reverses their pitch. |
| Compounding continuity | Every approved fact enriches the Spine; value compounds with tenure | Session-based tools reset by design; continuity requires the other four first. |
Source: 17 Differentiation.
3.6 Business model
Per-seat. A seat is a human + Twin pair — the Twin is never priced separately,
because pricing the AI as an add-on would contradict the category.
| Starter $19 | Growth $59 | Command $119 | Enterprise | |
|---|---|---|---|---|
| Positioning | See your truth | Work with your Twin | Govern the work | Continuity at scale |
| Workbenches | 1 department | 3 departments | Unlimited | Unlimited + custom |
| Twin | Workbench + signals only | Observes · explains · prepares · suggests | Full grammar incl. propose + governed execution + TruthLayer | + policy customization |
| Governance | Audit log | Approvals + audit | Full lifecycle + export | + SSO/SCIM, DPA, SLA |
Per seat / month, annual billing; monthly +20%. India ₹499 / ₹1,499 / ₹2,999 and
UAE/GCC $12 / $39 / $79 activate with those market launches. Deal math: 15 × Growth
≈ $10.6K ACV · 20 × Command ≈ $28.6K ACV · Enterprise 100+ ≈ $150K+ ACV.
Gross margin 97%+ (COGS $0.55–2.10/seat).
Source: 30 Pricing Strategy.
3.7 GTM motion
Category-led, activation-assisted, proof-gated. Create demand for the category →
qualify a concrete cross-system problem with executive, operator, and control champions
→ activate a bounded ecosystem and role-appropriate Workbenches → demonstrate
evidence → proposal → approval → execution → receipt → expand across capabilities,
Workbenches, and connected systems.
Customer Success is one proof path among twelve Workbenches — never the category,
the homepage, or the only buyer. (This resolves the conflict with 67 Investor
Narrative §7, which still describes a CS
wedge; GTM Canon §1 explicitly supersedes it and §7 should be updated.)
North-star metric: time to first approved governed outcome for an activated
organization.
3.8 Stage and the ask
Stage as of 2026-07-31: pre-launch, design-partner program. Technical rollout is
recorded No-Go pending npm authorization, warning-free Wrangler configuration, and
strict test/production isolation. Public T1 launch is No-Go pending the commercial
proof gate.
Source: Go-Live and GTM Plan §3.
Seed $750K–1.2M: 45% engineering (spine hardening, connectors, SOC 2), 25% GTM,
15% infrastructure, 10% ops, 5% reserve. Buys: launch, 25 customers, ~$1M ARR
run-rate trajectory, Series A metrics. (Supersedes the ₹2–4 Cr figure in the legacy
pitch deck.)
4. Claims register
Decision of 2026-07-31: evidence-gated posture. A deck states the stage honestly;
the architecture and the working approval gate are the proof.
| May state | Must not state (until evidenced) |
|---|---|
| The frozen architecture, the four controls, the governance gate | "70+ connectors" or any connector count |
| That the Twin structurally cannot act without approval | "sub-200ms Entity360" as a live benchmark |
Design-partner outcomes as [n] placeholders the founder fills at use | Customer logos, certifications, SOC 2 |
| Pre-launch / design-partner stage | General availability |
| Named connected systems that are currently supported | "100+ integrations", "12 industries supported" |
| That the demo is the traction at this stage | "one click", "total continuity", "zero downtime" |
| Market context with its source named | Market statistics presented as our own measurement |
Every [n] and [x%] placeholder in the decks is deliberate. Fill at use; do not
guess.
5. The three cuts
Same core. Different question answered. No conflation of product philosophy, user
experience, architecture, and marketing.
| Investor | Design partner | Internal / architecture | |
|---|---|---|---|
| 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? |
| Opens on | The four failures + the demotion thesis | The operator's Monday morning | The kernel terms and frozen laws |
| Mechanism shown as | Market map + moat logic | Activation sequence + the four controls | Runtime sequence + four planes + flows |
| Numbers | Pricing, deal math, margin, ask | Per-seat pricing for their tier only | None |
| Proof | Architecture + approval gate + [n] design partners | A bounded first governed outcome | Release gates and evidence record |
| Excludes | Runtime internals, L-layers | Moat logic, cap table, architecture internals | All marketing language |
| Length | 14 slides | 12 slides | 13 slides |
6. Regenerating the decks
The three .pptx files in this directory are build artifacts, not sources. When
canon changes, edit this document and the matching generator, then rebuild:
cd docs/commercial/decks/build
npm install pptxgenjs # first run only
node build-investor.js && node build-partner.js && node build-internal.js
theme.js holds the shared palette, typography, and layout primitives — change it
once and all three decks stay visually consistent. Generators write to the current
directory; move the output up one level.
Open follow-ups
- 67 Investor Narrative §7 still
describes a Customer Success wedge that GTM Canon
§1 supersedes. Update §7 or annotate it as historical. - 67 §3 asserts "70+ connectors,
sub-200ms Entity360, live today." The Go-Live record does not currently evidence
these. Either evidence them or soften the claim; the decks omit them meanwhile. integratewise.onlineappears in the February collateral and, presumably,
in live properties. Confirm redirect or retirement in favour ofintegratewise.ai.
Related: 00 Current GTM Canon ·
17 Differentiation ·
30 Pricing Strategy ·
67 Investor Narrative ·
Architecture Lock