In preview: the post-mortem pipeline at submit close
The moment a proposal marks won or lost, PursuitAgent opens a structured post-mortem against the captured pair. In preview while the post-mortem template, reflection, and write-back loop mature toward general availability.
The post-mortem pipeline is in preview this week behind a feature flag. Short changelog post — what it does, how to use it, and what it links to. The structured-debrief and theme-retirement layer it feeds into is described on the Win-Loss Intelligence page; the auto-open-on-disposition pipeline itself is the new bit and has not yet rolled into the marketed surface.
What shipped
When a proposal’s disposition flips from “submitted” to a terminal status (won, lost, withdrawn, no-decision), PursuitAgent automatically opens a structured post-mortem record tied to that bid. The record draws on the captured win/loss pair and pre-populates the sections a human would otherwise type by hand:
- Bid summary (opportunity, commercials, disposition) — filled from the bid record.
- Win themes committed vs. win themes landed — surfaced from the capture plan vs. the shipped response.
- KB blocks used, blocks edited heavily, blocks missing — surfaced from the drafting log.
- Compliance posture at submission — from the compliance matrix snapshot.
The template above is pre-filled. The human-written sections (what the debrief said, what the three follow-up tickets are) stay empty until the proposal manager completes them.
Why this is the pipeline, not the analysis
This ship is the plumbing. It opens the record at the right moment, pre-fills what the system already knows, and routes the record to the proposal manager’s queue. It does not analyze anything — the analysis step (reflection, in the intelligence loop terminology) runs separately.
The specific sequencing: disposition flip → captured-pair snapshot → post-mortem record opened → proposal manager notified. Each step takes sub-second in the common case; records are queued and retried on transient failures.
How to use it
Nothing to turn on. For any bid with capture enabled, the post-mortem record opens automatically on the disposition flip. The proposal manager sees a new item in their queue labeled “post-mortem ready.” Clicking through lands on the pre-filled record; the manager fills in the debrief notes (if any) and the three follow-up tickets.
Teams can override the template on a per-tenant basis — see the docs at /docs/win-loss/post-mortem-template. The default template is the one previewed yesterday in the template preview post.
What’s next
The reflection step — which reads a completed post-mortem and produces candidate KB write-backs — is still offline-only while we tune precision. When reflection ships, the loop closes end-to-end: every disposition flip produces a post-mortem, every completed post-mortem produces candidate updates to the KB, every candidate gets human review before it graduates to canon.
Sarah’s full post on the discipline, the template, and the follow-through lands Thursday at proposal-post-mortems-discipline. The software has to exist for the discipline to be sustainable, but the software without the discipline is a pipeline that opens empty records.