{
  "@type": "help_guide",
  "id": "sales-enablement",
  "title": "Sales enablement (battle cards and competitive packs)",
  "kind": "feature",
  "summary": "Nexus turns the competitor research on file into sales assets the client's team can use on calls.",
  "aliases": [
    "battle card",
    "battle cards",
    "competitive pack",
    "sales enablement",
    "sales one-pager",
    "competitor comparison",
    "objection handling"
  ],
  "engine": null,
  "agents": [],
  "related": [
    {
      "id": "competitors",
      "page": "https://nexus.effiqs.com/help/competitors"
    },
    {
      "id": "g2m",
      "page": "https://nexus.effiqs.com/help/g2m"
    },
    {
      "id": "pain-point-mapping",
      "page": "https://nexus.effiqs.com/help/pain-point-mapping"
    }
  ],
  "reviewed": "2026-10-15",
  "sections": [
    {
      "heading": "What it does",
      "key": "what-it-does",
      "markdown": "Nexus turns the competitor research on file into sales assets the client's team can use on calls:\n\n- A **battle card** covers one competitor: who they are, how they position, where they win, where the client wins, landmines to set, objections with responses, proof points, and short \"if they say X, say Y\" lines.\n- A **competitive pack** is a one-pager across the top competitors: a positioning matrix, a comparison of approaches where there is evidence, and a short battle-card summary for each.\n\nBoth are written only from what is stored: the competitor research, the G2M, the brand voice and what Nexus knows about the client. Every claim names its source, and the sources are listed at the end. Nexus never invents numbers, prices or customer names. Each asset is delivered as a branded Google Doc in the client's Sales Enablement folder."
    },
    {
      "heading": "Set it up",
      "key": "set-it-up",
      "markdown": "A battle card needs research on the competitor first.\n\n1. The competitor must be on the competitor list (see the Competitors guide).\n2. Get research on file. Run the competitor sweep: **\"Run competitor moves for this client.\"** A UX teardown also counts. You can also log what the team already knows about a competitor.\n3. If there is no research yet, Nexus says so and tells you how to get it. It does not write a card from general knowledge."
    },
    {
      "heading": "Use it",
      "key": "use-it",
      "markdown": "- **\"Make a battle card for Acme.\"** One competitor. Add who reads it if it matters, such as \"for SDRs\".\n- **\"Build a competitive pack.\"** Uses every competitor with research on file, up to six. Name competitors to choose them.\n- **\"List our battle cards.\"** Shows what has been made, newest first, with the Doc links."
    },
    {
      "heading": "Troubleshooting",
      "key": "troubleshooting",
      "markdown": "- **Nexus says there is no competitor research on file.** Run the competitor sweep or log a note on that competitor, then ask again.\n- **A competitor is missing from the pack.** It has no research yet; Nexus lists it as skipped and says how to fix it.\n- **A table cell says \"Not on file\".** The research doesn't cover that point. Add research, then make the pack again.\n- **The Doc upload failed.** The asset is still saved in Nexus. Ask again to make a new Doc."
    },
    {
      "heading": "Prompts",
      "key": "prompts",
      "markdown": "- \"Make a battle card for Acme.\"\n- \"Build a competitive pack.\"\n- \"List our battle cards.\"\n- \"Run competitor moves for this client.\""
    }
  ],
  "prompts": [
    {
      "text": "Make a battle card for Acme.",
      "tool": "generate_battle_card"
    },
    {
      "text": "Build a competitive pack.",
      "tool": "generate_competitive_pack"
    },
    {
      "text": "List our battle cards.",
      "tool": "list_sales_enablement_assets"
    },
    {
      "text": "Run competitor moves for this client.",
      "tool": "enqueue_run"
    }
  ],
  "page": "https://nexus.effiqs.com/help/sales-enablement",
  "markdown": "https://nexus.effiqs.com/help/sales-enablement.md"
}