battlecard-builder

name	battlecard-builder
description	Create competitor battlecards for revenue teams with practical talk tracks, proof, and red flags. Use when asked for compete guidance, head-to-head positioning, buyer objections, or seller-ready competitive artifacts. Route broad positioning strategy to value-prop-and-positioning and objection handling systems to objection-library-builder.

Battlecard Builder

Build concise battlecards that help reps handle real competitive situations without guessing.

Confirm Inputs First

• If a current revenue-enablement-context exists, use it first for ICP, persona priorities, and approved claim boundaries.
• Confirm competitor scope and market context.
• Confirm target segment and common deal scenarios.
• Confirm known competitor claims and buyer perceptions.
• Confirm internal strengths, limitations, and no-go claims.
• Confirm available win-loss evidence and proof artifacts.
• Confirm enablement audience (new reps, enterprise AEs, managers).
• If inputs are incomplete, ask for only the minimum missing items or proceed with labeled assumptions.

Read The Right Reference

• Read references/battlecard-template.md when you need a stable structure and claim handling rules.

Default Workflow

1. Define the competitor and the deal context. Note where this competitor shows up, which segment it shows up in, and why buyers care.
2. Capture the competitor story. Summarize strengths, common buyer appeal, and the claims reps hear most often.
3. Clarify where you win. Call out win zones, disqualifying fit conditions, and the situations where you should not compete hard.
4. Build the claim-response-proof table. For each high-frequency claim, add the response, proof point, and when to use it.
5. Check freshness. Note the source and date for each competitive claim so the card does not go stale.
6. Add trap handling. Include the comparisons and questions that usually pull reps off message.
7. Add do-not-say guardrails. List claims that are too weak, too broad, or not approved.
8. Route adjacent work: For category messaging, use value-prop-and-positioning. For objection playbooks, use objection-library-builder. For account-specific prep, use account-brief-builder.

Output Contract

• Competitor snapshot with overlap context.
• Win zones and loss-risk conditions.
• Claim-response-proof table.
• Freshness and source notes.
• Trap handling and red-flag guidance.
• Do-not-say list and escalation notes.
• Assumptions list when source inputs were incomplete.

What To Avoid

• Repeating stale competitive claims without verification date/source.
• Treating battlecards as one-sided attack sheets instead of tradeoff guides.
• Letting reps use counters that have no legal-safe proof path.

Quality Bar

• Guidance reflects credible market tradeoffs, not one-sided hype.
• Counters are evidence-backed and legally safe.
• Win conditions are specific enough for rep decision-making.
• Landmines prevent common self-inflicted errors.
• Output is compact enough for quick call prep.