{"slug":"public/product/overview","title":"SpineWorkspace / IntegrateWise — Website Canonical","section":"public","sectionLabel":"Public","status":"unclassified","type":"document","path":"public/product/overview.md","bytes":8555,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"<!-- DOCUMENT CLASS: PUBLIC | SOURCE: 11_SPINEWORKSPACE_WEBSITE_CANONICAL.md -->\n<!-- STATUS: Aligned with Founder Canon (31 August 2026) -->\n\n# SpineWorkspace / IntegrateWise — Website Canonical\n\n**Status:** Canonical Website Content & IA Target\n\n## 1. Domain architecture\n\n### `integratewise.ai`\n\nCompany website.\n\nPurpose:\n\n- company;\n- technology;\n- platform;\n- trust;\n- corporate narrative;\n- resources;\n- market education.\n\n### `spineworkspace.com`\n\nProduct website.\n\nPurpose:\n\n- product;\n- Workbench;\n- Twin;\n- Business Context Spine;\n- solutions;\n- capabilities;\n- pricing;\n- demo conversion;\n- product resources.\n\nThe existing source material already distinguishes IntegrateWise as company/brand and SpineWorkspace as product and identifies the product's Business Context / memory / continuity framing.\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.** fileciteturn21file8L1039-L1055\n\n## 2. IntegrateWise corporate sitemap\n\n```text\nintegratewise.ai\n├── /\n├── /platform\n├── /technology\n├── /solutions\n├── /company\n├── /about\n├── /careers\n├── /partners\n├── /resources\n├── /security\n├── /privacy\n└── /terms\n```\n\n### `/`\n\nPurpose:\n\nEstablish IntegrateWise as the company building infrastructure for human–AI operational continuity.\n\nHero:\n\n> **Operational continuity infrastructure with governed intelligence.**\n\nSupporting:\n\n> **IntegrateWise connects business context, work, intelligence, governance and execution so organizations can operate continuously across the systems they already use.**\n\nCTA:\n\n> Book a Demo\n\nSecondary:\n\n> Explore SpineWorkspace\n\n## 3. SpineWorkspace product sitemap\n\n```text\nspineworkspace.com\n├── /\n├── /product\n├── /platform\n├── /workbench\n├── /twin\n├── /spine\n├── /capabilities\n├── /governance\n├── /connectivity\n├── /solutions\n│   ├── /account-success\n│   ├── /business-operations\n│   ├── /revops\n│   └── /business-intelligence\n├── /pricing\n├── /resources\n│   ├── /guides\n│   ├── /docs\n│   ├── /customer-stories\n│   ├── /architecture\n│   └── /faq\n├── /demo\n├── /contact\n├── /security\n├── /privacy\n└── /terms\n```\n\nThe existing marketing-source material has a compact SaaS sitemap with Home, Features, Solutions, Pricing, Resources and Demo as the primary sales path. fileciteturn21file1L293-L324 This version retains that compression while making the new product ontology explicit.\n\n## 4. Homepage narrative\n\n### Section 1 — Hero\n\nHeadline:\n\n> **Work from the context your business already has.**\n\nAlternative:\n\n> **One operational context for humans and AI.**\n\nSupporting:\n\n> **SpineWorkspace connects the systems your business already uses into Business Context, then gives every person and their Twin the context, work and governed capabilities needed to move outcomes forward.**\n\nCTA:\n\n> Book a Demo\n\nSecondary:\n\n> Explore SpineWorkspace\n\n### Section 2 — The problem\n\n> **Your business already has the information. The problem is keeping it connected to the work.**\n\nShow:\n\n```text\nCRM\nEmail\nChat\nMeetings\nDocuments\nBilling\nSupport\nProjects\nBI\nAI\n   ↓\nfragmented context\n   ↓\nhuman coordination\n   ↓\nlost continuity\n```\n\n### Section 3 — The core idea\n\nHeadline:\n\n> **Business context is the foundation. Work is the outcome.**\n\nExplain:\n\n```text\nSystems\n ↓\nBusiness Context Spine\n ↓\nBusiness Context\n ↓\nWorkbench + Twin\n ↓\nShared Work\n ↓\nOutcome\n```\n\n### Section 4 — Business Context Spine\n\nHeadline:\n\n> **Turn fragmented business data into connected context.**\n\nExplain:\n\n- ingestion;\n- normalization;\n- schema synthesis;\n- entity resolution;\n- relationship linking;\n- event continuity;\n- Organizational Memory.\n\n### Section 5 — Adaptive Workbench\n\nHeadline:\n\n> **Give every person the context their work requires.**\n\nExplain that each user sees shared organizational reality according to:\n\n- role;\n- domain;\n- responsibility;\n- authority;\n- permissions;\n- current work.\n\n### Section 6 — Your Twin\n\nHeadline:\n\n> **Your AI work partner, grounded in your business context.**\n\nShow:\n\n```text\nObserve\nOrient\nDecide\nAllocate\nDelegate\nExecute\nVerify\nReport\n```\n\n### Section 7 — Human + AI Work\n\nHeadline:\n\n> **Let humans and AI share the work — not the authority.**\n\nShow:\n\n```text\nHuman\nJudgment\nRelationships\nAccountability\nExceptions\n\nAI\nContext gathering\nAnalysis\nRepetitive work\nCoordination\nExecution\n\nHuman + AI\nDecision\nStrategy\nCommunication\nOutcome\n```\n\n### Section 8 — Governed execution\n\nHeadline:\n\n> **AI can propose. Governance decides.**\n\nExplain:\n\n```text\nCapability\n ↓\nPolicy\n ↓\nAuthority\n ↓\nApproval\n ↓\nExecution\n ↓\nReceipt\n ↓\nReconciliation\n```\n\n### Section 9 — Communications over the Bridge\n\nHeadline:\n\n> **Work does not stop when the conversation leaves the workspace.**\n\nShow:\n\n```text\nWorkbench\n ↕\nBridge\n ↕\nSlack / Email / Meetings / Chat\n ↕\nTwin / Agents\n ↕\nBusiness Context Spine\n```\n\n### Section 10 — Continuity loop\n\n```text\nContext\n ↓\nWork\n ↓\nAction\n ↓\nSource State\n ↓\nRe-ingestion\n ↓\nReconciliation\n ↓\nKnowledge\n ↓\nContext\n```\n\nHeadline:\n\n> **Every completed action makes the next piece of work better informed.**\n\n### Section 11 — Solutions\n\nRoute to:\n\n- Account Success;\n- Business Operations;\n- Revenue Operations;\n- Business Intelligence.\n\n### Section 12 — CTA\n\n> **See what your work looks like when its context stays connected.**\n\nCTA:\n\n> Book a Demo\n\n## 5. Product page hierarchy\n\n### `/product`\n\nExplain SpineWorkspace as the customer product.\n\n### `/spine`\n\nExplain Business Context, Business Context Spine, memory, continuity and ingestion.\n\n### `/workbench`\n\nExplain adaptive human work.\n\n### `/twin`\n\nExplain the user-specific AI work partner.\n\n### `/capabilities`\n\nExplain business capabilities without coupling the narrative to APIs/MCP.\n\n### `/governance`\n\nExplain authority, approvals, policies, evidence and accountability.\n\n### `/connectivity`\n\nExplain how existing business systems connect without becoming the product.\n\n## 6. Solutions\n\n### Account Success\n\nProblem:\n\n> Customer context is scattered across CRM, support, product usage, communications and billing.\n\nProduct outcome:\n\n> One connected account context with a Twin that prepares, monitors and coordinates renewal work while the CSM retains relationship and commercial judgment.\n\n### Business Operations\n\nProblem:\n\n> Cross-functional operational work is trapped in handoffs.\n\nProduct outcome:\n\n> Shared Work, context and governed execution across teams.\n\n### RevOps\n\nProblem:\n\n> Revenue workflows cross systems and teams, creating reconciliation and handoff gaps.\n\nProduct outcome:\n\n> Connected revenue work with continuity across pipeline, customer, finance and execution state.\n\n### Business Intelligence\n\nProblem:\n\n> Analytics explains isolated signals but not always the operational context behind them.\n\nProduct outcome:\n\n> Business context linked to Work, decisions and outcomes.\n\n## 7. Pricing page\n\nDo not lead with technical resource consumption.\n\nUse:\n\n> **Price the operational work you coordinate, with transparent platform and usage economics.**\n\nPricing needs to remain evidence-backed and should not claim a finalized model unless one is actually approved.\n\n## 8. Resource architecture\n\n```text\nResources\n├── Product Guides\n├── Architecture\n├── Business Context\n├── Work Allocation\n├── Human–AI Work\n├── Governance\n├── Customer Stories\n├── Technical Documentation\n├── FAQ\n└── Continuity Map\n```\n\n## 9. Website voice\n\nUse:\n\n- precise;\n- calm;\n- enterprise-grade;\n- direct;\n- operational;\n- contextual.\n\nAvoid:\n\n- exaggerated autonomy claims;\n- generic AI buzzwords;\n- \"magic\";\n- consumer-style anthropomorphism;\n- claims that tools disappear or are replaced.\n\n## 10. Website proof model\n\nEvery major claim should be supported by one of:\n\n```text\nArchitecture\nProduct Walkthrough\nCustomer Evidence\nMetric\nDemo\nCase Study\nTechnical Contract\n```\n\nDo not use unverifiable proof language.\n\n"}