Sales enablement · 12 min read · Updated 1 Aug 2026
Objection Handling Template (Free Sales Objection Handling Matrix)
A blank objection handling matrix you can fill in today, plus the guidance for what belongs in each field. Built around the concern beneath the sentence, because reps who answer the words a buyer said rather than the worry behind them lose deals they had already won.
Copy pastes straight into Google Sheets or Excel with the columns intact. Downloads are free with a work email.
The objection handling template
This is exactly what you get when you copy or download. Blank fields are yours to fill in; each table ships with one example row to show the pattern, which you delete.
Matrix header
Fill this in first. The last field matters most: a matrix reps cannot reach during a call is a document, not enablement.
- Product and segmentThe specific product and deal shape this covers
- Competitors coveredNamed products whose claims appear below
- OwnerOne named person, not a team
- Last verifiedThe date every competitor claim below was last checked
- Where reps access thisThe exact place they open it, in the tools they already use
1. Objection categories
First row is an example, delete it. Categorise before you script. The category tells a rep which of the responses below to reach for, and whether the objection is even theirs to solve.
| Category | What it sounds like | What it usually means | Stage it appears at | Who resolves it |
|---|---|---|---|---|
| ExamplePrice | "You're more expensive than Acme" | I cannot justify the difference internally | Late, once options are shortlisted | Rep, with a pricing proof point |
2. The objection handling matrix
First row is an example, delete it. The core of the template. The third column is the one people skip, and it is the one that makes the response work.
| What they say, verbatim | Category | The concern underneath | What to say back | Proof to send |
|---|---|---|---|---|
| Example"You're more expensive than Acme" | Price | I have to defend this to finance | "Let's compare the 12-month total, including the add-ons their plan needs for SSO" | Pricing comparison one-pager |
3. Diagnostic questions to ask first
First row is an example, delete it. A question before an answer. Responding to the literal sentence is the most common way a handled objection turns into a lost deal.
| Question to ask | Objection it follows | What it uncovers | How to use the answer |
|---|---|---|---|
| Example"When you say expensive, what are you comparing it against?" | Price | Whether it is a budget limit or a value gap | Budget: discuss scope. Value: return to outcomes |
4. Competitor-specific claims
First row is an example, delete it. What each competitor actually says about you, and the factual answer. Every row needs a source and a date, because their claims change.
| Competitor | Claim they make about us | Is it true, partly true or false | Our factual response | Source + date |
|---|---|---|---|---|
| ExampleAcme Analytics Pro | "They can't do custom reporting" | Partly true: no report builder, scheduled exports yes | "We cover scheduled exports and the standard reports; here's what we don't do" | Heard in 3 deals, Mar |
5. Price and budget objections
First row is an example, delete it. Price gets its own section because it is the most frequent objection and the one most often mislabelled. Half of these are value objections wearing a price costume.
| Price objection | What is really being compared | How to reframe it | Evidence to use | When to hold, when to concede |
|---|---|---|---|---|
| Example"Acme quoted us 30% less" | Entry tier against our full plan | Compare like for like over 12 months, with add-ons | Both public pricing pages, dated | Hold: the gap closes once SSO is added |
6. Do not say
First row is an example, delete it. Objection handling is where reps are most tempted to overstate, because they are under pressure and defending. Disparaging a named competitor loses buyer trust and carries real legal risk.
| Avoid saying | Say instead | Why |
|---|---|---|
| Example"Their product is unreliable" | "Here's what customers mention in their public reviews" | Verifiable, and it does not sound defensive |
7. Practice and rollout
First row is an example, delete it. A matrix nobody has rehearsed is a document reps read once. This section is what turns it into something they can say under pressure.
| Objection to master | Who needs it | How we practise it | Owner | Checked by |
|---|---|---|---|---|
| Example"You're more expensive than Acme" | All mid-market AEs | Live role-play in the weekly sales meeting | Sam, Enablement | 30 Apr |
8. What the objections tell us
First row is an example, delete it. Objections are free market research. This section sends the pattern back to the teams who can remove the objection instead of answering it forever.
| Objection pattern | How often it appears | What it tells us | What we will do | Owner and date |
|---|---|---|---|---|
| ExampleSSO raised as a blocker | In most mid-market deals | Our packaging is the problem, not the pitch | Move SSO into the entry tier | Marie, PMM, 14 Apr |
How to fill in your objection handling
How to fill in the objection handling matrix header
Four of these fields are administrative and one decides whether the work gets used. "Where reps access this" is the field that separates enablement from documentation. A matrix in a wiki nobody opens during a live call has the same practical value as no matrix at all, and most teams discover this only after building one.
Product and segment
Objections differ sharply by segment: "mid-market, 50-200 seats, ops-led evaluations". A single matrix covering every segment ends up generic enough to be useless in all of them.
Competitors covered
Name the products whose claims appear in section 4. If a competitor is not listed, a rep hearing their name should know this document does not cover them rather than guessing.
Owner
One named person: "Marie, PMM". Objection content decays faster than most sales material, because competitors change their claims specifically to counter yours.
Last verified
The date the competitor claims were last checked. Anything older than a quarter should be treated as unverified, and a rep quoting a stale competitor price in a live deal is the exact failure this field prevents.
Where reps access this
Be literal: "pinned in the deal room template and in the CRM opportunity sidebar". If the honest answer is a document in a shared drive, fix that before writing any content, because usage is the entire measure of success here.
How to fill in objection categories
Categorising before scripting is what stops this template becoming an unusable list of forty responses. Categories let a rep recognise the shape of what they are hearing, and, more importantly, tell them whether the objection is theirs to solve at all. Five or six categories is the working range.
Category
The durable groupings are price and budget, need and value, authority and process, timing and priority, trust and risk, and competitor-specific. Most objections in most B2B deals fall into these six, and starting from them beats inventing a taxonomy.
What it sounds like
One real sentence you have actually heard: "You're more expensive than Acme." Not a paraphrase. Reps recognise the category by the wording, and cleaned-up wording is not what they hear.
What it usually means
The concern beneath the sentence: "I cannot justify the difference internally." This is the whole reason to categorise, because the surface sentence and the underlying worry rarely match.
Stage it appears at
Early objections are usually about relevance and fit; late ones are about risk and justification. The same words at discovery and at contract mean different things, and knowing the stage changes the correct response.
Who resolves it
Rep, solutions engineer, manager, or nobody, because it is a genuine disqualifier. Naming "nobody" is valuable: some objections mean the deal should be qualified out, and a matrix that never says so trains reps to fight everything.
How to fill in the objection handling matrix
This is the core of the template and its third column is the one that makes it work. Most objection documents jump straight from what the buyer said to what the rep should say, and that gap is where the scripted, slightly robotic quality of bad objection handling comes from. Naming the concern underneath forces the response to answer the real question.
What they say, verbatim
The buyer's literal words, in quotes. Collect these from call recordings rather than from memory, because remembered objections are already summarised into your categories and lose the phrasing reps will actually hear.
Category
One of the categories from section 1, so the matrix stays navigable as it grows past twenty rows.
The concern underneath
The real worry: "I have to defend this to finance." Answering the surface sentence instead of this is the single most common failure in objection handling. "You're expensive" answered with a feature list addresses nothing the buyer was actually thinking.
What to say back
Written the way a rep would say it out loud, in one or two sentences, no jargon: "Let's compare the 12-month total, including the add-ons their plan needs for SSO." Read it aloud before you save it. If it sounds like marketing copy, it will not be said.
Proof to send
A named, linked asset: "pricing comparison one-pager". If a rep has to hunt for it, they will send nothing. Rows whose proof does not exist are a task for enablement, not a gap to leave blank.
How many rows
Fifteen to twenty-five covering the objections you actually hear. A matrix of sixty rows including hypotheticals is a reference document, and reps do not read reference documents between calls.
How to fill in diagnostic questions
The instinct when an objection lands is to answer it. That instinct loses deals, because the same sentence carries several different meanings and the wrong answer confirms the buyer's doubt rather than resolving it. A short question first costs ten seconds and changes which of your responses is correct. This section is what most objection templates leave out entirely.
Question to ask
Open, short, genuinely curious: "When you say expensive, what are you comparing it against?" Not a rhetorical question with a trap in it, which buyers detect immediately and resent.
Objection it follows
Link each question to the objection it belongs after, so a rep scanning the matrix finds the question before the answer rather than instead of it.
What it uncovers
The distinction the question resolves: "whether it is a budget limit or a value gap". If a question does not separate two different situations, it is conversational filler.
How to use the answer
Both branches, briefly: "Budget: discuss scope. Value: return to outcomes." A question with no branching plan just delays the same wrong answer by one turn.
Keep it to one question
One question, then answer. Two in a row feels like an interrogation and shifts the tone of the call. The goal is to understand the objection, not to postpone responding to it.
How to fill in competitor-specific claims
This section covers what competitors say about you in deals, which is different from objections buyers arrive at themselves. It needs a discipline the rest of the template does not: an honest verdict column. A response that denies a partly-true claim is the fastest way to lose a technical buyer, because they will check.
Claim they make about us
Their words as relayed by the buyer: "They can't do custom reporting." Collect these from loss interviews and call recordings, which is also why the win/loss report and this matrix should be maintained by people who talk to each other.
Is it true, partly true or false
The most important column and the one usually missing. Be honest: "Partly true: no report builder, scheduled exports yes." Most competitor claims are partly true, and a matrix that marks everything false teaches reps to distrust the whole document.
Our factual response
Concede the true part, then correct the frame: "We cover scheduled exports and the standard reports; here's what we don't do." Conceding first is what makes the correction credible, and it is counterintuitive enough that reps need to see it written down.
Source + date
Where you heard it and when: "heard in 3 deals, Mar". Claims made once are anecdotes; claims made repeatedly are a competitor's live talk track and worth a considered answer.
Feed this back to the battlecard
Anything in this section that recurs belongs on the competitor's battlecard too. This template is the depth; the battlecard is the one-screen version a rep scans before a call.
How to fill in price and budget objections
Price gets its own section because it is the most frequently reported objection and the most frequently mislabelled. A substantial share of recorded price objections are value objections in disguise: the buyer did not fail to afford it, they failed to see why it was worth it. The second column is where you make that distinction visible.
Price objection
The real sentence, including the number if they gave one: "Acme quoted us 30% less." Vague versions cannot be answered specifically, and specificity is the only thing that works here.
What is really being compared
Almost always an unlike-for-unlike comparison: "entry tier against our full plan". Establishing what is in each quote is most of the work, and doing it as a question rather than an assertion keeps the buyer on your side.
How to reframe it
Move to the comparison that is actually fair: twelve-month total, including the add-ons their plan requires. Not "we're worth more", which asserts the thing in dispute.
Evidence to use
Both public pricing pages, dated. Never a competitor price you inferred: a prospect who corrects you on a competitor's price has ended your credibility for the rest of the deal, and they usually know the real number.
When to hold, when to concede
Say it explicitly: "hold, the gap closes once SSO is added" or "concede, we are genuinely more expensive for this shape of deal". Reps who are never told when they can stop fighting either discount too early or fight deals they should release.
Watch what price objections tell you
If the same price objection appears in most deals in a segment, it is not an objection handling problem. It is a packaging problem, and it belongs in section 8 rather than being answered forever.
How to fill in the do-not-say list
Objection handling is the moment reps are most likely to overstate, because they are under pressure and defending their own product. This section exists for two reasons that are both real: disparaging a named competitor damages buyer trust immediately, and false factual statements about a named competitor carry genuine legal risk. Four rows drawn from what you have actually heard on calls is enough.
Avoid saying
The real phrases, not hypotheticals: "Their product is unreliable", "They're going out of business", "Nobody actually uses that feature." Pull them from call recordings. Written from imagination, this list covers the wrong things.
Say instead
The sourceable version: "Here's what customers mention in their public reviews." It is more persuasive as well as safer, because it moves from your opinion to evidence the buyer can verify themselves.
Why
One line so the rule sticks: "Verifiable, and it doesn't sound defensive." Reps follow rules they understand and route around rules that feel like legal caution.
Cover the unsourced-claim habit
The most common real-world violation is not insulting a competitor, it is stating their pricing or roadmap from memory. Add a row for it: quoting a competitor's price without a dated source is the practice to stop.
How to fill in practice and rollout
The gap between a rep having read an objection response and being able to say it naturally under pressure is large, and it is the reason so much objection content produces no measurable change. Reading a matrix builds recognition; saying it out loud builds recall. This section is short and it is the difference between the two.
Objection to master
Pick three to five, not the whole matrix. The ones that appear most often and cost the most when handled badly, which is usually the top price objection and the top competitor claim.
Who needs it
Be specific: "all mid-market AEs". Enterprise and SMB reps face different objections, and blanket training on the wrong ones is how enablement loses the room.
How we practise it
Live role-play in an existing meeting beats a new session nobody attends. Recorded self-practice and call-review with real recordings both work. Reading it in a deck does not, however good the deck is.
Owner
The person running the practice, usually enablement or a sales manager, not the person who wrote the content. Authorship and rollout are different jobs and the second one is where this usually stalls.
Checked by
A date to verify it stuck, ideally by listening to real calls rather than asking. Self-reported confidence in objection handling is consistently higher than observed performance.
How to turn objection patterns into decisions
Objections are the cheapest market research a company has: buyers telling you, unprompted and at scale, what is wrong with your positioning, packaging or product. Most organisations spend that signal entirely on responses and never route it to the teams who could remove the objection. This section is that route.
Objection pattern
Something recurring, not a memorable one-off: "SSO raised as a blocker". One buyer's unusual objection is noise; the same objection in most deals in a segment is a finding.
How often it appears
Even roughly: "in most mid-market deals". Frequency is what distinguishes a product gap worth fixing from one worth answering, and it is what makes the case to product credible.
What it tells us
The diagnosis: "our packaging is the problem, not the pitch". Objections that recur despite good handling are almost never objection handling problems.
What we will do
A concrete change: "move SSO into the entry tier". The three usual destinations are pricing and packaging, positioning, and roadmap. Note which, because it determines who owns the row.
Owner and date
A named person outside the sales team in most cases, with a real date, agreed with them before publishing. Findings assigned to a function are the ones still in the matrix a year later.
Sourcing and upkeep: keeping objection handling accurate and used
These rules apply to every section above. Objection handling content fails in two distinct ways, and they need different fixes. It goes stale, because competitors change their claims and their pricing specifically in response to yours. And it goes unused, because it lives somewhere reps do not open when a call is running.
Collect from recordings, not from memory
Remembered objections arrive pre-summarised into your own categories, stripped of the phrasing reps will actually hear. Ten minutes in a call recording tool produces better raw material than an hour of workshop discussion.
Source every competitor claim, with a date
Pricing, packaging and capability statements about a named competitor get a link and a date. A rep who quotes a competitor's price and is corrected by the prospect has lost the deal's credibility, and they will not trust the matrix again.
Never write a response you would not say out loud
Read each row aloud before saving it. Written responses drift toward marketing language, and marketing language is exactly what a rep will not repeat on a call. If it is unsayable, it is not a response.
Mark partly-true claims as partly true
The honesty column in section 4 is what makes the whole document credible with the people who use it. A matrix that denies every competitor claim gets classified as marketing and stops being opened.
Review quarterly, and on competitor moves
A quarterly pass, plus an immediate check after a competitor pricing change, launch or repositioning. Those events are exactly when their talk track about you changes.
Measure usage, not completeness
The question is not how many objections are covered, it is whether reps used the responses in week three. If usage is low, the problem is length, location or credibility, and adding more rows makes all three worse.
Route recurring objections out of the matrix
The goal is not to answer every objection forever. An objection that appears in most deals should be removed by fixing packaging, positioning or product, and section 8 exists to make that hand-off happen.
How to roll out your objection handling
- 1Copy or download the blank template. Use Copy to paste it straight into Google Sheets or Excel with the columns intact, or download the CSV, Notion or PDF version.
- 2Pull the objections from call recordings, not memory. Remembered objections arrive already summarised into your own categories and lose the exact wording reps will hear.
- 3Delete the example rows. Each table ships with one example row so the pattern is obvious. Remove it before you roll the matrix out.
- 4Categorise before you script. Five or six categories: price, need and value, authority, timing, trust and risk, competitor-specific. The category tells a rep whether the objection is even theirs to solve.
- 5Always fill the concern underneath. Answering the literal sentence rather than the worry behind it is the most common way a handled objection becomes a lost deal.
- 6Be honest in the competitor claims section. Mark partly-true claims as partly true and concede that part first. A matrix that denies everything gets classified as marketing and stops being opened.
- 7Read every response out loud before you save it. If it sounds like marketing copy, a rep will not say it. Unsayable responses are the reason objection documents go unused.
- 8Rehearse three to five, and route the rest out. Practise the objections that cost the most, and send the recurring ones to whoever can fix the packaging or product that causes them.
Objection handling FAQ
What is an objection handling template?
An objection handling template is a structured matrix of the objections your buyers raise, the concern behind each one, the response to give, and the proof to send. Good ones add three things most versions leave out: a diagnostic question to ask before responding, an honest verdict on competitor claims that are partly true, and a route for recurring objections back to the team who can remove them rather than answer them forever.
What are the 5 steps of objection handling?
There is no standards body for this, and the step counts you find vary between three and six depending on who is selling the training. The common spine underneath them is: listen without interrupting, acknowledge the concern so the buyer knows they were heard, clarify what they actually mean with one question, respond to that meaning rather than to the sentence, and confirm the answer landed before moving on. The widely-taught LAER model, from Carew International, compresses this to four: listen, acknowledge, explore, respond. The confirm step is the one most often dropped and the one that prevents an objection resurfacing at contract stage.
What are the 4 P's of objection handling?
Worth being direct: there is no canonical four-P framework, and at least two incompatible versions circulate widely. One gives pause, probe, provide and proceed; another gives personalisation, perceived value, performance value and proof. Neither traces to an attributable origin, and both appear mainly on pages written to rank for the question rather than to teach the skill. The first version is essentially the listen-clarify-respond-confirm spine with alliteration applied. Use that spine and skip the acronym.
What is the AAA model of objection handling?
AAA is most commonly taught as acknowledge, address, ask: acknowledge the concern before answering it, address it with specific information, then ask a question to check the answer landed and to keep the conversation moving. Variants exist, including versions using associate or assure for the middle step, so it is a family of related approaches rather than one defined method. Its useful contribution is the first A. Reps skip acknowledgement and go straight to rebuttal, which reads as confrontational and hardens the objection.
What are the three golden rules for objection handling?
Presented as canonical in a lot of sales content, but there is no agreed set. The three rules that hold up in practice: never answer before you understand what the objection means, because the same sentence carries several meanings and the wrong answer confirms the doubt. Never deny something that is partly true, because the buyer will check and you lose everything else you said. And never fight an objection that is really a disqualifier, because the cost of a badly-qualified deal is higher than the cost of releasing it early.
What are the major objection categories?
Most B2B objections fall into six durable groups: price and budget, need and value, authority and process, timing and priority, trust and risk, and competitor-specific. Some frameworks compress this to three (no need, no money, no trust) or four by adding no hurry. The number matters less than the reason for categorising, which is that the category tells a rep which response to reach for and, critically, whether the objection is theirs to solve at all.
What are the 5 most common objections in sales?
In B2B software, the recurring five are: it costs more than the alternative, we do not have budget this cycle, we are happy with what we have, we need a capability you do not have, and I am not the person who decides. The first is the most reported and the most frequently mislabelled, because a substantial share of recorded price objections are value objections in disguise. The buyer could afford it; they could not see why it was worth it, which is a different problem with a different fix.
What are the most difficult objections to handle?
The ones that are true. A genuine capability gap, a genuinely higher price for that shape of deal, or a genuinely riskier vendor profile cannot be talked away, and attempting it is what costs the deal. The correct handling is to concede the point plainly, scope how much it actually matters for their situation, and let them decide. The second-hardest category is the unstated objection, where the buyer goes quiet: no response works because nobody has said what the problem is, which is why the diagnostic questions section exists.
What is an example of objection handling?
A buyer says "you're more expensive than Acme". Rather than justifying the price, the rep asks what is being compared: "When you say expensive, what are you comparing it against?" The buyer says they were quoted Acme's entry tier. The rep now knows this is an unlike-for-unlike comparison, not a budget limit, and responds: "That tier doesn't include SSO, which was on your requirements list. Let's compare the 12-month total with SSO on both sides." Then sends the dated pricing comparison. One question changed which of three possible answers was correct.
What is the best objection handling technique?
Asking one clarifying question before responding. It is unglamorous and it outperforms every scripted rebuttal, because it converts a guess about what the buyer meant into knowledge. Techniques like feel-felt-found or reframing are useful once you know which objection you are actually facing; applied to a misdiagnosed objection they make things worse, since a confident answer to the wrong question tells the buyer you were not listening.
How do you handle competitor-specific objections?
Start by being honest about whether the claim is true. Most competitor claims are partly true, and the effective pattern is to concede the accurate part first, then correct the frame: "You're right that we don't have a report builder. We do scheduled exports and the standard reports, which covers what your team listed. Here's exactly what we don't do." Denying a partly-true claim loses technical buyers permanently, because they will check. Every claim in your matrix needs a source and a date, since competitor talk tracks change in response to yours.
How do you turn a no into a yes in sales?
Often you should not try. A meaningful share of no's are correct: wrong fit, no real problem, no budget for two quarters. Fighting those produces long-cycle deals that close badly or not at all, and the time is better spent elsewhere. What is worth converting is the no that is really a not-yet or a not-understood, and the way to tell them apart is a question rather than persistence. If the objection survives one clear, honest answer, it is usually information rather than resistance.
What are some creative ways to handle objections?
Creativity is generally the wrong lever, and reaching for it is usually a sign the underlying answer is weak. What actually moves an objection is specificity: a real number, a dated source, a named customer with the same problem, a concrete comparison. The one technique worth borrowing from the creative end is pre-empting: raising the objection yourself before the buyer does, which removes its power and demonstrates that you are not hiding from it. That works because it is honest, not because it is clever.
How do you practise objection handling?
Out loud, against a person, using real objections from call recordings. Reading a matrix builds recognition; saying the response builds recall, and only recall survives the pressure of a live call. Practical formats that work: five minutes of live role-play inside an existing sales meeting rather than a new session, and reviewing recordings of real objections as a group. Pick three to five objections to master rather than the whole matrix, and verify by listening to calls afterwards, since self-reported confidence consistently overstates observed performance.
What is the difference between an objection and a brush-off?
An objection is a specific concern about your product or the deal: it names something. A brush-off is a general deferral, such as "send me some information" or "we're not looking at this right now", that avoids naming anything. They need opposite treatments. Objections should be answered directly. Brush-offs should not be answered at all, because there is nothing there to answer, and the useful move is a question that finds out whether a real problem exists.
What is the difference between an objection handling template and a battlecard?
A battlecard covers one competitor on one screen, with a handful of objection rows among its sections, and is read in the minute before a call. An objection handling matrix covers all objections across all competitors and objection types, with the underlying concern, diagnostic questions, proof assets and a practice plan. The matrix is the depth and the source; the battlecard is the distilled competitor-specific extract. Most teams need both, and they should be maintained by the same person so they do not disagree.
How often should you update objection handling content?
Quarterly as a floor, and immediately after a competitor changes pricing, launches something significant or repositions. Those moments are precisely when their talk track about you changes, which makes your existing responses stale in the way that matters most. Every competitor claim in the matrix carries a date for this reason: anything older than a quarter should be treated as unverified before a rep quotes it.
Who should own objection handling content?
Product marketing usually owns the content, sales enablement owns the rollout and practice, and sales owns the feedback loop that supplies new objections. Splitting authorship from rollout matters: the most common failure is a well-written matrix that nobody rehearsed, which produces recognition without recall. Ownership of the recurring objections that need fixing rather than answering sits elsewhere again, usually with pricing or product.
Can you build an objection handling matrix in Excel or Google Sheets?
Yes, and for most teams it is the right starting point. Use Copy above to paste the structure into a sheet with the columns intact, or download the CSV, with one tab per section and a filter on the category column. The limit is distribution rather than structure: a spreadsheet does not open itself during a live call, and it will not tell you that the competitor pricing in row twelve changed last week. That is why the header asks where reps actually access it.
Keep objection handling current on every competitor
Flares tracks what competitors claim and charge, so every response reflects what they actually say today.
Discover Flares14-day free trial · 30-second setup