Get Started with Competitive Intelligence
Track a competitor, create an evidence-backed battlecard, and publish reviewed guidance for Sales.
Competitive Intelligence: 1 pages
Competitive Intelligence turns competitor evidence into guidance for sales conversations. Start with one competitor and one useful battlecard, then improve it with feedback from your team.
In the app, open Intelligence → Getting started at the bottom of the sidebar for the short guide.
Find guidance for a conversation
Open Sales library to browse published battlecards, find answers to objections, prepare for a deal, or compare products. Check supporting evidence and review warnings before using a claim. Request guidance if the answer you need is missing.
Sales readers see published guidance. Authors work on a separate draft, so saving edits does not change what the team sees.
Before you begin
Your workspace needs access to Competitive Intelligence. Ask an administrator if it is unavailable.
| Permission | What it allows |
|---|---|
| CI View | Read published guidance. |
| CI Manage | Create, edit, publish, and unpublish battlecards. |
| CI Manage and Run | Add tracked competitors and start monitoring, subject to research access and integration settings. |
Monitoring must be configured, with Exa background access enabled in Research integrations. Checks use research credits or your connected provider account. If the app says monitoring setup is incomplete, an administrator needs to finish connecting it. You can still edit a battlecard for an existing tracked competitor without running new research.
1. Track your first competitor
- Open Competitors.
- Choose Track competitor in the sidebar header.
- Enter the competitor name and website domain.
- Describe What should we follow? Be specific: for example, pricing, integrations, or product changes relevant to your buyers.
- Choose daily or weekly checks and select Start tracking.
Review the findings and their original sources. A discovered claim is evidence to assess, not automatically approved sales guidance.
2. Create a battlecard draft
Open Battlecards, choose Create battlecard in the sidebar header, select the competitor, and choose Create draft.
There is one battlecard per competitor. If it already exists, Coherence opens it. Creating and editing cards does not use research credits.
3. Fill in the guidance
On Edit draft, keep each section useful during a live conversation.
Start with an AI draft
With CI Manage and Run permission, choose Draft with AI. Save any existing edits first. Select the sections you want, then Generate draft. Preview the suggestions and use only the sections you want to replace. Your other sections remain unchanged.
AI uses saved competitor research, findings reviewed as relevant, and sourced published product comparisons. It uses AI credits and does not launch fresh web research. If own-product evidence is missing, add a sourced comparison rather than expecting AI to invent an advantage. Evidence gaps remain visible for review.
You can also ask Chat or Copilot: “Draft a battlecard for HubSpot using our saved research.” It finds the tracked competitor and saves an editable draft, returning a link to the editor. You can request selected sections, such as “Update only the objection handling in our HubSpot battlecard.”
Edit each generated section and check I reviewed … and its supporting evidence. Editing the section or its sources requires that acknowledgement again. Saving a draft never publishes it; Publish battlecard remains a separate author action.
What each section covers
| Section | What to write |
|---|---|
| Quick pitch | Who this comparison helps and why it matters. |
| Where we win | Verified differences connected to customer needs, including evidence for your own product. |
| Objection handling | The buyer's objection, a respectful response, and supporting evidence. |
| Discovery questions | Open questions that uncover requirements and tradeoffs. |
| Watch-outs | Competitor strengths, situations where you may not fit, and claims sellers should avoid. |
Add source links or competitor findings to factual sections. Check dates, product editions, and the scope of each claim. Use Save draft to retain work in progress.
For example, an objection such as “HubSpot is cheaper” could lead to a discovery question: “Which edition, seats, onboarding, and AI usage are included in the quote?” Avoid claiming a cost advantage until you have comparable evidence.
4. Review and publish
Before choosing Publish battlecard in the Edit draft toolbar:
- Complete Quick pitch, Where we win, and Objection handling.
- Add supporting evidence to every populated factual section. Discovery questions does not require a source.
- Check every claim against its source.
- Complete any practice scenarios you added.
Publishing confirms your review and starts the configured review period. Open Sales battlecard to inspect the published version, then find it in the Sales library.
Later changes remain in the draft until you publish again. Use this separation to update guidance without exposing unfinished edits to Sales.
5. Practice and maintain the card
After the first publication, authors with Run permission can use Generate drafts in Objection handling to create editable practice scenarios from published guidance. Review the scenarios, edit them, and publish the updated card. This is separate from Draft with AI, which drafts the battlecard's guidance sections.
Review seller feedback, new competitor findings, and Needs review indicators. Correct outdated guidance and publish the reviewed update so the team uses the current version.
Common questions
Why is Create battlecard unavailable?
You need CI Manage permission and a tracked competitor. Ask a teammate with setup permissions to add a competitor if none exists.
Why can't I publish?
Check the required sections, supporting evidence, and any incomplete practice scenarios. Follow the validation message shown in the editor.
Why can't Sales see my changes?
Saving a draft does not publish it. Confirm that you published the changes and are viewing the current Sales battlecard.