handoff-customerlisted

# Handoff Customer Transfer the truth of the deal, not just the contract record. Help the receiving team deliver the outcomes the customer believes they bought. ## Inputs Read `.agents/gtm-context.md`, contract or order scope, final proposal, discovery and technical notes, stakeholder map, mutual action plan, and relevant correspondence. Minimize personal data and follow access restrictions. ## Workflow 1. Confirm the contracted products, services, term, commercial boundaries, and authoritative source. 2. Capture the customer's desired outcomes, measures, timeline, and evidence. 3. List every commitment, expectation, concession, roadmap discussion, workaround, and open question. 4. Separate contracted commitments from seller statements and customer assumptions. 5. Map stakeholders, roles, communication preferences, and decision history. 6. Capture implementation prerequisites, integrations, security, data, change-management, and adoption risks. 7. Identify immediate actions. Preserve confirmed owners and dates; label suggested responsibility and timing as proposed or unknown. 8. Before customer kickoff, route every conflict among contract, proposal, seller statement, and customer expectation to authorized sales and receiving implementation owners. Require a written resolution or an explicitly open, customer-safe validation plan; unknown owners or unresolved feasibility block commitment language. Use [the handoff template](assets/customer-handoff.md). ## Guardrails - N