"We Have a Quote Thirty Percent Below Yours" — Working the Competing Bid Without Panicking

A buyer says it near the end, usually on a call you thought was a formality. "We have a quote thirty percent below yours." Sometimes they say it flatly, like weather. Sometimes there's a little apology in it, which is worse, because it means they've already decided and they're being kind about it.

Whatever happens in the next ninety seconds decides the deal. Not the next follow-up email. The next ninety seconds.

The two instincts, and why both of them lose

The first instinct is to move toward the number. You hear it, your stomach drops, and something in you wants to say "let me see what I can do." That sentence has ended more good deals at bad prices than any competitor ever has. The moment you say it, you have told the buyer three things: your price was soft, you knew it was soft, and the real number is somewhere below where you started. You have also made every future negotiation with this account harder, because you have taught them that pressure produces movement.

The second instinct is to attack. "Who's the quote from? Oh. Yeah. Look, I don't want to say anything bad about them, but..." and then you say something bad about them. This feels strong and lands weak. The buyer hears a vendor who is scared. Worse, if their champion was the one who sourced the other quote, you have just told a person you need on your side that their judgment is poor. I have watched reps lose deals in that exact sentence, and the loss doesn't show up for two weeks, so they never connect it back.

Both instincts come from the same place: treating the competing bid as a verdict. It isn't. It's information, and it is almost always incomplete information, and your job in the next few minutes is to find out what's actually in it.

Say the boring thing first

Before anything clever, buy yourself room. What I say, more or less verbatim:

"Okay. Thanks for telling me that — a lot of people wouldn't. Can I ask you some questions about their proposal? Not the price. I don't want to see their price. I want to understand what they've scoped, because if they've solved this for less than we can I'd genuinely like to know how."

That last clause is the important one and it has to be true when you say it. You're signalling that you're not about to defend yourself, you're about to investigate with them. It also quietly reframes who is on which side of the table. You are now both looking at a document, together.

Notice what you did not do. You did not concede that the quotes are comparable. You did not ask who the competitor is — you'll usually find out anyway, and asking makes it feel like you're building a rebuttal deck. And you did not react to the number at all. Not a wince, not a "wow." The number is a claim, and you don't argue with a claim you haven't examined.

Also, be honest with yourself about who is saying it. A procurement lead saying it in a scheduled call is running a process, and the number may be directional or may not exist at all. Your champion saying it unprompted on a Thursday afternoon is doing you a favour and probably wants help defending you internally. An end user saying it is usually repeating something they overheard. Same words, three completely different conversations. Ask yourself which one you're in before you open your mouth.

The quote is almost never for the same thing

In my experience the competing bid is cheaper for one of four reasons, and only one of them is a real problem for you.

It's scoped smaller. Something is out of the proposal that will absolutely be needed — the migration, the integration work, the second site, the training, the units nobody counted. Buyers don't hide this. They usually haven't noticed it, because the two documents are formatted differently and nobody has laid them side by side line by line.

It's staged differently. The other vendor has quoted a first phase and will quote the rest later. Their number is real for what it covers and irrelevant to what the buyer actually needs by the end of the year.

It's priced to land. First-term pricing that steps up, or a rate that assumes volumes the buyer won't hit, or a low headline with the expensive part billed as change orders. This is a business model, not a scam, and pointing at it as if it's a scam makes you sound bitter.

Or — and this happens — it is genuinely the same work for less money, because that vendor's cost base is lower or they want the logo badly enough to eat margin. That's the real problem case and I'll get to it.

Until you know which of the four you're in, you have nothing to say. Discounting before you know is just guessing with your own margin.

The three questions

These are the ones I keep coming back to. None of them require you to name a competitor, criticise anybody, or claim to know what's in a document you've never seen. They're all questions the buyer can answer or go find out, and going to find out is itself useful, because it puts them back in the other vendor's inbox asking pointed questions.

One: "What does their number cover between signature and the day this actually works?"

Every industry has a gap here and it's always the same gap: the distance between buying the thing and the thing producing value. Implementation. Onboarding. Data migration. Site prep. Sourcing the first candidates. Getting the trucks scheduled. Ask what's in the other proposal for that period, and ask specifically who does the work.

The answer is often "I assume that's included" — and that word, assume, is the whole conversation. You don't pounce on it. You say: "That might well be. Worth pinning down, because on our side that's a named team and a defined number of weeks, and it's in the figure you're holding."

Two: "When something goes wrong in month four, who picks up?"

Not "what's their SLA." That gets you a document. Ask it as a scenario, in their world, with a failure they've actually experienced before. "The shipment misses the window and the customer is calling you. Who do you call, and are they in your time zone?" "The placement doesn't work out in week three. Who eats that and how fast do they backfill?" "The integration breaks after a release. Is that a ticket queue or a person?"

Buyers are very good at imagining this scenario because they have lived it. And the answer is genuinely differentiating far more often than price is. If your support model is better, this is where it shows up, and it shows up as their story rather than your claim.

Three: "What's the number in year two?"

Or second term, or after the introductory period, or once the pilot volumes end. Whatever the shape of your business, there is a moment where the other vendor's price resets and the buyer has not asked about it. Get them to ask.

"I'd want to see both numbers over the full period you're going to own this, not just the first term. If theirs holds flat, that's a real advantage and you should take it. I'd just want to see it written down."

That last line is doing a lot of work. You have given the buyer permission to prefer the competitor, which makes you credible, and you have sent them to ask a question that very frequently comes back with an uncomfortable answer. You didn't accuse anyone of anything. You suggested they read the whole document.

