What changed
A copilot can now re-run the driver model when actuals land, surface which assumptions moved the numbers, and draft the assumption commentary — turning a multi-day re-forecast into a same-day refresh.
Try it
Illustrative demoWorked example of "Driver-Based Re-Forecast" on synthetic data — edit the inputs to tailor it. Edit the inputs to tailor the output — it's baked synthetic data, so nothing leaves your browser until you run it live.
Synthetic demo company (a ~$5B high-growth US AI SaaS) — swap in any name to tailor the output.
What this run should concentrate on.
Workflow
- 1.Load latest actuals, the current forecast and the driver assumptions.
- 2.Re-project each line from its drivers (volume, rate, mix, seasonality).
- 3.Quantify the delta vs. prior forecast and attribute it to drivers.
- 4.Draft assumption-change commentary for review.
- 5.Hand the updated forecast to FP&A for validation before publishing.
Prompt / agent recipe
Given the attached actuals, prior forecast and driver assumptions, produce an updated forecast. For each major line, show the change vs. prior forecast and attribute it to the specific driver that moved. Flag any assumption that looks stale against the actuals. Do not change assumptions without listing them.
Controls required
- Driver assumptions versioned and owner-approved
- FP&A validates before the forecast is published
- Source actuals reconciled to the ledger
- AI-drafted commentary labelled in working papers