{"id":"prod2-sales-renewal-pre-mortem","audience":"sales","category":"decisions","track":"productivity","technique":"format","title":"Pre-mortem a big renewal with dated prevention steps","free":false,"task":"Your largest account, Tallgrass Foods, renews on March 31. Imagine it's April 1 and they didn't renew. Write exactly 4 numbered reasons from the account notes, each as 'Reason: ... | Prevent by: action - date', with every date before March 31. One worry from last quarter is already solved, so leave it out. Plain text, under 160 words.","materialLabel":"Your account notes (attached to your prompt automatically)","material":"Account: Tallgrass Foods - renewal Mar 31 - $186k/year\nAccount owner: me (Sam). CSM: Dana.\n\nNotes since January\n- Jan 9: their champion, Ruth Kim (ops director), is leaving in February. New director not named yet.\n- Jan 15: usage down 22% since November. Mostly the warehouse team stopped logging in.\n- Jan 22: procurement asked for 3 competitor quotes \"as policy\" this year.\n- Jan 30: they still complain about the missing single sign-on (SSO).\n- Feb 3: invoice dispute from December ($4,100 credit) still open with our billing team.\n- Feb 6: SSO shipped to all customers. Tallgrass IT turned it on Feb 7 and said thanks.\n- Feb 10: Dana says the warehouse team never got trained on the new mobile app.\n\nPersonal: Ruth likes golf, sent her a card when she got promoted.\nToday is Feb 12.\n","rules":[{"type":"numberedItems","count":4},{"type":"maxWords","max":160},{"type":"plainText"}],"mistakes":[{"title":"Listing a solved worry","why":"SSO appears in the notes as a complaint, so the AI includes it.","fix":"Add: \"SSO shipped Feb 6 and they turned it on. Leave it out.\"","checks":["r1"]},{"title":"No dates on actions","why":"The AI suggests 'build a relationship with the new director' with no deadline.","fix":"Add: \"Each Prevent by has a date before March 31.\"","checks":["r2"]},{"title":"Generic churn reasons","why":"The AI lists textbook reasons like 'poor ROI' instead of what's in your notes.","fix":"Add: \"Use only the risks in my notes.\"","checks":["r1"]},{"title":"Letting the AI pick the shape","why":"The AI writes a long risk analysis with headings.","fix":"Show it: \"1. Reason: ... | Prevent by: action - date\". Plain text.","checks":["r0","numberedItems","plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting words, so a total word cap usually lands over.","fix":"Cap each line: \"each line under 22 words.\"","checks":["maxWords"]}],"promptHints":[{"label":"Frames it as a pre-mortem","patterns":["pre.?mortem","didn.t renew","april 1"]},{"label":"Shows the line shape","patterns":["prevent by"]},{"label":"Drops the solved risk","patterns":["sso","solved","shipped"]},{"label":"Dates every action","patterns":["before march 31","date"]},{"label":"Caps the length","patterns":["\\d+\\s*words"]}],"hint":"A pre-mortem is only useful if each risk turns into a dated action. Tell the AI the line format, the deadline, and which worry is already handled.","rubricLabels":["Every one of the 4 lines has the form 'Reason: ... | Prevent by: action - date'","The 4 reasons match the open risks in the notes (champion leaving, usage drop or untrained warehouse team, competitor quotes, open invoice dispute), and SSO is not listed as a reason","Every Prevent by date falls between Feb 12 and March 31"]}