{"slug":"strategy/business-strategy/09-competitive-battle-cards","title":"09 — Competitive Battle Cards","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/business-strategy/09-competitive-battle-cards.mdx","bytes":10938,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CANONICAL · Commercial OS\nOwner: Sales + Product Marketing\nLast verified: 2026-07-21\nRules: 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.\n\n---\n\n## Purpose\n\nDeal-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.\n\n**Target audience:** Sales (primary), founders on calls, SEs.\n\n**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.\n\n---\n\n## Card 1 — Microsoft 365 Copilot (and Gemini for Workspace)\n\n**You'll hear:** \"We get Copilot free with E5.\" / \"IT standardized on Microsoft AI.\"\n**Their real strength:** distribution, price framing (\"included\"), IT comfort, genuinely good at document/email work inside the suite.\n**Where they win:** if the evaluation is \"AI for writing things,\" concede it — that's not our deal.\n**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.\n**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.)\n**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.\"\n**Proof to show:** Entity360 assembling cross-tool truth; approval + audit on a Twin action.\n**Trap to avoid:** arguing model quality — irrelevant and unwinnable. We rent models too.\n\n## Card 2 — ChatGPT / Claude Enterprise (general assistants)\n\n**You'll hear:** \"We already use ChatGPT — the team likes it.\"\n**Their real strength:** familiarity, versatility, low price, real utility for drafting/thinking.\n**Where they win:** individual creative/analytical tasks with no org context needed.\n**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).\n**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.)\n**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.\"\n**Proof to show:** Twin answering from grounded account context with evidence links; TruthLayer approval queue.\n**Trap to avoid:** dismissing the assistant — the team likes it; position as different jobs.\n\n## Card 3 — Salesforce Agentforce (and HubSpot Breeze)\n\n**You'll hear:** \"Our CRM is adding agents — why not wait?\"\n**Their real strength:** the data's already there (for CRM-shaped data); procurement path exists; roadmap theater is persuasive.\n**Where they win:** CRM-native task automation for CRM-only workflows, all-Salesforce shops with no stack sprawl (rare — disqualify if true).\n**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.\n**Landmine:** \"When an account goes sideways, where do the early signals actually show up first — the CRM, or support tickets and usage data?\"\n**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.\"\n**Proof to show:** churn signal composed from usage + support + billing + email — nothing purely CRM-visible.\n**Trap to avoid:** \"Salesforce is legacy\" talk — buyers own it and like it; we complement.\n\n## Card 4 — Gainsight / Totango (CS platforms)\n\n**You'll hear:** \"We already have a CS platform.\" (Wedge-market incumbent — most common named rival.)\n**Their real strength:** CS-specific workflows, health-score vocabulary, install base, playbook culture.\n**Where they win:** large CS orgs with years of configured rules and admin investment — displacement is a slog; consider the feed posture instead.\n**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.\n**Landmine:** \"How many admin-hours a month go into keeping the health-score rules current — and did the score catch your last surprise churn?\"\n**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.\"\n**Proof to show:** signal with cross-stack evidence chain; QBR prep 4 hrs → 12 min.\n**Trap to avoid:** feature-by-feature CS checklists — their turf; keep it on cross-stack truth + governed AI.\n\n## Card 5 — Glean (enterprise search / knowledge AI)\n\n**You'll hear:** \"We're rolling out Glean so people can find anything.\"\n**Their real strength:** search quality, connector breadth, \"one search bar\" simplicity.\n**Where they win:** the find-a-document job. Not our job; say so.\n**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.\n**Landmine:** \"After someone finds the document — where does the _work_ happen, and what remembers the outcome?\"\n**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.\"\n**Proof to show:** workbench state (commitments, signals, timeline) that no search index holds; Store in Spine.\n**Trap to avoid:** competing on retrieval quality benchmarks.\n\n## Card 6 — Notion AI / Atlassian Rovo (work-management AI)\n\n**You'll hear:** \"Our wiki/projects tool has AI now — same thing?\"\n**Their real strength:** beloved surfaces, cheap add-on pricing, docs+projects gravity.\n**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.\n**Landmine:** \"When the wiki page about the account disagrees with the billing system, which one does your AI believe?\"\n**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.\"\n**Proof to show:** provenance panel — every field with its source system and freshness.\n**Trap to avoid:** attacking their beloved product; align to different objects (pages vs. operational entities).\n\n## Card 7 — Zapier / Workato / n8n (automation + \"AI agents\")\n\n**You'll hear:** \"We'll just wire it with Zapier and add an AI step.\"\n**Their real strength:** cheap, familiar, genuinely useful for stateless A→B automation.\n**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).\n**Landmine:** \"Who reviews what the AI step decided before it writes to your CRM — and where's that decision recorded?\"\n**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.\"\n**Proof to show:** governed handoff — proposal → approval → execution with audit.\n**Trap to avoid:** being priced against a $30/mo automation plan — different category, reframe or walk.\n\n## Card 8 — Internal builds (\"we made our own dashboard\")\n\n**You'll hear:** \"Our ops engineer built exactly what we need.\"\n**Their real strength:** pride, sunk cost, custom fit, zero license line item.\n**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.\n**Landmine:** \"What happens to it when its builder changes teams?\"\n**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.\"\n**Proof to show:** side-by-side — their metric view vs. the same entity with signals, evidence, and a prepared next step.\n**Trap to avoid:** insulting the build (you're insulting the buyer's team).\n\n---\n\n## Universal Rules of Engagement\n\n1. **Never open competitive.** Let them name the rival; plant landmines beforehand.\n2. **Concede honestly** what each rival is good at — credibility is the currency of every card above.\n3. **Always return to the two forks nobody else takes:** owned truth (Spine) + mandatory approval (governance). Every card resolves there.\n4. **One doctrine anchor per conversation:** \"Truth you own. AI you rent. Approval in between.\"\n5. **Log the matchup** in CRM with rival + outcome + which flip was used ([74 Sales Metrics](../13-operations/74-sales-metrics.md)).\n\n**KPIs:** win rate per card; landmine usage rate in recorded calls; card freshness ≤ 90 days ([08](08-competitive-landscape.md) quarterly review feeds updates).\n\n---\n\n**Related:** [08 Competitive Landscape](08-competitive-landscape.md) · [17 Differentiation](../03-positioning-messaging/17-differentiation.md) · [41 Objection Handling](../07-sales/41-objection-handling.md) · [37 Sales Playbook](../07-sales/37-sales-playbook.md)\n"}