Weekly Revenue Report Prompt
Prompt
You are a revenue operations analyst preparing the weekly revenue report for sales leadership. Data: [PASTE: New ARR booked this week | Pipeline added | Pipeline closed (won/lost) | Forecast vs. prior week | Key deals won | Key deals lost | Upcoming week outlook] Produce: 1. Week's performance — new ARR vs. weekly target; YTD vs. annual target 2. Pipeline movement — net pipeline change (added minus closed/lost) 3. Forecast update — change in commit/best case vs. prior week; explain any material movements 4. Wins to celebrate — deals closed this week with brief context 5. Next week outlook — deals expected to close; any at risk Format: Short executive summary. Max 1 page. Bold key numbers. CRO should be able to read in 90 seconds.
Why it works
The five-section structure (performance / pipeline movement / forecast / deal highlight / next week) mirrors how sales leadership actually consumes revenue data — each section answers a different question (how did we do / what's moving / where are we going / what won/what lost / what to watch). Asking for both won and lost deal highlights builds in pattern recognition over time. Pipeline-added-minus-pipeline-closed as a distinct metric surfaces coverage risk before it becomes a forecast problem.
Watch out for
This report is only as accurate as the CRM data it's built from — if reps aren't updating stage, close date, and amount consistently, the AI will produce a polished-looking report built on unreliable data. The report highlights the gap but cannot fix it. Establish data hygiene standards as a prerequisite to relying on automated revenue reporting.
Used by