Nobody Beat Us. The Calendar Did.

Last week we did the thing every sales team says it does and almost none actually do. We read every deal we have closed since we started selling. Not the dashboard. The deals. Every customer deal, won and lost, with every note, every logged call and meeting, every email thread, every objection that came up in a conversation, and the stage history.

It took most of a day. It was worth more than any pipeline review we have held.

The headline finding fits in one sentence: nobody beat us. Thirteen percent of our losses went to a named competitor. Thirty-six percent were lost to timing, twenty-six percent to "what we have is good enough". The calendar and inertia took more than sixty percent of our losses. Our lost-reason dropdown in the CRM, meanwhile, said "chose competitor" on deals where the buyer had decided to prospect with their own marketing team, and "no budget" on a deal that was actually an acquisition freeze.

This post is about how to do that exercise properly, how to turn it into rules your team follows next week, and what we are building so you never have to spend a day on it.

Why win/loss analysis usually teaches nothing

Most teams have a lost-reason field. Most of those fields have five or six options that were set up on day one, and the rep picks one in two seconds on the way to the next call. In our data, almost half of the losses had no reason at all. Of the ones that did, a third contradicted the notes on the same deal.

The reasons are structural, not personal:

• The dropdown is filled from memory, at the moment of least interest. The deal is dead. The rep wants it off the board.
• The options are not a taxonomy. "Stay with current setup" and "postponed" overlap. "Chose competitor" has no field for who.
• Win reasons are never recorded at all. You learn why you lose but never why you win, which is the half you can repeat.
• It happens once a year, as a slide. A pie chart of reasons with no way to click into the deals behind a slice is a summary of guesses.

The fix is not a better dropdown. It is reading the record, and then building the categories from what the record says.

Step 1: Put the evidence in one place first

Before you categorise anything, collect what actually happened on each deal: calls and their summaries, meetings and their notes, email threads, CRM notes, stage moves, the contract or proposal events, who from your side touched it and when. If your conversations are captured on the deal, this takes minutes. If they live in reps' inboxes and memories, this is the step where you discover that.

Then look at the shape of the effort before you look at reasons. Ours:

The last row is the one that changed how we think. The deals we won got a contract in front of them, early. Most of the deals we lost never did. Some of that is selection, of course. A lot of it is not.

Step 2: Decide the categories before you read a single deal

You need a fixed taxonomy so that this quarter is comparable with the next one, and so two people reading the same deal land on the same answer. Ours, for losses:

• Timing and bandwidth. No room now: another project, an acquisition, a CRM migration, a new hire to onboard. Door left open.
• Status quo. The existing tool, the in-house team or the manual process was judged good enough. Nobody chose a rival. They chose not to change.
• Chose competitor. A named vendor won. The name is mandatory.
• Price, budget or value. No budget, price too high, or value not perceived at that price.
• Champion or authority. The champion left, went on leave, got fired, or never had authority.
• Ghosted after proposal. Contract sent, then silence.
• Fit. Wrong market, wrong customer type, a partner model that cannot work.
• Data or product gap. The trial output missed, or an integration was missing.
• Trust and vendor risk. Young vendor, stability, GDPR, no references.
• Merged or converted. Not a real loss. Excluded from the win rate.

And for wins, because the half you can repeat deserves the same rigour: warm relationship, referral or partner channel, low-entry pilot, demo-to-close speed, trial that proved value, replaced an incumbent tool, expansion of an existing customer, acute data need, and trust built through references or security answers.

Every deal gets one primary category and at most one secondary. Ten categories is about the limit; past that, people stop agreeing.

Step 3: Read the deal, not the dropdown

This is the step that costs a day and pays for the year. For each deal, read the last three touches and the notes, then ask: what actually ended this? Write two sentences. Then write one sentence starting with a verb: what would we do differently?

Three of ours, anonymised:

Recorded: no budget. Actual: the company was acquired and put a freeze on new systems until the new owner had reviewed the setup. Do differently: set a six-month reminder instead of closing lost.

