Continuous forecast rebuilt on evidence (L6)
The weekly forecast ritual is replaced with a continuously updated forecast that combines rep commit, model output, and conversation evidence, with variance attributed to a cause every month.
The steps
- 01
Publish three numbers, not one
Tool: Salesforce
Rep commit, model forecast, and evidence adjusted view, shown side by side with the gap. Blending them into one number hides the disagreement that carries the information. Owner: RevOps lead. DoD: three number view live for leadership.
- 02
Attribute variance monthly
Tool: Snowflake
Every month, attribute the miss or beat to specific causes: slipped deals, pricing changes, sourcing shortfall, or model error. Unattributed variance repeats. Pitfall: narrative attribution with no data behind it. DoD: monthly attribution with data references.
- 03
Score forecasters, not just forecasts
Tool: Manual
Track accuracy by manager over time. Persistent optimism is coachable once it is visible and unarguable. Owner: sales leadership. DoD: rolling accuracy by manager published.
- 04
Retire the ritual meeting
Tool: Gong
When the continuous view is trusted, the weekly call becomes a risk conversation on the largest gaps only. If the meeting stays the same length, nothing was rebuilt. Owner: sales leadership. DoD: forecast meeting agenda and length formally changed.
Tools in this playbook
- Salesforce
- Snowflake
- Manual
- Gong
Next playbooks
Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.
