Battle Cards · Worksheet

Battle Card Template for Win/Loss Objections

The seven-field card that converts a lost-deal objection into a reusable sales asset. Fill it in during the loss-interview debrief, and reps stop re-hitting the same objection cold.

3 min read·For PMM·Updated Apr 19, 2026

Most lost-deal objections die in the CRM comment field. The rep logs "went with competitor X because of Y," and the next rep who hears the same objection six weeks later has to improvise a response from scratch. The cost is not the improvisation — it's the 3–4 deals each quarter lost to objections the team has already heard, debated, and could have answered if anyone had written the answer down.

The seven-field objection battle card below is the cheapest conversion from "lost-deal intel" to "reusable sales asset." It takes 12 minutes to fill in. It lives in the sales enablement tool, not in a Google Doc. It gets used.

The seven fields

The objection battle card fields, in order

    How to fill it in

    The card gets filled in during the 30-minute debrief with the rep who ran the lost deal, not later by the PMM alone. The rep supplies the verbatim objection and the buyer context; the PMM supplies the reframe, response, and proof. The template with both inputs produces a card that reads as if the team wrote it together — because they did.

    What this card is not

    Build the first three cards from the three most common objections your team hears. Ship them to sales within a week. Watch for reps citing them in calls. The card that gets cited in the first month is durable; the card that doesn't needs a rewrite. Iteration on the format itself — field order, script length — should happen from month three onward, not before. First, make sure the cards are being used.

    Related capability

    Battle Cards

    Auto-updating per-competitor rebuttal kits. Each card updates when Competitor Signals detects a material move.

    See how it works
    The Stratridge Dispatch

    One sharp positioning read, most Thursdays.

    Field-tested frameworks, teardowns, and pattern notes from our working library. No "Top 10" lists. No launch roundups. Unsubscribe whenever.

    Keep reading