how to handle "your competitor is cheaper" without racing to a discount

by Isaiah Rios, founder of Brutus AI

call example

prospect:"we got a quote from one of your competitors and it came in about thirty percent cheaper than what you're proposing."

rep:"ok, that's a real gap. let me see what we can do on our pricing this week."

prospect:"yeah, it's a pretty significant difference. our finance team is leaning that way."

rep:"before we touch our number, can you walk me through what's in their quote? same seat count, same onboarding, same support tier, same contract length?"

prospect:"honestly, i'd have to look. i think it's their standard package, but i'm not sure on support."

"your competitor is cheaper" is not a price objection. it is a comparison test. the prospect has two quotes in front of them and is asking whether you will fold first or explain the gap. most reps fold. they defend the number, list a few features, or volunteer a discount before they have even asked what the cheaper option includes. now the call is a price negotiation instead of a vendor decision, and you started it. the fix is not to argue with the number. it is to compare what each number is actually buying. cheaper usually means fewer seats, weaker support, slower onboarding, less reliable coaching, a different contract term, or risk the buyer has not priced into their spreadsheet yet. before you touch your invoice, find out whether the prospect is comparing the same thing on both sides of the page. apples-to-apples is a yes or no question. if the answer is no, the cheaper quote stops being the same conversation.

why this happens

buyers under pressure simplify. a real vendor decision involves scope, risk, support quality, implementation effort, contract length, and outcomes. that is too many variables to weigh on a deadline, so the brain reduces all of it to the one column that is easy to compare: invoice price. it feels rational. it is also the move a procurement team coaches the buyer to make. naming a cheaper competitor is pressure, not a final answer. the cheaper quote is almost never the same offer. it usually pushes work, risk, or scope back onto the buyer in a way that does not show up on the price line. when the rep matches the number without testing the comparison, both vendors end up in a race the buyer wins by default. the rep loses margin. the buyer loses the chance to find out which option actually fits. the only way out of the shortcut is to slow the comparison down and make it honest.

free sales rep dna test

which sales habit is costing you margin?

take the Sales Rep DNA Test and see whether you defend price, avoid tension, over-explain, or stall at the close.

take the dna test

counter-frames

apples-to-apples test

are we comparing the same scope, the same support, and the same outcome, or just two invoice numbers? get the comparison on the table before either side argues about price.

scope gap

what does the cheaper quote leave your team responsible for after the contract is signed? onboarding, integration, training, and adoption rarely show up on the line item but always show up on the calendar.

negotiation pressure

if the price were identical on both proposals, which option would you trust to get the result you actually need? the answer surfaces whether price is the issue or the lever.

risk test

where would the cheaper option create work for your team a quarter from now? a vendor that ships a thinner offer is moving risk, not removing cost.

common mistakes and fixes

defending the price the second a cheaper competitor is named. fix: stop. ask one scope question first. you cannot defend a number against a quote you have not seen.
matching the cheaper quote in the first 60 seconds. fix: never match on a reflex. matching teaches the buyer that your real price was the lower number all along, and procurement will use that number on every renewal.
attacking the competitor. fix: do not name them as bad. name what their offer is missing. "i don't know what's in their quote, but here is what's in ours" beats any insult.
listing features instead of comparing scope. fix: a feature list is not a comparison. swap the feature dump for a side-by-side on seats, support tier, onboarding plan, and contract term.
treating a procurement pressure tactic like a real product objection. fix: if the buyer cannot tell you what is in the cheaper quote, you are not in a product debate. you are being shopped. respond with scope questions, not price moves.
assuming "cheaper" means "better deal" without testing it. fix: better deal is total cost over the contract, not the line on the proposal. ask what the cheaper option costs the buyer in time, risk, and rework before you touch your number.

when to walk away

the prospect can confirm identical scope, identical support, identical onboarding, and identical contract terms, and price is the only remaining decision driver
the prospect refuses to share what is in the cheaper quote and will not let you compare scope on the call
procurement has issued a sealed bid where price match is the only acceptable response and your minimum is above their target

what Brutus does live

Brutus listens for the moment a rep starts justifying price after a competitor is named. the tells are longer sentences, hedged phrasing, the word "flexible," and the rep floating a discount before any scope question has been asked. the live cue is: "don't defend the price. ask what's included in the cheaper quote."

cue 01

faq

Should I ever match a competitor's price?

you can match a competitor's price, but only after you know the comparison is real. first confirm scope, seat count, onboarding, support, contract term, implementation work, and risk. if those items are actually identical and the buyer would choose you at the same number, then you are negotiating a margin decision. if they are not identical, matching too early rewards a bad comparison and teaches the buyer that your first proposal was inflated.

How do I avoid sounding like I am attacking the competitor?

keep the language neutral and compare the offer, not the company. say that you do not know what is inside their quote yet, then ask what support, onboarding, usage limits, and contract terms are included. the tone should be practical, not defensive. your job is to help the buyer understand whether they are buying the same outcome, not to convince them the other vendor is weak.

What if the cheaper competitor really is good enough?

if the cheaper option is truly good enough for the problem, say so and do not chase the deal past your minimum. the point of the scope test is not to force every buyer back to you. it is to find out whether the cheaper quote creates a gap the buyer has not priced in. if there is no gap, protect margin and leave the door open for a future conversation when the stakes change.