Jordan Research All articles
Sales & Commercial Insight

After the Handshake: Making Win/Loss Debriefs a Standing Habit in UK B2B

Jordan Research
After the Handshake: Making Win/Loss Debriefs a Standing Habit in UK B2B

Photo: EU2017EE Estonian Presidency, CC BY 2.0, via Wikimedia Commons

Ask a UK B2B sales director why a deal was lost and you will usually get one of four answers: price, incumbency, timing or procurement. Ask for the evidence and the conversation tends to end. The debrief happened, the lesson did not.

This is not a failure of intelligence. It is a failure of process. Win/loss insight is one of the few forms of primary evidence a B2B firm can generate almost for free, because the interviews are with people who have already engaged with the business. Yet in most organisations the file is thin, the notes are unstructured, and nobody owns the synthesis.

Why the file gathers dust

Three mechanisms are usually at work. The first is attribution: the account executive who lost the deal is asked to explain it, which invites a defensible narrative rather than an honest one. The second is granularity: notes are captured deal by deal, so nobody can see that the same objection has appeared in nine of the last fourteen losses. The third is ownership: the debrief is treated as a sales administrative task rather than a commercial insight activity with a named owner and a quarterly output.

None of these requires a large budget to fix. They require a routine.

A routine that survives a busy quarter

Interview within ten working days. Memory decays and goodwill evaporates. A short note to the buyer's contact asking for fifteen minutes to learn from the process, framed as process improvement rather than a pitch, works best immediately after the decision.

Keep the interviewer separate from the account. Where possible, someone from insight, proposition or a senior sales figure without a stake in the deal should conduct the conversation. Buyers are markedly more candid with someone who is not defending a relationship.

Twenty to thirty minutes, six to eight questions. Enough to get beneath the summary, short enough to secure agreement. Ask who was involved in the decision, what the shortlist looked like, what the evaluation criteria were and how they were weighted, what the buyer expected before the process began, where the proposal diverged from that expectation, and what would have had to change for the outcome to differ.

Write up within forty-eight hours, in a fixed format. Free-text notes are where insight goes to die. Use a short structured record: deal identifier, sector, deal size band, buying committee roles represented, stated criteria, evidence cited, and the interviewer's confidence in each element.

Do not let the summary stand alone. Record the buyer's own words against the key judgements. A line such as 'we could not get internal sign-off on the implementation resource' is worth more than a ticked box marked 'implementation concern'.

Separating the excuse from the pattern

A single debrief tells you about a deal. A hundred debriefs, coded consistently, tell you about a market. The coding scheme is the bridge.

Keep it deliberately small. A workable set of codes might cover buying committee composition, evaluation criteria, perceived differentiation, price and commercial terms, implementation and risk, incumbent advantage, and process friction. Add a code for 'buyer volunteered an unprompted reason' — these are disproportionately informative.

Then apply a threshold before drawing conclusions. A theme appearing in three losses out of twenty is an anecdote with a spreadsheet. The same theme appearing in three consecutive quarters, across sectors, and in deals of different sizes, is a finding.

Two further tests are worth applying. First, triangulation: does the pattern appear in the CRM's structured loss reasons, in the objections logged by the bid team, and in the debrief interviews? Where the three diverge, the divergence is itself the insight. Second, negative-case checking: are there won deals in which the same objection was raised and overcome? A theme that appears equally in wins and losses is not a driver of the outcome.

Where the findings should land

Win/loss evidence earns its keep when it reaches a decision that has a budget attached.

For pricing, the useful output is not 'we are too expensive' but the specific comparison buyers made, the alternatives they weighed, and whether discounting changed the outcome or merely changed the margin. Many UK B2B firms discover that price was raised late and never decisive, while implementation risk was raised early and never answered.

For proposition, the recurring gap between what the buyer expected before the process and what the proposal emphasised is usually the richest seam. It tends to point at messaging and proof rather than product.

For enablement, the pattern of buying committee composition is actionable. If debriefs consistently show a finance or IT stakeholder joining late, then the sales playbook, the collateral and the qualification questions should all reflect that.

Governance in three lines

Give the file an owner — typically the commercial or marketing leadership rather than sales operations alone. Agree a redaction rule so that individual buyers are never identifiable in circulated summaries. And commit to a quarterly read-out, even when the sample is small, so the habit is protected through busy periods.

The honest limits

Win/loss interviews sample the buyers who agree to talk, and those buyers are not representative of all buyers. They also capture a decision as the buyer remembers and chooses to present it, which is a reconstruction rather than a record. Both limitations are tolerable if they are stated, and if the debrief file is read alongside structured CRM data rather than instead of it.

The organisations that get value from this are rarely the ones with the most sophisticated programme. They are the ones where the interview happens on time, the write-up is consistent, and somebody reads the file before the next pricing review.

All Articles

Related Articles

Who Read the Transcript? A Buyer's Checklist for Qualitative Evidence When AI Does the Summarising

Who Read the Transcript? A Buyer's Checklist for Qualitative Evidence When AI Does the Summarising

Counting the Aisle: Turning Repeat Store Visits into Defensible Category Evidence

Counting the Aisle: Turning Repeat Store Visits into Defensible Category Evidence

The Sentence Before the Statistic: A UK Buyer’s Wording Audit for Board-Bound Surveys

The Sentence Before the Statistic: A UK Buyer’s Wording Audit for Board-Bound Surveys