---
interpretation: lens
---
**Mandate:** The agent **MUST** verify the deal close and customer handoff are complete — contract executed, PO received, every commitment documented, every stakeholder context preserved for the receiving team. Trust gaps at handoff cause renewal loss; the lens exists to prevent them.

## Check

The agent **MUST** verify, filing feedback for any violation:

- **Contract terms finalized and signed** — every section of the executed contract reconciles to the `NEGOTIATION-TERMS.md` record; any drift was flagged BEFORE signature and resolved.
- **PO issued and payment terms confirmed** — purchase order number recorded with issuer name and line-item match to contract; net-X terms, invoice destination, currency, AR/banking setup all confirmed through the seller's secure channels.
- **Receiving-team handoff context is complete** — the `HANDOFF-PACKAGE.md` includes named goals, named timeline, named contacts with relationship history, named risks with watch-for signals. Handoffs of only a contract and a contact list fail this check.
- **Implementation-kickoff counterpart identified** — the right person/role on the receiving team is named in the handoff packet so the receiving stage can schedule kickoff. Scheduling itself belongs to the receiving stage, not to sales.
- **No verbal commitment lives outside the documented record** — any side-letter, named verbal commitment, or out-of-contract understanding is captured in writing in the final-terms confirmation or the handoff package.
- **Win factors captured** — the `## Win Factors` section names 2-4 things that materially advanced the deal, while context is still fresh.

## Common failure modes to look for

- A signed contract where a pricing or term detail drifts from the negotiated terms record — never flagged before signature.
- A handoff package with a contact list but no relationship history, personal-stake mapping, or engagement preferences.
- A verbal commitment made during sales (special escalation path, named integration commitment, reference participation) that doesn't appear anywhere in the documented terms.
- Implied expectations from the proposal narrative (the ROI math the prospect saw, named outcome metrics) that aren't captured for the post-sale team.
- Adoption-risk or stakeholder-risk patterns visible from sales context that aren't named in the post-close risk section.
- A handoff packet that schedules implementation kickoff itself — wrong stage; this lens flags scope-creep into the receiving stage.
- A missing `## Win Factors` section, or one filled with vague claims ("good relationship," "strong fit") rather than specific moments and moves.
- A PO field marked "to be issued" at the time of handoff without a named owner and target date for resolution.
