Verified against ChatGPT · 2026-08-08
Write the sales-to-CS handoff that keeps every promise made during the sale
Structures the account context, commitments, and risk flags a closing rep hands to customer success, so a promise made during the sales cycle does not quietly disappear the moment the account changes hands.
The prompt
Ready to copy — highlighted parts are example details you can swap.
This deal at Thornbury Retail Holdings just closed and I need to hand it off to customer success without any promise or context getting lost in the transition. Deal summary: 18-month contract, mid-tier plan, primary use case is inventory forecasting across 40 stores. Specific promises or commitments made during the sales cycle: promised a dedicated onboarding specialist for the first 60 days and a custom report built for their regional manager view. Key stakeholders and their roles: the VP of Merchandising was the champion and economic buyer; the IT lead was mildly skeptical about data migration but came around after a technical call. Any known risks or red flags from the sales process: the VP mentioned this is their second attempt at a forecasting tool after a failed rollout with a previous vendor two years ago. What success looks like for this account, in their own stated terms: wants to see stockout rate on their top 50 SKUs drop noticeably before their holiday planning cycle starts. WRITE THE HANDOFF BRIEF 1. WHO'S WHO — the VP of Merchandising was the champion and economic buyer; the IT lead was mildly skeptical about data migration but came around after a technical call, each with their actual role in the decision, not just their job title — who was the champion, who was the economic buyer, who was skeptical, who barely showed up to calls but will likely resurface post-sale as a day-to-day user. CS walking in blind to who actually mattered during the sale wastes their first several interactions rebuilding context that already exists. 2. WHAT WAS PROMISED — every specific commitment from promised a dedicated onboarding specialist for the first 60 days and a custom report built for their regional manager view, stated plainly enough that CS could be held to the exact same standard the prospect heard during the sales cycle. If any commitment was informal or made in passing rather than formally documented in the contract, flag it as such rather than letting it blend in with the contractual commitments — an informal promise that CS doesn't know about is the single most common source of a customer's very first complaint post-close, and it's almost always something the sales team said with good intentions that never made it into any document CS actually has access to. 3. WHAT SUCCESS LOOKS LIKE — wants to see stockout rate on their top 50 SKUs drop noticeably before their holiday planning cycle starts in the customer's own words wherever possible, not a rephrased version that drifts toward generic product-success language; if the customer defines success narrowly and specifically, CS needs that exact framing to know what "on track" actually means for this account, not a generic health-score proxy. 4. RISK FLAGS — the VP mentioned this is their second attempt at a forecasting tool after a failed rollout with a previous vendor two years ago, stated directly with enough context that CS understands not just that a risk exists but why it matters and what to watch for — a risk flag with no context attached tends to get treated as boilerplate and skipped over the same way generic disclaimers get skipped. 5. FIRST 30 DAYS — based on everything above, name the single highest-priority thing CS should do or check on in the first month, and the single thing most likely to go wrong if nobody does anything differently from a standard onboarding. CONSTRAINT Write this for someone who was in none of the sales calls and has zero context beyond what's in this document — do not assume any shared context with the sales team that isn't explicitly written out here. HONESTY CHECK If promised a dedicated onboarding specialist for the first 60 days and a custom report built for their regional manager view includes anything that sounds like it may have overstated what the product or team can actually deliver, flag it directly rather than passing it along at face value — a handoff brief that quietly launders an overpromise into an apparently normal commitment sets CS up to fail at something that was never realistic in the first place.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Separating who's who by actual role in the decision, rather than by job title alone, matters because job title tells CS almost nothing about how to prioritize their own early attention — a VP who barely engaged during the sale and an IT lead who quietly did the real evaluation work are both plausible holders of a senior title, and CS treating them identically because their titles look similar wastes the narrow early window where getting the right person's attention matters most. Explicitly flagging informal promises separately from contractual commitments targets what is, in practice, one of the single most common sources of a new customer's first complaint: a sales rep who tells a prospect something true and well-intentioned in the moment — a specific report will get built, a certain specialist will handle onboarding — that never makes it into any document CS actually has visibility into, so the promise simply evaporates from the record the instant the deal closes, and the customer's first interaction with CS becomes explaining a commitment CS has never heard of and has no way to independently verify was ever made. Capturing success criteria in the customer's own specific words, rather than translated into generic product-health language, is what lets CS actually tell the difference between an account that's healthy by a standard usage metric and one that's failing by the actual, narrower bar the customer set for themselves — a customer who defined success as a specific stockout-rate improvement before a specific seasonal deadline is not adequately served by a CS team tracking generic login frequency as their proxy for account health. The instruction to flag anything that sounds like it may have overstated deliverability, rather than passing every sales-cycle claim along at equal face value, protects CS from inheriting a doomed expectation without knowing it — a handoff that treats every promise as equally solid sets CS up to be blindsided by a customer holding them to a commitment the sales team may have made optimistically, and naming that risk at handoff time is meaningfully cheaper than discovering it three months in when the account is already unhappy.
Verified against
ChatGPT GPT-5.1 · 2026-08-08
Claude Sonnet 4.5 · 2026-08-09
Changelog
- 2026-08-09 — Initial publish, verified against ChatGPT (GPT-5.1) and Claude (Sonnet 4.5).
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
