{"id":"revops-win-loss-themes-exec-summary","audience":"executives","category":"sales-work","technique":"verification","track":"sales","level":"advanced","title":"Summarize win-loss themes for a CEO without claiming causes","free":false,"task":"Write a summary for the CEO in plain text with exactly three labeled lines: Top reason named, Second reason named, Caution. Each reason line must include the count out of 20 interviews (like \"7 of 20\"), and say \"mentioned\" not \"caused\". The Caution line states one limit of the data in the notes. Under 100 words. Do not recommend any action.","materialLabel":"Win-loss interview tally (attached to your prompt automatically)","material":"Win-loss program, Q3 2026. Interviews completed: 20 lost-deal buyers (out of 46 lost deals; 26 declined or didn't respond).\n\nReasons buyers mentioned (buyers could name more than one):\n- Price too high: 7\n- Missing integration with their accounting system: 9\n- Onboarding time too long: 5\n- Preferred competitor's brand: 3\n- Support concerns: 2\n- Other / not specified: 4\n\nBuyer notes:\n- 6 of the 9 integration mentions came from one segment, manufacturers.\n- The 26 buyers who did not respond skew toward smaller deals (under $20K).\n- Sales reps believed price was the top reason in 31 of the 46 deals (rep-entered loss reasons in CRM).\n\nProduct note: The accounting integration is on the roadmap with no committed date.\nInterviewer: Hassan from RevOps.","rules":[{"type":"plainText"},{"type":"maxWords","max":100}],"mistakes":[{"title":"Claiming causes","why":"The AI writes \"we lost because of the integration\".","fix":"Add: \"Say mentioned, not caused.\"","checks":["r1"]},{"title":"Using the rep CRM beliefs","why":"The AI mixes in the 31 of 46 rep-entered price figure.","fix":"Add: \"Use only the interview tally.\"","checks":["r2"]},{"title":"Recommending actions","why":"The AI suggests building the integration.","fix":"Add: \"Do not recommend any action.\"","checks":["r2"]},{"title":"No caveat","why":"The AI presents the sample as representative.","fix":"Add: \"Caution states one limit of the data.\"","checks":["r0","plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and runs long when you only give a total.","fix":"Cap each part, like \"each line under 15 words,\" so the total lands well under the limit.","checks":["maxWords"]}],"promptHints":[{"label":"Lists the three labels","patterns":["top reason","second reason","caution"]},{"label":"Asks for counts","patterns":["of 20","count"]},{"label":"Bans causal wording","patterns":["mentioned","not caused","caus"]},{"label":"Bans recommendations","patterns":["no recommend","don.t recommend","no action"]},{"label":"Limits length","patterns":["\\d+\\s*words","under \\d+"]}],"hint":"Name the three lines, require counts and careful wording, and forbid recommendations.","rubricLabels":["Has exactly three lines starting with Top reason named:, Second reason named: and Caution: in that order","Top reason is the accounting integration (9 of 20) and second is price (7 of 20), using the word mentioned and not the word caused","Caution states one data limit (only 20 of 46 lost deals interviewed, non-responders skew small, or the segment skew), and the summary does not recommend an action or cite the reps' 31-of-46 price belief as an interview result"]}