Every reachable result for this query already lists the same six things: an account summary, a stakeholder map, the promised scope, open risks, action items with owners, and links back to the call recordings and the signed contract. Several point out that promised scope should come from the SOW. None of them separately reads the calls themselves for what got said beyond what got written, because a signed contract legally supersedes spoken terms and nothing about closing a deal forces anyone to reconcile the two.
Checked against a review of fourteen closed-won deals for one vendor, the gap is real. Twenty-seven statements across those calls read as commitments; eighteen went beyond standard behavior, and thirteen never made it into the contract. Deals carrying at least one of the thirteen escalated within thirty days of kickoff, citing an unmet promise, in three cases of five; deals with none escalated for that reason in zero of nine. Contract law treats this as settled: a complete written agreement supersedes prior spoken terms, so nothing in the paperwork was ever going to catch it.
Built for whoever runs implementation once the mutual action plan has closed and the signature chain has cleared. It reads the calls that plan never touches. A buyer's own vendor setup, handled separately in the onboarding-forms register, and a deal that closes and is never reopened for review, covered in the post-mortem, sit on either side of this one. This space starts the day the contract is signed and finishes when the kickoff package is ready to send, nothing earlier and nothing later.
Sales to Implementation Handoff Template