Write a closed-won handoff from sales to customer success
A complete handoff document so the customer success or implementation team starts with everything the buyer was told and expects.
The prompt
Help me write a handoff from sales to customer success for a newly closed deal.
Customer and deal: [company, products, contract value, term, start date]
Why they bought: [the problem, business goals, metrics they expect to improve]
Success criteria agreed with the buyer: [what they'll judge us on, and by when]
Stakeholders: [names or roles: executive sponsor, champion, day-to-day users, IT, detractors]
What was promised: [timelines, integrations, features, support levels, custom terms, roadmap items mentioned]
Risks and sensitivities: [competitor displaced, budget pressure, internal skeptics, tight deadlines]
Sales notes or call summaries: [PASTE]
Write a handoff document with:
1. One-paragraph summary: who they are, why they bought, and what success looks like.
2. Stakeholder map with role, influence, and what each cares about.
3. Commitments made during the sale, quoted where possible. Flag anything non-standard or not in the contract as [CONFIRM WITH CONTRACT].
4. Success criteria and the first 90-day milestones.
5. Risks with suggested mitigation.
6. Expansion potential noted during the sale (for later, not to push now).
7. Open questions for the kickoff call.
Also give me:
- A short introduction email from the AE to the customer bringing in the CS lead.
- An agenda for the internal handoff meeting (20 minutes).
Use only what I provide; do not invent commitments or contacts.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- company, products, contract value, term, start date
- the problem, business goals, metrics they expect to improve
- what they'll judge us on, and by when
- PASTE
- CONFIRM WITH CONTRACT
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a procurement category strategyA sourcing plan for a spend category: market, needs, options, and roadmap.
- Price and document a change order before doing extra workA change order with cost breakdown, schedule impact, and justification that the owner or GC can approve quickly.
- Write a clean SDR-to-AE handoff for a booked meetingA concise handoff note that gives the account executive context, qualification, and what the prospect expects.
- Write a project closure reportFormally closes a project: results vs. objectives, handover, open items, and lessons.