How to handle objections on a slide

Every buyer has doubts. Some say them out loud and some don’t, but either way they shape the decision. A sales deck that ignores them leaves the buyer to resolve those doubts alone, usually after the meeting and without you. A deck that names them and answers them shows you understand the risk the buyer is taking.

Not every objection deserves a slide. Here’s how to decide which do, and how to build them.

Choose the objections worth a slide

Start with a list of every objection you have heard in deals like this one. Your CRM notes, lost-deal reviews and colleagues are good sources, and so are the notes from your discovery call. Then sort them:

• Common and predictable. Price, switching effort, implementation time, integration with existing tools. If most buyers raise it, answer it in the main deck.
• Specific to this buyer. Something that came up in discovery, such as a bad experience with a previous vendor. Address it directly, often on its own slide.
• Occasional. Security reviews, data residency, contract terms. Keep these in backup slides and bring them out when asked.

Aim for no more than two or three objections in the main deck. More than that and the deck starts to sound defensive.

Three formats that work

Name it, then answer it

The simplest format. The headline states the objection in the buyer’s words, and the body answers it in two or three short points.

For example:

“Switching will disrupt our team for months.” Most of the setup is done by our team, not yours. Your team needs two short training sessions. The old system can run alongside the new one until you’re confident.

This works because it doesn’t dodge. The buyer sees their concern taken seriously before hearing the answer. Only use claims you can stand behind; an objection slide with a weak answer is worse than none.

The side-by-side

For objections about value or price, a simple comparison often does more than an argument. Show the cost of the current approach next to the cost of yours, using the buyer’s own figures from discovery where possible. Label estimates clearly.

Area	Today	With the change
Hours spent each month	About 40 (your estimate)	Your projected figure
Errors needing rework	Your current rate	Your projected rate
Cost per year	₹ figure	₹ figure

The buyer does the reasoning. You just lay out the numbers. If you don’t want to build the table from scratch, a comparison slide layout works for this, as long as you fill it with the buyer’s own figures.

The risk reducer

Some objections aren’t really about the product. They’re about the risk of being wrong. For these, the answer is a smaller first step: a pilot with agreed success measures, a phased rollout, or an exit clause. A slide that sets out “what a pilot would look like” turns “we’re not sure” into “let’s test it”.

Where objection slides go

Placement matters as much as content.

• After the proof, before pricing. This is the natural spot for the common objections. The buyer has seen what you offer and why it works; now they’re weighing the risks. Clearing those first makes the pricing slide easier to accept.
• Early, for the elephant in the room. If you know the buyer has a strong concern, such as a failed project with a previous vendor, acknowledge it in the opening slides. Leaving it until late lets it colour everything that comes before.
• In the appendix, for the rest. Anything occasional or technical.

This follows the overall order set out in how to structure a sales deck that closes, where objections come just before pricing and the next step.

Backup slides: the objections you don’t show

Backup slides are the slides you hope not to need. Keep a set ready for the occasional objections: security and compliance, data handling, support hours, contract flexibility, company background. Give each a clear title so you can find it quickly in the meeting.

When an objection comes up that you have a backup for, jump to it, answer, and return to the main flow. It shows preparation without cluttering the core story. If an objection comes up that you don’t have a slide for, write it down and answer it in the follow-up email. Then add it to your backup set for the next deal.

What to keep off an objection slide

A few things make these slides backfire:

• Arguing with the buyer. “This isn’t really a concern” tells them they’re wrong to worry. Acknowledge the concern, then answer it.
• Unverifiable reassurance. “Trusted by leading companies” answers nothing. Use facts the buyer can check, or don’t make the claim.
• Comparisons that attack competitors. If you compare, compare approaches or outcomes, fairly. Buyers discount slides that run down another vendor.
• Too much text. An objection slide is read under scrutiny. Keep the answer short enough to read in a few seconds.

Turn objections into a living list

The most useful objection slides come from real conversations. After each deal, won or lost, note which objections came up and which answers worked. Update the main deck and the backup set every quarter.

Many teams keep this list as a battlecard: one page per competitor or common objection, with the answer and the evidence behind it. A sales battlecard template is a quick way to set one up.

Over time, your team builds a shared library of honest, tested answers. New reps get up to speed faster, and buyers get clear answers to the questions they were going to ask anyway.