Aircover
Book a demo
← Guides
Guide Sales operations January 2026

How to find out why deals are lost, and fix it

By Andrew Levy · 5 minute read

A sales manager alone in a conference room reads through printed call notes laid out in a row

The closed-lost reason field in your CRM will not tell you why deals are lost. Reps fill it in weeks after the fact, from memory, from a list someone else wrote. To find the real reasons, go back to what was said on the calls, look for the same pattern across ten or twenty lost deals, and then change one thing at a time in how the team sells. Here is how to run that.

Why the loss-reason field is fiction

Look at the distribution of closed-lost reasons in almost any CRM and you'll see the same thing: "price" and "no decision" at the top, "competitor" third, and a long tail nobody trusts. Those aren't the real reasons. They are the easiest options to click when a manager is asking you to clean up your pipeline before the forecast call. Price is an easy reason to give. Reps rarely record that they never found the economic buyer.

The field also asks the wrong person at the wrong time. The rep is the one person with a stake in the answer, and they're answering weeks after the last conversation. Nobody asks the buyer. Nobody re-reads the calls. So the report that reaches the board is a summary of what reps were willing to admit, not a record of what happened.

What a real loss analysis looks at

A lost deal is a sequence of calls, and the reasons are in those calls. When you go back through the conversations, you're looking for a small number of things:

  • Whether the pain was ever stated in the customer's words, or only in the rep's pitch.
  • Who was on the calls, and whether the person who controls budget ever showed up.
  • What the buyer said about their decision process and timeline, and whether the rep asked at all.
  • Every mention of a competitor or of doing nothing, and how the rep responded.
  • The moment the deal changed. There almost always is one: a question that went unanswered, a stakeholder who went quiet, a pricing conversation that came before value was established.

None of that requires a survey or an outside win-loss project. It requires the transcripts or notes from the calls and a couple of hours per deal.

Step 1: pick the deals

Don't analyze everything. Pull last quarter's closed-lost deals above a size that matters to you, and cap the set at fifteen or twenty. Add a few deals that went to "no decision" and sat in the same stage for ninety days, because stalled deals often show the same gaps as clean losses, earlier. Leave out the ones that were never qualified in the first place; those are a pipeline hygiene problem, not a loss problem.

Step 2: read the calls, not the notes

For each deal, go through the conversations in order. If you have transcripts, read them. If you only have the rep's notes, treat them as one input and interview the rep as a second, with specific questions rather than "what happened": Who did you speak to? When did price first come up, and who raised it? What did they say about how they would decide? Did anyone on their side ever describe the problem in their own words?

Write down, for each deal, one sentence of what the buyer actually said about why they stopped, if it's on the record, and one sentence on where the rep believes it turned. Those two sentences rarely match, and the gap between them is usually the finding.

Step 3: find the pattern across deals

Lay the deals out side by side and look for repeats. A pattern is three or more deals with the same missing piece. The common ones:

  • The economic buyer never joined a call. The champion carried the deal as far as they could and then couldn't get it funded.
  • Discovery ended at the first pain. The rep heard a problem, pitched, and never found out whether it was a priority this quarter.
  • Price came up before impact. In the deals where the buyer raised cost on the first or second call, nobody had quantified what the problem was costing them.
  • A competitor was mentioned once and never again. The rep didn't ask why they were looking, so the comparison happened without you in the room.
  • Next steps were vague. Calls ended with "I'll send some information" instead of a date.

Resist the urge to find ten patterns. Find the two that account for most of the lost revenue in the set.

Step 4: change one thing in how the team sells

A finding is only useful if it turns into a change on the next call. Match each pattern to a specific behavior you can check on real calls:

  • No economic buyer: no deal advances past the evaluation stage without a named economic buyer and a scheduled meeting with them. Make it a stage gate, not a suggestion.
  • Discovery stops early: give reps three follow-up questions to ask after the first pain, and look for them in call reviews.
  • Price before impact: reps quantify the cost of the problem before sharing pricing, and if the buyer asks first, they have a line ready to redirect.
  • Competitor mentioned once: a two-question response every rep uses when a competitor comes up. "What made you look at them?" and "What would you need to see from us to be confident?"

Pick the behavior with the most revenue attached, roll it out to the team, and check it on real calls for six weeks before you touch the next one. The redirect for early price questions can be as simple as this:

"Happy to walk through pricing. Before I do, can I make sure I understand what this problem is costing you today? Otherwise I'm quoting a number with nothing to compare it to."

Step 5: close the loop with enablement and product

Loss analysis is also the best input marketing and product will get all year, if you hand it over in their language. For enablement: the exact objections and competitor claims that came up, in the buyer's words, so battlecards and talk tracks get rewritten from reality rather than from a positioning document. For product: the capability gaps buyers named, with deal size attached, so the roadmap conversation is about revenue rather than opinions. Do this quarterly and the analysis earns its keep outside the sales team.

Where this goes wrong

  • Analyzing the CRM field instead of the calls. The field is the problem you're trying to fix, so it can't be the source.
  • Letting reps self-report without the record. Interviews help, but only alongside transcripts or detailed notes. People remember losses differently from how they happened.
  • Finding ten patterns and fixing none. Two patterns and one behavior change do more than a deck of findings.
  • Doing it once. Patterns shift as the team and the market change. Quarterly is the right cadence; an annual review is too late to act on.
  • Turning it into a blame exercise. If reps learn that loss reviews end in punishment, the calls that matter stop getting logged at all.

Where Aircover fits

Aircover captures the sales calls it is configured to join through live transcription, without recording by default, and produces notes, qualification results, and scorecards for each one. That means the loss analysis above can run from a complete record of what was said across every rep, instead of a sample of what got remembered. The conversation intelligence page shows how those patterns surface across deals.

See it work on a live call.

Book a demo and watch real-time guidance, notes, and CRM sync run on a real conversation.