Open most competitive enablement material and you will find a table with two columns: the objection, and the response. Ask the sales team how often they use it and the answer is usually a polite version of never.
The reason is nearly always the same. The objections were imagined, and the responses were written to be read rather than said.
Start by finding the real objections
You cannot write comebacks to objections you have guessed. The real ones are recorded, in roughly this order of value:
- Call recordings. The actual words, in the actual moment. Nothing else is close.
- Lost-deal notes. Particularly free-text fields, which are messier and more honest than the structured ones.
- Reps, asked specifically. Not “what objections do you hear?” but “what did the buyer say in the last deal you lost to them, as close to word-for-word as you can get?”
- Public threads. When someone asks a community to compare you against a competitor, the replies are objections written down by strangers. See listening where you don't own the channel.
Collect twenty. You will find they collapse into four or five, because buyers in a category object along a small number of axes.
Separate the objection from the concern
This is the analytical step, and skipping it produces responses that answer the wrong thing.
“Their pricing is simpler” is rarely about price. Underneath is usually one of: I am worried about a surprise bill, I do not want to defend a complicated invoice internally, or I cannot tell what this will cost at scale and that makes me uneasy.
Those need different answers. A rep who responds to the stated objection with a pricing justification loses to a rep who responds to the concern with predictability.
For each objection, write down the concern beneath it before writing a word of the response.
The structure that works
A comeback that survives a live call has three parts, in order:
1. Acknowledge, without hedging. If the point is fair, say so plainly. “You're right that their pricing page is simpler than ours” costs nothing and buys the rest of the sentence. Reps who argue with true statements lose the room.
2. Reframe onto the concern. Move from the stated objection to what it is really about. “What usually matters more by month six is whether the bill is predictable, and that's where the two models diverge.”
3. Evidence, specific. One checkable fact. Not a claim — a fact. See proof points vs claims.
Three parts, four sentences, under fifteen seconds. Anything longer will not be used.
Write it the way it will be said
The most common failure is register. Written enablement language does not survive being spoken:
- “Our solution provides superior scalability characteristics” — no human says this.
- “They tend to hit a wall around 50 seats; we've moved a few teams over at exactly that point” — a human says this.
A reliable test: read the comeback aloud. If you feel faintly embarrassed, a rep will feel it too, and will improvise instead. Improvised responses are where inaccurate claims come from.
The rules that keep the card trusted
Never write a claim you cannot source. One comeback that gets a rep contradicted by a well-informed buyer will retire the entire card. This is not a hypothetical failure mode; it is the usual one.
Never disparage. Beyond the legal exposure, it reads as insecurity, and buyers who have heard it before discount everything after it.
Concede the genuine wins. If a competitor is better at something, the comeback is a qualification question, not a rebuttal. Reps need to know which deals to leave.
Date every claim. Competitors change pricing and ship features. A comeback that was true last quarter can be actively harmful now — see why battlecards go stale in 90 days.
The objection you cannot answer
Sometimes the competitor is simply the better fit. The correct comeback is not a comeback.
Give reps explicit permission and explicit language to disqualify: “Honestly, if that's the primary requirement, they'll serve you better on it.” This costs a deal you were going to lose anyway, saves weeks of pipeline theatre, and buys credibility that occasionally returns as a referral.
Enablement material that never says this trains reps to push on deals that cannot close.
Testing them
Before publishing, run each comeback past two people: a rep who has lost a deal to the competitor, and someone who will argue back. The first tells you whether it is realistic. The second tells you whether it holds up when the buyer pushes, which is the only conditions that matter.
Our Sales Battlecard report builds this block from evidence rather than imagination — objections sourced from public review and community material, each comeback tied to a citable proof point, and the deals worth walking away from named explicitly.