Skip to main content

How to run a dead deal post-mortem your team will actually use

A dead deal review process for CRE teams. When to hold the post-mortem, the questions to ask, a reasons-lost taxonomy, and how to track patterns over time.

14-day free trial · Full access · Cancel anytime

MotionCRE Editorial

Written by the MotionCRE team.

Published July 13, 2026

A dead deal post-mortem is a 30-minute structured review held within two weeks of a deal dying, where the deal team reconstructs the timeline, assigns the loss a standard reason code from a fixed taxonomy, and records one thing the firm would do differently. Reviewed quarterly across all dead deals, the coded reasons show whether the firm is losing on price, on diligence findings, or on deals it never should have pursued, and where the process needs to change.

Why dead deals deserve a formal review

Most of what an acquisitions team touches dies. A typical shop receives 10 to 15 offering memorandums a week and kills roughly 80 percent at initial screening, and PropRise estimates that screening work alone costs a two-analyst team about $21,800 a year in fully loaded time. The pipeline produces dead deals at many times the rate it produces closings, which means the dead deals hold most of the information about how the firm actually operates.

Screening kills do not need a meeting. The deals that deserve a post-mortem are the ones that died after the firm committed real resources. A deal the firm lost at best and final. A deal that went under contract and fell out in diligence. A deal where the seller retraded at the eleventh hour. Deaths like these commonly carry $25,000 to $75,000 in pursuit costs each, and they carry lessons that screening kills cannot.

Most firms handle both kinds of death the same way. The deal gets dragged to a Lost column, someone types "seller went another direction" in a note, and the file goes quiet. Twelve months later nobody can say whether the firm loses mostly on price, mostly on diligence surprises, or mostly on deals it never should have chased. The post-mortem exists to make that question answerable.

Set the trigger rules in writing

A review process without trigger rules becomes a review process for deals people feel like discussing, which selects for the dramatic losses and ignores the instructive ones. Write down three rules and apply them mechanically.

  • Any deal that reached a signed LOI gets a post-mortem, no exceptions.
  • Any deal with pursuit spend above a fixed threshold, say $10,000 in reports, legal, and travel, gets one even if it died before LOI.
  • Everything else gets a one-line reason code logged at the moment the deal is marked dead, with no meeting.

The two-week clock matters as much as the trigger. HubSpot's postmortem guidance recommends holding the session within a week of the loss with facts prepared in advance, and two weeks is a realistic outer bound for a deal team juggling live pursuits. Past that, the timeline gets rebuilt from memory, and memory is where revisionism lives.

Use a fixed reasons-lost taxonomy

Free-text loss reasons produce a drawer full of unique explanations that cannot be compared. A fixed taxonomy produces a distribution. Copy the codes below into your system as a required field on every dead deal, and force a single primary code per deal even when several apply. The sample distribution shows what a year of 40 dead deals past screening might look like at a mid-size shop; your own numbers will differ, and the differences are the finding.

CodeReason lostWhat it usually meansSample share of 40 dead deals
L1Lost on priceA cleaner or more aggressive bid won35 percent (14 deals)
L2Seller behaviorRetrade, withdrawal, or a broken process15 percent (6 deals)
L3Diligence findingEnvironmental, title, survey, or physical surprise12.5 percent (5 deals)
L4Financing failedQuotes came back wide of underwriting10 percent (4 deals)
L5Underwriting gapOur numbers were wrong and we caught it late7.5 percent (3 deals)
L6Outside the buy boxShould have died at screening, died after spend instead12.5 percent (5 deals)
L7Internal declineIC said no, or capital was unavailable7.5 percent (3 deals)

Each code implies a different fix. A heavy L1 share is a bidding and conviction question. L3 concentration points at diligence sequencing, ordering the reports that kill deals earliest. L5 is a modeling standards problem. L6 is the expensive one, because every L6 deal represents pursuit dollars that a working screening process would have saved.

Join CRE teams already running their deals on MotionCRE.

Run the meeting in 30 minutes

Keep the format identical every time. The deal lead, the analyst, and whoever ran diligence attend. Ten minutes on the factual timeline, circulated in writing beforehand. Five minutes to agree the primary reason code. Ten minutes on the single question that produces value, which is what the process should catch next time. Five minutes on external feedback.

