AI Product Marketing
Battlecard

Battlecard objection handling

In our method, battlecard objection handling gives every real objection three parts on the card. They are the objection in the buyer's own words, the honest answer, and the point where that answer becomes "we are not the right fit." The objections come only from calls that happened. No answer runs down a product the buyer already owns.

Last updated by Omair Dawood.

On this page

Where objections sit on the card

Objections are step 7 of the eleven steps in our battlecard method, the one our Battlecard tool runs (read 2026-10-14). The card gives them one table with three columns:

Objection, in the buyer's wordsThe honest answerWhen to walk

The five steps below gather the method's rules for that table: its input rule, step 7 itself, the sourcing rule from step 9, and the quality bar. Each step names where it comes from. The rest of the card, from the one-line read to the refresh log, is in how to build a competitive battlecard.

The five steps

  1. Collect real objections first (Required inputs). Real objections are one of three inputs the method refuses to run without. Ask sales for lines buyers said on calls that happened. The method's reason: invented objections train sellers for a conversation nobody has. If you have none, the card stops and says who can supply them.
  2. Write each one in the buyer's words (step 7). Keep the buyer's phrasing, even when it is rough. In our view, a seller listens for those exact words on a call, and a tidied version is harder to spot.
  3. Write the honest answer from messaging you already have (step 7, step 9, quality bar). The method says the card does not write the pitch. Counter-language points at your current positioning, and the card invents no new claims. Any claim about the rival in the answer needs a public source and the date you checked it. Label anything you cannot verify UNVERIFIED, or cut it.
  4. Write the when-to-walk line (step 7). For each objection, name the point where the honest answer is "we are not the right fit." The method's rule: a card without that line teaches reps to bluff, and technical buyers detect bluffing fast. Every objection gets one.
  5. Check that nothing runs down what the buyer owns (step 7, quality bar). Read every answer once more for any line that knocks a product the buyer already uses. The method bans it outright, so rewrite the line around what you do instead.

Worked sample: Webflow's WordPress FAQ, read as a card row

In our view, real objection lists are private call data, so no public page shows one. A vendor's comparison FAQ is the closest public stand-in we found, because it answers a buyer's doubt in writing. Webflow's WordPress page asks one question in the buyer's voice:

"WordPress has a huge plugin ecosystem and can connect to my martech tools. Will I lose this extensibility with Webflow?"

"You won’t! In fact, Webflow improves on the traditional open-source plugin ecosystem model in 2 ways:"

Read on . Source: Webflow vs WordPress page

The second of the two ways reads:

"Second, a large diversity of plugins itself is an indication of missing functionality out of the box."

Read on . Source: Webflow vs WordPress page

What the copy does well. In our reading, the question passes step 2. It is in the first person, names what the buyer owns, and states the fear in one word: extensibility. The first of the two ways is specific. The page says Webflow offers a set of APIs for integrations and an App Marketplace of vetted apps that run in a sandboxed model. It adds that updates or crashes in a plugin will not affect the core site. A seller can check each of those against the page and date it, as step 3 asks.

What a card could not take as written. In our view, a public FAQ has a different job from a card. We read it against our steps, not as a fault in the page. Three gaps show. First, we cannot tell whether a buyer said these words on a call, and step 1 needs that. Second, in our reading, "You won’t!" leaves no case where the answer fails, so the row has no when-to-walk line for step 4. Third, the second reason calls WordPress's range of plugins a sign of missing functionality, which knocks the product the buyer runs. On a card, step 5 cuts it.

The fix: the row a card could carry. The when-to-walk slot stays open, because only your own product facts can fill it.

| Objection, in the buyer's words | The honest answer | When to walk |
|---|---|---|
| "WordPress has a huge plugin ecosystem and can connect to my martech tools. Will I lose this extensibility with Webflow?" [confirm a buyer said this on a real call] | Ask which plugins the site relies on, then match each one. Webflow states it offers APIs for integrations and an App Marketplace of vetted apps that run sandboxed. Source: webflow.com/vs/wordpress, checked 2026-10-14. | [the plugin or integration with no app or API route: needs your product facts] |

The answer keeps the page's checkable claims and drops the knock on plugins. It also asks a question first, so the seller learns what is at stake before promising anything.

Common mistakes

  • Writing objections from a whiteboard. The method's reason for refusing them: invented objections prepare sellers for calls that never happen. Take the lines from real calls, and mark any you cannot trace to one.
  • Answering with a feature list. In our view, a list of features dodges the doubt the buyer named. Answer that doubt, using language from your current messaging.
  • Leaving out the when-to-walk line. In our view, a table without it reads as "we always win," the bluff the method warns about. Give every row its limit, even a narrow one.
  • Knocking the product they own. Your proven strengths belong in "Where we win," with a source and a date. The answer to a buyer who uses the rival today never runs that product down.
  • Unsourced claims about the rival. An answer that says what the rival cannot do needs a public source and a check date. Without one, mark it UNVERIFIED or cut it.

Questions people ask

What is the best way to handle customer objections?

Our method starts before the call. Take the objection from a real call, write it down in the buyer's words, and prepare the honest answer from your current messaging. Then decide in advance where the answer stops being true for this buyer. In our view, a seller who knows that line can say "we are not the right fit" without losing trust.

What are the 5 steps for objection handling?

Our method has no five-step script for the live call. On the card, this page groups the method's rules for the objections table into the five steps above. They run from collecting real objections to checking that nothing runs down what the buyer owns. The sales battlecard guide shows where that table sits on the card.

What does a battlecard objection handling example look like?

One row has three cells. The first is the buyer's exact line, such as the Webflow question above. The second is an honest answer that a seller can back with a dated source. The third names the case where you walk. For a blank layout of the whole card, use our competitive battlecard template.

Sources

Put your objections on a card with the Battlecard tool

The tool asks what buyers actually say against you: real objections only, in the buyer's words, two or more, one per line. Name one rival, or leave the name and website blank and the tool picks the closest competitor, or the standard product buyers compare you to. It also asks for your positioning or homepage copy, and an optional buyer seat. You get a dated profile of the competitor, where each side wins, three traps and the real objections, and questions to ask on the call. It takes about 3 minutes of typing.

Turn your buyers' real objections into a battlecard