A Voicify "Competitor A or Competitor B" battlecard library only stays sharp if the deals it touches feed back into it. The slot-decision tree picks the slot, the rep runs the call, the deal lands one way or the other — and then most teams drop the deal into a CRM debrief field that no one ever reads. This is the post-deal debrief template we attach to every slotted Voicify card: slot-tagged questions, signal scoring on the same six categories as the objection map, and a structured handoff to the sales-enablement lead so that what gets learned in Q1 actually shows up in the Q2 refresh.
TL;DR
One template. Two halves. Slot-tagged. The rep fills the recall half within 48 hours of close or loss. The sales-enablement lead fills the scoring half within five business days, working from the rep submission plus call recordings. Both halves track the same six categories the objection map uses: pricing, switch cost or stability, integration depth, staff training, HIPAA, dental-pure comparison. Record initial slot, final slot, and the trigger if the slot flipped mid-cycle. Loss debriefs run full template; win debriefs run two or three landed patterns only. Outputs feed the quarterly refresh that updates the pre-loaded six.
Why a Slot-Tagged Debrief Beats a CRM Notes Field
The CRM debrief field collects free-text notes. The slot-tagged debrief collects structured signals. The difference matters because the battlecard library — the A-slot card, the B-slot card, the objection map, the QA checklist — is built around six categories with named response patterns inside each. A free-text note like "lost on integration" cannot be parsed back into those categories without someone reading every note and re-tagging it by hand. A structured field that asks "which integration-depth response pattern was used, and did it land" produces a row in a spreadsheet that the sales-enablement lead can sort, count, and act on. The point of the debrief is not to capture more — it is to capture the right shape, so the feedback loop into the objection map and the QA checklist actually closes.
The Two-Half Structure
The template splits cleanly into a recall half and a scoring half. The rep owns the recall half because only the rep was in the room and only the rep remembers what the prospect's face did when a particular response landed. The sales-enablement lead owns the scoring half because asking the rep to score their own deal always biases toward attributing losses to product gaps rather than card-execution gaps. Two halves, two owners, two windows.
| Half | Owner | Window | Output |
|---|---|---|---|
| Recall half | Rep on the deal | Within 48 hours of close or loss | Structured notes by category, initial and final slot, slot-flip trigger if any |
| Scoring half | Sales-enablement lead | Within 5 business days of recall submission | Numeric scores on each category, Tier 2 promotion candidates flagged, refresh inputs queued |
The Recall Half — What the Rep Fills In
The recall half is fifteen minutes if the template is right. Every field is closed-ended or short structured text — no free-text narrative boxes, no "any other thoughts" catch-all. The rep is filling slots in a form, not writing a memo. The fields:
- Initial slot. A or B, set at the discovery-brief stage by the slot-decision framework.
- Final slot. A or B at the close-or-loss point. If different from initial, the trigger that caused the flip.
- Dental-pure competitor in the room. Named, with a one-line note on which evaluation stage they entered at.
- Pre-loaded objections that surfaced. Check the six. For each that fired, the response pattern used.
- Unscripted objections that surfaced. Short structured text. Each becomes a Tier 2 backlog candidate.
- Rep recall on what landed. Two or three responses, with the indicator the rep saw — explicit verbal acknowledgment, follow-up question, body-language shift, request for the relevant proof point.
- Rep recall on what stalled. Two or three responses, with the same indicator format.
- Outcome. Win, loss, no-decision, or stalled. If loss, the competitor that won — named.
The Scoring Half — What the Sales-Enablement Lead Fills In
The scoring half is twenty minutes per debrief if the lead is also reviewing the call recordings, which they should be on losses and on any flipped-slot deal. The output of the scoring half is what actually gets carried into the quarterly refresh — the rep's recall is the source data, the lead's scoring is the decision input.
| Field | What it captures | Refresh use |
|---|---|---|
| Slot accuracy | Was the initial slot the right call given what showed up in the room | Slot-decision tree calibration |
| Response pattern fidelity | Did the rep use the pre-loaded response or improvise | Rep certification flag if fidelity is low; card simplification if multiple reps improvise the same field |
| Category-level pressure | Which of the six categories saw the most live pressure | Direct input to objection-map Tier 2 promotion ranking |
| Unscripted objection severity | How close to deal-flipping was the unscripted objection | Tier 2 backlog priority — high-severity unscripted objections get fast-tracked to next quarterly refresh |
| Leave-behind hygiene | Did any rep-internal language end up in the leave-behind by accident | Direct input to QA-checklist file-hygiene section |
| Proof-point freshness | Were any proof points cited that the QA-checklist would have flagged as stale | Direct input to QA-checklist proof-point-freshness section |
Win Debriefs Versus Loss Debriefs
Both wins and losses get a debrief, but the shapes differ. A loss debrief runs the full template because every category needs to be checked for what failed. A win debrief asks only for the two or three response patterns that landed and lets the rest stay neutral. A win debrief that claims six landed patterns is overclaiming — the lead down-weights it during the refresh. Wins are useful for confirming which pre-loaded responses to keep in the next quarter. Losses are what surface the Tier 2 promotion candidates and the rep-certification gaps.
The Mid-Cycle Slot Flip Signal
One of the few signals that only the debrief can capture cleanly is the mid-cycle slot flip — the deal that started in A and ended in B, or vice versa. CRM stage history will not show it because the slot lives on the battlecard library, not in the pipeline schema. The slot-decision framework is supposed to lock the slot before the rep dials, so flips happening more than once per ten deals are a calibration signal worth reading carefully. The debrief asks the rep to record the trigger — usually a discovery surprise: a hidden incumbent contract, a champion turnover, a CFO who showed up late in the cycle. The lead aggregates triggers across deals and decides whether the discovery brief that feeds the slot-decision tree needs a new question.
How the Outputs Feed the Quarterly Refresh
The debrief produces three queueable outputs that drop into the quarterly refresh cycle without further translation. First, Tier 2 promotion candidates ranked by category-level pressure and unscripted-objection severity — the sales-enablement lead reviews these and promotes anything that has hit three or more deals into the pre-loaded six. Second, rep-certification flags for fidelity gaps — these go to the sales manager for ride-along scheduling, not into the card itself. Third, direct inputs into the QA-checklist sections for file hygiene and proof-point freshness — fixes that happen at the file level, not the rep level. For the full QA pass that consumes these inputs, see the pre-deploy QA checklist and the core battlecard.
The debrief is the part of the system that nobody wants to build because the cost shows up immediately and the benefit shows up two quarters later. Build it anyway. The slotted card library is only as sharp as the feedback loop running into it, and a CRM notes field is not a feedback loop — it is a graveyard.