"We ran your proposal through ChatGPT last night, and it thinks we could build most of this ourselves," the VP of finance tells Lena twenty minutes into a final-stage call. Lena has her team's sales objections and responses doc open in another tab. Marketing wrote it last spring, and it has no row for a buyer who brings an AI's opinion to the call.
Lena answers by listing features for two minutes, and the VP promises to circle back after the budget meeting. On Thursday, her manager Victor plays the recording and stops where the VP raised the objection. Lena never asked what the VP had typed into the chat or what the answer had compared. As a result, she spent those two minutes arguing with a document she had never seen.
Victor's fix was a question Lena should have asked first, and that pattern runs through all 25 sales objections and responses below, grouped by type. Each one shows the buyer's words, the question to ask first, a response, and the trap that loses the deal.
A sales objection is a buyer's stated reason for not moving forward. Good responses to sales objections answer the reason behind the words, which can differ from what the buyer said. The VP's one sentence carried at least three concerns: build cost, ownership after launch, and budget. Your first job is to find out which one matters, and only a question can do that.
That is why every script here starts with a question before any response. "Your price is too high" can mean the buyer found a cheaper tool or has no budget line yet. It can also mean they want a story for finance about how hard they negotiated. Each meaning needs a different answer, so a rep who responds before asking is guessing.
Responses to sales objections need proof because buyers now arrive with research they want a rep to confirm. According to Gartner, 69% of B2B buyers turn to sales reps to validate AI-generated insights. Read that way, the VP's ChatGPT line asked Lena to check the AI's work, even though it sounded like a rejection.
Forrester expects that pressure to grow. In its 2027 B2B go-to-market predictions, the firm says AI agents will influence 75% of B2B purchase decisions in 2027. It also predicts that two-thirds of providers will lose deals because buyers cannot verify claims. Buyers, in Forrester's view, will double their human interactions to validate AI-generated recommendations.
For objection handling, this means the response itself has to carry something the buyer can verify. "Our customers love the onboarding" gives the buyer nothing to check, while a call with a customer of the same size does. A line in the contract or a live demo of the disputed feature works the same way. Lena had a reference that matched the VP's company almost exactly, and it never came up because she was busy defending features.
Price objections are easy to misread on sales calls, because "too expensive" often means the buyer cannot justify the purchase yet. The five scripts below cover the versions Victor found most often on his team's calls.
| Objection | Ask first | Respond | Trap |
|---|---|---|---|
| "Your price is higher than the other option we're looking at." | "Which line items are you comparing, and what does the other option leave out?" | Walk through the comparison line by line and price the gap they would have to fill. | Discounting before you know what they compared. |
| "We don't have budget for this." | "Is there no budget this year, or no budget line for this yet?" | If the line is missing, help the champion build the case for whoever owns the budget. | Treating it as a final no. |
| "Can you do better on price?" | "If we got there, what else would need to happen to sign this month?" | Trade any concession for something you need, like a longer term or a reference. | Giving a discount with nothing in return. |
| "We can get something cheaper." | "What would the cheaper option cost you in setup and admin time?" | Compare total cost over the contract, including the hours their team spends running it. | Attacking the cheaper product instead of pricing the difference. |
| "The price is fine, but finance won't approve it." | "What does finance need to see to approve a purchase this size?" | Offer to build the business case with the champion, using numbers the champion supplies. | Sending a generic ROI calculator. |
"We don't have budget" is the hardest price objection, because it can be a real limit or a polite exit. The ask-first question separates the two. A buyer with no budget line often has a real problem and no internal case for fixing it. Helping the champion write that case for the budget owner can keep the deal alive into the next planning cycle.
"Can you do better on price?" is the other hard one, because the urge to say yes runs strong late in the quarter. Buyers know that, so ask what else stands between you and a signature before you move on price. A discount that does not change the close date only lowers the number.
Timing objections usually point to a competing priority the buyer has not named. These four scripts surface that priority and attach the next step to it.
| Objection | Ask first | Respond | Trap |
|---|---|---|---|
| "Now isn't a good time." | "What's happening now that makes it a bad time?" | Tie the next step to the event they name and agree on a date to reconnect. | Accepting "next quarter" without a reason. |
| "Call me back next quarter." | "What will be different next quarter?" | If nothing changes, show what waiting costs in the problem they described. | Logging a follow-up task and calling it pipeline. |
| "We're in the middle of a reorg." | "Who will own this problem after the reorg?" | Offer to meet the future owner now, so the deal does not restart from zero. | Going silent until the reorg ends. |
| "We need to finish another project first." | "Does that project need the same people this one would?" | Propose a phased start with a small team the other project does not need. | Agreeing to wait without a date. |
"Call me back next quarter" sounds harmless, but it leaves a deal in pipeline with nothing behind it. Asking "What will be different next quarter?" makes the buyer say whether a real event is coming. A budget reset or a new hire gives the rep a date and a reason. If the buyer shrugs, the deal never belonged in this quarter's forecast.
The reorg objection is hard for another reason, since the buyer may not know who will own the problem. Ask anyway, and offer to brief the likely owner before the reorg settles. A rep who waits for the dust to clear can come back to a new leader with a new vendor shortlist.
Authority objections tell you the person on the call cannot sign alone. Each of these four responses moves the rep closer to the people who can.
| Objection | Ask first | Respond | Trap |
|---|---|---|---|
| "I need to run this by my boss." | "What will your boss ask you that we haven't covered?" | Offer a short call with the boss, or draft the summary the champion will forward. | Letting the champion pitch alone. |
| "The committee decides, not me." | "Who sits on the committee, and what does each person care about?" | Map each member and plan a touchpoint with the ones you have not met. | Single-threading through the person who said it. |
| "Legal needs to review this." | "How long did legal take on the last contract like this?" | Send the contract and security documents now and offer a call between legal teams. | Waiting for legal to come back on its own. |
| "IT has to sign off." | "What has IT turned down before, and why?" | Book a technical review with your SE before the buyer asks for one. | Answering IT's questions through the champion. |
"I need to run this by my boss" causes the most trouble here, because the champion thinks they can carry the pitch. In practice, they will summarize your best points in two sentences between other agenda items. Asking what the boss will want to know gives the rep a list of gaps to fill. A short summary written for the boss then makes the champion look prepared.
The committee objection is easy to handle and easy to ignore, because reps keep talking to whoever raised it. In effect, the buyer has just told you the deal has more voters than you have met. Our five-step objection handling framework covers the listening steps that matter most at this point.
Need objections mean the buyer does not yet see a problem worth paying to fix. All four scripts start by finding one before showing anything.
| Objection | Ask first | Respond | Trap |
|---|---|---|---|
| "We're happy with what we have." | "If you could change one thing about the current setup, what would it be?" | Explore that one thing until the buyer names a cost, then decide if it merits another meeting. | Pitching features before the buyer names a problem. |
| "We built something in-house." | "Who maintains it, and what's on their backlog?" | Compare maintenance time and missing capabilities against buying, using their own numbers. | Criticizing a tool that someone on the call built. |
| "I don't see how this applies to us." | "Which part felt furthest from how your team works?" | Show one workflow or customer story that matches their team's size and motion. | Running the full demo again. |
| "We tried something like this, and it failed." | "What went wrong, and who was there when it did?" | Address that specific failure and show how your rollout handles it. | Promising it will be different without saying how. |
"We're happy with what we have" gives a rep the least to work with, and sometimes the buyer is right. The ask-first question gives them room to name one irritation, and the rep then checks whether it costs enough to matter. If it does not, a polite exit saves both sides a month of meetings that end in no decision.
"We tried something like this, and it failed" carries real scar tissue. Ask who took part, because a buyer who led the failed rollout will hear any criticism of it as criticism of them. Explain how your rollout differs on the point that broke last time, and offer a reference who had the same worry.
Switching-risk objections come from buyers who believe your product could work but fear the cost of being wrong. These four responses lower that risk with specifics.
| Objection | Ask first | Respond | Trap |
|---|---|---|---|
| "Switching would be too much work." | "Which part of the switch worries you most?" | Lay out the migration plan with dates and the hours you need from their team. | Saying "it's easy" with no plan behind it. |
| "We're locked into a contract." | "When does it end, and what notice does it require?" | Work back from the renewal date to a start that avoids paying twice. | Dropping the deal instead of scheduling it. |
| "How do I know you'll be around in two years?" | "What would you need to see to feel confident?" | Share the proof they ask for, like references, data export terms or contract protections. | Answering with funding headlines. |
| "Your references are hand-picked." | "What kind of customer would you trust?" | Offer a reference that matches their size and use case, and let them choose the questions. | Getting defensive about the reference list. |
"Switching would be too much work" trips up reps, because the buyer usually has the effort right. Reps lose this one by minimizing it. A migration plan with named dates and an honest estimate of the buyer's hours earns more trust than a promise of ease. The buyer can hold you to the plan.
Buyers who call your references hand-picked have a fair point, and conceding it helps. Let the buyer describe the customer they would trust, then find the closest match, even one with a rocky first quarter. A reference who explains how the vendor fixed a problem can be more convincing than one who never had a problem.
AI-informed objections arrive when the buyer has already run your category, proposal or pricing through an AI tool. These four scripts treat the AI's answer as a starting document to examine together.
| Objection | Ask first | Respond | Trap |
|---|---|---|---|
| "We asked ChatGPT, and it recommended something else." | "What did you ask it, and what criteria did it weigh?" | Go through those criteria and add the ones the prompt left out, with proof for each. | Arguing with the AI's conclusion. |
| "An AI summary says your product can't do this." | "Can you share the summary so we can check it together?" | Show the capability live, or confirm the gap honestly if it exists. | Claiming the AI is always wrong. |
| "Our AI agent already compared vendors, so just send pricing." | "What did the comparison cover, and what does it still need from us?" | Send pricing along with the two facts the comparison could not check without you. | Sending a price sheet and nothing else. |
| "We could build this ourselves with AI." | "Who would own it after launch, and what else is on their roadmap?" | Compare build, run and maintenance cost against buying, with engineering time as the main input. | Dismissing the idea instead of pricing it. |
Lena's objection was the last one in this table, and it is the hardest because the AI is partly right. A capable team can build a first version of many tools quickly. The real question is who maintains it next year. Asked calmly, that question turns the talk into a cost comparison the buyer runs with their own numbers.
The "we asked ChatGPT" objection is hard because the buyer may feel a little defensive about using it. Treat the AI's answer as a reasonable first pass and ask to see the prompt. An AI comparison weighs only what the buyer typed. Adding the criteria the prompt left out, each with proof the buyer can check, can change the answer. Our piece on selling to AI buyers covers negotiation and procurement with these teams.
Build your library of sales objections and responses from what buyers said on your own recorded calls. Use marketing's draft only as a starting list. Lena's doc came from a spring win-loss survey, so it missed the phrasing buyers use on calls and every objection that appeared since.
Victor rebuilt his team's library in an afternoon after the Lena call. He searched last quarter's recorded calls for phrases like "budget," "my boss" and "ChatGPT," then sorted each hit into one of the six groups above. Next he counted which objections came up most and which ones came before a stalled deal. He kept the buyer's actual words in the objection column.
For the response column, he linked a clip of a rep handling each objection well. A new AE learns more from ninety seconds of a teammate handling "call me back next quarter" than from a paragraph of advice.
Review the library every quarter, because objections shift as buyers' tools and budgets change. A library built from calls catches a new objection in its first month. Lena's spring doc, by contrast, still has no row for the AI objection.
Victor's library took an afternoon of keyword searches, and Rafiki AI shortens that work. The Notetaking Agent, one of Rafiki AI's autonomous AI agents, records, transcribes, and summarizes every sales call. On Lena's call, that summary would have listed the VP's build-it-ourselves line before Victor ever pressed play.
Gen AI Search lets Victor find every sales call with the build-it objection and compare reps' responses side by side. With Smart Call Scoring, he can also add a custom criterion: did the rep ask a question before responding? Those scores show whether the ask-first habit is spreading across the team.
For practice, AI Role Play lets reps rehearse the hardest scripts against a custom persona, such as a skeptical VP of finance. It scores objection handling and active listening, so Lena could run the build-it-ourselves objection several times before her next meeting. The overview for account executives shows how this fits an AE's week.
Start by pulling last quarter's top five sales objections and the responses reps gave to each, in the buyer's own words. For each one, find a call where the response worked and one where the deal stalled afterward. Put the ask-first question at the top of each script, and share the scripts with the team before Friday's pipeline review.
Then measure one thing for the next 30 days: how often reps ask a question before responding to an objection. When the VP of finance came back after the budget meeting, Lena opened by asking what the AI had compared. She then walked the VP through a build-versus-buy cost model filled in with the buyer's own engineering numbers. The next meeting added the buyer's head of engineering.
Rafiki AI's conversation intelligence platform starts at $19 per seat per month with no minimums and no annual commitment. Start your free trial today or book a demo to find your buyers' exact objections in last quarter's sales calls and compare your reps' responses.
Every answer here follows the same rule as the scripts, which is to ask what the buyer means before you respond.
Keep responses only for the objections that actually show up on your calls, which may be fewer than the 25 here. Group them by objection type, and retire any script nobody has used on a call in two quarters.
Reps should memorize the ask-first question and the shape of each response, then use their own words on the sales call. Buyers notice a recited script quickly, and it tells them the rep is not listening. Role play helps reps find their own phrasing while keeping the structure.
An objection is a concern the buyer is willing to discuss, while a rejection is a decision the buyer has already made. The ask-first question tells you which one you have, because a buyer with a real objection will answer it. If the buyer will not engage, treat it as a rejection and ask what would have to change for them to revisit.
Raise it when your calls show that buyers in a segment almost always bring it up, such as switching effort for teams under contract. Naming it early lets you answer on your terms. Skip objections the buyer shows no sign of holding, because raising them plants doubts the buyer did not have.
Start for free — no credit card, no seat minimums, no long contracts. Just better sales intelligence.
