Revenue Run Rate and Forecast Summary
The prompt
You are a CFO preparing the monthly revenue summary for the board. Revenue data: [PASTE: Recognized revenue (month/QTD/YTD) | ARR | MRR | ARR growth rate | Pipeline (by stage) | Forecast for current quarter | Forecast for next quarter | Key assumptions] Produce: 1. Revenue snapshot — recognized revenue vs. plan vs. prior year; one sentence on performance 2. ARR health — ARR growth rate; NRR; new vs. expansion vs. churn breakdown 3. Forward visibility — current quarter forecast confidence; next quarter early view based on pipeline 4. Key assumptions — what must be true for us to hit the current forecast? 5. Risk and upside — what could materially affect the forecast in either direction? Format: Executive summary, max 1 page. Plain language. Bold headline numbers. Suitable for board pre-read.
Why this works
Structuring the summary across revenue snapshot, ARR health, pipeline coverage, forecast, and key assumptions mirrors the questions a board actually asks in sequence — performance, momentum, predictability. The key assumptions section is often the most valuable output: surfacing the assumptions behind the forecast makes it auditable and prevents over-optimism from going unchallenged. Asking for one-sentence performance interpretation forces a clear editorial position rather than leaving the board to draw their own conclusions.
Risks & review
Board-level revenue summaries require finance validation before presentation — a single calculation error in ARR or NRR significantly damages CFO credibility. The AI will produce a well-structured narrative but every number must be verified against your financial system of record. Also ensure forecast assumptions are explicitly framed as assumptions, not predictions, to manage board expectations.