Practice resource

Sales objection handling examples, from objection to evidence

A good answer to an objection is short, true and backed by something you can show. Each example below runs the same chain, from the buyer’s words to the fact you can stand behind, and the worksheet lets you build the same chain for your own objections.

The worksheet is free to copy, with no form. Saley, the Mac app that can use these answers on a live call, needs macOS 13 or later and starts at $69/month for 20 call hours.

How to read the examples

Objection, question, fact, response, limit, next step.

Each example gives the objection in the buyer’s words, what to find out first, the source fact and where it is written, a safe response that stays inside that fact, what not to promise, and the next step. The last line says what to do if no source supports the answer.

Fictional seller

Fictional seller: Tallyline, scheduling software for clinic groups. Its prices, documents and page numbers, and the competitor Rotawise, are invented for these examples. None of this is Saley’s pricing or a customer conversation.

Six worked examples

Six objections, each traced to a source.

Price against a free alternative

“Your price is double what we pay for spreadsheets.”

  • What to find out first. What does the spreadsheet process cost in scheduler hours each week, and who pays for those hours?
  • Source fact. Team plan is $18 per scheduler per month, billed annually. Source: pricing-2026.pdf, page 2.
  • Safe response. Fair point: the spreadsheet costs nothing to license. The real comparison is the hours your schedulers spend on it. Let's check together whether $18 a month covers those hours. If it doesn't, it isn't worth it.
  • Do not promise. A payback figure you have not worked out with them, or a discount you are not allowed to give.
  • Next step. Send a one-page calculation using their own hours and book 15 minutes to go through it.
  • If no source supports it. If you do not know the price for their team size, say so and confirm it in writing the same day.

A competitor already on the shortlist

“We're already looking at Rotawise.”

  • What to find out first. What made you shortlist them, and what would they have to fix for you to choose them?
  • Source fact. Rotawise is strong on mobile shift swaps. Our difference: union rule checks run before a rota is published. We do not offer payroll export. Source: battlecard-rotawise.docx, page 1.
  • Safe response. Rotawise is good at mobile shift swaps, so if that is the main need they are a fair choice. Where we differ is checking union rules before a rota goes out. Has a rule breach ever forced you to republish one?
  • Do not promise. Payroll export, which Tallyline does not offer, or claims about what Rotawise cannot do.
  • Next step. Agree the two criteria that decide it and compare on those in the next call.
  • If no source supports it. If they ask about a Rotawise feature you have not checked, say you have not checked it rather than guessing.

Not this quarter

“This isn't a priority until next quarter.”

  • What to find out first. Is that a budget date, another project in the way, or a polite no?
  • Source fact. Implementation takes about three weeks from signature, including two scheduler training sessions. Source: onboarding-plan.pdf, page 1.
  • Safe response. Understood. If you want it live before your summer rota, the three weeks of setup would need to start by early May. Shall we put a check-in on the calendar for mid-April so you can decide then?
  • Do not promise. A shorter implementation than the plan states, or holding a price beyond its written validity.
  • Next step. Book the check-in date and ask what has to be true by then.
  • If no source supports it. If they ask for a go-live date you cannot support, give the plan's three weeks and confirm anything faster in writing.

Someone else decides

“I'll need to run this past our operations director.”

  • What to find out first. What will the director push back on first, and what do they need to see to say yes?
  • Source fact. Call goal: a second call with the budget owner before any proposal is sent. Source: Playbook entry: Call goal.
  • Safe response. That makes sense. Rather than you carrying my pitch to them, could we find 20 minutes with the director and you? I'll keep it to the two problems you described today.
  • Do not promise. Special terms for the director, or a proposal before you know what they care about.
  • Next step. Book the call with the director while you are both still on this one.
  • If no source supports it. If you do not know who signs, ask. Do not assume the director holds the budget.

Where is our data?

“Where is our data stored, and who can see it?”

  • What to find out first. Is this a requirement from security or legal, and is there a questionnaire to fill in?
  • Source fact. Customer data is hosted in the EU (Frankfurt region). Backups are kept for 30 days. Support staff access requires customer approval. Source: security-overview.pdf, page 3.
  • Safe response. Our security overview says customer data is hosted in the EU, in the Frankfurt region, and backups are kept for 30 days. I'll send you that page and pass your questionnaire to our security lead.
  • Do not promise. Anything the document does not say, such as on-premise hosting or a certification you do not hold.
  • Next step. Send the page and confirm who owns the questionnaire on their side.
  • If no source supports it. If the document does not answer it, say you will get a written answer from the security lead.

We tried this before

“We tried a tool like this and nobody used it.”

  • What to find out first. What happened in the first month, and who stopped using it first?
  • Source fact. Week 1: schedulers trained in two 45-minute sessions. Week 2: managers review the first swap requests with the customer success lead. Source: onboarding-plan.pdf, page 2.
  • Safe response. That happens. The plan here is two short training sessions in week one and a review of real swap requests in week two. What would have made the last tool stick?
  • Do not promise. An adoption rate, or that this tool will succeed where the last one failed.
  • Next step. Ask them to name one owner on their side for the first month.
  • If no source supports it. If they ask for adoption results you do not have, say you do not have them rather than inventing a number.

Worksheet

Build the same chain for your own objections.

The worksheet has the six examples above and blank rows for your own. Open the CSV in any spreadsheet app, or print the Markdown version.

  1. Write the objection the way buyers say it, in their words. Do not paste customer recordings or personal details.
  2. Write the one question that tells you which version of the objection you are hearing.
  3. Find the fact in a document you would be happy to show the buyer, and note the file and page. If no document exists, leave it blank: that is a gap to fix, not a fact.
  4. Write a response of one or two sentences that stays inside that fact.
  5. Write the promise you must not make: a discount above your limit, a feature you lack, a date you cannot support.
  6. Write the next step you want the call to end with.
  7. Write what you say when no source supports the answer.

Using it with Saley

Each row belongs in two places.

The objection and response

Put them into your Playbook’s objection to response pairs, with the “do not promise” line in the same entry. Automatic objection cards do not search your uploaded files. They use the recent conversation, your structured Playbook and the attached Prospect Brief.

The source document

Upload the document itself as a Playbook file. Ask Saley and Next question can retrieve eligible uploaded files and show the filename and page number when a citation is available.

You can use the worksheet without Saley. It is a plain spreadsheet, and the chain works the same on paper.

Objection examples FAQ

Questions about handling objections with evidence

What is a good way to handle a price objection?

Find out what the price is being compared with before you defend it. In the price example on this page, the buyer compares a subscription with a free spreadsheet, so the useful question is what the spreadsheet costs in staff hours. The response stays inside the written price and avoids a payback figure nobody has worked out.

How do I handle an objection when I don't know the answer?

Do not improvise. Say you will confirm it in writing, note it as an action item and send the answer with its source. Each example on this page ends with what to say when no source supports the answer.

What should an objection handling worksheet include?

The objection in the buyer's words, what to find out first, the source fact with its file and page, a safe response, the promise you must not make, the next step, and what to say when no source supports the answer.

Can Saley use this worksheet during a call?

Not as a file for automatic cards to search. Put each objection and response into your Playbook so automatic objection cards can use it, and upload the source documents so Ask Saley and Next question can retrieve them and show the file and page when a citation is available.

Are these real sales conversations?

No. Tallyline, Rotawise and every price, file and page number on this page are fictional, written for this guide.

Get Saley

Want these answers on screen during the call?

Put your objection pairs and source files into Saley's Playbook on your Mac. From $69/month.

From $69/month · Cancel anytime · macOS 13+ · Apple Silicon & Intel