{"id":"sales-win-loss-note-for-vp","audience":"sales","category":"sales-work","technique":"verification","track":"sales","level":"beginner","title":"Write a loss note for your VP based on what the buyer said","free":false,"task":"Your VP of Sales, Teresa Gomez, wants a short note on why you lost Wexley Insurance. The rep's CRM note blames price, but the buyer's email says otherwise; go with the buyer. In at most 4 sentences, plain text, start with \"Teresa,\", give the real loss reason, and end with one change the team could make. Don't quote the buyer word for word.","materialLabel":"The CRM note and buyer email (attached to your prompt automatically)","material":"CRM CLOSE NOTE (rep: Kyle Benz), Nov 4: \"Closed lost. Lost on price, Covara was cheaper. Nothing we could do.\"\n\nEMAIL from buyer, Maya Ross (Claims Ops Director, Wexley Insurance), Nov 5:\n\"Hi Kyle, thanks for all the time. Honestly price wasn't the deciding factor, your quote was within $3k of Covara's and inside our budget. What tipped it was go-live timing. We need to be live before our March renewal season. Covara committed to 6 weeks and your team said 12-14 weeks for implementation. We also liked that Covara assigned a named implementation manager from day one. Happy to stay in touch for next year.\"\n\nDeal facts: $84k ARR, 7-month sales cycle, 2 demos, 1 security review passed.\nInternal: our implementation backlog is 9 weeks right now (per Onboarding lead, Nov 1).","rules":[{"type":"maxSentences","max":4},{"type":"plainText"}],"mistakes":[{"title":"Trusting the CRM note","why":"The AI repeats the rep's \"lost on price\" because it's labeled as the close reason.","fix":"Add: \"The buyer's email is the source of truth. Use the reason she gives.\"","checks":["r1"]},{"title":"A report instead of a note","why":"The AI writes headings, deal stats and bullets for a VP who wants four sentences.","fix":"Add: \"At most 4 sentences, plain text.\"","checks":["maxSentences","plainText"]},{"title":"No takeaway","why":"The AI explains the loss but doesn't say what to change.","fix":"Add: \"End with one change the team could make.\"","checks":["r2"]},{"title":"Wrong opener","why":"The AI starts with a subject line or \"Hi Teresa, I hope you're well.\"","fix":"Add: \"Start with: Teresa,\"","checks":["r0"]}],"promptHints":[{"label":"Names the reader","patterns":["teresa","vp"]},{"label":"Picks the source","patterns":["buyer'?s email","source of truth","not (the )?price","maya"]},{"label":"Asks for a change","patterns":["one change","recommend","lesson","end with"]},{"label":"Sets the length","patterns":["\\d+\\s*sentences","short"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]}],"hint":"When two sources disagree, tell the AI which one to trust. Then say who reads it, how long it is and how it should end.","rubricLabels":["Starts with \"Teresa,\"","Gives go-live or implementation timing (12-14 weeks vs Covara's 6) as the main loss reason, and does not say price was the main reason","Ends with one concrete change the team could make (for example faster implementation options or naming an implementation manager early)"]}