Weighed, Not Predicted
The video explains how Anthropic's Forecast skill multiplies each deal's amount by a default stage probability and adds the results. It shows why the output measures pipeline size and confidence, not which deals will actually close.
A common assumption is that an AI forecast skill predicts which sales deals will close. The video argues that it does not: the Forecast skill weighs deals by probability, which is a different thing. It walks through the mechanism with one example deal and shows what the resulting number can and cannot tell you.
How a pipeline becomes one number
Forecast turns a pipeline into a single figure. You give it your deals, each with a name, an amount, a stage and a close date, along with your quota. Each stage carries a default probability, with negotiation at 80% and discovery at 20%, for example. The skill multiplies each deal's amount by its stage's probability and adds up the results. That sum is the weighted forecast.
One deal, weighed
The video anchors the idea with a single deal: Acme Corp, $50,000, in negotiation, closing January 31st. At 80%, it adds $40,000 to the weighted forecast. That confidence is high enough for the deal to sit in Commit, the group of deals you would stake your number on. Deals with lower confidence go into a separate group called Upside. Acme Corp is described as the skill's own illustrative sample rather than a real customer.
The one flag: your own data
The default stage probabilities are generic. The video flags that if you connect a CRM, those defaults stop being used. The skill then pulls your pipeline automatically, applies your team's actual historical win rates in place of the generic table, and tracks how the forecast moves over time. Until that connection exists, every probability in the forecast is a general assumption rather than something learned from your team.
Commit can still slip
Back to Acme Corp: if there is no activity on the deal for 14 days, the skill flags it for a re-engage, even though it sits in Commit. The video's point is that a committed deal is not a closed deal. It is simply the one you would bet on, and that bet can still go wrong.
Low odds can still land
The reverse also holds. A Discovery-stage deal at 20% is not written off, because it can still close. It just is not what you plan around. The video adds that the gap analysis only tells you how far short of quota you are. It never tells you which deals will close that gap.
Key takeaways
- Forecast weighs deals by stage probability; it does not predict which deals will close.
- The weighted forecast is each deal's amount multiplied by its stage probability, added together.
- A $50,000 deal in negotiation at 80% adds $40,000 to the forecast.
- Commit holds deals you would stake your number on; lower-confidence deals go to Upside.
- Default probabilities are generic until a CRM supplies your team's historical win rates.
- A Commit deal can go quiet and need a re-engage, and a 20% Discovery deal can still land.
- Gap analysis shows how far short of quota you are, not which deals will close it.
Try it yourself
Paste a prompt into Claude with your own pipeline rather than the video's example. The video suggests describing a few deals with their amounts, stages and close timing, stating your quarterly quota, and asking for a weighted forecast with best, likely and worst cases, split into Commit versus Upside, with anything at risk flagged. Then check what the forecast promises and what it does not.
Chapters
Full transcript(auto-generated, with timestamps)
The naive framing: "does Claude predict which deals close?"
[0:00]Someone assumed the forecast skill predicts which deals will actually close. It doesn't, it weighs them. So, does Clod predict which deals close or just weigh the odds?
Pipeline becomes a number
[0:09]Forecast turns your pipeline into one number. You hand it deals name, amount, stage, close date, plus your quota. Each stage carries a default probability. Negotiation 80%, discovery 20. Multiply amount by probability stage by stage and add it up. That sum is the weighted forecast. Take one deal from that
One deal, weighed (the anchor)
[0:27]Pipeline, Acme Corp, $50,000 negotiation, closing January 31st. At 80% it adds 40,000 to the weighted forecast. Confident enough to sit in commit, the deals you'd stake your number on. Lower confidence deals go in a separate pile, upside. One flag,
The one flag: your own data
[0:43]Connect your CRM and those stage probabilities stop being defaults. The skill pulls your pipeline automatically, uses your team's actual historical win rates instead, and tracks how the forecast moves over time. Until then, every probability above is a generic assumption. Back to Acme Corp, no
Commit can still slip
[1:00]Activity in 14 days flags it for a re-engage, even though it's sitting in commit. A committed deal isn't a closed deal, it's just the one you'd bet on, and the bet can still go wrong.
Low odds can still land
[1:11]The other direction holds, too. A discovery stage deal at 20% isn't written off, it can still close, it's just not what you plan around. And the gap analysis only tells you how far short of quota you are. It never tells you which deals will close it. The
Carry-out
[1:25]Forecast weighs probability, not certainty. A stage weighted number tells you how big your pipeline is, never which deals inside it will actually close.
Your turn
[1:34]Your turn, paste this into Clod. Here's my pipeline. Acme Corp, $50,000 in negotiation, closing this month. Tech Start, $25,000 in discovery. My quota is 100,000 this quarter. Give me a weighted forecast, best likely, and worst case, split into commit versus upside, and flag anything at risk. That's the actual test of what a forecast promises and what it doesn't. Weighed, not predicted.
Outro
[1:56]Liam, in for bear.