Recorded: chose competitor. Actual: the referred contact had never heard of us, saw "one more initiative", and the company decided to prospect with its internal marketing team. Do differently: go back to the head of sales who made the referral instead of leaving it with the person she handed us to.

Recorded: stay with current setup. Actual: the account manager was enthusiastic and wanted to test, but his boss decided and we never got the joint meeting. Do differently: decision maker in the second meeting, or no trial.

None of these three losses was about the product. All three would have taught us the wrong thing from the dropdown.

Step 4: Look at time, not just reasons

Once every deal has a category, put the cycle length next to it. Ours split cleanly: half of our wins closed within a week of the first touch, with the contract sent in or right after the demo. About five percent of the losses did. Past sixty days, timing and status quo took over almost completely.

That is not an argument for rushing buyers. It is an argument for honesty in the second meeting: if there is no contract on the table by then, the deal is parked, not pursued, and it should be treated that way in the pipeline.

Also look at silence. Our lost deals had typically been quiet for more than two weeks before they were closed. The signal was there long before anyone acted on it.

Step 5: Slice it, because the pattern is not uniform

The same categories mean different things by rep, company size and channel:

• Referrals closed in one meeting. Every deal that came through a partner or a person who already knew us signed within days. Cold-booked demos to companies with twenty to fifty employees mostly stalled.
• Trust questions arrive at twenty employees. Below that, nobody asked about our stability, our references or GDPR. Above it, every longer cycle did, and we answered late.
• Trials before budget and authority did not convert. Every trial that ran with those two fields blank was lost. The trials that closed had a named decision maker and a stated budget first.

You cannot see any of this in a pie chart. You see it when you can click a bar and get the deals behind it.

Step 6: One rule per category

This is where the analysis becomes actionable, and where most teams stop. A category is a description. A rule is a change in behaviour. Ours, one per category, written for next week:

Seven rules. Each one traces to specific deals a rep can go and read. That is what makes them stick.

Step 7: Make it a page, not a slide

A win/loss deck is read once. A page with filters is used. The version that changed our behaviour has a handful of properties:

• Filters for outcome, rep, reason, company size and period, and a search box.
• Reason bars you can click to see the deals behind them.
• Every deal expandable to the two-sentence why, the one-sentence lesson, the recorded reason next to the inferred one, and the full footprint: meetings, calls, emails, signals, contacts, days silent.
• A hygiene list: deals with no reason, deals where the dropdown contradicts the record, five-figure deals with zero logged activity.

We built ours by hand. It is the only way to do it the first time, and everyone should do it once. Nobody should have to do it twice.

What we are building

Everything in that page is now being built into Funnelfeedr, under Insights › Closed deals. We are being specific about it because vague roadmap language is exactly the kind of thing this post argues against.

• Every closed deal is classified automatically from the conversation record that already sits on the deal in Funnelfeedr: call summaries, meeting notes, email threads, the objections and competitor mentions that were raised, stage history, line items and contacts. Primary and secondary category from the fixed taxonomy above.
• Each deal gets the two-sentence why and the one-sentence lesson, with the evidence attached, the same way our deal status and qualification already point at the quote they came from.
• The recorded lost reason is shown next to the inferred one. Your dropdown does not disappear. It gets audited.
• The whole page is filterable by rep, reason, size band, period and text, with the effort-and-speed medians, the by-rep table, competitors built from actual mentions in your calls and meetings, and the learning cards that link back to the deals they rest on.
• The hygiene list ships with it, because the fastest improvement in any win/loss analysis is fixing the deals with no reason recorded.

The taxonomy is fixed on purpose. If the categories drift every quarter, you cannot compare quarters, and comparing quarters is the whole point.

We wrote earlier this month about where deals die between meetings and about where the sales process should live. This is the same argument, pointed backwards: the record of what was said on a deal should tell you why it ended, without a rep having to remember, and without a manager having to spend a day reading. The day we spent was the best sales investment we made this quarter. It should also be the last time anyone has to make it by hand.

Want to see what your last quarter of closed deals actually says, with the recorded reasons next to what the record shows? Book a demo and bring your lost deals →