# How to debrief a lost deal with your rep (without it feeling like a trial)

https://salesbond.app/blog/lost-deal-debrief-rep/
Published: 2026-10-05 · Updated: 2026-10-26

Debrief a lost deal in one short one-on-one, not in a meeting. Open the deal’s timeline in Pipedrive together, ask the rep when they first felt it slipping, put that next to the lost reason they entered, and agree on one thing they will do differently in the next deal. Twenty minutes is enough. Skip the customer survey and the group post-mortem for most losses; they earn their time on deals well above your usual size.

## What the twenty minutes are for

This is coaching, not analysis. One manager, one rep, one deal, and the only question that matters is what the rep does at the same point in the next deal.

That makes it a different exercise from the two we have written about before. A [win-loss round with buyer calls](https://salesbond.app/blog/win-loss-analysis-small-team-pipedrive/) is about the team and what buyers say. [Lost reasons in Pipedrive](https://salesbond.app/blog/pipedrive-lost-reasons/) is about the field itself and what a month of it adds up to. Both look at many deals from above. The debrief looks at one deal from inside, with the person who worked it, and it exists because a pattern on a page does not change how Maria handles her next proposal. A conversation about her proposal might. It’s the same logic as the rest of [coaching in a small team](https://salesbond.app/blog/ai-sales-coaching-small-teams/): one rep, one habit at a time.

Most of what ranks for lost deal analysis is a question bank. The Brooks Group publishes [nineteen questions for a dead deal autopsy](https://brooksgroup.com/sales-training-blog/dead-deal-autopsy-19-questions-ask-when-conducting-lost-deal-analysis/); HBR has [three to ask after any win or loss](https://hbr.org/2023/07/3-questions-sales-teams-should-ask-after-losing-or-winning-a-deal). Good questions, built for a room. In a team of three to ten people there is no room. You know the deal and you know the rep, so the format is the two of you and the CRM record, and nineteen questions in twenty minutes would be an interrogation.

Which is the other thing the debrief is not. The moment a rep feels they are on trial, you get a defence, and a defence teaches nobody anything.

## Which losses get a debrief

One or two a month. Not every loss, and not the biggest by default.

Pick the surprise: the deal the rep expected to win, the one that was in the forecast two weeks before it died. That is where the learning is, because something happened that the rep did not see, and the timeline probably did. A small deal lost after a proposal teaches more than a large one lost at the first call.

Leave out the losses no rep could have turned around. The buyer got acquired, a new CFO froze every purchase for the year. A debrief on one of those becomes a conversation about luck, and the rep learns that debriefs are about luck. If the deal on your shortlist was never really alive, that is a question about [when to close a deal as lost](https://salesbond.app/blog/when-to-close-a-deal-lost/), not about the rep. And don’t pick the same rep two months running. One debrief is coaching; three in a row reads as a case being built, whatever you say at the start.

## Five minutes before: read the deal, not the rep

Everything you need is in the deal’s detail view in Pipedrive. Open it before the conversation and look in three places.

The progress bar at the top shows the stage the deal reached and how many days it spent in each stage ( [Pipedrive: deal detail view](https://support.pipedrive.com/en/article/deal-detail-view)). The History section below holds the notes, activities, emails and files, with a tab for each. The Changelog tab under History lists changes to stage, value, label, contact person, expected close date and fields, sorted by date. And the lost reason sits in the details section of the same view; any comment the rep typed when marking the deal lost was saved as a note ( [Pipedrive: lost reasons](https://support.pipedrive.com/en/article/lost-reasons)).

From those, write down three dates:

- the last activity actually completed with the buyer, from the History;
- the last stage move, from the Changelog;
- the day the deal was marked lost.

The gap between the first and the third is usually the whole conversation. Note as well whether the expected close date moved in the Changelog and how many times. A date pushed three times is a rep who already knew. If the deals live in HubSpot, the reason the rep picked sits in the [HubSpot closed lost reason](https://salesbond.app/blog/hubspot-closed-lost-reason/) property.

![Pipedrive deal timeline with stages Qualified, Demo, Proposal sent; the gap from last buyer activity to marked lost is where the conversation lives](https://salesbond.app/wp-content/uploads/2026/10/lost-deal-debrief-with-rep-pipedrive-2.png)

What you do not prepare is a verdict. If you walk in knowing what went wrong, the rep will hear it in the first question, and the rest of the twenty minutes is theatre. Before you walk in, settle [person or process: one check before you coach](https://salesbond.app/blog/sales-coaching/).

## Four questions, and the one we don’t ask

Open by saying what this is: “I want to understand this one deal with you, not grade it. Let’s look at the timeline together.” Then share the screen or sit at the same one, and ask these four, in this order.

1. **“When did you first think this one might not close?”** Let the rep answer from memory before either of you looks at a date. Then find that moment in the History. Reps often place it earlier than their activity log does, and that difference is the first useful thing you will learn.
2. **“What did you do that week?”** Read the timeline rather than interpret it. “The Changelog shows the close date moved on the 12th and again on the 26th, and I don’t see an activity in between” is an observation the rep can answer. “You let it drift” is a judgment they can only absorb.
3. **“What were you waiting for from them?”** A signature, a reply from IT, a meeting their boss kept moving. The post-mortem advice that circulates on LinkedIn, and the Brooks Group list, both press on who influenced the decision and what they cared about. Asked of the rep about one deal, it becomes a question about the stretch where the rep was waiting instead of acting, which is exactly the stretch the next question is about.
4. **“If the next deal reaches that same point, what do you do differently?”** This is the question the other three were setting up. The answer should name a moment and an action, not a resolution to try harder.

The question we don’t ask is “Why did we lose?” The rep has answered it once already, in the lost reason, and asking again gets the same answer with a longer justification. The reason is the input to this conversation, not its output.

Two rules for the manager’s side. The rep talks first on every question, and you read the record aloud instead of summarizing it. The “zero-pressure” tone that the post-mortem guides recommend is not a courtesy here; it is what makes the fourth question answerable.

## Does the lost reason match what the rep just said?

Usually not quite, and that is useful rather than embarrassing. The field says “competitor”. The rep has just told you the deal really stalled three weeks earlier, when their contact went on leave after the demo and nobody else on the buyer’s side picked it up. Both are true. The lost reason records how the deal ended; the story records where it turned, and the turning point is what the fourth question needs.

So don’t argue about the field. Add a note to the deal with one line on what actually happened and today’s date; it sits in the same detail view as the lost reason. The rep has just described the deal in their own words, and a record that only holds the ending quietly undoes that, because the next person to open the deal gets the guess first, and the note right under it.

## One change, and when to check it

Agree on one change. Not two, and not “follow up better”.

Phrase it as a moment in the next deal with a visible action, tied to something both of you can see in Pipedrive: “When a deal sits in Proposal sent for ten days without a reply, I call instead of sending a third email, and I log the call.” Or: “Before I move a deal to Proposal sent, there is a second contact linked to it or a note saying why there isn’t.” A stage, a field or an activity type, so the check later is a glance and not a memory test.

Write the change as a note on the the lost deal, or in whatever you keep for one-on-ones. Then check it on the next deal of that rep’s that reaches that stage, not at next month’s one-on-one. Open that deal’s History together for two minutes and look for the action. That is the whole follow-up, and it folds into the [deal review questions](https://salesbond.app/blog/deal-review-questions-buyer-action/) you already ask about open deals. If the change held, say so, if it didn’t, that is the next debrief, and you have the deal for it.

## Having the conversation while the deal is still open

The best version of this debrief happens before the loss, on the day the rep first thinks the deal is slipping, and the reason it rarely does is that nobody is looking at that deal on that day. We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Its Deal Health checks every deal in the connected CRM against more than 20 rules, shows which rules a deal breaks and what to do about it, so the “when did you first think it might not close” question can be asked while there is still something to do. It works from what is in the CRM record, so it can show that a deal breaks a rule but not why. The why is still the twenty minutes. [Check your CRM with SalesBond](https://salesbond.app/) if you want those deals flagged for you; the conversation stays yours.

Start with one deal this month. Pick the one that surprised you, spend five minutes with its timeline, and ask the first question before you look at the dates.