# Late-Stage Deal Objection Autopsy Checklist

> A structured post-mortem checklist for diagnosing which unresolved or unspoken objection actually killed a deal you thought was won, correcting the CRM record, and setting a real win-back trigger.

Free checklist for sales leaders. Topic: [Objection Handling](https://www.peerlab.ai/library/topic/objection-handling/). Published by PeerLab in the [Sales Enablement Resource Library](https://www.peerlab.ai/library/). Source: https://www.peerlab.ai/library/late-stage-deal-objection-autopsy-checklist/

## How to use it

Run this checklist within a week of any deal marked Closed-Lost or gone cold that had looked like a probable win, correct the CRM loss-reason with the verified root cause, and route the finding to rep coaching or content/enablement depending on whether it was a skill gap or a missing asset.

## What's inside

- Evidence-gathering checklist
- Stakeholder map reconstruction checklist
- Chronological objection-by-objection audit
- Silent/unspoken objection detection checklist
- Root-cause categorization with skill-gap vs. structural-gap tagging
- CRM correction checklist
- Win-back trigger list

Run this within a week of any deal marked Closed-Lost (or gone cold) that had looked like a probable win.

## Phase 1: Gather the Evidence

- [ ] Pull the full CRM activity timeline (calls, emails, stage changes, dates)
- [ ] Re-listen to / re-read the last 3 substantive conversations before the deal went quiet
- [ ] Collect every internal note/Slack mention about this deal from rep, SE, and manager
- [ ] Flag the logged CRM "loss reason" as **unverified** until the autopsy is complete

## Phase 2: Reconstruct the Stakeholder Map

- [ ] List every stakeholder who touched the deal (champion, economic buyer, procurement, legal, end users, blockers)
- [ ] For each, note the last objection or concern THEY personally raised: not the champion's summary of it
- [ ] Identify which stakeholder went silent first, and when
- [ ] Determine whether the champion actually had internal influence, or was a "false champion"

## Phase 3: Objection-by-Objection Audit

- [ ] List every objection raised across the deal's lifecycle, in chronological order
- [ ] For each, mark: Resolved / Partially addressed / Never addressed / Never actually surfaced (silent)
- [ ] Identify the LAST objection raised before the deal went cold: this is the prime suspect
- [ ] Check whether the same objection recurred more than once (recurrence = false resolution the first time)
- [ ] Check whether a NEW stakeholder introduced a fresh objection late in the cycle (common in procurement/legal stage)

## Phase 4: Detect Silent Objections

- [ ] Did engagement (email opens, meeting attendance, response time) drop sharply after a specific event? Map that event to a likely unspoken objection
- [ ] Did anyone ask a "soft no" question late ("what happens if we don't move forward") that went unprobed?
- [ ] Did competitor mentions increase near the end without being addressed directly?
- [ ] Did a budget/procurement/legal cycle date pass without follow-up, suggesting a structural (timing/budget) objection rather than a product one?

## Phase 5: Root-Cause Categorization

- [ ] Tag the deal with ONE primary root cause: Price/Budget · Trust/Risk · Timing/Priority · Authority/Champion Failure · Competitor/Status Quo · Procurement/Legal Stall · Product Fit
- [ ] Note whether this was a **rep skill gap** (objection raised, rep didn't resolve it) vs. a **structural gap** (no rebuttal/proof existed yet)
- [ ] If skill gap → flag for coaching using the Objection Handling Certification Rubric
- [ ] If structural gap → flag for content/enablement to build the missing rebuttal/proof asset

## Phase 6: Correct the CRM Record

- [ ] Update the CRM loss-reason field to the VERIFIED root cause, not the rep's original guess
- [ ] Add a one-paragraph autopsy summary to the deal record
- [ ] Tag the specific unresolved objection (verbatim quote where possible) for inclusion in the team's objection log/rebuttal library

## Phase 7, Win-Back Trigger List

- [ ] Set a win-back reminder tied to the actual root cause (e.g. budget cycle reopening, competitor contract renewal, leadership change)
- [ ] Note what NEW proof point or change would need to exist to reopen this deal
- [ ] Assign a named owner for the win-back follow-up, not "whoever remembers"