That last item separates useful reviews from theater. The Brooks Group's lost-deal framework pushes teams to ask the decision maker directly what would have changed the outcome instead of accepting the first surface explanation. In acquisitions, that means calling the listing broker after the dust settles. Ask where the winning bid landed, how the terms compared, and whether your team's diligence asks read as disciplined or as difficult. Brokers answer these questions more often than teams expect, and the answers reprice your internal story.

Design against the known failure modes. Clozd's critique of traditional post-mortems lands on two points worth taking seriously, that the meetings collapse into blame-shifting and exclude the person who actually made the decision, and that firms over-rotate on a single dramatic loss. The fixes are structural. Facts circulate before opinions form, the code gets assigned against the taxonomy before anyone editorializes, no single deal changes strategy by itself, and once or twice a year the team runs the same format on a deal it won.

A 30-minute agenda you can copy

  • Minutes 0 to 10. Timeline review. The analyst walks through the circulated facts, dates, bid movements, and diligence findings. Corrections to the record happen here, opinions do not.
  • Minutes 10 to 15. Reason code. The group agrees one primary code from the taxonomy. Disagreement between two codes is itself worth recording.
  • Minutes 15 to 25. The counterfactual. One question, asked plainly. At what point did this deal become unwinnable, and what would the process have needed to see it earlier?
  • Minutes 25 to 30. The lesson. One sentence, one owner if it implies a process change, logged on the deal.

Resist the urge to extend the meeting when the deal was painful. The discipline of the fixed format is what keeps the ritual cheap enough to survive contact with a busy quarter, and a review process that gets skipped when the team is busy is a review process that only studies slow markets.

Distinguish losses from walk-aways

Not every dead deal is a loss. A deal the firm walked away from after diligence surfaced a real problem is the process working, and coding it identically to a lost bid poisons the data. Track the direction of the death alongside the reason code. Walked away, lost to another buyer, or seller pulled the deal.

The walk-aways deserve their own quarterly question. If the firm walked away from five deals after spending an average of $40,000 in pursuit costs on each, the useful follow-up asks whether any of those five problems were knowable for less money and earlier in the sequence. Sometimes the answer is no, and the $200,000 was the honest cost of discipline. When the answer is yes, reordering one report in the diligence sequence is worth five figures a year.

Record the outcome where the deal lives

A post-mortem that ends in someone's notebook did not happen. The record needs to live on the deal itself, in the same system that holds the bid history, the reports, and the correspondence the review drew on.

In MotionCRE, dead deals move to a Lost stage on the pipeline board instead of getting deleted, so the full history stays searchable. A custom field holds the reason code, and the closing note in the deal workspace captures the one-sentence lesson next to the files, key dates, and financing quotes the deal accumulated. When the same seller's broker sends the next OM, or the same submarket surfaces again, the record is one search away rather than one departed employee away.

Read the pattern quarterly

The individual review is the input. The quarterly read is the output. Once a quarter, pull every dead deal and look at the code distribution against pursuit spend.

The math makes the case for the ritual. A firm that loses 12 post-LOI deals in a year at an average pursuit cost of $30,000 spent $360,000 on deals that died. If the quarterly read shows 2 of the 12 coded L6, outside the buy box, that is $60,000 of pursuit spend the screening gate should have intercepted, and tightening the written criteria is worth roughly that amount next year. If 5 of the 12 are L3 diligence findings and 4 of those were environmental, moving the Phase I earlier in the sequence has a calculable payback.

Bring the distribution to the weekly acquisitions pipeline meeting once a quarter and give it 15 minutes. The dead deals already cost the firm the tuition. The quarterly read is the only step in the whole process that collects the education.

Browse more playbooks, templates, and definitions in the MotionCRE resource library.

Common questions

It is a short structured review of a deal that died after the firm committed real resources, typically anything that reached LOI or beyond. The deal team reconstructs what happened, assigns a standard reason code for the loss, and records what the firm would change. The output lives on the deal record so the pattern across many dead deals can be read later.

Keep every dead deal, reason code, and lesson on the pipeline where your team can find it

Your pipeline, your deals, and everything it takes to execute, in one place.

14-day free trial · Full access · Cancel anytime