Notes for owners · Sales management
How to debrief a deal you lost without blaming anyone
A neutral way to ask a buyer why they chose someone else, a short call script, and a loss log whose reason codes make patterns visible after a dozen entries.
The GullySales team · Updated 17 Oct 2026 · 6 min read

On this page
To debrief a lost deal, ask the buyer for three minutes once the decision is final, say you are not trying to reverse it, and ask what they weighed. Write the answer in their words in a loss log, with one reason code per deal. One lost deal gives you a story. Twelve rows in one log show which reason keeps coming back, and that is the one worth fixing.
Why does the owner's theory so often turn out wrong?
Because the theory comes first and the buyer is seldom asked. The owner says "price", the salesperson says "bad lead", and both say it with confidence. Nobody checks, so the same deal is lost again for the same hidden reason.
A debrief does not exist to prove anyone wrong. It exists so you stop guessing at what buyers meant when they said "we have decided to go another way".
How do you ask without sounding hurt?
Send a short message after the decision, not during a tense phone call. The message gives the buyer a way out.
"Thank you for letting us know, and we respect the decision. If you have three minutes sometime, I would value hearing what made the difference, so we serve the next customer better. A reply by message is fine."
Notice what it leaves out: a last offer, a discount, and any sentence beginning "why did you not". If the buyer replies, call at a time they choose.
What do you ask on the call?
Five questions, in this order, not read out like a survey.
- "What made you start looking in the first place?" It reminds them of the need and shows whether you understood it.
- "Who else did you speak to, and what did they do well?" You hear the comparison without asking about price.
- "What was the deciding point?" One thing. Let them be silent.
- "Was anything we sent unclear?" This opens the door to faults in your papers.
- "If we had done one thing differently, what would it have been?"
Then thank them and stop. Do not argue, correct or sell. If they hint at a future opening, note it and leave.
What goes in the log?
One row per lost deal, their words first, the code second. These are sample rows with invented dates and buyers.
| Date | Buyer | Their words | Reason code | Winnable? | Stage lost |
|---|---|---|---|---|---|
| 4 Feb | School trust | "Other builder matched our grant payments" | Payment terms | Yes | After quote |
| 19 Feb | Travel firm | "We went with a friend's relative" | Relationship | No | Before quote |
| 2 Mar | Dairy | "Delivery date was vague" | Scope or schedule | Yes | After quote |
Keep the codes few and fix them in advance. A starter set: price, payment terms, scope or schedule, speed of reply, trust or references, no decision made, relationship elsewhere, our fit. Adding a code for every odd case destroys the comparison.
"Winnable?" keeps you honest. Some losses were never yours: a cousin got the job, or the budget vanished. Mark them "No" and do not rebuild your process around them.
For example: a bus-body builder in Karur
Imagine a body builder in Karur who loses an order for six school buses, worth ₹54 lakh (an invented figure), to a builder from another district. The owner is certain it was price, because the school trust's transport manager said "your rate was higher".
The owner calls the manager three days later using the script. The rate gap was small. What decided it was payment: the trust receives its grant in instalments, and the rival offered stage payments matched to those dates. The owner's terms asked for half in advance, which the trust could not release in one go.
The theory had been price. The reason was payment terms. The fix is only partial: at the trust's next tender the owner offers stage payments and wins four of the six buses, because the other two need a chassis supplier on credit that the owner cannot yet match. The log records it as winnable, and the owner now asks every institutional buyer, in the first meeting, when their money arrives. After a few more rows, three carry the same code, so the change in terms stops being an opinion.
How do you stop it turning into blame?
Write reasons about the process, never about a person: "Quote did not say when the trust would pay", not "the salesperson forgot to ask". Review the log together with names removed, and read the codes, not the faces. End each review with one change and one name against it.
If the same salesperson's name keeps appearing, coach them on the step where deals slip. That is a conversation for another day, and it should not happen in front of the team.
When should you skip the debrief?
Skip it for orders so small that the call costs more than the sale, for buyers who were never real (no budget, no authority), and for buyers who were angry when they declined. In those cases, log the deal from your own notes, mark it "No" and move on.
Never use the call to reopen the sale. If the buyer senses an agenda, you lose the honest answer and perhaps the relationship.
Start with five rows
Make the sheet above, fill in your last five lost deals from memory and notes, then ask the next buyer who declines for three minutes. A lost-deal review is the last loop of the sales process, and if you want help setting up the log and reading it with you, win-loss analysis is that work. The way in is to tell us what you need.






