Objection handling template
Most objection handling guides are lists of clever rebuttals, and rebuttals are the wrong tool: they answer the words the buyer used, not the concern behind them. 'It's too expensive' can mean the buyer has no budget, does not see the value, has a cheaper quote, or needs a reason to say no. This template starts every objection with what usually sits behind it and a question that finds out which one you are facing, then records the response and proof that have actually worked on your deals.
Download it
What you get
- An objection library with the concern behind it, a clarifying question, a response, and proof for each
- Example rows for price, timing, status quo, competitor, and authority objections
- An objection capture log so the library is built from real calls rather than guesses
- A quality checklist for adding new responses and a quarterly review routine
Who it's for
- Enablement teams building an objection library from call recordings
- AEs and SDRs who want responses that come from won deals
- Frontline managers running objection roleplays
What's inside
5 sections, each listed with its own size. The first is previewed below; the remaining 4 come with the download, with blank rows ready to fill in.
| Section | Size | Previewed |
|---|---|---|
| Objection library | 6 columns, 5 worked example rows | Below |
| Objection capture log | 7 columns, 2 worked example rows | In the download |
| Before a response goes in the library | 8-point checklist | In the download |
| Quarterly review | 5-point checklist | In the download |
| Why rebuttals do not work | Guidance notes | In the download |
Preview of section 1
Objection library
One row per objection. Ask the clarifying question before choosing a response.
| Objection (buyer's words) | What usually sits behind it | Clarifying question | Response that has worked | Proof | Stage it appears |
|---|---|---|---|---|---|
| It's too expensive. | No budget this year; value not clear; cheaper quote in hand; looking for a reason to say no | Too expensive compared with what: your budget, another quote, or what you expect to get from it? | If budget: offer a smaller first phase tied to one outcome. If value: go back to the cost of the problem they described. If a cheaper quote: compare scope line by line. | Customer case with payback period; phased pricing option | Proposed |
| Now isn't a good time. | Competing priority; no trigger event; champion lacks support to push it | What would need to be true for this to be the right time? | Agree a specific date to revisit tied to their event (planning cycle, new hire, renewal of current tool), and ask what they will do about the problem in the meantime. | Timeline showing implementation fits before their planning cycle | Validated |
How to use it
1. Collect objections from recordings, not memory
Pull 20 to 30 recent calls, including lost deals, and log every objection word for word in the capture log. The objections reps remember are the dramatic ones; the ones that cost deals are often quieter.
2. Write what usually sits behind each objection
For each objection, list the two or three concerns it commonly stands for. This is the column that changes how reps respond, because it stops them answering the surface words.
3. Always ask the clarifying question first
The response column is only used after the clarifying question tells you which concern you are dealing with. A rep who goes straight to the response is guessing.
4. Only add responses that have worked
A response goes in the library when it has moved a real deal forward, with the deal named in the proof column. Marketing-written responses that have never been used on a call go in a draft tab until someone tries them.
5. Roleplay the top five every month
Pick the five most frequent objections from the capture log and roleplay them in a team meeting. Practice on the clarifying question matters more than practice on the response.
Frequently asked questions
What is an objection handling template?
A shared document listing common buyer objections, what usually sits behind each one, a question to clarify it, a response that has worked on real deals, and proof to back it up. It is built from call recordings and reviewed each quarter.
What are the most common sales objections?
Price, timing, satisfaction with the status quo, a competitor's offer, and needing someone else's approval come up in most B2B sales. The exact wording and frequency vary by market, so build your list from your own calls.
What is the best way to handle an objection?
Acknowledge it, ask a clarifying question to find the concern behind it, then respond to that concern with something specific and a piece of proof. Skipping the question and going straight to a rebuttal is the most common mistake.