The 'we lost on price' excuse, decoded
What 'we lost on price' actually masks. An opinion piece, with evidence from the GAO debrief corpus and the patterns I've watched in our own win-loss data.
This is an opinion piece. The opinion is that “we lost on price” is the most over-claimed and under-examined sentence in B2B sales.
I write this knowing it lands sideways with most go-to-market leaders. Pricing is real, price gaps are real, and yes — sometimes the buyer genuinely needed the cheapest option and you weren’t it. But the frequency with which “lost on price” is the entire post-mortem in companies I’ve talked to is wildly out of step with what the actual data says when teams structure their debriefs.
The data says price is a proxy
The research team read 120 public debrief transcripts — federal protest decisions and state procurement appeals — and coded the stated reasons. Price was named in 22 of 120 cases. In nearly every one of them, the agency’s actual language was something like “the protester’s price was higher and the technical advantages did not justify the difference.”
That’s not a price loss. That’s a value loss in price language.
The distinction matters because the fix is different. A real price loss is solved by being cheaper, walking away from the deal, or restructuring the offering. A value-in-price-clothing loss is solved by tightening the technical case, adding past-performance evidence at scale, and making the differentiation legible to a non-technical evaluator who has to defend the selection internally.
Most teams hear “we lost on price” and respond by being cheaper. Most of the time, they’re solving the wrong problem.
Why buyers say price
Buyers say “we lost on price” because it’s the least painful sentence to deliver. It doesn’t require them to defend an evaluation rubric. It doesn’t open the door to “what would we have needed to be?” It doesn’t require them to admit their own organization didn’t quite know what it wanted.
If you’re the procurement officer running a debrief, “you were 12% higher” is a sentence that ends the conversation. “Your technical approach didn’t differentiate from the incumbent” is a sentence that starts a conversation. Buyers ration their time the same way you do.
This means you have to read past the sentence. The first follow-up question in a debrief — every time — should be: was price the only factor, or was it the deciding factor among others? If they came up with the others when prompted, those are the actual reasons.
Why sellers prefer “lost on price”
Sellers prefer it for the mirror reason: it doesn’t require an internal post-mortem about the proposal itself. “We lost on price” routes the work to product or finance — they need to fix discounting, tier the offering, change the comp model. None of that lands on the proposal team’s plate.
If the loss was actually about a thin executive summary, an under-evidenced past-performance section, or a win theme that didn’t match the evaluation rubric, then the proposal team owns the fix. That’s a less comfortable conversation. Cultures that don’t run real debriefs default to the comfortable conversation.
What I’d ask in the debrief
When I sit in on a debrief — buyer-side or internal — I push three questions before I let “price” stand as the answer.
One: did the price gap correlate to a feature gap? If yes, the loss was a packaging or feature problem, not a price problem. If no, the gap is structural and either we live with it or we don’t bid.
Two: was the technical case strong enough that the evaluator would have defended a premium? This is the question I most often see skipped. Premiums get paid; they get paid when an evaluator can defend the premium internally. That defense requires evidence. Without it, even a small premium becomes a loss.
Three: where did our win themes show up in the buyer’s evaluation language? If the buyer’s debrief paraphrases your win themes back to you, your themes landed. If the buyer’s debrief uses different vocabulary entirely, your themes didn’t reach the evaluator and price probably wasn’t the issue at all — visibility was.
The internal post-mortem question
When my own team reports “we lost on price” in a deal review, the question I ask is whether we rejected our own bid before submission. Did we present an offer we’d have selected if we were the buyer? Or did we present an offer we hoped the buyer would select because they didn’t have a better choice?
Bids that were structurally weak — thin past performance, generic win themes, compliance-by-inference rather than by evidence — and that lose, lose to the next-cheapest competent vendor, regardless of price. The team writes “lost on price” because the price was the visible delta. The actual delta was that the bid wasn’t competitive on its merits and the buyer used price as the tiebreaker.
A bid that loses on price after a strong technical case is a different kind of loss. We should walk away from those deals or restructure the offer. A bid that loses on price after a weak technical case is a self-inflicted loss dressed in market language.
What we capture for this
In the win-loss dashboard we shipped this month, the outcome record has a stated reason from the buyer (verbatim where possible) and an internal-inference field. Every “lost on price” outcome from a buyer triggers a prompt to the team: was the technical case independently strong, or did price become the explanation by default?
The point isn’t to override the buyer. The buyer’s stated reason is the data. The point is to require the team to consider the alternative explanation before treating “price” as the closed answer. Most teams that do this consistently for two quarters find that “lost on price” drops to about a third of where it started — not because they got cheaper, but because they got more honest about what the buyer was actually telling them.
That’s the takeaway. “We lost on price” is sometimes true. It’s almost never the whole truth. The teams that compound are the ones that stop treating it as the end of the analysis and start treating it as the beginning.