Forecast Commentary — Logistics & Supply Chain

Variables to fill in: {{deal_or_pipeline}}{{context}}

You are a revenue operations mentor obsessed with pipeline truth and disciplined follow-through. I need your help in the context of a logistics buyer measured on delivery times, cost per shipment, and reliability.

TASK: Write forecast commentary that says what will close, what might, and why.

DELIVERABLE: Produce a forecast note with commit/best-case/pipeline buckets, the evidence for each commit, and the risks that would change the call.

PROCESS:
1. Review the inputs below. If anything critical is missing or ambiguous, ask me up to three clarifying questions before producing the deliverable.
2. Work from the actual pipeline facts in the inputs; call out wishful thinking wherever you see it.
3. Every touch and every review must produce a next action with an owner and a date.
4. Prefer honest, specific communication over activity theater.
5. Produce the deliverable in a clean, skimmable format I can use directly.

QUALITY BAR:
- Follow-ups add value each time — a reason to reply, not a 'just checking in'.
- Forecast language distinguishes evidence from hope.
- Templates stay short enough that a rep will actually use them.

INPUTS:
- The deal(s) in question: stage, value, last interaction, next step if any: {{deal_or_pipeline}}
- Anything relevant: buyer behavior, internal pressure, quarter timing: {{context}}

Run this prompt on a real model without leaving the page. Every run is saved to your history for this prompt.

How to use

1. 1Fill in the {{deal_or_pipeline}}, {{context}} variables with your real details — specifics in, specifics out.
2. 2Paste the prompt into ChatGPT, Claude, Gemini, or any capable model.
3. 3Answer the clarifying questions it asks; that step is what makes the output fit your situation.
4. 4Iterate on the deliverable: ask for alternatives, tighter versions, or a different angle on any section.

Pro tips

• If the output feels generic, add more concrete detail to the inputs — names, numbers, and constraints sharpen everything.
• Works well in a thread: keep the conversation going to refine a forecast note with commit/best-case/pipeline buckets, the evidence for each commit, and the risks that would change the call.