Knowing your pitch and knowing what to say when a buyer cuts in with “that is more than we budgeted” are two different skills. An objection lands in about a second, and the rep either freezes, gets defensive, or reaches for a discount. None of those close deals. Objection handling scripts fix that, but only when they work as decision frameworks rather than lines to memorize. Below are six battlecards covering what B2B reps actually hear, with the structure underneath them and the language you can make your own.
Why a Framework Beats Improvising
The research on this is unusually clear. JOLT analysis of 2.5 million recorded sales conversations found medium to high buyer indecision in 87% of deals, and when indecision runs high, win rates collapse to around 6%. The instinctive rep response is to re-pitch the value proposition, which 73% do. In 84% of those cases, re-pitching made the deal more likely to be lost.
So the goal of a script is not a better argument. It is to slow the moment down, find the concern underneath the words, and answer that one instead. A framework gives a rep something to lean on while their pulse is up.
The Six Objections Every B2B Rep Runs Into
Almost everything you hear on a call sorts into six buckets. Recognizing which one you are in is most of the work, because each has a different fear behind it.
| Objection type | What it sounds like | What is really going on |
|---|---|---|
| Price and budget | “That is more than we planned to spend.” | Fear of defending the spend internally, not disbelief in the value |
| Timing | “Let’s revisit next quarter.” | Risk aversion. Waiting feels safer than deciding |
| Authority | “I need to run this past the team.” | Real internal politics, or a polite way to avoid saying no |
| Competitor | “We are also looking at someone else.” | Wants leverage, or genuinely cannot see the difference yet |
| Status quo | “What we have works fine.” | Loss aversion. Switching feels riskier than staying |
| Trust | “This sounds too good to be true.” | A past vendor burned them, or the pitch outran the proof |
The Four-Step Structure
Every battlecard below runs on the same four moves, which is the point. A rep learns one pattern and applies it to all six.
- Acknowledge. Say the concern is reasonable, in one short line. Skipping this reads as defensive and everything after it lands worse.
- Clarify. Ask one question before answering. This buys thinking time and, more importantly, tells you whether the stated objection is the real one.
- Respond. Answer the concern the question surfaced, with something specific. One point, not five.
- Confirm. Check that it landed before moving on, so you are not carrying a silent objection into the next stage.
Six Battlecards You Can Use Today
Treat the sample lines as raw material. Rewrite them in words you would actually say, out loud, before you use them.
1. Price and budget
Trigger: “That is more than we budgeted for.”
Acknowledge: “That is fair, and I want this to make financial sense on your side.”
Clarify: “Is this about the total number, or about how the budget is allocated this quarter?” Those are two entirely different problems and only one of them is about price.
Respond: If it is allocation, discuss timing and phasing. If it is the total, move the conversation to the cost of the current situation rather than defending your number.
Confirm: “Does that change how this looks against what you had in mind?”
2. Timing
Trigger: “Let’s pick this up next quarter.”
Acknowledge: “Understood, timing matters as much as fit.”
Clarify: “What changes between now and then?” If nothing specific changes, this is indecision wearing a calendar.
Respond: Name the cost of waiting in their numbers, not yours. Then recommend a decision rather than offering three options, because more options deepen the paralysis.
Confirm: “If we did nothing until Q3, would that be a problem for you, or genuinely fine?”
3. Authority
Trigger: “I need to check with my team.”
Acknowledge: “Of course, a decision like this should not be made alone.”
Clarify: “Who else will weigh in, and what will they care about that we have not covered?”
Respond: Arm your contact for a meeting you will not be in. Deals are far more likely to die when the decision maker never appears, so offer to join, or give them a short internal summary they can forward.
Confirm: “What would make this easy for you to put in front of them?”
4. Competitor
Trigger: “We are talking to someone else too.”
Acknowledge: “Good. You should compare, that is how this ought to work.”
Clarify: “What matters most as you compare them: price, support, or fit with how your team works?”
Respond: Answer only on the dimension they named, and concede where the other option is genuinely stronger. Reps who never concede anything sound like brochures and get believed less, not more.
Confirm: “Does that distinction actually matter for your use case, or is it noise?”
5. Status quo
Trigger: “What we have is working fine.”
Acknowledge: “Then you should keep it unless something is clearly better.”
Clarify: “What would have to break before you looked at an alternative?”
Respond: Do not attack the incumbent. Arguing against the status quo backfires more often than it works. Ask about the specific moment it costs them something and let them describe it.
Confirm: “Is that gap worth fixing this year, or is it something you live with?”
6. Trust and skepticism
Trigger: “This sounds too good to be true.”
Acknowledge: “You are right to be skeptical. Plenty of tools promise this.”
Clarify: “Has something like this let you down before?” The answer tells you exactly which proof they need.
Respond: Trade claims for evidence: a specific customer in their situation, a number with its assumptions named, or a pilot small enough to be low risk.
Confirm: “What would you need to see to believe it?”
Adjust the Script to the Buyer, Not Just the Objection
Two buyers can raise the identical price objection and need opposite responses. A fast, decisive buyer wants your recommendation in one sentence and gets impatient with evidence. A careful, detail-driven buyer hears that same confident one-liner as a dodge and wants the spreadsheet. Same objection, same script, two different outcomes.
This is the part a static battlecard cannot cover, because it depends on who is on the call. If you want a read on that before you dial, our free buyer compatibility tool compares your LinkedIn profile against theirs and shows how they communicate, what moves them, and where the two of you are likely to clash.
How to Use These on a Live Call
- Read the card before the call, not during it. Scanning a script mid-conversation wrecks your tone and your listening. Five minutes beforehand is enough.
- Say the framework out loud first. Rehearse acknowledge, clarify, respond, confirm in your own words until it sounds like you rather than a document.
- Listen for the objection behind the objection. “Send me a proposal” usually means “I am not convinced,” not “I am ready to buy.”
- Ask before you answer, every time. The clarifying question slows the moment down and stops you from solving the surface complaint.
Keeping Them Sharp
A battlecard written once and parked in a shared drive goes stale in a quarter. New competitors appear, pricing pushback shifts with the market, and the objections your team hears now are not last year’s.
- Pull the actual phrases from call recordings and win-loss notes instead of guessing how your buyers talk
- Match the tone to the market, since a healthcare compliance objection reads nothing like a SaaS procurement one
- Keep every card to one page, because anything longer will not get read before a call
- Rewrite anything that sounds like marketing copy, since buyers notice canned language and discount everything after it
- Review quarterly, and immediately when a new objection shows up three times in a month
Where Scripts Run Out
A battlecard prepares a rep before the call. It cannot adjust to what is happening inside one, and it depends on the rep remembering it under pressure, which is exactly when memory is worst.
That is the gap Dextego’s real-time coaching fills. It listens live and surfaces the right framework while the objection is still on the table, on the rep’s screen only, so the buyer sees a normal call. Before the call, Tego lets the rep rehearse the hard version until it stops feeling like a script. If you are weighing that against the recorder you already own, we compared the two categories in real-time coaching vs conversation intelligence.
Frequently Asked Questions
What is the difference between a script and a battlecard?
A script is the language itself: the acknowledge line, the clarifying question, the response. A battlecard is the one-page sheet that organizes several scripts by objection type so a rep can find the right one fast, with the trigger phrase, framework, and response together.
Will using a script make me sound robotic?
Only if you read it word for word. Used as a structure, it does the opposite. Reps who rehearse the framework out loud until the phrasing is theirs sound more confident, because they are not hunting for words in the middle of an objection.
How often should we update our battlecards?
Quarterly at minimum, and immediately when a new competitor or pricing objection starts repeating on calls. Pull the wording from recent recordings and win-loss notes rather than from what worked last year.
What if the stated objection is not the real one?
Assume it often is not, especially with “send me a proposal” or “let me check internally.” That is what the clarifying question is for. Answer only the surface complaint and you will solve the wrong problem and still lose the deal.
Can scripts replace coaching?
No. A script prepares a rep for the objections you predicted. Coaching handles the moment nobody scripted, and it is the only thing that changes what a rep does while the call is still live.
See Objection Handling Coached Live
Book a demo and watch Dextego surface the right response in real time, on an actual call.