Unclassified

09 — Competitive Battle Cards

Status: CANONICAL · Commercial OS
Owner: Sales + Product Marketing
Last verified: 2026-07-21
Rules: sales conversations only — never in advertising. Compare categories respectfully; never mock brands. Lead with their pain, not our feature. Anchor the doctrine once per conversation.

Purpose

Deal-ready material per competitor: how to recognize them, where they beat us, where we beat them, landmines to plant early, and the flip for their favorite objection.

Target audience: Sales (primary), founders on calls, SEs.

How to use: read the card before the call when a rival is known; in-call, reach for the Landmine early (before the rival is named) and the Flip when they're raised.

Card 1 — Microsoft 365 Copilot (and Gemini for Workspace)

You'll hear: "We get Copilot free with E5." / "IT standardized on Microsoft AI."
Their real strength: distribution, price framing ("included"), IT comfort, genuinely good at document/email work inside the suite.
Where they win: if the evaluation is "AI for writing things," concede it — that's not our deal.
Where we win: operational work across the stack. Copilot cannot see HubSpot + Zendesk + Stripe + Slack as one account truth; it has no canonical state, no approval gates on actions, no cross-tool memory with provenance.
Landmine (plant early): "When your team preps a QBR, how much of that context lives in Office documents — versus your CRM, support desk, and billing?" (Answer is always: mostly outside.)
Flip: "Keep Copilot — it's good at documents. IntegrateWise is where your operations live: one workbench over all the systems Copilot can't see, with approval on anything that acts. They're not substitutes; only one of them knows your accounts."
Proof to show: Entity360 assembling cross-tool truth; approval + audit on a Twin action.
Trap to avoid: arguing model quality — irrelevant and unwinnable. We rent models too.

Card 2 — ChatGPT / Claude Enterprise (general assistants)

You'll hear: "We already use ChatGPT — the team likes it."
Their real strength: familiarity, versatility, low price, real utility for drafting/thinking.
Where they win: individual creative/analytical tasks with no org context needed.
Where we win: the Four Enemies. Amnesia (session memory, or auto-written guesses), Babysitting (no follow-through), Hallucination (no grounding in verified truth), Human API (the user still shuttles context in and out by hand).
Landmine: "What does your team actually use it for today — and what did they stop using it for?" (Surfaces the Quiet Demotion — every team has this story.)
Flip: "That's exactly the tool your team demoted to writing emails — not because the model is bad, but because it starts blank, guesses its memory, and can't touch your systems. IntegrateWise is the opposite architecture: the Twin starts in your context, remembers only what you approve, and acts only with your approval. ChatGPT remembers what it wants. IntegrateWise remembers what you approve."
Proof to show: Twin answering from grounded account context with evidence links; TruthLayer approval queue.
Trap to avoid: dismissing the assistant — the team likes it; position as different jobs.

Card 3 — Salesforce Agentforce (and HubSpot Breeze)

You'll hear: "Our CRM is adding agents — why not wait?"
Their real strength: the data's already there (for CRM-shaped data); procurement path exists; roadmap theater is persuasive.
Where they win: CRM-native task automation for CRM-only workflows, all-Salesforce shops with no stack sprawl (rare — disqualify if true).
Where we win: the silo boundary. Their agent's world is the CRM; account truth lives across support, billing, product usage, and conversation. And their incentive is deepening the silo, not neutralizing it.
Landmine: "When an account goes sideways, where do the early signals actually show up first — the CRM, or support tickets and usage data?"
Flip: "Salesforce is one of the tools we connect — keep it as your system of record. The question is where the whole truth lives. An agent inside one silo sees one silo. The Spine assembles all of them, and your CRM gets better data back."
Proof to show: churn signal composed from usage + support + billing + email — nothing purely CRM-visible.
Trap to avoid: "Salesforce is legacy" talk — buyers own it and like it; we complement.

Card 4 — Gainsight / Totango (CS platforms)

