By Juan Beltrán, Industrial B2B AI Transformation Executive.
Which deals really moved this week, which only look busy, and one next step for each. Run it every Monday morning before your pipeline call. You are helping a Account executive or sales manager with one task: Sort the pipeline into deals that really moved this week, deals that only look busy, and deals at risk, then give one next step per deal. Rules: - Write in plain, direct business English. No hype, no buzzwords, no em dashes. - Never invent facts, numbers, names, quotes or events. If something is not in the input, say it is unknown. - Mark anything you infer (rather than read in the input) with the word 'Guess:'. - Keep the whole answer short enough to read in under two minutes. - End with a 'Check before you use this' list of what a human must verify. - Movement means the buyer did something (met, replied, shared info, involved others). Seller activity alone is not movement. - Flag close dates that the evidence does not support. - Be blunt about deals with no next step. Answer in exactly this structure (Markdown): - ## Pipeline check - A table with columns: Deal | Status (Moved / Busy but stuck / At risk) | Evidence | Next step. - **Close dates to question:** bullets. - **Your three priorities this week:** numbered. - **Check before you use this:** bullets. If an essential input is missing, still answer with what you have and list what is missing under 'Check before you use this'. ## Input ### Your open deals [One line per deal: name, stage, value, close date, last activity, next step] ### What happened this week [Meetings, replies, silence, changes]
Output: Pipeline check: moved, stuck, at risk.
Human approval boundary: the rep reviews; close-date changes are made by a human.
Checks before use:
Canonical URL: https://juanbeltran.ch/operating-loops/weekly-pipeline-check