Blog
Nobody Logs Why a Deal Was Lost
Ask your team why a deal fell through last month. Most of the time you’ll get a vague answer like “the customer went quiet,” or nobody will remember at all. The moment a deal is marked lost, everyone shifts focus to the next one. Nobody goes back to write down why a deal was lost. A sales team without that habit keeps losing the same kind of deal every quarter without noticing, because there’s no record anywhere to compare against.
Why a Lost Deal Goes Silent
A deal marked “won” has a next step waiting: handoff, a new owner, someone tracking delivery. That motion forces a record to exist without anyone intending to create one. A deal marked “lost” has no next step. The status changes and the matter ends there. Nobody has to write anything else, and nobody has to read anything else. Most pipeline systems are built to track where a deal is right now, not to answer the more useful question of why it never got anywhere.
The result is that an owner or sales lead only sees how many deals closed this month, not the shape of why the rest fell through. A team might be losing to the same cause over and over: talking to someone without approval authority, or showing up too late for a competitor who already won. Nobody sees the pattern, because every lost deal is filed away separately, never lined up against the others.
Why Nobody Logs It: It Stings, There’s No Field, Nobody Asks
This isn’t laziness. Three separate things keep the reason from ever getting written down. First, writing up your own loss isn’t pleasant; a salesperson who just spent weeks on a deal doesn’t want to dig into what went wrong. Second, the system doesn’t force it. Marking a deal lost is a single click with nothing else required. Third, even when someone does write a reason, nobody is ever scheduled to come back and look at it, so the entry feels pointless. The information has nowhere to go.
Each of these needs its own fix. Telling salespeople to write down the reason, without the other two, won’t work. Even a willing team will write it differently every time if there’s no required field forcing a consistent entry, and the habit fades within a few weeks if no review is ever waiting at the other end.
Four Fields to Fill Before Closing a Deal as Lost
Before marking a deal lost, four fields need to be filled in, not just a status change.
The date it was actually marked lost, not the date it went quiet. These two dates often don’t match, and letting the system record the status-change date instead of the real decision date quietly skews your average deal age.
The stage the deal was in when it fell through. A deal that dies in the first stage and one that dies right before close are different problems. The stage tells you where in the process things are actually breaking.
A reason category, picked from a fixed list, not typed as free text. More on that below.
The competitor who won, or an explicit note that no one won and the customer simply went silent with no decision at all. These are different failures. Losing to a competitor is a problem with your offer. A silent no-decision is usually a problem with timing or how the lead was qualified in the first place.
These four fields take a couple of minutes to fill in right after the call, while the details are still fresh. That’s why this happens at the moment of closing, not later.
Categorize the Reason So It’s Comparable, Not Free Text
“The customer said we were too expensive” and “their price was lower” carry the same information, but worded differently they can’t be counted together. To make the data usable, reasons need to come from a fixed list. Six categories cover most of it: price or terms that couldn’t be negotiated, timing that wasn’t right, lost to a competitor, no approval authority or the deal never cleared the customer’s internal process, a mismatch between what you offer and what the customer actually needed, and silence with no reply at all.
Pick one primary category, and a secondary one if it applies. Skip the long write-up; the point of this step is to make the reason countable, not to make it a good read. If you want more detail, keep it in the deal’s regular notes, separate from the category itself.
The payoff shows up after a month, when you can count exactly which category most of your lost deals fall into. Free text never gives you that, no matter how carefully someone reads every line.
When to Review Lost Deals, and Who Needs to Be in the Room
Run this review monthly, not deal by deal, and keep it separate from the weekly pipeline review. The two serve different purposes. The weekly review looks at where open deals are currently stuck. The lost-deal review looks at the past month as a whole, at which reason category is becoming more or less common.
The sales lead and whoever owns the sales system need to be in the room. You don’t need every salesperson there, because what you’re looking at is a pattern across the whole team, not an audit of one person. If “no approval authority” keeps climbing month after month, that’s usually not a sales-execution problem, it’s a qualification problem further upstream, where deals aren’t reaching the actual decision maker. If “lost to competitor” spikes in a specific period, it’s worth asking which competitor is showing up more often.
One thing to avoid: using this review to judge individual performance. The moment a team suspects the categories they log will be used against them, the entries quietly start skewing toward whatever looks better, usually within a few cycles.
Start With the Last Deal You Just Marked Lost
You don’t need to go back and reconstruct every old deal. Pull whatever fell through last month, fill in the four fields from memory while you still can, and make them required fields going forward for every deal marked lost from here on. The one thing worth deciding upfront is whether the six reason categories above actually match your business; if not, adjust the wording to match how your team actually talks, and then leave it alone. A list that changes every month makes it impossible to compare one month to the next.
This belongs to the sales process as a whole, not just a closing form. If your pipeline is still a guessing game about how many deals will close, knowing why deals are lost is part of what makes your forecast more accurate. And if your deals usually involve more than one decision maker, check whether a recurring “no approval authority” category points back to never mapping every decision maker from the start.
If your team doesn’t have this written down anywhere yet, BUILD 30 installs the whole sales process in 30 days, built for your team to run on its own. Start with a 45-minute call.