Prompt library
Write sales-to-success handoff notes
The volunteered-versus-suggested split on success criteria identifies the promises the renewal actually rides on, and the promise ledger with contractual/verbal/implied labels is where churn-causing surprises get caught early. The customer-could-read-it rule keeps candor from sliding into cynicism.
Last reviewed July 17, 2026
The prompt
Write the sales-to-customer-success handoff document from my deal notes.
Deal notes: {{notes}}
Sections:
1. Why they bought: the problem in their words and the outcome they expect by when. This sentence is what CS gets measured against; get it exact.
2. Success criteria: what the buyer said "working" looks like, with any numbers they used. Mark criteria WE suggested versus criteria THEY volunteered; the volunteered ones are the real contract.
3. The people: economic buyer, champion, skeptic, and day-to-day users, with each one's stake and communication style observed during the cycle.
4. Promises made: every commitment from the sales cycle (features, timelines, support levels, pricing exceptions), each marked contractual / verbal / implied. Implied promises churn accounts; surface them now.
5. Landmines: objections raised and how they were resolved, competitors still lurking, internal politics observed.
6. The first 30 days: what onboarding must nail given all of the above, and the one thing that would make them feel buyer's remorse.
Rule: nothing in this document may surprise the customer if they read it. It is candid, not cynical.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{notes}} | Your CRM notes, call summaries, email threads | [paste the deal's notes and key emails] |