Unclassified

07 — Industry Landscape

Status: CANONICAL · Commercial OS
Owner: Product Marketing
Last verified: 2026-07-21

Purpose

The map of forces around us — vendor blocs, protocols, infrastructure, capital, and regulation — and what each means for strategy. Competitive positioning lives in 08; this is the terrain it happens on.

Target audience: Founders, investors, senior hires; background for analyst and press conversations.

1. The Six Blocs

Bloc 1 — Suite giants (Microsoft, Google)

Own the productivity surface and bundle copilots "free" into it. Strategy: AI as a retention feature of the suite. Structural limit: their AI's truth is their suite; cross-silo operational state (CRM + support + billing) is outside their model, and governance is a compliance checkbox, not architecture. Implication: never fight for the document/email surface; own the operational work surface they don't model. Their bundling normalizes "AI at work" — free education for our category.

Bloc 2 — System-of-record giants (Salesforce, ServiceNow, SAP, HubSpot)

Adding agents inside their records (Agentforce et al.). Strategy: defend the silo by making it smarter. Structural limit: they cannot sell truth-above-the-silo without cannibalizing the silo; their agents see their own data. Implication: we are their complement in the customer's eyes ("Salesforce is one of the tools we connect") and their long-term strategic threat — expect language adoption, respond with the category rubric (05 §5).

Bloc 3 — Model vendors (OpenAI, Anthropic, Google DeepMind)

Own intelligence; racing into enterprise workspaces from the chat surface. Structural tension: their memory is their memory — organizational truth inside a model vendor is exactly what 82% of the market fears. Implication: they are suppliers, not competitors, in our architecture — provider-agnostic by doctrine; "AI you rent" names the relationship. Watch: any model vendor shipping org-owned, approval-gated memory would be the serious move (none has — their engagement economics forbid it).

Bloc 4 — Work-management & knowledge (Notion, Atlassian, Monday, Asana, Glean)

Closest surface neighbors: they own projects/docs/search and are adding AI. Structural limit: their state is self-authored content, not operational truth from the org's systems; search (Glean) finds, but doesn't hold state or govern action. Implication: sharpest positioning discipline needed here — "the Spine captures what happens, not what someone wrote down."

Bloc 5 — Automation & integration (Zapier, Workato, Make, n8n, iPaaS)

Own the pipes; adding "AI agents" on trigger-action rails. Structural limit: no canonical state, no memory of why, no collaboration surface. Implication: category to escape, partner to embrace — customer automation stacks are execution targets for governed handoff (Canonical Handoff Contract), not rivals.

Bloc 6 — Vertical AI & CS platforms (Gainsight, Totango, Sierra, agent startups)

Own one department's moment. Structural limit: single-department, rules-heavy or autonomy-first. Implication: our wedge collides here first (CS) — "feed your CS platform better data; see what it can't see."

2. Cross-Cutting Forces

Force	State (mid-2026)	Strategic meaning
MCP & open protocols	De-facto standard for tool-AI connection	Our connector economics improve with every adopter; IW-Continuity-Bridge speaks the standard natively. Bet: MCP-first stays right.
Edge infrastructure	Mature (Workers, D1, Vectorize et al.)	97%+ gross margin structure; per-seat COGS $0.55–2.10 (FINANCIAL_MODEL) — a cost moat vs. VM-era incumbents
AI governance regulation	EU AI Act phasing in; oversight requirements spreading	Every new rule converts our architecture from preference to procurement requirement — regulation is our sales tailwind
Capital climate	AI application layer well-funded; autonomy hype cooling toward accountability	Our "governed collaboration" thesis matches the correction; fundraising narrative leans in (68)
Talent expectation	Workers expect AI at work; trust it less than ever	Adoption friction low, trust bar high — exactly our design point

3. Landscape Scenarios (watch conditions)

Scenario	Probability	Our response
Giant adopts our category language	High (expected)	Rubric offense; grade them publicly on owned truth + mandatory approval (05 §5)
Model vendor ships org-owned governed memory	Low-medium	Compete on neutrality + workspace surface; accelerate multi-model proof
MCP fragments into vendor dialects	Low	Bridge abstracts protocols; connector layer already provider-agnostic
Autonomy backlash event (public AI incident)	Medium	Prepared narrative: governance-by-architecture; do not gloat, educate (65 Press Kit holds statement template)

Review cadence: quarterly, with 08 Competitive Landscape; update blocs and scenarios, log changes in the evolution ledger.

KPIs: scenario watch-conditions reviewed quarterly; zero strategic surprises (no bloc move unanticipated by a scenario); partner conversions from Bloc 5 (48 Partner Strategy).