As of 13 August 2026, AI can only partly create your weekly pipeline report.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, chat-fluent skill, and roughly 30 minutes until you can act on the result.

   How to actually do it

   1. Open your CRM and export the opportunities for the reporting period, including deal name, account, owner, stage, value, probability, close date, created date, last activity date and next step.
   2. Gather the previous week’s report, relevant call notes and your team’s definitions for qualified, at-risk, commit, closed won and closed lost.
   3. Remove records and notes that the report audience should not see, then paste the remaining data into the prompt with the reporting dates, currency and audience filled in.
   4. Ask the chatbot to produce the report and to separate recorded CRM facts from interpretations, unknowns and needs-checking items.
   5. Compare every deal count, stage total, value, close date and movement in the draft against the current CRM export, correcting any mismatch before circulation.
   6. Check each risk, forecast comment and proposed action against the source notes and ask the relevant deal owner to confirm anything labelled unknown or needs checking.
   7. Paste the corrected report into your team’s normal document or sales channel and send it only after adding any management judgement that the source data cannot establish.

   Prompt

   Create a weekly sales pipeline report from the data and notes below.
   
   Reporting period: [START DATE] to [END DATE]
   Audience: [SALES MANAGER, LEADERSHIP TEAM, OR OTHER]
   Currency: [CURRENCY]
   Pipeline definitions:
   - Qualified opportunity: [DEFINITION]
   - At-risk deal: [DEFINITION]
   - Commit: [DEFINITION]
   - Closed won: [DEFINITION]
   - Closed lost: [DEFINITION]
   
   Use only the supplied information. Do not invent values, dates, probabilities, reasons, customer statements or next steps. If a field is missing or contradictory, label it "unknown" or "needs checking" and list the issue separately.
   
   Produce:
   1. An executive summary of the main changes this week.
   2. Pipeline totals by stage, including deal count and value, with the reporting currency shown.
   3. Deals added, moved forward, moved backwards, closed won and closed lost during the period.
   4. Deals with no recorded next step, overdue next action or an unusually long time in stage, using only the supplied rules and dates.
   5. A table of material risks, with the deal, evidence from the source data, likely impact and the specific fact that needs checking.
   6. A forecast section separating recorded facts from judgement. Do not recalculate probabilities unless I provide the rule.
   7. A prioritised action list for next week, assigning an owner only where one is stated in the source data.
   8. A short data-quality section listing duplicates, missing fields, inconsistent stages, stale dates and any totals that do not reconcile.
   
   For every numerical total, show the calculation or source rows used. Keep the tone factual and concise. End with five questions I should answer before sending the report.
   
   Source data and notes:
   [PASTE CRM EXPORT, CALL NOTES, PREVIOUS REPORT AND PIPELINE RULES HERE]

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.