Lost deal analysis: recording why you missed the sale
How do you analyse lost quotes? Steps for recording the loss reason on the same day with fixed options and learning from those records at the end of each month.
Lost deal analysis means recording why unsuccessful quotes were lost using fixed options and reviewing them together at regular intervals. The record is made on the day the opportunity moves to the Lost stage: main reason, short explanation, competitor information and a follow-up date. At the end of the month the reasons are grouped and one improvement is chosen.
Lost deal analysis is a sales habit that records why unsuccessful quotes were lost in the same format every time and reviews these records together at regular intervals. The aim is not to find someone to blame; it is to make recurring causes such as price, timing, product fit or missing follow-up visible.
In most companies, won quotes get discussed while lost ones close quietly. The salesperson hears “we are not considering it for now”, closes the file and moves on to the next call. A few months later, when a manager asks “why are we losing so many quotes”, all that is left are memories and general opinions.
Why should the loss reason be written on the same day?
The details of the last conversation with the customer are clearest on that day. A loss summarised as “price” a week later may actually have been a delivery time the customer found too long, or a decision maker who was never reached. The longer the record is postponed, the more reasons end up under one general heading and the analysis loses its value.
Prepare a fixed list of loss reasons
Loss notes written as open text cannot be grouped later; every salesperson describes the same situation in different words. So first define a short, fixed list of reasons and add the explanation separately as open text. For many B2B companies, these headings are a good starting point:
- Price and payment terms: The budget was exceeded, or the payment term or plan did not fit.
- A competitor was chosen: The customer went ahead with another company.
- Timing: The project was postponed or is waiting for the next budget period.
- Fit with needs: The offered product or scope did not cover the customer’s work.
- Decision maker: Talks continued with someone who had no authority to decide.
- Missing follow-up: The quote was sent but nobody got back in time.
- Change on the customer side: The contact person left or the company changed its priorities.
Keep the list short. As the number of reasons grows, salespeople fall back on the “other” option and the records become unreadable again.
Fields a loss record should contain
- Main reason: A single choice from the fixed list.
- Short explanation: What the customer said in their own words; facts, not interpretation.
- Competitor information: If known, which alternative was chosen.
- Stage of the quote: Was the deal lost after the demo or after the quote was sent?
- Follow-up date: For timing-related losses, when to call again.
“They liked the quote, but the purchasing budget moved to the new year. Call again in the second week of January.”
This note counts the opportunity as lost but leaves the door open. Timing-related losses are often not real losses but postponed sales; if no follow-up date is written, they are forgotten.
Learning from the records at the end of the month
The value of the records appears when they are read together regularly. Once a month, in a short meeting, group the lost opportunities by reason and look at these questions:
- Which reason stood out this month, and did it change compared with last month?
- At which stage of the funnel do losses cluster: after the demo or after the quote?
- Is there a recurring reason in a particular industry or region?
- At which stage do losses caused by missing follow-up pile up?
Taking a single improvement from each meeting is enough. For example, if replies after quotes are delayed, setting a reminder date after a quote is sent is a concrete step for the next month.
Placing the loss record inside the sales flow
When lost deal analysis is kept in a separate Excel file, it quickly goes out of date. The record needs to sit in the same place as the opportunity and the company’s history. YazSis CRM AI tracks opportunities through the New, Contact, Demo, Quote, Won and Lost stages in board and list views; meetings, opportunities, quotes and e-mail history stay on the same company card. Quotes are tracked through a draft, awaiting approval, sent, accepted and rejected flow. So when you return to a lost opportunity months later, previous meetings with that company and the quote that was sent are visible on one screen.
Recording lost quotes regularly lets the sales team talk based on records instead of guesses. YazSis CRM AI is used today in YazSis’s own support and sales hub; to see how the opportunity funnel and the company card work, you can visit the YazSis CRM AI page.
Frequently asked questions
How often should lost deal analysis be done?
The loss reason should be written on the same day each opportunity is closed. For the joint review, a short monthly meeting is a sufficient starting point for most teams.
Is writing “price” as the loss reason enough?
On its own it is not. State in a short explanation whether it was the price, the payment terms or a scope too large for the budget; writing down the customer’s own sentence makes later interpretation easier.
Should postponed projects be counted as lost?
That depends on your team’s rule. If you close the opportunity, mark the reason as “timing” and always write a follow-up date, so the postponed sale is not forgotten.
Is it right to ask the customer about the loss reason?
Yes, a short question without pressure is usually received well. A question such as “May we ask what influenced your decision most?” both protects the relationship and makes the record clearer.
More articles
Answering foreign patients in their own language in health tourism
A message in Arabic and a photo arrive at midnight, and nobody at the clinic can read them. Here is how to answer foreign patients in their own language and time zone.
October 28, 2026 · 5 min readWhy is process analysis needed before starting an ERP project?
Everything works smoothly in the demo; the catch is that the company in the demo is not your company. Process analysis shows how work actually runs before you move to ERP.
October 28, 2026 · 6 min readSales call lists: a practical way to plan the salesperson’s day
Handing a salesperson a 200-company spreadsheet is not planning their day. A call list decides up front who calls whom, in what order, and where the result gets recorded.
October 28, 2026 · 6 min read