A cloud storage company believed it lost most of its larger deals on price, and its CRM agreed. When every qualifying deal was joined across the CRM, recorded calls, email, Slack and product activity, a different pattern appeared: every deal that was cut down to fit a stated budget was lost.
At a glance
| Measure | Count |
|---|---|
| Qualifying deals | 62 opportunities above $50K, closed in the trailing 180 days |
| Descoped to fit a budget | 14, after the buyer named a budget figure |
| Descoped deals won | 0 of 14 |
| Other deals won | 21 of 48 |
| CRM loss reason on the 14 | Price, in 9 |
| Descope decisions recorded in the CRM | 0 |
The question
Sales leadership's working answer for lost larger deals was price. It was a loss reason the CRM recorded often, and the obvious response was more room to discount. The pattern below was a genuine surprise to them.
How it was counted
- Population. Every opportunity above $50K that closed, won or lost, in the trailing 180 days: 62 deals.
- Sources. CRM opportunity records and field-level change history, recorded calls and transcripts, email with external participants, internal Slack threads, and product activity, all matched to the same opportunities.
- Definition. A deal counts as descoped when the proposed configuration was reduced after the buyer named a budget figure, or the full configuration was never proposed because of it. Each of the 14 has a dated moment of descoping: a call, an email or a CRM amount change.
- Comparison group. The 48 qualifying deals that were not descoped.
What it found
Of the 14 descoped deals, none closed won. Of the other 48, 21 closed won. In 9 of the 14 the CRM recorded price as the loss reason, and in none of them did the CRM record the descope itself.
The descope lived in three places the CRM does not read: the pricing call where the configuration was cut, the email that sent the revised quote, and the internal thread where the team agreed it. In one account, the buyer then downloaded the competitive comparison from the company's website and went quiet.
Deals cut down to fit a budget did not become smaller wins. In this period, they were not won at all.
What the finding is not
It is an association, counted across 62 deals in one period at one company. It does not prove that descoping caused the losses. Fourteen deals is enough to act on and not enough to generalize from. No change in revenue is claimed here.
The most likely explanation
The explanation sales leadership is now testing is that these opportunities were not well qualified for budget, and their pricing drove prospects to competitors. Cutting the scope did not rescue them. That makes it a qualification problem early in the cycle rather than a discounting problem late in it.
The questions it put to leadership
- Qualification. Is budget being qualified before a configuration is proposed, or after?
- Value. When a buyer names a budget below the proposal, is the case for the full scope being made to the economic buyer?
- Commercial terms. Would phasing, or different terms, hold the scope where cutting it did not?
- Rescue tactics. Should descoping need a deal desk review, or should these deals be defocused faster?
Owner: sales leadership. How to tell if it works: track the share of large deals descoped, and the win rate of those that are, over the next two quarters.
Questions we get asked
-
Does this prove that descoping causes losses?
No. It is an association across 62 deals in one period at one company. It was strong enough to act on, and sales leadership is testing the most likely explanation. A cause would need the pattern to change when the practice changes.
-
Why didn't the CRM show it?
The descope decisions were made on pricing calls, sent as revised quotes and agreed in internal threads. In the CRM the only trace was an amount revised down with no reason, and a closed lost reason of price.
-
Would the same pattern show up in our deals?
We can't know without counting. It is one of the first patterns worth testing in any business where large deals are often reshaped to fit a budget.
About Rev-Lens. Rev-Lens is a founder-delivered go-to-market intelligence practice. In an eight-week engagement it joins a company's CRM, recorded calls, email, internal chat and intent data at the opportunity level, inside the company's own infrastructure, and returns win-rate findings by week five, each with a denominator, the evidence behind it and a named owner. The company keeps the joined dataset and the agents, and its team is trained to run them.
Keep reading: the definition of win-rate forensics and the four tests this finding passed, or why risk alerts don't explain your win rate.