> ## Documentation Index > Fetch the complete documentation index at: https://docs.integratewise.ai/llms.txt > Use this file to discover all available pages before exploring further. # Overview # SpineWorkspace / IntegrateWise — Website Canonical **Status:** Canonical Website Content & IA Target ## 1. Domain architecture ### `integratewise.ai` Company website. Purpose: * company; * technology; * platform; * trust; * corporate narrative; * resources; * market education. ### `spineworkspace.com` Product website. Purpose: * product; * Workbench; * Twin; * Business Context Spine; * solutions; * capabilities; * pricing; * demo conversion; * product resources. The existing source material already distinguishes IntegrateWise as company/brand and SpineWorkspace as product and identifies the product's Business Context / memory / continuity framing. ### The Tier-0 Principle > **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. > > **The Spine gives work its business context.** fileciteturn21file8L1039-L1055 ## 2. IntegrateWise corporate sitemap ```text theme={null} integratewise.ai ├── / ├── /platform ├── /technology ├── /solutions ├── /company ├── /about ├── /careers ├── /partners ├── /resources ├── /security ├── /privacy └── /terms ``` ### `/` Purpose: Establish IntegrateWise as the company building infrastructure for human–AI operational continuity. Hero: > **Operational continuity infrastructure with governed intelligence.** Supporting: > **IntegrateWise connects business context, work, intelligence, governance and execution so organizations can operate continuously across the systems they already use.** CTA: > Book a Demo Secondary: > Explore SpineWorkspace ## 3. SpineWorkspace product sitemap ```text theme={null} spineworkspace.com ├── / ├── /product ├── /platform ├── /workbench ├── /twin ├── /spine ├── /capabilities ├── /governance ├── /connectivity ├── /solutions │ ├── /account-success │ ├── /business-operations │ ├── /revops │ └── /business-intelligence ├── /pricing ├── /resources │ ├── /guides │ ├── /docs │ ├── /customer-stories │ ├── /architecture │ └── /faq ├── /demo ├── /contact ├── /security ├── /privacy └── /terms ``` The 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. ## 4. Homepage narrative ### Section 1 — Hero Headline: > **Work from the context your business already has.** Alternative: > **One operational context for humans and AI.** Supporting: > **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.** CTA: > Book a Demo Secondary: > Explore SpineWorkspace ### Section 2 — The problem > **Your business already has the information. The problem is keeping it connected to the work.** Show: ```text theme={null} CRM Email Chat Meetings Documents Billing Support Projects BI AI ↓ fragmented context ↓ human coordination ↓ lost continuity ``` ### Section 3 — The core idea Headline: > **Business context is the foundation. Work is the outcome.** Explain: ```text theme={null} Systems ↓ Business Context Spine ↓ Business Context ↓ Workbench + Twin ↓ Shared Work ↓ Outcome ``` ### Section 4 — Business Context Spine Headline: > **Turn fragmented business data into connected context.** Explain: * ingestion; * normalization; * schema synthesis; * entity resolution; * relationship linking; * event continuity; * Organizational Memory. ### Section 5 — Adaptive Workbench Headline: > **Give every person the context their work requires.** Explain that each user sees shared organizational reality according to: * role; * domain; * responsibility; * authority; * permissions; * current work. ### Section 6 — Your Twin Headline: > **Your AI work partner, grounded in your business context.** Show: ```text theme={null} Observe Orient Decide Allocate Delegate Execute Verify Report ``` ### Section 7 — Human + AI Work Headline: > **Let humans and AI share the work — not the authority.** Show: ```text theme={null} Human Judgment Relationships Accountability Exceptions AI Context gathering Analysis Repetitive work Coordination Execution Human + AI Decision Strategy Communication Outcome ``` ### Section 8 — Governed execution Headline: > **AI can propose. Governance decides.** Explain: ```text theme={null} Capability ↓ Policy ↓ Authority ↓ Approval ↓ Execution ↓ Receipt ↓ Reconciliation ``` ### Section 9 — Communications over the Bridge Headline: > **Work does not stop when the conversation leaves the workspace.** Show: ```text theme={null} Workbench ↕ Bridge ↕ Slack / Email / Meetings / Chat ↕ Twin / Agents ↕ Business Context Spine ``` ### Section 10 — Continuity loop ```text theme={null} Context ↓ Work ↓ Action ↓ Source State ↓ Re-ingestion ↓ Reconciliation ↓ Knowledge ↓ Context ``` Headline: > **Every completed action makes the next piece of work better informed.** ### Section 11 — Solutions Route to: * Account Success; * Business Operations; * Revenue Operations; * Business Intelligence. ### Section 12 — CTA > **See what your work looks like when its context stays connected.** CTA: > Book a Demo ## 5. Product page hierarchy ### `/product` Explain SpineWorkspace as the customer product. ### `/spine` Explain Business Context, Business Context Spine, memory, continuity and ingestion. ### `/workbench` Explain adaptive human work. ### `/twin` Explain the user-specific AI work partner. ### `/capabilities` Explain business capabilities without coupling the narrative to APIs/MCP. ### `/governance` Explain authority, approvals, policies, evidence and accountability. ### `/connectivity` Explain how existing business systems connect without becoming the product. ## 6. Solutions ### Account Success Problem: > Customer context is scattered across CRM, support, product usage, communications and billing. Product outcome: > One connected account context with a Twin that prepares, monitors and coordinates renewal work while the CSM retains relationship and commercial judgment. ### Business Operations Problem: > Cross-functional operational work is trapped in handoffs. Product outcome: > Shared Work, context and governed execution across teams. ### RevOps Problem: > Revenue workflows cross systems and teams, creating reconciliation and handoff gaps. Product outcome: > Connected revenue work with continuity across pipeline, customer, finance and execution state. ### Business Intelligence Problem: > Analytics explains isolated signals but not always the operational context behind them. Product outcome: > Business context linked to Work, decisions and outcomes. ## 7. Pricing page Do not lead with technical resource consumption. Use: > **Price the operational work you coordinate, with transparent platform and usage economics.** Pricing needs to remain evidence-backed and should not claim a finalized model unless one is actually approved. ## 8. Resource architecture ```text theme={null} Resources ├── Product Guides ├── Architecture ├── Business Context ├── Work Allocation ├── Human–AI Work ├── Governance ├── Customer Stories ├── Technical Documentation ├── FAQ └── Continuity Map ``` ## 9. Website voice Use: * precise; * calm; * enterprise-grade; * direct; * operational; * contextual. Avoid: * exaggerated autonomy claims; * generic AI buzzwords; * "magic"; * consumer-style anthropomorphism; * claims that tools disappear or are replaced. ## 10. Website proof model Every major claim should be supported by one of: ```text theme={null} Architecture Product Walkthrough Customer Evidence Metric Demo Case Study Technical Contract ``` Do not use unverifiable proof language.