{"slug":"strategy/market-positioning/05-category-definition","title":"05 — Category Definition","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/market-positioning/05-category-definition.mdx","bytes":7789,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: HISTORICAL REFERENCE · Superseded for current category definition\nOwner: Founder + Product Marketing\nLast verified: 2026-07-21\n\n> **Current authority:** [00 Current GTM Canon](../09-gtm/00-current-gtm-canon.md)\n> supersedes this document's category name, definition, requirements, and\n> category-creation plan as of 2026-07-22. The historical text below is\n> retained as an evolution record and must not be used for new external-facing\n> work until migrated.\n\n---\n\n## Purpose\n\nDefine the category we intend to create and lead: its name, boundaries, requirements, and the rules for defending it. Category definition is offense — whoever writes the category's dictionary grades every vendor in it.\n\n**Target audience:** Analysts, press, investors, senior prospects; internally, everyone who frames the company.\n\n---\n\n## 1. The Category\n\n> **Workspace for Human and AI Collaborative Work**\n\nShort forms: \"the collaborative work workspace\" · \"the Workspace\" (in context). Evolution ledger and forbidden alternates: [18 Terminology §1](../03-positioning-messaging/18-terminology-guide.md).\n\n**Definition (the sentence analysts should repeat):**\n\n> A workspace for human and AI collaborative work is a system where people and governed AI counterparts do work together on shared surfaces, over canonical operational state the organization owns, with human approval and audit on every consequential action.\n\n---\n\n## 2. Why a New Category (and not a niche of an old one)\n\nExisting categories structurally cannot hold the product:\n\n| Adjacent category            | Why we don't fit                                                                                                   |\n| ---------------------------- | ------------------------------------------------------------------------------------------------------------------ |\n| AI assistant / copilot       | Assistants converse beside work; we share state inside work. No collaboration model, no owned truth.               |\n| iPaaS / integration platform | Moves data without meaning, memory, or governance. We connect _context_, not just apps.                            |\n| BI / dashboards              | Read-only yesterday. Workbenches are read-write operational surfaces. \"Dashboards show work. Workbenches do work.\" |\n| Knowledge base / wiki        | Stores what people write. The Spine captures what _happens_, with provenance.                                      |\n| CS platform / CRM add-on     | One department, one system of record. We're role-composed across all departments, above all systems.               |\n| Agent platform               | Races toward autonomy. We architect for governed collaboration — the opposite bet.                                 |\n\nA product that is mispositioned into any of these loses: priced like iPaaS, evaluated like a chatbot, or dismissed as another dashboard. Category creation is not vanity — it's the pricing and evaluation frame.\n\n---\n\n## 3. Category Requirements (the grading rubric we publish)\n\nTo qualify as a Workspace for Human and AI Collaborative Work, a system must have **all five**:\n\n1. **Shared work surface** — human and AI operate on the same live work object, not a chat beside it.\n2. **Canonical operational state** — truth assembled across the org's tools, owned by the organization, with provenance.\n3. **Governed collaboration** — AI proposes; humans approve; every consequential action is gated and audited.\n4. **Persistent continuity** — context survives sessions, tools, personnel, and AI-model changes.\n5. **Capability execution** — approved actions actually execute across connected systems (not advice-only).\n\nThe rubric is our analyst artifact ([66](../12-corporate/66-analyst-relations.md)) and evaluation checklist for buyers ([43 Procurement FAQ](../07-sales/43-procurement-faq.md)). Scoring competitors against it: [08 Competitive Landscape](08-competitive-landscape.md). By construction and honest audit, only IntegrateWise currently meets all five — requirement 2 (owned truth with provenance) and 3 (mandatory approval) are the fork most vendors cannot take.\n\n---\n\n## 4. Category Narrative (why now — compressed from [04](../01-foundation/04-long-term-narrative.md))\n\nFragmentation made the person the integration layer. Bolted-on AI made fragmentation worse and burned trust (~80% quiet demotion). Three forces make the recentering inevitable now: the measurable Empty Context Tax, protocol + edge-infrastructure maturity (MCP, serverless edge), and institutional demand for human oversight (76% of enterprises). The category is the shape of the resolution: work recenters into one workspace; truth consolidates under organizational ownership; AI joins the bench under governance.\n\n---\n\n## 5. Category Strategy & Defense\n\n**Naming discipline:** we always say the full category name in first mention of every asset; shorthand after. We never accept \"AI workspace\" (ambiguous, model-vendor-friendly) or \"agentic workspace\" (autonomy frame) as substitutes.\n\n**Category creation plan:**\n\n| Phase                 | Move                                                                                                                                | Artifact                                                                                                               |\n| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |\n| Now (design partners) | Manifesto + rubric published; founder-led narrative                                                                                 | Manifesto post ([56](../11-marketing/56-content-strategy.md)), category page ([54](../10-website/54-landing-pages.md)) |\n| Launch                | Name the category in every press/launch asset ([51](../09-gtm/51-launch-strategy.md))                                               | Launch narrative, press kit ([65](../12-corporate/65-press-kit.md))                                                    |\n| Post-launch           | Analyst briefings with rubric; invite scoring of all vendors                                                                        | AR deck ([66](../12-corporate/66-analyst-relations.md))                                                                |\n| Scale                 | Community + events own the vocabulary ([62](../11-marketing/62-community-strategy.md), [63](../11-marketing/63-events-strategy.md)) | Category report, annual survey                                                                                         |\n\n**Contested-category playbook:** when a giant adopts similar language (expected — Microsoft/Salesforce will say \"humans and agents working together\"), we respond with the rubric, not volume: publish the five requirements, grade publicly, and emphasize the two they will fail — _owned truth_ (their truth is their silo) and _mandatory approval_ (their pitch is autonomy). Their adoption of our language is distribution for the category; the rubric keeps the definition ours.\n\n**KPIs:** category-term search volume and share of voice ([55 SEO](../10-website/55-seo-strategy.md)); analyst usage of our definition; % of inbound describing us in category terms; competitor adoption of the vocabulary (a _win_ indicator, tracked not feared).\n\n---\n\n**Related:** [11 Positioning](../03-positioning-messaging/11-positioning.md) · [04 Long-term Narrative](../01-foundation/04-long-term-narrative.md) · [08 Competitive Landscape](08-competitive-landscape.md) · [66 Analyst Relations](../12-corporate/66-analyst-relations.md)\n"}