Build a deal-specific competitive battlecard for an upcoming sales conversation. Treat uncertain competitor information as a research gap, not a fact. Our product and differentiated capabilities: [OUR PRODUCT] Competitor and verified evidence about them: [COMPETITOR EVIDENCE] Prospect, use case, and current situation: [PROSPECT CONTEXT] Known buying criteria, stakeholders, and objections: [DEAL INTELLIGENCE] Desired next step: [NEXT STEP] First separate facts, prospect statements, reasonable hypotheses, and unknowns. Identify the business problem the prospect is trying to solve and rank the buying criteria by likely importance. Do not frame the battlecard around feature checklists alone. Produce a one-page battlecard with these sections: 1. Deal snapshot: trigger, use case, incumbent or status quo, stakeholders, decision process, and open questions. 2. Positioning: a 30-second point of view that links our strengths to the prospect’s stated priorities, plus three differentiated proof points from the supplied facts. 3. Competitive risks: what the competitor is likely to win on, where we are vulnerable, and what evidence would change the assessment. 4. Discovery: six open questions designed to test assumptions about workflow, implementation, economics, risk, and success measures. Label the reason for each question. 5. Objection handling: three short talk tracks using acknowledge, clarify, evidence, and next question. Never make unsupported comparisons, pricing claims, or promises. 6. Action plan: the exact meeting outcome to seek, owner, and evidence needed before the next stage. Include a “do not say” section for claims we cannot substantiate. Before finalizing, check that every competitor statement traces to supplied evidence and that the proposed next step is realistic for the deal stage. Ask up to three clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [OUR PRODUCT] | Enter your product’s relevant capabilities, limitations, customer proof, and implementation facts. | FlowLedger automates month-end close checklists for multi-entity finance teams; native NetSuite sync, role-based approvals, audit trail, and implementation usually takes 3-5 weeks. We have two published customer stories showing 25% faster close cycles. |
| [COMPETITOR EVIDENCE] | Enter verified competitor facts, customer statements, public materials, and clearly labeled unknowns. | ClosePilot is the incumbent candidate. Its public site emphasizes task management and Slack alerts. Prospect’s controller said ClosePilot quoted lower per-user pricing. We do not know its NetSuite sync depth or implementation time. |
| [PROSPECT CONTEXT] | Enter the prospect’s business, use case, current workflow, and why the opportunity exists now. | Harbor Foods has 11 legal entities and closes in 12 business days using spreadsheets, email, and NetSuite. The controller is frustrated with missed handoffs before an audit next spring. |
| [DEAL INTELLIGENCE] | Enter known stakeholders, buying criteria, decision timing, objections, and deal-stage information. | Controller is champion; CFO cares about audit readiness and cost; IT must approve security. Evaluation begins next month. Prospect asked how migration works and said price may decide if both products look similar. |
| [NEXT STEP] | Enter the specific next meeting, evaluation, or commitment you want to achieve. | Secure a 45-minute workflow mapping session with the controller and one accounting manager, ending with agreement on success criteria for a pilot. |
How to use
- Gather direct prospect quotes, current workflow facts, and competitor sources before pasting the inputs.
- Keep unknowns labeled and use the discovery questions to turn them into evidence in the next call.
- Share only approved product claims and replace generic proof with the customer evidence your team can substantiate.
- Follow up with: "Using the answers from this discovery call, update the risk section and write a pilot success-criteria document."
Variations
Executive brief
Use this to prepare an internal deal review for a sales leader.
Create an executive competitive-deal brief for [ACCOUNT] against [COMPETITOR]. Use these verified facts: [DEAL FACTS]. Our relevant proof and constraints are [OUR EVIDENCE]. Produce a one-page brief covering deal stage, business case, champion strength, decision criteria, competitive posture, top three risks, gaps in evidence, and the next two actions with owners. Separate prospect-confirmed facts from seller assumptions. Include a recommendation only if evidence supports it. Do not claim forecast confidence, competitor weaknesses, or stakeholder support that the notes do not establish. Check that every action resolves a stated risk or moves the decision process.
Discovery plan
Use this before a first or second call where a competitor is already in the account.
Build a competitor-aware discovery plan for [PROSPECT] evaluating [OUR PRODUCT] and [COMPETITOR]. The known context is [KNOWN FACTS], and the meeting attendees are [ATTENDEES]. Produce an opening hypothesis, eight prioritized open questions, the signal each answer would reveal, and two follow-up paths for favorable and unfavorable answers. Cover status quo cost, workflow, success metrics, implementation risk, evaluation process, and economic buyer. Avoid leading questions or unsupported competitor comparisons. Finish with a meeting close that seeks [DESIRED NEXT STEP]. Flag assumptions that need validation first.
Objection talk tracks
Use this when the buyer is comparing price, features, or implementation risk.
Write practical sales talk tracks for these competitive objections: [OBJECTIONS]. Our verified capabilities and proof are [OUR FACTS]; competitor information we can safely cite is [COMPETITOR FACTS]; the prospect’s priorities are [PRIORITIES]. For each objection, give a 60-90 word response following acknowledge, clarify, evidence, and next question. Add one “do not say” warning where a claim could become misleading. Do not disparage the competitor, make pricing promises, or state unverified implementation results. Check that every proof point directly supports the objection being addressed.
Tips
- A battlecard is strongest when it begins with the buyer’s decision criteria, because feature differences matter only when they change the prospect’s outcome.
- Separate competitor knowledge from assumptions in the document; sales teams often repeat old hearsay until it becomes treated as fact.
- Use discovery questions to uncover how the prospect will score options, who can veto the decision, and what implementation risk means in their environment.
- Do not use customer logos or performance claims unless your organization has approval and evidence for the specific claim.
FAQ
Should a battlecard say that our product is better?
It should show where your product is a better fit for stated buying criteria, with evidence. Broad superiority claims are weak and can create trust problems.
How often should we update a battlecard?
Update deal-specific sections after meaningful discovery and refresh competitor facts whenever the source changes. Date the evidence so old information is visible.
Can AI research the competitor for me?
It can organize sources you provide, but verify current claims through approved, reliable sources before presenting them to a prospect.