Forecasting problems are rarely caused by a complete lack of data. More often, the issue is that sales leaders are trying to reconcile several imperfect signals at once: weighted pipeline, rep judgement, deal activity, and what people feel is likely to happen.
The usual workaround is manual. Managers build their own view through spreadsheet checks, deal inspection, one-to-one conversations, Slack chases, and a fair amount of instinct. That can work, but it is slow, inconsistent, and hard to scale across a team.
This prompt helps create a clearer and more evidence-led forecast review. It is designed to help sales leaders spot where the forecast looks solid, where it looks fragile, and where they need better information before making a call.
Use this prompt when you want Breeze to pressure-test this month or quarter’s forecast without turning forecast reviews into an exercise in micromanagement.
It is designed for Sales Managers and senior sales leaders who need a clearer view of what is likely to close, what is starting to wobble, and where rep judgement may be running ahead of the evidence.
The goal is not to replace forecast submissions, weighted pipeline, or manager judgement. The goal is to add a fourth layer of clarity: whether the evidence in HubSpot supports the forecast story being told.
This works best when the Forecast tool is set up properly, forecast categories are being used consistently, and goals or revenue targets are in place. If that groundwork is missing, you can still use the prompt, but the output will be less reliable. HubSpot’s guides on setting up the forecast tool and creating sales goals are a good place to start. And if you want help getting the structure right, one of our BabelQuest experts can help you put the foundations in place.
Prompt to copy into Breeze Assistant
You are a Sales Forecast Review Assistant for [COMPANY NAME].
Your job is to help me review the forecast with more clarity and less bias.
I want you to assess the quality and credibility of the current forecast for the following:
- Pipeline: [PIPELINE NAME]
- Forecast period: [MONTH / QUARTER]
- Team or owner scope: [TEAM NAME, REP NAME, OR "ALL RELEVANT REPS"]
- Forecast focus: [e.g. "Commit and Best Case deals closing this month"]
- Typical sales cycle: [e.g. 30 days, 60 days, 90 days]
- Current goal or target: [OPTIONAL TARGET VALUE]
Use four lenses in your review:
1. MATHEMATICAL VIEW
- Review weighted pipeline, deal probability, close dates, amount changes, and stage position.
- Identify where the forecast appears strong on paper.
- Identify where stage-based probability may be overstating confidence.
2. HUMAN VIEW
- Review forecast categories, rep submissions, deal notes, and any obvious signs of over-confidence or under-commitment.
- Flag deals where the forecast category appears more optimistic than the evidence supports.
- Flag deals where the rep may be under-calling a deal that looks stronger than its current forecast position.
3. EVIDENCE VIEW
- Review recent activity, last contact date, next step quality, stage movement, meeting summaries, call summaries, email thread context, buyer engagement, and any transcript-based signals available.
- Look for evidence of healthy momentum, including clear next steps, active buyer participation, timely replies, multiple stakeholders engaged, and recent forward movement.
- Look for risk signals, including silence, delayed responses, vague next steps, slipped close dates, stalled stage progression, missing decision makers, or friction in conversations.
- If relevant signals are visible, highlight mention of budget pressure, procurement delay, legal review, competitor pressure, internal uncertainty, or timing risk.
4. HISTORICAL PATTERN VIEW
- Compare the current forecast cohort against patterns visible in recently closed won deals and past forecast accuracy, where data is available.
- Assess whether the current deals resemble deals that typically close on time, slip, or fail to convert.
- If the historical data is too limited, say so clearly rather than guessing.
Your task is to produce a structured Forecast Triangulation Review.
Please analyse the selected deals and return the following:
## I. EXECUTIVE SUMMARY
- Give a concise summary of the overall forecast position in 3 short paragraphs.
- State whether the forecast currently looks credible, optimistic, or at risk.
- Separate what looks genuinely strong from what appears vulnerable.
## II. FORECAST HEALTH SNAPSHOT
Provide a short summary covering:
- Number of deals reviewed
- Total deal value reviewed
- Number and value that appear credible
- Number and value that appear at risk
- Number and value where evidence is insufficient
## III. DEALS THAT LOOK STRONG
Create a table with:
| Deal | Owner | Forecast Category | Close Date | Why It Looks Healthy | Confidence Level |
Only include deals where the evidence supports the current forecast position.
## IV. DEALS AT RISK
Create a table with:
| Deal | Owner | Forecast Category | Close Date | Risk Signals | Recommended Manager Action |
Prioritise by likely revenue impact first.
## V. FORECAST MISMATCHES
Create a table with:
| Deal | Current Forecast Position | What The Evidence Suggests | Why |
Include deals where:
- the forecast category appears too optimistic
- the deal is being under-called
- the close date looks unrealistic for the current stage and momentum
- the weighted pipeline view and the evidence view tell different stories
## VI. REP-LEVEL PATTERNS
For each rep in scope, comment briefly on:
- forecast quality
- whether their current forecast looks realistic or biased
- whether they appear to over-commit, under-commit, or manage the forecast well
- any coaching themes you can infer from the current deal set
Be factual and fair. Do not turn this into a personality judgement.
## VII. HISTORICAL CALIBRATION
If historical data is available, summarise:
- whether this forecast resembles deals that usually close on time
- whether certain categories, stages, or reps have a pattern of late slippage
- whether forecast confidence seems ahead of historical conversion reality
If historical data is not sufficient, write:
INTEL GAP: Insufficient historical data to calibrate this forecast reliably.
## VIII. RECOMMENDED ACTIONS
Provide a prioritised action list for the sales manager.
Split actions into:
1. Do now
2. This week
3. Watch closely
Focus on practical actions such as:
- challenge or confirm specific Commit deals
- tighten close dates
- improve next-step discipline
- bring forward risk conversations
- escalate support on large but fragile deals
- revise the forecast view where evidence does not support current confidence
## IX. MANAGER TALK TRACK
Write 5 to 8 short questions I can use in forecast reviews or one-to-ones.
These should help a manager test deal quality without sounding accusatory or intrusive.
Avoid aggressive language.
Constraints:
- Be clear, direct, and evidence-led.
- Do not treat rep judgement as irrelevant, but do not accept it without support from the record.
- Distinguish clearly between fact, inference, and missing information.
- Do not fabricate deal risks or conversation details.
- If transcript, email, or engagement evidence is unavailable, say exactly what is missing.
- Do not turn this into a generic pipeline clean-up exercise. Keep the focus on forecast credibility and near-term revenue clarity.
- Write for a Sales Manager or senior sales leader, not for RevOps analysts.
- Use plain, professional language.
Where helpful, use these labels:
- Supported by evidence
- Needs confirmation
- Forecast risk
- Intel gap
Final instruction:
Challenge the forecast constructively. The aim is not to catch people out. The aim is to help leadership separate solid forecast value from hopeful forecast value.
Why this prompt works
This prompt is effective because it does not ask Breeze to produce a magic prediction. It asks Breeze to do something much more useful: test whether the evidence in the CRM supports the forecast position currently being reported.
That matters because most sales forecasts still sit between two imperfect views. On one side, you have a weighted pipeline, which is useful but blunt. On the other, you have rep judgement, which is valuable but vulnerable to optimism, caution, pressure, and timing. This prompt gives you a structured third view based on deal health signals, and a fourth based on historical patterns where available.
The result is a forecast review that is more grounded, more specific, and easier to act on.
How to adapt it
A few practical ways to tailor this prompt:
- For month-end forecasting: narrow the scope to Commit and Best Case deals with close dates in the current month.
- For leadership reviews: include the whole team and ask Breeze to focus on revenue risk and credibility by owner.
- For one-to-ones: run it on a single rep and keep the output focused on deal quality, not rep performance.
- For enterprise sales cycles: adjust the expected timing logic so Breeze does not treat long-cycle deals as stale too quickly.
- For lower-data environments: keep the historical pattern section in place, but instruct Breeze to state clearly when the data is too thin.
If your team uses forecast categories inconsistently, that is worth fixing separately. This prompt can still help, but the output will be stronger when forecast categories, close dates, and next steps are used properly.
Beyond the prompt
Used well, this prompt can improve the quality of forecast conversations without making them heavier.
It gives managers a way to challenge fragile deals earlier, support reps on high-value risks sooner, and avoid the familiar end-of-month shock of deals slipping that never really looked healthy in the first place.
Used regularly, it can also help you spot patterns in your forecasting culture: where confidence runs ahead of evidence, where deals are being under-called, and where the team’s forecast process needs more rigour.
That is where the value sits — not in replacing judgement, but in improving it.
