{"slug":"public/company/overview","title":"IntegrateWise — Marketing & Brand Canonical","section":"public","sectionLabel":"Public","status":"unclassified","type":"document","path":"public/company/overview.md","bytes":8956,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"<!-- DOCUMENT CLASS: PUBLIC | SOURCE: 10_INTEGRATEWISE_MARKETING_BRAND_CANONICAL.md -->\n<!-- STATUS: Aligned with Founder Canon (31 August 2026) -->\n\n# IntegrateWise — Marketing & Brand Canonical\n\n**Status:** Canonical Marketing Target  \n**Company:** IntegrateWise  \n**Company domain:** `integratewise.ai`  \n**Product:** SpineWorkspace  \n**Product domain:** `spineworkspace.com`  \n**Foundation:** Business Context Spine (THE semantic foundation)\n\n## 1. Brand hierarchy\n\n```text\nINTEGRATEWISE\nCompany / Platform Builder\n        │\n        ▼\nSPINEWORKSPACE\nCustomer Product\n        │\n        ▼\nBUSINESS CONTEXT SPINE\nTHE Organization's Memory\n        │\n        ▼\nHUMAN + AI WORK\n```\n\nNever use IntegrateWise as the name of the customer-facing product.\n\n## The Tier-0 Principle\n\n> **Business Context is the semantic foundation of SpineWorkspace.** It connects organizational business reality to Work, Humans, AI, Agents, Memory, Knowledge, Capabilities, Communication, Decisions, Governance, Execution, Evidence, Continuity and Outcomes. Without Business Context, SpineWorkspace has no meaning; it becomes another collection of tools and interfaces.\n>\n> **The Spine gives work its business context.**\n\n## 2. Category\n\n### Company category\n\n> **Operational continuity infrastructure with governed intelligence.**\n\n### Product category\n\n> **Human–AI work coordination platform.**\n\n### Product foundation\n\n> **Business Context as the semantic foundation. Business Context Spine as the organization's memory.**\n\nThe strongest narrative is:\n\n> **Business Context is the foundation; human–AI work coordination is what that foundation enables.**\n\n## 3. Core problem\n\nOrganizations already have systems for CRM, finance, support, communication, projects, documents and analytics.\n\nThe problem is not the absence of applications.\n\nThe problem is that:\n\n- business context is fragmented;\n- work crosses application boundaries;\n- people become the integration layer;\n- organizational knowledge gets trapped in conversations and individuals;\n- AI sees partial context;\n- humans repeatedly reassemble context;\n- workflows break at handoffs;\n- approvals become disconnected from execution;\n- execution outcomes do not reliably return to shared context.\n\nAI introduces another problem:\n\n> **Who should do what — human, AI, agent, system, or human + AI — given the objective, context, capability, responsibility, authority, risk and current state?**\n\n## 4. Product answer\n\nSpineWorkspace connects the organization's existing operating environment into Business Context Spine.\n\nBusiness Context Spine:\n\n- connects Business Context;\n- preserves operational continuity;\n- assembles context for work;\n- provides governed projections for humans;\n- provides bounded operational context for AI;\n- connects Work across systems;\n- carries approved execution back to source systems;\n- reconciles outcomes;\n- allows validated knowledge to compound over time.\n\n## 5. Core product statement\n\n> **SpineWorkspace is where people and AI work together on business work, using shared contextual business memory and governed execution across the systems the organization already uses.**\n\nSupporting statement:\n\n> **SpineWorkspace continuously determines how work should be shared between humans and AI according to capability, responsibility, authority, risk, context and need.**\n\n## 6. The product hierarchy\n\n```text\nIntegrateWise\n  ↓\nSpineWorkspace\n  ↓\nBusiness Context Spine\n  ↓\nBusiness Context\n  ↓\nWork\n  ↓\nHuman + Twin\n  ↓\nAgents / Capabilities / Workflows\n  ↓\nExecution\n  ↓\nReconciliation\n  ↓\nBusiness Context Updated\n  ↓\nContinuity\n```\n\n## 7. Product pillars\n\n### 1. Contextual Business Memory\n\nBusiness reality from multiple systems becomes connected Business Context in Spine.\n\n### 2. Adaptive Workbench\n\nEach user receives a role-, domain-, responsibility- and work-aware projection of the organization's shared context.\n\n### 3. Personal Twin\n\nEach user receives a bounded AI work partner that reasons over operational context, coordinates work and delegates bounded execution.\n\n### 4. Governed Human–AI Work\n\nHumans retain responsibility, judgment and consequential authority. AI absorbs suitable repetitive, analytical, coordination and execution work.\n\n### 5. Connected Execution\n\nCapabilities execute through APIs, MCP, workflows, agents and provider tools and return actual outcomes to Spine.\n\n### 6. Operational Continuity\n\nWork, context, decisions, evidence and outcomes remain coherent across systems, people, agents and time.\n\n### 7. Compounding Organizational Knowledge\n\nReconciled outcomes can become governed knowledge and Organizational Memory for future work.\n\n## 8. What SpineWorkspace is not\n\nDo not position SpineWorkspace primarily as:\n\n- CRM;\n- chatbot;\n- AI wrapper;\n- generic copilot;\n- workflow automation tool;\n- integration-only platform;\n- generic productivity workspace;\n- autonomous agent platform;\n- replacement for every source application.\n\nThose categories describe only pieces of the system.\n\n## 9. Human + AI narrative\n\nThe story is not:\n\n> Humans use AI.\n\nThe story is:\n\n> **Humans and AI work on the same business work, with different capabilities, responsibilities and authority.**\n\nAI should take work that does not require human judgment where appropriate:\n\n- repetitive work;\n- high-volume coordination;\n- context gathering;\n- analysis;\n- preparation;\n- monitoring;\n- structured execution.\n\nHumans remain responsible for:\n\n- judgment;\n- relationships;\n- accountability;\n- negotiation;\n- exceptions;\n- consequential decisions;\n- organizational leadership.\n\n## 10. Spine narrative\n\n> **Spine gives the organization one connected operational context without forcing the organization to replace the systems it already uses.**\n\nSpine is not marketed as a generic memory database.\n\nThe stronger narrative is:\n\n> **Spine is the contextual business memory and continuity layer between the systems, people and AI that perform the organization's work.**\n\n## 11. Twin narrative\n\n> **Your Twin is your AI work partner — a persistent digital representative that understands your current work, assembles the context it needs, coordinates bounded execution and brings decisions, exceptions and outcomes back to you.**\n\nTwin is not positioned as an autonomous enterprise authority.\n\n## 12. Workbench narrative\n\n> **The Workbench is the adaptive operational surface where the right business context appears around the work you need to move.**\n\nThe user sees:\n\n- current state;\n- relevant context;\n- work;\n- communications;\n- evidence;\n- decisions;\n- risks;\n- recommendations;\n- next actions.\n\n## 13. Bridge narrative\n\n> **The Continuity Bridge carries communication, contextual references and governed work between SpineWorkspace and the systems and channels where people and AI already operate.**\n\nThe Bridge connects:\n\n- Workbench;\n- Twin;\n- agents;\n- Slack;\n- email;\n- meetings;\n- APIs;\n- MCP;\n- workflows;\n- source systems.\n\n## 14. Differentiation\n\n### Traditional software\n\n```text\nApplication\n ↓\nData\n ↓\nTask\n```\n\n### Traditional automation\n\n```text\nTrigger\n ↓\nPredefined Workflow\n ↓\nAction\n```\n\n### Generic AI assistant\n\n```text\nPrompt\n ↓\nModel\n ↓\nAnswer\n```\n\n### SpineWorkspace\n\n```text\nBusiness Context\n ↓\nWork\n ↓\nContext Assembly\n ↓\nHuman + Twin\n ↓\nWork Allocation\n ↓\nGovernance\n ↓\nExecution\n ↓\nReconciliation\n ↓\nKnowledge\n ↓\nContinuity\n```\n\n## 15. Messaging hierarchy\n\n### One sentence\n\n> **SpineWorkspace is where humans and AI work together on business work using shared contextual business memory.**\n\n### One paragraph\n\n> **SpineWorkspace connects the systems your organization already uses into a shared Business Context through the Business Context Spine. It projects the right context into each user's Workbench, gives every user a bounded Twin to coordinate digital work, and governs how work is divided between humans, AI, agents and systems until outcomes are executed, reconciled and carried forward into organizational continuity.**\n\n### Company statement\n\n> **IntegrateWise builds operational continuity infrastructure with governed intelligence.**\n\n## 16. Trust language\n\nPreferred:\n\n- governed;\n- bounded;\n- contextual;\n- reconciled;\n- traceable;\n- connected;\n- continuous;\n- role-aware;\n- evidence-backed;\n- operational.\n\nAvoid unsupported superlatives such as:\n\n- fully autonomous;\n- replaces every tool;\n- eliminates all manual work;\n- guarantees profitability;\n- never fails.\n\n## 17. Primary CTA\n\nPrimary:\n\n> **Book a Demo**\n\nSecondary:\n\n> **Explore SpineWorkspace**\n\nProduct CTA where appropriate:\n\n> **Activate Workspace**\n\n## 18. Marketing design principle\n\nThe visual identity should feel:\n\n- infrastructure-grade;\n- premium B2B;\n- serious;\n- precise;\n- connected;\n- contextual;\n- operational.\n\nAvoid making the brand look like:\n\n- a consumer chatbot;\n- a toy AI agent;\n- generic workflow SaaS;\n- developer-only infrastructure;\n- crypto/web3 futurism.\n\n"}