The Real Reason You Lost That Deal
Nobody buys from the cheapest vendor when they're afraid of being the person who made the wrong call.
That decision happens before the spreadsheet comes out, before the proposal gets scored, before anyone mentions price. The customer across from you is running a different calculation: if this goes sideways, how bad does it get, and whose fault is it?
Business development professionals who understand that win business at better margins. The ones who don't end up in a price war they didn't need to be in.
Chasing the lowest rate is a shot in the foot—it saves the customer a little and costs your margin a lot more later.
Certainty is the product. Everything else is packaging.
What customers are actually buying
When a customer evaluates vendors, they're running a mental calculation that almost never shows up in formal criteria: if something goes wrong with this vendor, how bad does it get, and how hard is it to fix?
A vendor with a lower rate but an unpredictable track record scores poorly on that calculation. A vendor with a higher rate and a reputation for showing up, delivering on spec, and communicating proactively when something changes scores well. The second vendor wins more often—not because they're cheaper, but because they reduce the customer's exposure to the thing they're most afraid of.
This is why a conversation focused on price almost always loses to one focused on risk. Price is visible and easy to compare. Risk is invisible until it isn't—and by then the damage is done.
One GWA client learned this the direct way: after a three-day session built around exactly this shift, a $300,000-a-month account closed the next morning. Nothing about the offer changed overnight. What changed was which fear the proposal was actually answering.
The pre-proposal exercise
Here's a piece of what we teach. Before you submit anything, run this:
Name the fear. What is the customer most afraid will go wrong if they choose us?
Answer it with evidence, not a claim. A named reference in a comparable situation beats a feature list every time.
Spell out the failure plan. Not "we'll fix it"—how, how fast, and who calls whom. If a shipment's late, does the customer hear it from you at 8am, or find out from their own ops team at 2 pm?
Most proposals answer the question the vendor wants to answer. This exercise forces you to answer the one the customer is actually asking.
Where the certainty argument gets lost
The promise made in the meeting and the reality delivered in the field have to match. When they don't, the customer remembers—and the next opportunity goes to someone else without an explanation. No amount of pre-proposal work survives an operations team that doesn't deliver on what was promised.
One more thing worth knowing
When a customer raises a concern instead of just walking away, that's not rejection—it's usually a request for more information. Reading it as a wall to get past instead of a door to walk through is where a lot of good proposals lose ground they never needed to lose. How to actually work that conversation is its own discipline, and it's not this article.
Price wars are a choice, not a market condition. This shows up across several of our programs—tell us where your team's actually losing deals on price they shouldn't be, and we'll point you to the right fit and customize it to your needs.
Want to understand why you're losing deals you should be winning? Click here to book a free consultation and ask about our Business Development Program.
Kind regards,
The Executive Team
Gary Waldron & Associates
Comments