08 — Competitive Landscape
Status: CANONICAL · Commercial OS
Owner: Product Marketing
Last verified: 2026-07-21
Purpose
Who we actually meet in deals, how each rival's story works, and where each one structurally breaks against the category rubric. Battle-ready per-competitor material lives in 09 Battle Cards; this document is the strategic map.
Target audience: Sales, marketing, product, founders.
1. The Real Competitive Order (by deal frequency)
- Status quo / do nothing — the Human API endures because it's free-looking. Beat with quantified pain (29 ROI).
- Internal builds — "we made a dashboard." Beat with maintenance truth + intelligence gap.
- General assistants (ChatGPT/Claude/Gemini in a tab) — "we already use AI." Beat with the Four Enemies.
- Suite copilots (Microsoft 365 Copilot, Gemini for Workspace) — "it's included." Beat with cross-silo truth + governance.
- CS platforms (Gainsight, Totango) — wedge-market incumbent. Beat with cross-stack signals + no rules engine.
- Record-vendor agents (Salesforce Agentforce, HubSpot Breeze) — "our CRM does AI now." Beat with above-the-silo neutrality.
- Search/knowledge AI (Glean, Notion AI) — "we can find everything." Beat with state vs. documents; action vs. answers.
- Automation agents (Zapier, Workato, n8n agents) — rarely head-to-head; category confusion risk. Reframe, then partner.
2. Category Rubric Scorecard
Grading everyone against the five category requirements (05 §3): shared work surface · owned canonical state · governed collaboration · persistent continuity · capability execution.
| Competitor | Surface | Owned state | Governed | Continuity | Execution | Verdict |
|---|---|---|---|---|---|---|
| IntegrateWise | ✅ shared workbench | ✅ Spine + provenance | ✅ approval + audit by architecture | ✅ TruthLayer, survives model swap | ✅ governed actions via connected tools | Category-complete |
| M365 Copilot | ⚠️ sidecar in each app | ❌ truth = the suite | ⚠️ admin policy, not action gates | ⚠️ within-suite only | ⚠️ suite actions only | Suite feature |
| Gemini for Workspace | ⚠️ sidecar | ❌ suite silo | ⚠️ policy | ⚠️ suite | ⚠️ suite | Suite feature |
| ChatGPT/Claude Enterprise | ❌ chat destination | ❌ vendor-held memory | ❌ auto-memory, no action gates | ⚠️ per-user memory | ⚠️ nascent tool-use | Assistant |
| Salesforce Agentforce | ⚠️ inside CRM | ❌ truth = Salesforce | ⚠️ configurable | ⚠️ CRM-scoped | ⚠️ CRM-scoped | Silo agent |
| Gainsight | ❌ dashboards | ❌ CRM-derived, rules-based | ❌ rules ≠ governance | ⚠️ CS-scoped | ⚠️ playbooks | Department platform |
| Glean | ❌ search box | ⚠️ index ≠ state (no write path, no provenance-of-truth) | ❌ read-only | ⚠️ index freshness | ❌ none | Search |
| Notion AI | ⚠️ in-doc | ❌ self-authored content only | ❌ none | ⚠️ workspace docs | ❌ none | Docs AI |
| Zapier/Workato agents | ❌ config UI | ❌ no state model | ⚠️ run logs ≠ approval | ❌ stateless flows | ✅ execution (ungoverned) | Automation |
| Internal builds | ❌ dashboards | ⚠️ partial warehouse | ❌ none | ❌ leaves with the engineer | ❌ none | Status quo |
The pattern: everyone has a fragment. Nobody else has owned truth + mandatory approval — the two requirements that conflict with every incumbent's business model (silo defense or engagement economics). That's the structural read: our moats are their strategy taxes.
3. Competitive Postures
| Versus | Posture | One line |
|---|---|---|
| Suites | Coexist — we're the operational layer over the stack they're part of | "Keep Copilot for documents. IntegrateWise is where your operations live." |
| Record vendors | Complement now, category-compete later | "Salesforce is one of the tools we connect." |
| Model vendors | Suppliers — provider-agnostic by doctrine | "Truth you own. AI you rent." |
| CS platforms | Displace in wedge (or feed, when entrenched) | "We catch what it can't see — signals across the whole stack." |
| Automation | Partner — execution targets for governed handoff | "Your Zapier gets smarter instructions." |
| Assistants | Reframe — different job entirely | "That's a chat tab. This is where the work lives." |
| Internal builds | Respect, then retire | "What happens when its engineer leaves?" |
4. Standing Intelligence Discipline
- Quarterly: refresh scorecard, re-verify "only approval-gated memory" claim, update battle cards; log competitor moves against 07 scenarios.
- Every loss tagged to a competitor + moat in CRM (74 Sales Metrics); any moat losing >30% of matchups triggers repositioning review (17).
- Never name competitors in advertising; sales conversations only (standing rule).
KPIs: competitive win rate by rival; % deals with no competitor (category creation working); scorecard freshness ≤ 90 days.
Related: 09 Battle Cards · 17 Differentiation · 07 Industry Landscape · 41 Objection Handling