You'll hear: "We already have a CS platform." (Wedge-market incumbent — most common named rival.)
Their real strength: CS-specific workflows, health-score vocabulary, install base, playbook culture.
Where they win: large CS orgs with years of configured rules and admin investment — displacement is a slog; consider the feed posture instead.
Where we win: no rules engine to configure and maintain; signals reasoned across the whole stack, not CRM-derived; approval-gated memory (they have none); any-department expansion (they're CS-only); per-seat price vs. $2,500+/mo platform minimums.
Landmine: "How many admin-hours a month go into keeping the health-score rules current — and did the score catch your last surprise churn?"
Flip: "Gainsight tells you what happened in the CRM. IntegrateWise tells you what's happening across everything — and it doesn't ask your team to write rules. If you keep Gainsight, we make it smarter; most teams eventually notice they've stopped opening it."
Proof to show: signal with cross-stack evidence chain; QBR prep 4 hrs → 12 min.
Trap to avoid: feature-by-feature CS checklists — their turf; keep it on cross-stack truth + governed AI.

Card 5 — Glean (enterprise search / knowledge AI)

You'll hear: "We're rolling out Glean so people can find anything."
Their real strength: search quality, connector breadth, "one search bar" simplicity.
Where they win: the find-a-document job. Not our job; say so.
Where we win: search returns documents; work needs state. Glean can find the renewal deck; it doesn't know the renewal is at risk, can't hold the commitment you made Tuesday, and can't draft-and-gate the follow-up. Read-only vs. read-write-govern.
Landmine: "After someone finds the document — where does the work happen, and what remembers the outcome?"
Flip: "Glean answers 'where is it?' IntegrateWise answers 'what's true, what changed, and what should we do — and did anyone approve it?' Search is a feature of the workspace, not the workspace."
Proof to show: workbench state (commitments, signals, timeline) that no search index holds; Store in Spine.
Trap to avoid: competing on retrieval quality benchmarks.

Card 6 — Notion AI / Atlassian Rovo (work-management AI)

You'll hear: "Our wiki/projects tool has AI now — same thing?"
Their real strength: beloved surfaces, cheap add-on pricing, docs+projects gravity.
Where we win: their AI reasons over what people wrote; the Spine holds what happened — from the systems, with provenance. Self-authored content is opinion; operational truth is evidence. No governance, no capability execution, no cross-system state.
Landmine: "When the wiki page about the account disagrees with the billing system, which one does your AI believe?"
Flip: "Documentation stores what you write. The Spine captures what happens across every tool — with a source on every fact. Keep Notion for pages; workbenches are for accounts, pipeline, and operations."
Proof to show: provenance panel — every field with its source system and freshness.
Trap to avoid: attacking their beloved product; align to different objects (pages vs. operational entities).

Card 7 — Zapier / Workato / n8n (automation + "AI agents")

You'll hear: "We'll just wire it with Zapier and add an AI step."
Their real strength: cheap, familiar, genuinely useful for stateless A→B automation.
Where we win: automation moves data; it doesn't understand it, remember it, or govern it. No canonical state, no evidence, no approval semantics, no memory of why. Fragile at exactly the moments that matter (exceptions, judgment).
Landmine: "Who reviews what the AI step decided before it writes to your CRM — and where's that decision recorded?"
Flip: "Keep your automation stack — it's the hands. IntegrateWise is the judgment in front of it: assembled truth, a reasoned proposal, your approval, an audit trail — then governed execution through the tools you already trust. Zapier connects tools. We connect context."
Proof to show: governed handoff — proposal → approval → execution with audit.
Trap to avoid: being priced against a $30/mo automation plan — different category, reframe or walk.

Card 8 — Internal builds ("we made our own dashboard")

You'll hear: "Our ops engineer built exactly what we need."
Their real strength: pride, sunk cost, custom fit, zero license line item.
Where we win: static vs. reasoning (a dashboard shows the usage drop; the Twin correlates it with the ticket spike and contract date and drafts the response); maintenance forever; the continuity risk — the build's logic lives in one engineer's head.
Landmine: "What happens to it when its builder changes teams?"
Flip: "Your dashboard shows data — that took real work, keep it. IntegrateWise adds what a dashboard can't: reasoning, memory, and governed action. And when people change roles, the intelligence stays — because it lives in your Spine, not in someone's head."
Proof to show: side-by-side — their metric view vs. the same entity with signals, evidence, and a prepared next step.
Trap to avoid: insulting the build (you're insulting the buyer's team).

Universal Rules of Engagement

Never open competitive. Let them name the rival; plant landmines beforehand.
Concede honestly what each rival is good at — credibility is the currency of every card above.
Always return to the two forks nobody else takes: owned truth (Spine) + mandatory approval (governance). Every card resolves there.
One doctrine anchor per conversation: "Truth you own. AI you rent. Approval in between."
Log the matchup in CRM with rival + outcome + which flip was used (74 Sales Metrics).

KPIs: win rate per card; landmine usage rate in recorded calls; card freshness ≤ 90 days (08 quarterly review feeds updates).