Closed Lost

Where to put a deal that didn't work was unclear for a long time. Signed deals were obvious and live deals had someone working them, but a deal where the customer simply stopped answering belonged to no column at all. Closing it removed the amount from the rep's own numbers, so there was no reason to close it, and deals that had ended three months earlier stayed in the pipeline.

The problem surfaced whenever anyone read the totals. Grace would ask mid-quarter what was in play and hear $600,000, and opening the records one by one showed that half of them had no activity in over two months. The total said the target was reachable, and only after the quarter closed did it become clear that half that money was never there.

Closed lost is the box built to clear those deals out. It doesn't delete them — it records why each one ended. Written down, the pattern shows up at quarter end: twelve of thirty lost deals died for the same reason, and those twelve become something the product or the pricing can address next quarter.

It's the final box in the pipeline and it pairs with closed won. When a live deal — one transaction with one customer — moves here, its amount leaves the in-play total and drops out of the quarter's forecast.

Closing moves several numbers at once. Win rate, the share of worked deals that closed successfully, gains one in the denominator, so twenty worked deals with six wins reads as 30 percent only once the losses are actually closed. Pipeline coverage, the multiple of accumulated deal value against the target, falls by the same amount. A $150,000 quarterly target against $450,000 in play is 3x coverage; close a $38,000 deal as lost and it becomes 2.75x. The sales forecast drops whatever that deal contributed after its stage probability. Leave deals open and all three numbers read better than reality until the quarter ends.

The reason code is mandatory at close. Not a free-text note — a selection from a fixed list. Pagedeck uses five: price didn't work, wrong timing, missing capability, chose another product, contact changed and the conversation stopped. The list is fixed because prose can't be counted. "On hold, budget issue" and "budget spent for the year" mean the same thing and land as two different entries, so a quarter that lost twelve deals to budget reports twelve separate one-off notes and no pattern at all.

When to close is defined too. An explicit no closes the same day, but silence is the more common ending. So the team sets a rule: a fixed number of weeks after last contact. Pagedeck uses four weeks, and requires a record of one more attempt through a different channel before a deal can be closed.

What the rep feels belongs to this stage as well. Marking a deal lost means writing down that you lost, which invites delay. That's why many teams establish up front that reason codes are never used in performance reviews. The moment the codes feed evaluations, reps pick whichever one points away from themselves, and the collected reasons become useless for fixing the product.

What reopens a closed deal depends on the reason, and half the point of forcing a reason code sits here.

1. Timing means setting a date. If the budget for this year is already spent, the follow-up gets scheduled now against the next planning cycle.
2. A missing capability means the day that capability ships. Group the deals lost that way and the call list is already built when it launches.
3. Choosing another product means that contract's end date. Usually one or two years out, so the term gets noted at close so someone can ask again then.
4. Price means the terms have to change — a new plan, or a smaller way to start.
5. A contact change means a person. The new contact needs the whole story again, so the prior discussion gets written up while it's fresh.

Reopening creates a new deal rather than reviving the closed one. Reviving the record blurs which quarter the loss belonged to and quietly rewrites that quarter's win rate. The loss stays a loss, and the new deal enters at the first stage.

"I'm closing this one as lost. Four weeks with no reply."

The agreed waiting period has passed, so it comes out of the pipeline.

"Can you pull this quarter's loss reasons? I want to see how many were price."

Gather the losses and look for something in the product or pricing to fix.

"This one was closed lost, but that capability shipped, so I'm reaching back out."

The reason recorded at close has been resolved, which makes it a reason to reopen.

At Pagedeck, Sofia gathers the quarter's lost deals into a thirty-minute session at close. It isn't a session for relitigating individual deals, only for reading counts by reason. Last quarter, nine of twenty-eight losses cited a missing capability, and seven of those nine pointed at the same capability.

Mia read those seven records herself and moved that capability onto the next quarter's priorities. Without the session, the fact that the same request arrived seven times would have lived only in Sofia's memory, where nothing choosing what to build could reach it.

The most common misreading is that closed lost records a rep's failure. It's a deal that didn't close, so it looks like somebody fell short. In practice more than half of them close for reasons no rep controls: the customer's budget gets pulled, the org reshuffles, or a competitor objection never fully clears. Treat losses as failures and reps stop closing them, and the pipeline swells again with money that isn't there.

The other mistake is assuming the record is a formality once the deal is over, which is why reason fields get filled in carelessly. But this record is close to the only evidence available for deciding what to fix next quarter. Won deals rarely come with the customer explaining why they won; lost deals leave the reason behind plainly. A quarter recorded sloppily reports twenty-eight losses and not one instruction about what to change.