--- title: "The Deal You Think You Lost on Price, You Probably Didn't" canonical: "https://winlossresearch.com/perspectives/lost-on-price-probably-not/" pubDate: "2026-07-14T00:00:00.000Z" author: Daniel Oxenburgh description: "\"Pricing/Budget\" is the most common Closed Lost reason in any CRM, and often the least informative. Three deals logged that way told three different stories." --- # The Deal You Think You Lost on Price, You Probably Didn't "Pricing/Budget" is the emptiest answer in your CRM. It's also one of the most common Closed Lost reasons logged, and the least informative. A rep logs it when the buyer mentioned cost and it got taken at face value, when there's no better answer at hand, or when a deal goes quiet and someone has to pick something from the dropdown before the pipeline review. It's a catch-all, and entire strategies get built on it. Here are three deals from one of my win/loss engagements, all logged as lost on Pricing/Budget. Three buyers, three different stories. The first: *"The competitor's pricing was much more transparent, whereas the vendor's pricing felt a bit opaque. It seemed like there were hidden levers that could cause us to incur greater costs at a later stage."* The second: *"The sales rep came in with a wild, crazy low price. At first, I thought it was great, but then we realized it was weird. It just seemed like a desperation move, which turned us off."* The third: *"The vendor offered to buy out our remaining contract months. At that point, it just kind of fizzled out because making the move to a new system would be a lot of work. I wasn't in the mindset to consider it, and if they sent an email, I probably just skipped over it."* Two of these touched on price for reasons that have nothing to do with the number on the proposal. Transparency and trust drove the first. A discount so aggressive it read as desperation, and killed confidence instead of building it, drove the second. None of it was really about the number. The third had nothing to do with price at all. It was a change management problem the team never recognized as a live deal, a buyer who had already mentally checked out before the contract buyout offer ever landed in their inbox. All three losses looked identical in the CRM. The only thing they actually had in common was that none of them were lost on price. None of these buyers were being evasive when they gave price as their first answer either. Cost is the easiest thing to point to in a post-decision conversation, concrete, quantifiable, and impersonal enough that naming it doesn't require explaining anything uncomfortable about the process itself. A rep hearing "the pricing didn't work for us" has no reason to dig further, and a dropdown built around that same word has no way to capture the trust problem, the change-management fatigue, or the confidence collapse actually sitting underneath it. This matters past the individual deal. A CRM that shows "we lose 40% of the time on price" becomes the working theory a whole GTM team plans around: sharper discounting, earlier concessions, a pricing page rewrite. Every one of those responses treats the symptom the dropdown reported, not the actual cause sitting underneath it, and none of them would have fixed what these three buyers actually described. The rep who oversold a discount doesn't get coached on trust-building because the deal is filed under pricing. The murky-cost complaint doesn't reach product marketing because it's logged the same way as a straightforward budget loss. Required fields and standardized dropdowns make your CRM more consistent. They don't make it more accurate, because consistency and accuracy are solving different problems entirely. A rep forced to pick from five loss reasons still picks the closest available label, not the true one, and "Pricing/Budget" is usually the closest available label for almost anything that isn't a clean feature loss. A deal that stalled because a champion went quiet gets coded as budget because there's no dropdown option for "the internal advocate stopped responding to my emails." A deal lost to distrust after an aggressive discount gets the same code as a deal lost because the number genuinely didn't work. The dropdown was never built to hold the actual variety of reasons a deal falls apart. The reason this pattern is so persistent is that "price" is the easiest answer for everyone involved to accept. It's impersonal, it doesn't implicate anyone's process, and it closes the loss review cleanly. A rep would rather log a deal as lost on budget than admit a follow-up question sat unanswered for a week. A sales leader would rather report a pricing headwind to the board than a pattern of reps overcompensating with discounts that read as desperate. The label survives because questioning it means reopening conversations nobody particularly wants to have. The only way to know which of your price losses were actually about price is to ask the buyer directly, once the deal is closed and there's no relationship left to manage on either side. Some of what comes back will genuinely be about the number. Most of it won't be. The next time your pipeline review shows a wave of price losses, ask what's actually sitting inside that number before you touch your pricing strategy. You might be about to fix a problem you don't have. ## Related - [Why Internal Win/Loss Data Fails](/topics/why-internal-win-loss-data-fails/) - [Your CRM Is a Sales Story, Not a Buyer Story](/perspectives/your-crm-is-a-sales-story/) - [Internal Myths Survive Because They're Comfortable](/perspectives/internal-myths-win-loss/) - [Why is CRM win/loss data unreliable?](/faq/why-does-crm-data-miss-real-loss-reasons/) - [What does a CRM capture that win/loss research doesn't?](/faq/crm-vs-win-loss-research-coverage/) - [CRM loss reason](/glossary/crm-loss-reason/) - [Closed lost reason](/glossary/closed-lost-reason/)