Objection Prevention System
Script objection responses into your presentation so prospects have nothing left to object to
Gitomer's Objection Prevention System reverses the conventional approach of training salespeople to handle objections after they occur. Instead, he argues that there are very few genuinely new objections—most have been heard thousands of times—and the failure to anticipate and pre-empt them is a preparation failure, not a selling failure.
The system begins with an audit: identify every objection that has occurred in the past twelve months, group them, and write scripted responses for each. These responses are then woven into the presentation itself, so that when the prospect would have raised the objection, it has already been addressed. The outcome is a presentation that ends with nothing left to object to.
Critically, the system requires sales tools that support each response—testimonials, comparison charts, articles—so that the prevention is backed by proof, not just assertion. The process is team-based, updated continuously, and treated as a living document rather than a one-time exercise.
- There are no new objections—only objections you have not yet scripted a response to.
- An objection raised during the presentation is more dangerous than one addressed before it can be raised.
- Objection prevention is not manipulation—it is thorough preparation on behalf of the prospect's decision-making.
- Sales tools—testimonials, comparison charts, stories—are the most effective objection prevention weapons, not verbal arguments.
- Objection responses must be tested on real customers and continuously revised to remain effective.
- Audit all objections from the past twelve monthsGather the entire sales team and brainstorm every objection encountered in the past year. Group similar objections and identify the five to ten that account for 80% of lost or stalled opportunities. This list is your objection inventory—the foundation of everything that follows.Pro tipInvolve customers in this audit. Invite two or three trusted customers to a session and ask them what concerns made them hesitate before buying. Their candour will surface objections the team has never articulated internally.
- Script multiple responses for each objectionFor each objection, write at least three responses: a story about a customer who had the same concern, a direct answer with proof, and a reframe that shifts the perspective. Role-play each response with the team until it sounds natural, not recited. Add a closing question to each response that moves the prospect forward.WarningScripts that sound scripted are worse than no script at all. The goal is internalised responses, not memorised lines. Role-play is essential.
- Build a sales tool for every objectionIdentify the most powerful proof for each objection: a testimonial video from a customer who had the same concern, a comparison chart that addresses competitive objections, an article that addresses credibility concerns. These tools must be ready to deploy in-meeting, not compiled post-meeting.Pro tipTestimonials that specifically address objections ('I thought the price was too high, but after a year the total cost was 20% lower...') are vastly more persuasive than generic testimonials. Collect these specifically.
- Embed prevention into the presentationRewrite the standard presentation to address each anticipated objection before it can be raised. This is not about manipulating the prospect—it is about demonstrating thoroughness. The technique: 'My customers often wonder about X. Here is what they told me after they found out...' This approach is transparent, builds credibility, and removes the objection without requiring the prospect to voice it.WarningDo not address objections the prospect has not raised if they are not on your standard objection list. Bringing up objections the prospect had not considered can introduce resistance that would not otherwise have existed.
- Test, revise, and update continuouslyAfter every significant presentation, note whether the prevention worked and what refinements are needed. Hold monthly team sessions to discuss revisions. When a new objection appears, add it to the script within 30 days. The system only remains valuable if it is maintained.Pro tipWhen a new salesperson joins, the objection prevention notebook is their fastest path to confidence and competence. Treat it as a living training manual.
Rather than waiting for the price objection, Gitomer coaches salespeople to address it proactively: 'I'd like to share why some of my customers initially thought my price was high and what they told me after twelve months of use.' A testimonial stating 'I thought the price was too high, but the total cost was 20% lower than last year' is then played or read. The objection is defused before it exists.
When a prospect declares they want to shop around, Gitomer's prevention script produces a pre-built comparison chart against the top twenty competitors, covering all the criteria the prospect typically cares about. 'Many of my customers want to comparison shop—I've done it for you. Here's how we compare on the criteria you mentioned.'
Gitomer recommends taking draft objection scripts to trusted customers before using them with prospects: 'I'm developing responses to concerns customers have expressed. Can I test these with you and get your honest reaction?' Customers are usually flattered and provide candid feedback that eliminates scripts that don't resonate and strengthens those that do.
This framework emerged from Gitomer's observation that experienced salespeople, year after year, were surprised by the same objections. 'Price is too high,' 'need to think about it,' 'satisfied with present vendor'—these five objections account for the vast majority of lost sales, yet most sales teams treat each encounter as if it were new.
Gitomer worked with his own sales training clients to formalise the prevention approach: if you have heard an objection ten times, you have all the data you need to script the perfect response. The only reason not to have done so is a lack of discipline, not a lack of ability.