Reframe onto the review they'll sit in twelve months from now

Here's the thing I wish someone had told me earlier. The buyer is not optimising for price. The buyer is optimising for not being embarrassed.

Somewhere in the next year there is a meeting where this decision gets looked at again. Sometimes it's a formal review, sometimes it's just their boss asking how it's going. Whatever number they signed will have been forgotten. What will be remembered is whether the thing worked, whether it caused chaos, and whether the person who chose it looks smart.

So move the comparison onto that meeting:

"Twelve months from now, when someone asks you how this went — what would have to be true for you to say it went well?"

Then shut up. What comes back is the actual decision criteria, and price is rarely at the top of it. They'll say something like "we didn't have to babysit it," or "we hit the deadline," or "my team stopped complaining." Now you have their words, and you can build the rest of the conversation on those words rather than on yours.

And when you come back to the two proposals, you come back through that frame: "Given that the thing you'd be judged on is the deadline, I'd want to be very sure about who's doing the implementation work in the cheaper option, because that's the part that slips." You are no longer defending a price. You are helping them protect themselves. Those feel completely different to the person on the other end.

When the quote is real and comparable

Sometimes you do the work and the answer is: yes, same scope, same term, same support model, genuinely cheaper. It happens. Pretending otherwise makes you a liar with a worse close rate.

At that point you have a decision to make, and it is a business decision, not a rapport problem. The wrong response is to slide down to their number in one move. The right response is to change the shape of the deal before you change the rate.

The flex order

There is an order to what you give away, and rate is last. Rate is last because it is the only concession that costs you full value, is permanent, and resets every renewal conversation you will ever have with this account.

Term first. Length is the cheapest thing a buyer can give you and often the easiest thing for them to approve, because it doesn't change the budget line this year. "I can't do that number on a twelve-month agreement. On thirty-six, with the commitment in writing, I can get much closer." You have not discounted. You have priced a different deal.

Scope second. If they want a smaller number, sell them a smaller thing. Take out the module, the second location, the extra service tier — and say clearly what's coming out. This is the single most underused move in the whole conversation. Buyers who say "we need a lower price" almost never mean "we need less," and when you show them the version that actually costs less, most of them put the scope back in themselves. That's not a trick. It's just making the trade visible.

Payment timing third. Annual up front instead of monthly. Deposit structure. Milestone billing. Net terms. Cash timing has real value to you and often costs the buyer very little, particularly if they've got budget to burn this quarter. Trading terms for rate is a trade both sides can defend internally.

Rate last, and never for free. If you do move on rate, it buys something: a signature date, a case study, a reference call, a multi-site commitment, an introduction to the sister division. Every point of margin should leave with something in its hand. The scripted, line-by-line version of this exchange is what the SaaS pricing negotiation playbook walks through for a post-technical-win deal, and the staffing and recruiting version runs the same structure for a rate-card fight after you've already been chosen.

The exact language for holding your number

Holding a price is not saying no repeatedly. It's saying no once, clearly, and then immediately handing the buyer something they can carry back to their boss. Buyers need a win to report upward. If you don't give them one, they will manufacture one out of your rate.

Here's roughly how I say it:

"I'm not going to be able to match that figure, and I don't want to pretend I might and waste your week. What I can do is [thing that isn't rate]. If it helps, here's how I'd frame it to your leadership: we're not the cheapest bid, we're the one where the implementation is contracted rather than assumed and the year-two number is fixed. That's the trade you'd be making, and I think it's the right one — but it's yours to make."

Three things in there. A clean no, so nobody is waiting for a phantom discount. A concrete alternative, so the conversation continues. And the sentence they can repeat internally, written for them, in their language, so your champion doesn't have to invent the argument on the fly in a room you're not in.

That last part matters more than people think. Your champion is going to be asked "why are we paying more?" by someone senior, probably in a hallway, probably with about eight seconds to answer. Give them the eight-second answer. Say it slowly enough that they can write it down.

And then stop talking. The silence after you hold a price is uncomfortable and you have to sit in it. Almost every rep I have watched fills that silence, and what they fill it with is a discount. If you're going to practise one thing out of this entire post, practise not filling the silence. The same beat shows up in the freight and 3PL negotiation script when the brokerage has already picked you and is testing whether the rate was real, and in the construction and trades version when a specialty contractor comes back with a number from someone else's bid sheet.

If you lose it anyway

Sometimes they take the cheaper quote. Fine. Do two things.

Ask what the deciding factor actually was, in one question, with no defensiveness in your voice — "was it purely the number, or was there something else?" You will get a straighter answer at the point of loss than at any other moment in the relationship.

Then calendar it. Set a reminder for the point where the gap you identified will have shown up — after the implementation window, after the first invoice cycle, after the phase two quote lands. Send one short note then. No I-told-you-so, just "how did the rollout go?" A meaningful share of the deals I've closed over the years were ones somebody else won first and didn't hold. The competing bid is a moment, not an ending.

What I'd do next

The reason this conversation goes badly is not that reps don't know the theory. It's that the number lands, the adrenaline hits, and the mouth defaults to whatever it has said most often. Reading a script doesn't change that. Saying it out loud twenty times, against a buyer who pushes back, does. That's what we built DrillCall for — you run the competing-bid call as a live roleplay, get told exactly where you flinched, and do it again before it costs you a real deal. If you'd rather not use us, fine: grab a colleague, have them say "we have a quote thirty percent below yours" and then say nothing at all, and see how long you last before you offer something. That number is the one worth measuring.