“We lost because of price.” Say this at a pipeline review and you will get sympathetic nods. Price is the most comforting loss reason ever invented. It is outside the rep’s control, it requires no change in the pitch, and nobody can argue with it because the customer is gone. Which is exactly why you should distrust it.
Why the CRM field misleads
The loss reason in the CRM is usually a drop-down chosen by the rep, in thirty seconds, after a disappointing day. Several biases push it the same way. Reps pick reasons that do not reflect on themselves. They often do not know the real reason, because buyers soften bad news (“your price was a bit higher”) rather than explain that they did not trust the implementation team. And the drop-down list itself forces a single answer when most decisions have several causes.
None of this makes reps dishonest. It makes them human and badly placed: the person who lost the deal is the worst person to explain why.
What a real programme looks like
The core method is simple: talk to the buyer, after the decision, through someone other than the rep who sold. That can be product marketing, a sales operations analyst, or an outside firm. A neutral interviewer gets franker answers, and the buyer feels no pressure to be polite to a salesperson they might still meet.
Practical points:
- Interview wins as well as losses. If you only study losses you will never learn what you do well, and may fix things that were not the reason anyone bought.
- Choose deals by a rule, such as every deal above a size threshold or a random sample, not by whoever agrees to talk. Volunteers skew.
- Wait a few weeks after the decision, long enough for emotion to settle, not so long that memory fades. Four to eight weeks is a common practice.
- Ask open questions about the buying process: what triggered the search, who was involved, what did you compare, what almost changed your mind. Avoid leading questions like “was our price too high?”.
- Talk to more than one person on the buying side. The champion’s story and the finance head’s story often differ.
Buyers are more willing to talk than most sales teams assume, especially if you say the purpose is to improve and keep it short, around twenty to thirty minutes. Some will decline, and in some Indian enterprises policy may restrict what employees can say about vendor evaluations. Respect that.
An illustration of the gap
Suppose a company lost 24 deals in a quarter. The CRM says price in 15 of them. A sales operations analyst interviews buyers in 10 of the losses. In those 10, the CRM had recorded price eight times and a feature gap twice. After the interviews, the coded reasons look like this:
| Main reason given by the buyer | Deals (of 10) |
|---|---|
| Doubts about integration with their existing systems | 3 |
| Internal sponsor left or lost influence | 3 |
| Price | 2 |
| Slow or unclear vendor responses during evaluation | 1 |
| Genuine feature gap | 1 |
Price shrinks from 8 of 10 to 2 of 10. Ten interviews are a small sample and should be treated as a signal, not proof; the point is the shape. What would a discount policy have done here? It would have cost margin and fixed perhaps two deals. Integration doubts, on the other hand, can be addressed with reference architectures, a technical proof earlier in the cycle and a named integration engineer. The sponsor problem points to multi-threading: building relationships beyond one champion. Each root cause has a different owner and a different remedy. The data is invented, but patterns like this are what these programmes commonly surface.
Turning findings into change
Interviews are cheap compared with what happens next, which is the hard part. Code the answers into a small, stable set of themes so you can compare quarter to quarter. Share a short summary with sales, product, marketing and delivery, with two or three specific recommendations, not a fifty-slide deck. Then track whether the numbers move. If integration doubts drive losses and you publish integration guides and add a technical call in the second meeting, check three months later whether integration shows up less often.
There is a political side. Feedback that says “your sales pitch confused us” or “the product roadmap lacks X” can be uncomfortable for whoever owns that area. Present it as patterns across deals, not as blame for individuals, and give leaders room to respond before it goes wider.
One more caution against over-reading. Win/loss tells you what buyers say and remember. People rationalise after the fact, and some reasons, such as a personal relationship with a rival’s salesperson, rarely surface. Use it alongside deal data, such as stage durations and stakeholder coverage, not instead of it.
Figures and names in the examples are illustrative.
Leave a Reply