Skip to main content
The forecast call asks reps to defend a number they submitted three days ago. The defence is a narrative, the narrative is unfalsifiable in the room, and the meeting ends with the same number and slightly more confidence in it. Forecast review does the checking beforehand. Which deals moved category and why, and for everything sitting in commit, whether the record actually supports it being there.

​
Data Sources

Starter (required only): forecast category changes since the last call, and what the calls say about each deal in commit. Full (required + recommended): the same, plus engagement between calls. Commit deals where the customer has not replied in two weeks are the ones that miss, and that signal only exists in email. See the Context Graph for how each source feeds the review.

​
Choose your path

​
Build in Clearskies

Build the workflow once and the forecast is checked before the call rather than during it.

​
The Workflow

In the Clearskies app, open the workflow builder and describe what you want in plain language:
The app configures the schedule, the deals in scope, and the destination. Scheduled workflows have no meeting context, so the deals come from a record lookup rather than a calendar. Forecast category is a CRM field, so what the workflow can check depends on what your CRM tracks. If category lives in a custom field, point the lookup at that field by name. Run it a day before the forecast call. The point is that reps see the same read leadership sees and can answer it before the meeting, rather than being surprised in it.

​
Deploy to Slack

Once published, the channel gets the read before the call:

​
Customize the rollout

  • Set the cadence to land ahead of your forecast call
  • Choose the scope: whole company, one segment, one team, one rep’s book
  • Define what “supported” means for you: your own criteria for a commit deal, checked against evidence
  • Route it to a leadership channel, or to each manager’s DM with only their team
  • Chain it with pipeline review so the movement read and the forecast read arrive together

​
Build in Claude or ChatGPT

The stronger path for the deal-by-deal version, because pressure-testing a forecast is a conversation. You read the answer, push on one deal, and ask again.

​
The Prompt

Open Claude or ChatGPT with the Clearskies MCP connected and paste this (or modify to your needs).
Then push on the weakest one: Walk me through Vantage. What would have to be true for that close date to hold?

​
Make it yours

  • Add Only [rep]'s deals before a manager’s forecast conversation.
  • Add Compare the commit deals to the deals we lost last quarter after they reached commit to check the pattern against your own history.
  • Add Which best-case deals have stronger evidence than my weakest commit deals to find the category assignments that are backwards.

​
The Skill (Claude)

Two skills in the Clearskies plugin for Claude do the deal-level work behind a forecast read. clearskies:deal-review audits a single deal against its risk signals: champion engagement, economic buyer status, unanswered communications, close-date health, deal velocity. Run it on any commit deal you doubt. clearskies:deal-strategy goes further on a deal that is stuck, including whether to push the date or qualify out, which is often the real decision behind a forecast conversation.
Want this packaged for your team? Reach out and we’ll help you customize the skill to your workflow.

​
The Plugin

Ready to make this part of your team’s workflow? We’ll set up the Clearskies plugin with you. Clearskies workflows, Claude skills, all tailored to how your team works. Book 15 minutes →

​
Next steps

  1. Sign in to Clearskies
  2. Connect your data sources
  3. Get your Clearskies MCP server and try with Claude or ChatGPT