The objection handling matrix: 11 field objections, what they hide, and what to answer

An objection handling matrix is a shared reference that lists, for each common objection, what it usually means, the question that reveals it, the answer and the proof. The eleven below come up again and again in face-to-face selling, at a client's kitchen table, in a showroom or on a B2B field visit. Copy them, then rewrite them in your clients' own words.

How to read this objection handling matrix

Each objection has five lines, in the order they are used in the meeting. The question always comes before the answer: that is the core of the CRAC method, and the reason the matrix works. The answers are examples to adapt to your offer; the proof must be something you actually have.

Price and budget objections

The family every rep meets first, and the one where a discount is most tempting. The full method is on our page about the price objection.

• Objection. “It's too expensive.”
• What it usually hides. The value is not yet connected to the client's own problem, or another doubt sits behind the price.
• Question to ask. “Too expensive compared with what: your budget, another quote, or what you had in mind?”
• Answer. Go back to the need stated during the discovery and to what the status quo costs the client.
• Proof. A calculation with the client's own figures: bills, premiums, current costs.

• Objection. “I have a cheaper quote.”
• What it usually hides. A different scope, product or service level, or a test to see whether your price moves.
• Question to ask. “Would you show it to me? I'll tell you honestly where we differ.”
• Answer. Compare line by line; if the other quote covers the same thing for less, say so.
• Proof. The two quotes side by side: scope, brand and model, installation, warranty, lead time.

• Objection. “The monthly payment is too high.”
• What it usually hides. A real cash-flow constraint, not a doubt about value.
• Question to ask. “What monthly amount would be comfortable for you?”
• Answer. Adjust the term, the deposit or the scope; never the value of what you promised.
• Proof. Two or three written financing or phasing options the client can compare.

Time and decision objections

These objections postpone rather than refuse. The detailed method is on our page about the “I need to think about it” objection.

• Objection. “I need to think about it.”
• What it usually hides. An unspoken doubt about the price, the product, the company or the timing; sometimes a real need for time.
• Question to ask. “So that your thinking is useful, what exactly would you like to think over?”
• Answer. Deal with the point named straight away, then agree on a dated next step.
• Proof. A one-page summary in the client's words, with the open questions and the date.

• Objection. “I have to talk to my wife.”
• What it usually hides. A decision-maker who is not in the room, or a polite way to postpone.
• Question to ask. “What do you think she will ask first?”
• Answer. Prepare the answer together and propose a short meeting with both of them.
• Proof. A document written for the person who was absent, not the brochure.

• Objection. “Not now, maybe next year.”
• What it usually hides. No perceived urgency, or a budget planned for later.
• Question to ask. “What would need to happen for this to become a priority?”
• Answer. Show honestly what waiting costs; if the client is right to wait, agree on when to talk again.
• Proof. The cost of waiting, calculated with the client's figures, not a false deadline.

• Objection. “Send me a proposal by email.”
• What it usually hides. A polite exit, or a real need to share the decision internally.
• Question to ask. “Which two points must it answer for you to be able to decide?”
• Answer. Send it, but agree now on the date you will go through it together.
• Proof. A short proposal built around those two points, sent the same day.

Trust and risk objections

Answered with proof and guarantees, never with enthusiasm.

• Objection. “I don't know your company.”
• What it usually hides. Fear of the installer or advisor who disappears after the signature.
• Question to ask. “What would reassure you about who we are?”
• Answer. Explain who will do what after the signature, with names and dates.
• Proof. Local references who agree to be called, the company's registration, its insurance certificates.

• Objection. “What if it doesn't deliver what you promise?”
• What it usually hides. A bad past experience, the client's own or a neighbour's.
• Question to ask. “Has that happened to you before? What went wrong?”
• Answer. Separate what you commit to in writing from what depends on conditions you do not control.
• Proof. The written warranty and the assumptions behind any estimate, stated plainly.

Status quo and competition objections

The client already has something. The goal is not to criticise it, but to find what it does not do. The same logic applies at first contact, covered on our page about the “not interested” and “no time” objections.

• Objection. “I already have an advisor.”
• What it usually hides. The need exists; the question is whether it is well served.
• Question to ask. “If you could improve one thing with your current advisor, what would it be?”
• Answer. Work on that one point; if the answer is “nothing”, thank the client and leave.
• Proof. A concrete comparison on that point only, never a criticism of the competitor.

• Objection. “What we have works fine.”
• What it usually hides. No visible pain, or a cost of change that feels higher than the cost of staying put.
• Question to ask. “What would make you change in the next two years?”
• Answer. Look at the total cost of staying as you are, including what is coming: maintenance, end of life, contract renewal.
• Proof. The age and condition of the current equipment or contract, checked together.

How to build your own matrix

Start from real meetings, not from a brainstorm. For two weeks, ask each rep to write down every objection in the client's exact words. Group them by family, keep the ten or twelve that come back most, and fill in the five lines together in a team meeting. The best answers often come from the reps who close most, not from the manual. Review the matrix every quarter: objections shift with prices, products and the news. The general method behind each line is in our guide to objection handling.

The weak point of any matrix is that first step: reps remember objections through the outcome of the meeting, and the exact words are lost. MIHOS records in-person meetings with the client's consent, finds the objections that were actually raised and how each was handled against your method, then turns them into AI role plays. The matrix is then built from what clients said, not from what the team remembers.

Frequently asked questions

What is an objection handling matrix? A reference table that lists common objections with, for each one, what it usually hides, the question to ask, the answer and the proof. It is used to prepare meetings and to run role plays.

How many objections should it contain? Ten to fifteen is enough for most field teams. Beyond that, reps stop using it. Keep the objections that come back every week and drop the rare ones.

Should reps learn the answers by heart? No. They should know the question by heart, because it comes first and under pressure. The answer has to adapt to what the client says.

Can I download this matrix? This page is the matrix: copy the lines you need into your own document or your CRM, and rewrite them in your clients' words.