Unclassified

05 — Category Definition

Status: HISTORICAL REFERENCE · Superseded for current category definition
Owner: Founder + Product Marketing
Last verified: 2026-07-21

Current authority: 00 Current GTM Canon
supersedes this document's category name, definition, requirements, and
category-creation plan as of 2026-07-22. The historical text below is
retained as an evolution record and must not be used for new external-facing
work until migrated.

Purpose

Define 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.

Target audience: Analysts, press, investors, senior prospects; internally, everyone who frames the company.

1. The Category

Workspace for Human and AI Collaborative Work

Short forms: "the collaborative work workspace" · "the Workspace" (in context). Evolution ledger and forbidden alternates: 18 Terminology §1.

Definition (the sentence analysts should repeat):

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.

2. Why a New Category (and not a niche of an old one)

Existing categories structurally cannot hold the product:

Adjacent category	Why we don't fit
AI assistant / copilot	Assistants converse beside work; we share state inside work. No collaboration model, no owned truth.
iPaaS / integration platform	Moves data without meaning, memory, or governance. We connect context, not just apps.
BI / dashboards	Read-only yesterday. Workbenches are read-write operational surfaces. "Dashboards show work. Workbenches do work."
Knowledge base / wiki	Stores what people write. The Spine captures what happens, with provenance.
CS platform / CRM add-on	One department, one system of record. We're role-composed across all departments, above all systems.
Agent platform	Races toward autonomy. We architect for governed collaboration — the opposite bet.

A 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.

3. Category Requirements (the grading rubric we publish)

To qualify as a Workspace for Human and AI Collaborative Work, a system must have all five:

Shared work surface — human and AI operate on the same live work object, not a chat beside it.
Canonical operational state — truth assembled across the org's tools, owned by the organization, with provenance.
Governed collaboration — AI proposes; humans approve; every consequential action is gated and audited.
Persistent continuity — context survives sessions, tools, personnel, and AI-model changes.
Capability execution — approved actions actually execute across connected systems (not advice-only).

The rubric is our analyst artifact (66) and evaluation checklist for buyers (43 Procurement FAQ). Scoring competitors against it: 08 Competitive Landscape. 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.

4. Category Narrative (why now — compressed from 04)

Fragmentation 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.

5. Category Strategy & Defense

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.

Category creation plan:

Phase	Move	Artifact
Now (design partners)	Manifesto + rubric published; founder-led narrative	Manifesto post (56), category page (54)
Launch	Name the category in every press/launch asset (51)	Launch narrative, press kit (65)
Post-launch	Analyst briefings with rubric; invite scoring of all vendors	AR deck (66)
Scale	Community + events own the vocabulary (62, 63)	Category report, annual survey

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.

KPIs: category-term search volume and share of voice (55 SEO); analyst usage of our definition; % of inbound describing us in category terms; competitor adoption of the vocabulary (a win indicator, tracked not feared).