Price Is Almost Never Why You Lost

What's actually happening when a proposal comes down to dollars and cents.

I want to push back on something that gets treated as gospel in almost every post-loss debrief I've ever sat through: "We lost on price."

Sometimes that's true. Commodity bids, where every specification is identical and the only variable is the number on page 47, yes, price decides. But most of what gets called a proposal is not a commodity bid. It's a complex ask from an organization trying to make a consequential decision about a vendor they're going to have to live with for months or years.

In those situations, "we lost on price" is almost always a story the losing team tells itself because it's easier than the real answer. Here's what's more often true: they lost on value clarity.

The buyer didn't understand, well enough, concretely enough, specifically enough, what they were getting for the difference in price. And when value isn't clear, price fills the vacuum. It's not that price won. It's that nothing else did.

Think about how this plays out in a couple of sectors I work in.

In public sector contracting, proposals can span millions of dollars and multi-decade financing structures. Two proposals might be $800,000 apart on a $7 million project. If the higher-priced proposal hasn't clearly articulated why, what's in that number, what risk it transfers, what it guarantees, what the lower bid is leaving out, that $800,000 looks like pure margin to a school board trying to protect taxpayer money. But if the proposal walks a facilities director through exactly what the gap covers, measurement and verification rigor, extended equipment warranties, staffing for the commissioning process, the shortfall guarantee structure, now it's not an $800K premium. It's an insurance policy. Those are completely different conversations.

In SaaS, proposals lose on price most often when they lead with features instead of outcomes. A platform priced at $120K that doesn't clearly show what $120K of business value and KPI outcomes looks like will lose to a platform at $80K every time, even if the expensive one is genuinely better for the user. The fix is not to lower the price. It's to make the value visible. What does this tool replace? What does it save in headcount or process hours? What does it enable that wasn't possible before? How is change management supported more clearly?

So what does a proposal that wins the value conversation actually look like?

It makes the cost of the alternative visible. Not in an aggressive way, but in a clear, honest, here's-what-you're-actually-choosing-between way. What does the lower-cost option require the buyer to absorb? What risk stays with them? What capability do they give up? What happens when something goes sideways and there's no one on the hook?

It translates price into outcomes. Not "our fee is $X" but "for $X, here's what you get, here's what it replaces, here's what it prevents, and here's what similar organizations have seen on the other side of this investment."

Great proposals show the math. Not to obscure it, but to make the comparison honest.

It gives the champion something to take to the room. The real buyer is often not the person reading the proposal. It's the person they report to. A proposal that gives your champion the language to defend the investment internally is worth more than almost any other thing you can put on the page.

Price matters. It always will. But in complex B2B and B2G sales, it rarely decides. What decides is whether the buyer trusts the value story enough to defend it. That's a writing problem, not a pricing problem.

And it's one good proposal writers solve every time.