# Objection-to-evidence worksheet

From https://saley.app/guides/sales-objection-handling-examples. Free to copy and edit.

The six filled examples use a fictional seller, Tallyline (scheduling software for clinic groups), and a fictional competitor, Rotawise. Every price, document and page number in them is invented. Replace them with your own objections and your own documents.

## How to fill in a row

1. Objection (their words): write it the way buyers say it. Do not paste customer recordings or personal details.
2. What to find out first: the one question that tells you which version of the objection you are hearing.
3. Source fact: a fact from a document you would be happy to show the buyer.
4. Source file and page: where that fact is written. If no document exists, leave it blank. That is a gap to fix, not a fact.
5. Safe response: one or two sentences that stay inside the source fact.
6. Do not promise: the commitment you must not make (a discount above your limit, a feature you lack, a date you cannot support).
7. Next step: what you want the call to end with.
8. If no source supports it: what you say instead of guessing.

## Your objections

| Objection (their words) | What to find out first | Source fact | Source file and page | Safe response | Do not promise | Next step | If no source supports it |
| --- | --- | --- | --- | --- | --- | --- | --- |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |

## Fictional examples

### 1. Price against a free alternative

- Objection (their words): "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 file and page: 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.

### 2. A competitor already on the shortlist

- Objection (their words): "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 file and page: 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.

### 3. Not this quarter

- Objection (their words): "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 file and page: 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.

### 4. Someone else decides

- Objection (their words): "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 file and page: 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.

### 5. Where is our data?

- Objection (their words): "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 file and page: 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.

### 6. We tried this before

- Objection (their words): "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 file and page: 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.
