The Complete Objection Handling Phrasebook for Non-Native Sales Reps
The Complete Objection Handling Phrasebook for Non-Native Sales Reps
An objection handling phrasebook for non-native sales reps is a reference library of the exact English phrases that land well with US and UK buyers when a prospect pushes back — organized by objection type, annotated with the mistake non-native reps typically make, and explained in terms of why the native-level response works at a linguistic and psychological level. This is not a list of scripts to memorize. It is a pattern library that trains your ear and your instinct so that the right phrase surfaces under pressure, not after the call ends.
Non-native reps handle objections with correct logic but wrong phrasing. The reasoning is sound. The response doesn't land. 75% of sales reps report anxiety before important calls in a second language (Kaiwa Research, 2024), and objection moments are where that anxiety peaks and language precision collapses. The goal of this guide is to give you pre-loaded native-level responses so that when a VP says "we don't have the budget," you don't freeze or reach for a literal translation that reads as defensive.
64% of companies report losing deals to language and communication barriers when entering English-speaking markets (Economist Intelligence Unit, 2023). Most of those losses happen not in the pitch but in the objection conversation — the moment when the buyer tests whether you can hold the conversation under friction.
This guide covers 15 objections across 5 categories. For each: the objection, the non-native default response (and what's wrong with it), the native-level response, and why it works.
Price Objections
1. "That's too expensive."
Non-native mistake response: "I understand, but our product has many features and the price is justified because of the value we offer."
What's wrong: "The price is justified" is a defensive posture. It signals that you heard the objection as an attack on your pricing rather than an opening for a value conversation. "Many features" is vague and does not address the buyer's actual concern, which is usually ROI or budget, not the feature count.
Native-level response: "Expensive compared to what? If you're benchmarking against [competitor], the difference is [specific point]. If it's a budget question, walk me through how you're thinking about it — I want to make sure we're looking at the right number."
Why it works: "Expensive compared to what?" is a classic but effective reframe that immediately shifts the conversation from a position (too expensive) to a comparison (relative to what?). It doesn't sound confrontational because it's delivered as a genuine question. The follow-up gives the buyer two exit paths — benchmark comparison or budget conversation — and signals that you're problem-solving, not defending.
2. "We don't have the budget."
Non-native mistake response: "Maybe we can find a way to reduce the price for you."
What's wrong: Immediately offering a discount when a buyer says "no budget" trains buyers to say "no budget" to get discounts. It also skips the diagnostic step: is this genuinely no budget, or is it "not prioritized yet" or "I don't control the budget"?
Native-level response: "Is this a 'budget doesn't exist' situation, or more of a 'not in the current cycle' situation? Those are pretty different problems, and I want to make sure I understand which one we're actually solving."
Why it works: This response does two things. It validates that you heard the objection while demonstrating that you've seen this conversation before and know the difference between genuine constraint and timing. The casual register ("pretty different problems") keeps it from feeling like a sales technique, which it is, but shouldn't feel like.
3. "We found something cheaper."
Non-native mistake response: "Our solution is more expensive because it is better quality."
What's wrong: "Better quality" is unsubstantiated and sounds defensive. It positions you against the competitor rather than for your buyer's outcome. US buyers in particular respond poorly to abstract quality claims without proof.
Native-level response: "How much cheaper? And what's included at that price? I ask because we've seen a few situations where the sticker price was lower but the total cost — onboarding, support, time-to-value — came out higher. Happy to walk through that if it's useful."
Why it works: It invites a real comparison rather than asserting superiority. "Total cost" reframes the conversation from price to value without using the word "value," which US buyers hear as a deflection. The tone is collaborative rather than competitive.
Timing Objections
4. "Now isn't the right time."
Non-native mistake response: "I understand, maybe we can talk again later when the time is better."
What's wrong: This is a polite exit that hands control entirely to the buyer and closes the conversation without a next step. "Maybe we can talk again later" is non-committal in English in a way that signals you won't follow up.
Native-level response: "Completely understand. Can I ask what would make it the right time? I want to make sure that when we do reconnect, we're not having the same conversation — I'd rather come back when something has actually changed."
Why it works: "What would make it the right time?" is the only question worth asking here. It surfaces whether the timing objection is real (genuine internal constraint) or soft (not yet convinced enough to prioritize). The last sentence is confident without being aggressive — it signals that you value both parties' time.
5. "Call me back next quarter."
Non-native mistake response: "OK, I will call you in October. Have a good day."
What's wrong: This ends the call with no qualification, no agreed reason for the callback, and no way to differentiate your follow-up from the dozen other reps who will also call back next quarter. You will be forgotten.
Native-level response: "I can absolutely do that. To make that call worth your time, can I ask — is next quarter when a budget decision actually happens, or more of a general timeline? I want to reach you at the right moment, not just the calendar moment."
Why it works: It sounds like you're doing the buyer a favor (optimizing the timing for them) while actually qualifying the objection. "Budget decision actually happens" versus "general timeline" is a specific distinction that sophisticated buyers respect. It also makes the follow-up call more likely to land because you've established a shared frame.
6. "We're in a freeze right now."
Non-native mistake response: "Oh I see, a freeze. What does that mean exactly?"
What's wrong: Asking "what does that mean" makes you sound unfamiliar with a standard business concept. Budget freezes are a common corporate reality; responding with confusion undermines your credibility as someone who understands enterprise buying cycles.
Native-level response: "Got it — is this a full stop or a slowdown? Some teams use the freeze period to evaluate and get approvals in place so they can move fast when it lifts. If that's useful, I'm happy to stay in the picture at whatever pace works."
Why it works: "Full stop or a slowdown" demonstrates fluency with how budget freezes actually work. The offer to "stay in the picture" is lower-stakes than "let's keep talking" and invites continued engagement without pressure. "At whatever pace works" signals respect for their constraints.
Authority Objections
7. "I need to talk to my boss."
Non-native mistake response: "Of course, please speak with your boss and tell me what he thinks."
What's wrong: "Tell me what he thinks" passively positions the rep as dependent on a secondhand report. It also cedes all influence over the next conversation to the buyer, who may or may not accurately represent the product or handle the internal questions well.
Native-level response: "Makes sense. When you have that conversation, what do you think his main question will be? I want to make sure you have what you need to answer it, or if it's easier, I'm happy to join for 15 minutes so nothing gets lost in translation."
Why it works: "What do you think his main question will be?" is the most useful question in this scenario. It surfaces the real objection (which often lives with the boss, not the contact), and the offer to join the conversation reframes you as a resource rather than a risk. "Nothing gets lost in translation" is an idiomatic phrase that non-native reps rarely reach for naturally — it signals fluency.
8. "Just send me an email."
Non-native mistake response: "Yes of course, I will send you an email with all the information right now."
What's wrong: This objection is almost always a soft dismissal, not a genuine request for information. Immediately sending a long email confirms the buyer's expectation that they can manage you asynchronously and ignore you at low cost.
Native-level response: "Happy to. What would make it worth your time to open it? I want to send you something specific, not a brochure — if I know what the question actually is, I can answer it directly."
Why it works: "What would make it worth your time to open it?" is an unusual enough question that it disrupts the pattern. It signals that you understand email dynamics and that you're not going to send a 12-slide deck. "Not a brochure" is casual and self-aware — it acknowledges what generic follow-up emails feel like from the buyer's side.
9. "We have a committee for these decisions."
Non-native mistake response: "OK, can you send me the names of the committee members so I can contact them?"
What's wrong: Asking for a list of committee members immediately is a common rookie move that signals you plan to go around your contact. It damages trust and almost always results in a wall going up.
Native-level response: "Completely standard for this kind of decision. How does your committee typically like to evaluate vendors — do they prefer a live demo together, a written summary, or a proof-of-concept first? I want to match however they work, not add friction to your process."
Why it works: "Match however they work" is a collaborative frame that positions you as process-aware rather than aggressive. Offering three specific options (demo, summary, POC) demonstrates that you understand enterprise buying journeys. It also surfaces which option your contact is most comfortable facilitating — which tells you a lot about where you actually are in the deal.
Competition Objections
10. "We already have a solution."
Non-native mistake response: "Yes, but our solution is better than what you have."
What's wrong: "Better" without specifics is not a claim — it's a position. US buyers, especially in SaaS, have heard this hundreds of times. It signals that you have not done your homework on their current stack.
Native-level response: "I assumed you might — most teams at your stage are using something. I'm curious what you'd want to be different about it if you could change one thing. That's usually a more interesting conversation than what we can do."
Why it works: "I assumed you might" demonstrates market awareness. "What would you want to be different" is the only question that matters in this scenario — it surfaces latent dissatisfaction without you having to manufacture it. The last phrase, "more interesting conversation than what we can do," is disarming because it de-centers your pitch.
11. "We built this internally."
Non-native mistake response: "Interesting, but maintaining an internal tool can be very costly for your team."
What's wrong: "Can be very costly" is a condescending frame when delivered to someone who built the tool. It implies you know their internal economics better than they do. It also positions you as immediately adversarial to a decision that was likely made by someone important at the company.
Native-level response: "That's a real investment — what drove the decision to build rather than buy? I ask because I've talked to a few teams that went that route, and the follow-up questions are usually about what you're doing with engineering capacity now that it's running."
Why it works: "What drove the decision to build rather than buy?" is non-judgmental and genuinely curious. The pivot to "engineering capacity" is a credible business question that opens the ROI conversation without you having to make a cost claim. It respects the decision they made while surfacing the natural next question.
Trust Objections
12. "I've never heard of you."
Non-native mistake response: "We are a new company but we have very good technology and many satisfied clients."
What's wrong: "New company" is the last thing to volunteer when a buyer is questioning your credibility. "Very good technology" and "many satisfied clients" are the exact phrases every startup uses and no buyer believes without evidence.
Native-level response: "That's fair. We've been intentional about staying focused on [specific niche] rather than spreading marketing budget thin. The teams that know us well are [specific company type]. Would it be useful if I sent you a quick case study from someone in your space?"
Why it works: "Intentional about staying focused" reframes obscurity as strategy. It's not defensive, and it's a common enough explanation in B2B that it lands as credible. The pivot to a case study from "someone in your space" makes the social proof specific and relevant, which is far more persuasive than abstract claims.
13. "Can you prove this actually works?"
Non-native mistake response: "Yes of course, we have many case studies and testimonials from satisfied customers."
What's wrong: "Many case studies" is generic. "Satisfied customers" sounds like a brochure. This response does not give the buyer any reason to believe the proof will be relevant to their specific situation.
Native-level response: "Yes, and I want to show you the right proof, not just the most impressive number. What would it take to convince you — and I mean specifically? Is it a customer reference call, a pilot, a specific metric from a company similar to yours?"
Why it works: "The right proof, not just the most impressive number" signals sophistication about what proof-of-concept conversations should look like. Offering three specific proof formats (reference call, pilot, metric) makes the conversation concrete and shows that you have experience running validation processes. Asking "what would it take to convince you — specifically?" is a direct question that most reps avoid but that serious buyers respect.
14. "Your reviews online aren't great."
Non-native mistake response: "Oh, maybe some clients were not happy but usually our reviews are positive."
What's wrong: "Maybe some clients were not happy" is both vague and slightly dismissive of actual customer feedback. It sounds like you haven't read the reviews. It also doesn't address the buyer's underlying concern, which is about risk.
Native-level response: "Which ones did you find? I'd rather look at the same thing you're looking at than guess. Some of the critical reviews I'm aware of are about [specific issue] — we've since [specific change]. But if there's something else, I want to address it directly."
Why it works: "Which ones did you find?" shows confidence — you're not avoiding the topic. Acknowledging a specific issue and the response to it demonstrates accountability. "Address it directly" signals that you're not going to spin or deflect, which is the exact opposite of what a buyer fears from a vendor on the defensive.
15. "We tried something similar before and it didn't work."
Non-native mistake response: "I understand your concern, but our product is different from what you tried before."
What's wrong: "Our product is different" is a claim every vendor makes and no buyer accepts at face value. It doesn't address the actual information the buyer just gave you — they have experience with this category and they were burned. That is important intelligence, and ignoring it to make a positioning claim wastes it.
Native-level response: "Tell me more about what happened — specifically where it broke down. Was it the technology, the implementation, the adoption, something else? I'm asking because that tells me where I need to be specific rather than general."
Why it works: "Tell me more about what happened" is the most important phrase in this entire phrasebook. It positions you as a diagnostician rather than a salesperson. The follow-up list (technology / implementation / adoption) shows that you understand the failure modes in this category. "Where I need to be specific rather than general" signals that you're going to respond to their actual experience, not deliver a rehearsed pitch.
How to Practice These Responses
Reading this phrasebook once will not help you. Language under pressure comes from pattern recognition built through repetition, not from memory. 87% of new skills are forgotten within a week without deliberate practice (Braintrust Growth, 2023). To make these responses automatic:
Daily repetition with realistic pressure. The only way to internalize these phrases is to use them in conditions that simulate real call pressure — a buyer who interrupts, who doesn't accept your first response, who escalates the objection rather than softening it. Reading scripts alone does not create this condition. AI-powered call simulation does.
One objection category per week. Do not try to practice all 15 at once. Take price objections this week. Practice "Expensive compared to what?" ten times with an AI prospect who gives you the full range of pricing pushback — too expensive, no budget, cheaper competitor. Next week, move to timing. In five weeks, you will have covered all five categories with enough repetition to wire the response.
Record and review. After each practice call, read the transcript. Identify where you reached for a literal translation, where you defaulted to a filler phrase, where your response was too long or too short. Surgical self-review is more efficient than general practice.
Use DojoSales for live objection roleplay. The platform simulates realistic AI buyers that respond to your exact phrasing, not just your intent. If you say "our product is better," the AI buyer will push back. If you say "expensive compared to what?" the conversation will proceed differently. That feedback loop, in real time, is what builds the pattern.
Frequently Asked Questions
Should I memorize these phrases word for word?
No. Word-for-word memorization creates brittle responses that break when the buyer says something unexpected. The goal is to internalize the logic of each response — why "expensive compared to what?" works — so you can adapt the phrasing under pressure while keeping the structure. Practice with variation, not with a script.
What if the buyer gives me an objection I've never heard before?
The five categories in this guide (price, timing, authority, competition, trust) cover over 90% of sales objections in B2B technology sales. A novel-sounding objection almost always belongs to one of these categories at its root. "We have a new CTO who wants to evaluate everything" is an authority objection. "We're focused on other priorities right now" is a timing objection. Categorize first, then apply the appropriate structure.
How do I practice without making mistakes in real calls?
That is what AI simulation is for. Practice the objection conversation 20 times in a low-stakes environment before you encounter it in a real deal. The goal of tools like DojoSales is to let you make all the language mistakes privately — the "our product is better" response, the "maybe we can reduce the price" reflex — so that those patterns are replaced before you're on a real call with a decision-maker. The rep who has handled a price objection 50 times in simulation will not freeze when it happens live.
Internal links: The Complete Sales English Guide for Non-Native Reps | How to Handle Price Objections in English