The debrief
The same-day leave-behind assembled from rehearsal artifacts, the retro on what the harness produced versus what it cost, and pruning the repo into the next template.
- Assemble a same-day leave-behind from artifacts you already have
- Run an honest retro on the harness — value produced versus cost
- Prune the engagement repo into the next engagement's template
The follow-up goes out the same day, and it is mostly assembled before the meeting ends. The leave-behind is the per-beat screenshots plus the S1–S6 traceability table — every criterion the client set, and the beat that met it. Alongside it: the open questions, each with an owner, and the update to the system of record. That last one follows the MSX pattern — MSX is Microsoft’s internal seller CRM, built on Dynamics 365⊙ — and the specifics of how a seller updates it are reconstructed, not documented:
The deck-writer drafts the leave-behind from the rehearsal folder — it has the screenshots and the traceability the understudy already produced, so the draft is a reassembly, not a fresh write. It keeps the register plain and never pastes customer data of record; the CRM update is a pasteable summary.
Then the retro, which is where the harness improves. What did it produce, and what did it cost — in time, in credits, in the two beats that drifted? And finally, prune: strip the dossier and the fabricated data, keep the agents, skills, and instructions, and the engagement repo becomes the template for the next one.
The debrief is where the compounding happens
A single engagement run with a harness is faster than running it by hand. A second engagement is where the harness pays for itself, because the pruned template means you start the next deal with the roster, the skills, and the instructions already in place. The debrief is the hinge: do it well and each deal makes the next one cheaper; skip it and every engagement starts from zero.
In the field
After your next demo — real or practice — assemble the leave-behind from whatever your rehearsal captured, then prune the repo into a template. Note one thing that generalized and one thing that did not. That distinction is the subject of Part V.
Part IV is done
You delivered a rehearsed system and left behind a traceable follow-up. In Part V, the harness outlives the deal.