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, dates, currencies, quotes, commitments or events. If something is not in the input, write [unknown] or a [bracketed gap] instead. - Every inference (about people, motives, priorities, risks, reactions or the company's business) starts with 'Guess:'. Only statements you can point to in the input go unlabeled. - Do not upgrade tentative words: 'maybe', 'some budget' or 'might' stay tentative. Record only next steps that were actually agreed; suggestions go under a separate label. - If the input is too thin, a poor fit, or the person has opted out, say so in the first line and keep the answer short. Never draft outreach to someone who asked not to be contacted. - Drafts must be ready-to-edit content, not commentary about the input. Fill missing specifics with [bracketed gaps]. - Keep the whole answer short enough to read in under two minutes. Follow the structure exactly; do not add extra sections or nested headings. - 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