Verified against ChatGPT · 2026-08-10
Turn a raw pipeline export into forecast commentary a CRO would actually trust
Writes the plain-language narrative that accompanies a forecast number — what changed since last week, what's driving upside or downside risk, and what's still uncertain — instead of restating the spreadsheet in prose.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Write the forecast commentary that goes alongside this week's number to the CRO — the narrative explaining what changed and why, not a restatement of the spreadsheet in sentence form. THIS WEEK'S FORECAST NUMBER AND CATEGORY BREAKDOWN $1.42M total: Commit $780K, Best Case $410K, Pipeline $230K. WHAT CHANGED SINCE LAST WEEK Commit is up $120K from last week; one $95K deal slipped from Commit to Best Case. DEALS DRIVING THE MOVEMENT Acme Corp, $95K, slipped to Best Case because legal review is taking longer than expected; Beacon Retail, $180K, moved into Commit after verbal approval from their CFO. COMMIT LEVEL YOU'RE ACCOUNTABLE FOR I'm accountable for the $780K Commit number holding without slippage. WHAT NOT TO DO Do not restate the number and category totals in prose — the CRO already has the spreadsheet in front of them; the commentary's only job is to explain movement and risk that the numbers alone don't show. Do not use hedge words like 'should' or 'hopefully' about a specific deal without naming the specific condition that hedge depends on — 'should close' is not commentary, 'closes if procurement returns the redline by Friday, which is the one open item' is. Do not present a deal moving in the rep's favor as more certain than the commit level implies; if a deal is only Best Case, don't describe it in language that would be appropriate for Commit. WRITE THE COMMENTARY IN THIS SHAPE Open with one sentence on the headline direction (up, down, flat) versus last week and the single largest driver of that movement. Then, for each deal significant enough to have moved the number meaningfully, state what changed, what has to happen for it to hold at its current commit level, and the date that condition needs to resolve by. Close with the one thing most likely to change next week's number in either direction, and what you're doing about it before the next forecast call.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Forecast commentary fails most often by becoming a prose mirror of the spreadsheet the reader already has open, and the explicit 'what not to do' instruction against restating totals is what breaks GPT-5.1 out of its default summarization behavior, which is to compress the input data back into sentence form when given a structured dataset and asked to 'write commentary' without a sharper constraint. Requiring every hedge word to be paired with the specific condition it depends on closes a subtler failure mode: without that rule, a model asked to sound appropriately cautious will often generate generic hedges ('this deal should close soon') that read as commentary but carry zero new information a CRO could act on — tying the hedge to a named condition and a date converts vague caution into something the reader can actually follow up on. The instruction not to describe a Best Case deal in Commit-level language matters because sales forecasting has a well-known bias where reps and even AI-generated summaries drift optimistic language onto uncertain deals simply because positive framing reads better in a narrative — explicitly anchoring the language register to the deal's actual commit category prevents the commentary from quietly inflating confidence beyond what the categorization already represents. Ending on a single largest swing risk, rather than a list, mirrors how an actual forecast call works: leadership has time for one clear risk and one action, not an exhaustive risk register.
What you get back
Forecast is up $120K week-over-week, driven primarily by Beacon Retail moving into Commit after verbal CFO approval. Acme Corp ($95K) slipped from Commit to Best Case — legal review is the open item, and it needs to clear by Thursday to have any chance of closing this month. Biggest swing risk next week: if Acme's legal review slips past Thursday, expect it to move to next quarter's pipeline rather than staying in this month's Best Case.
Verified against
ChatGPT GPT-5.1 · 2026-08-10
Changelog
- 2026-08-10 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
