An objection handling template is a worksheet that lists the objections a buyer is likely to raise on a deal, what each one points to, and the first question the rep will ask, then records what the buyer said back. The version below is free to copy.
The worksheet
It has two blocks. Part A is for one deal, filled before and after a call. Part B is the team's library, filled from real calls over a quarter.
- 01Predict from the deal
- 02Name what it points to
- 03Write the first question
- 04Say it out loud
- 05Fill the after-call block
- 06Move patterns into Part B
- 01Predict from the deal
- 02Name what it points to
- 03Write the first question
- 04Say it out loud
- 05Fill the after-call block
- 06Move patterns into Part B
PART A: OBJECTIONS ON ONE DEAL
Deal: ________ Buyer: ________ Call date: ________
BEFORE THE CALL: likely objections
| # | What the buyer may say | What it points to (evidence missing) | First question to ask | Said out loud? |
|---|------------------------|--------------------------------------|-----------------------|----------------|
| 1 | | need / cost / timing / trust / authority | | Y / N |
| 2 | | | | Y / N |
| 3 | | | | Y / N |
AFTER THE CALL: what happened
| # | Exact words the buyer used | Question asked | What the buyer said back | New evidence for the deal | Resolved / open |
|---|----------------------------|----------------|--------------------------|---------------------------|-----------------|
| 1 | | | | | |
| 2 | | | | | |
Next step on the deal (owner, date): ________
PART B: TEAM OBJECTION LIBRARY (update monthly)
| Objection (buyer's words) | Times heard this quarter | What it usually points to | The question that worked best | Example call (link) | Owner |
|---------------------------|--------------------------|---------------------------|-------------------------------|---------------------|-------|
| | | | | | |
The worksheet belongs to the objection section of our discovery call guide. The method behind it is in objection handling; the two most common objections have their own procedures, price and competitor.
Types of sales objections
Most sales objections fall into five types, and each type points to a different gap in the deal. Sorting an objection by type is the fastest way to pick the first question.
Need. "We're happy with how things are." The buyer has not agreed there is a problem worth fixing, or this person does not feel it. Go back to discovery on the problem.
Cost and budget. "It's too expensive" or "there's no budget this year." Usually the cost of the problem was never stated, so the price has nothing to sit against. Ask what leaving it costs.
Timing. "Now isn't a good time." There is no event that makes a decision this quarter matter. Ask what would make it a good time, and what happens if nothing changes.
Trust and alternatives. "We already use someone," "we built it ourselves" or "your competitor is cheaper." The buyer is comparing, and the comparison is not yet on criteria they care about. Ask what the current option was meant to fix.
Authority. "I need to run this by my boss." The approver is unnamed or has not heard the case. Ask what that person would need to see.
Circle the type in the "what it points to" column of Part A. If a rep keeps meeting the same type across deals, the gap usually sits earlier in their discovery calls, and that is the coaching topic.
How to use it
- Predict the objections from the deal, before the call. Look at what the deal is missing. If nobody has said what the problem costs, expect "too expensive." If an incumbent showed up in research, expect "we already use someone." If no approver has been named, expect "I need to run this by my boss." Write the likely words in Part A.
- Name what each one points to. Most objections are a missing piece of evidence wearing a disguise. Circle its type in Part A: need, cost, timing, trust or authority.
- Write the first question, without a rebuttal. The first response to an objection should be a question that finds out more. "Compared to what?" for price. "What made you take the call anyway?" for an incumbent. "What would your boss need to see?" for approval.
- Say each question out loud. Say it to a manager or a colleague taking the buyer's part, or run it in a roleplay built from the deal. Tick the column. A question that reads well on paper often comes out as a rebuttal the first time it is spoken.
- Fill the after-call block within the hour. Use the buyer's exact words. Record what the question uncovered. An objection that ended with a cost figure or an approver's name moved the deal.
- Move the patterns into Part B monthly. Count how often each objection appeared across the team and which first question got the most useful answer. Link one real call per objection, so new reps hear it.
- Retire scripts that do not work. If a question in Part B keeps producing a polite non-answer, replace it. The library is a record of what worked on your calls, and it should change.
Common objections, and where to start
Use this as a seed for Part B until your own calls fill it. Each row gives what the objection usually points to and a first question. Replace any row with the version your buyers use.
| Buyer says | Usually points to | First question | If the answer is vague, follow with |
|---|---|---|---|
| "It's too expensive." | Cost of the problem never stated | "Compared to what?" | "What does it cost you today to leave this as it is?" |
| "We don't have budget this year." | Owner or timing unknown | "When does next year's budget get set, and who sets it?" | "If this were in the plan, whose line would it sit on?" |
| "Now isn't a good time." | No event driving a decision | "What would make it a good time?" | "What happens if nothing changes for six months?" |
| "We already use someone for this." | Incumbent, outcome unclear | "What made you take this call anyway?" | "What would you change about it if you could?" |
| "We built something internally." | Decision against an internal option | "What did you build it to fix, and has it?" | "Who maintains it, and what does that take?" |
| "I need to run this by my boss." | Approver unnamed | "What would your boss need to see to say yes?" | "Could we put that in front of them together?" |
| "Send me some information." | No problem agreed | "Happy to. What should it answer for you?" | "What would make it worth a second conversation?" |
| "Your competitor is cheaper." | Comparison on price alone | "Cheaper for what, exactly?" | "What would you lose by going with the cheaper one?" |
| "We need to think about it." | Concern not yet said | "Of course. What part needs the most thought?" | "Is it the cost, the timing or who else needs to agree?" |
| "We're happy with how things are." | Problem not felt by this person | "What would need to be true for this to be worth changing?" | "Who on the team feels the problem most?" |
The follow-up column matters because the first answer to a good question is often still polite. The second question is where the evidence comes out.
After the first question
The first question buys time and information. What the rep does with the answer decides whether the objection moves the deal.
- Listen to the end. Let the buyer finish, then pause for a second. Reps who start answering mid-sentence miss the part that matters.
- Play it back. Repeat the key words: "So the wiki was meant to fix onboarding, and new CSMs are still shadowing for five weeks." It shows the buyer they were heard and checks the rep heard it right.
- Name what it means for the deal. "Then the question is what those five weeks cost." This turns the objection into the gap the deal needs to close.
- Ask for the next piece of evidence. A figure, a name or a date. If the buyer cannot give it now, agree who will find it and by when.
- Write it down in their words. That line goes in the after-call block.
An objection answered with a rebuttal tends to come back later in the deal. An objection answered with a question, and followed up until it produces evidence, can become the reason the buyer signs.
A cold call version
SDRs meet objections in the first thirty seconds, before there is any deal to read. Part A still works with three changes. Predict objections from the account and role, since there is no deal yet: a VP who owns a budget will say different things from a manager who does not. Keep the first question short enough to say in one breath. And treat a booked meeting as the after-call result, with the objection and the buyer's words logged so the account executive knows what to expect on the first meeting. "We already use someone" on a cold call becomes the first thing to explore in discovery.
Reviewing the worksheet in a one-on-one
The worksheet gives a manager a fast way into a rep's week. Ask for the Part A sheets from the last three calls and look at three things.
Did the predictions match? If a rep keeps predicting price and hearing approval, they are reading their deals wrong, and that is the coaching topic.
Did the first question end in a question mark? If the after-call block shows "Question asked" filled with a statement, the rep is still rebutting.
Did any objection produce evidence? Count the rows that ended with a figure, a name or a date. A rep with none is handling objections politely and leaving the deal where it was.
Pick one row, have the rep say the first question again out loud, and agree which deal they will try it on next.
Filled-in example (illustrative)
This deal is invented to show the worksheet in use. Avery sells a learning platform to Robin Okafor, director of customer success at a 500-person software company. It is their second call.
PART A
Deal: Kelvara Software Buyer: Robin Okafor Call date: Thu
BEFORE THE CALL
| # | What the buyer may say | Points to | First question | Said out loud? |
| 1 | "This is more than we budgeted." | cost (never stated) | "Compared to what? What does slow onboarding cost you today?" | Y |
| 2 | "We built a wiki for this." | decision (incumbent: internal) | "What did you build it to fix, and has it?" | Y |
| 3 | "I'd need to take this to my VP." | owner/approver (unknown) | "What would your VP want to see to say yes?" | Y |
AFTER THE CALL
| # | Buyer's words | Question asked | Buyer said back | New evidence | Status |
| 2 | "Honestly, we built a wiki last year." | "What did you build it to fix, and has it?" | "Onboarding. Nobody reads it. New CSMs still shadow for five weeks." | Problem confirmed, with duration | Resolved |
| 1 | "Feels like a lot for what it is." | "Compared to what?" | "Nothing really. We just don't have a line for it." | Cost not stated; budget timing unknown | Open |
| 3 | (did not come up) | | | | |
Next step: Robin estimates senior CSMs' shadowing hours by Tue; Avery drafts a one-page summary for Robin's VP.
Objection 2 turned into the best evidence on the deal: an internal attempt that failed, with a duration. Objection 1 is still open, and the next step aims at it. In Avery's debrief, Caty points out that Avery answered "nothing really" by moving on; the follow-up that was needed was "What does five weeks of shadowing cost, in senior time?" Avery adds it to Part B to try on the next price objection.
Turning the worksheet into objection handling training
Training on the worksheet is one Part B row a week, in three steps:
- Pick the row and play its call. Choose the objection that came up most on recent calls and listen together to the moment it lands.
- Practice it on a live deal. Each rep picks a deal where the objection is likely, runs a short roleplay built from that deal, and gets a debrief against the row.
- Check it on the next real call. In the one-on-one, the manager asks what the buyer said after the first question. If a different question got a better answer, it goes into the row with the call.
Three ways teams misuse it
Using it as a rebuttal script. Teams fill the first-question column with a counter-argument, usually a line about return on investment. The worksheet then trains reps to argue at the moment they should be asking. Every first response in Part A should end in a question mark.
Filling Part B from memory. The library gets written in a workshop, from what managers think buyers say. It ends up full of textbook objections and missing the odd, specific ones that come up every week. Fill it from Part A sheets and call recordings.
Skipping the out-loud column. Reps write a good question and freeze on the call because they have never said it under pressure. The tick box is the reason the worksheet exists. If nobody is available to play the buyer, the rep should at least record themselves.
Practicing every objection before the call
The out-loud column is the hard one at scale. A manager with eight reps cannot play the buyer before every call.
With Replicate Labs, the rep talks to an AI sales expert such as Caty before the call, by voice or video on a call, or by typing when they can't talk, and works through Part A on the live deal: the expert knows what the deal is missing and checks that each likely objection points at a real gap. After the call, the expert records what happened against the deal, and Bryce shows the manager the patterns across the team. For the out-loud column, the expert builds a roleplay from the deal that raises each objection, and debriefs each run until the first question sounds calm.
See overcoming objections and preparing for sales conversations, or talk to us about scoring how your reps handle objections on real calls. For the prep routine around the worksheet, see how to prepare for a sales call.
Fill Part A for one live deal before your next call, and tick the out-loud column only after you have said each first question to someone. If you want an AI sales expert to hear them for your reps, talk to us.
FAQ
What should an objection handling template include?
An objection handling template should include the objections a buyer is likely to raise and the first question the rep will ask for each. Next to each objection, add what it points to in the deal (usually a missing cost, approver or decision), whether the question has been rehearsed out loud, and an after-call record of what the buyer said back. A team version adds frequency and the question that worked best.
How do you create an objection handling script?
Collect the exact words buyers use from real call recordings, group them by what they point to, and write a first question for each, without a rebuttal. Rehearse each question out loud with someone playing the buyer. Then update the script monthly with the questions that produced useful answers on real calls, and drop the ones that did not.
What is the best framework for handling objections?
A simple sequence works best: pause, acknowledge it is a fair concern, ask a question that finds out what is behind it, then address what you learned. Most objections point to missing deal evidence such as an unstated cost or an unnamed approver, so the question is usually more valuable than any rebuttal.
How often should a team update its objection library?
Monthly is a good rhythm for most teams. Count how often each objection came up across the team's calls, check which first questions got the most useful answers, and link one real example call per objection. Retire scripts that keep producing polite non-answers, and add new objections as products and markets change.
What is the difference between an objection and a condition?
An objection is a concern the rep can explore and often resolve, such as price against an unstated cost. A condition is a hard limit, such as a legal requirement the product cannot meet or a contract that cannot end for two years. Treat every objection as an objection until questions show it is a condition, then say so plainly and agree what happens next.