Forecasting and scenarios
By the time the forecast is finished, the month it was built for is over. And running a scenario means copying the file and repairing half the links.
9 of 55
buyer companies named forecasting too slow to be useful, the fourth most common pain we heard.
Source: 55 buyer companies quoted in MCC sales conversations, 2026.
If you forecast rarely, or only at a high level with no real need for scenarios, this is a lighter fit. The budget may be the better place to start.
Growth and board or investor demand both create pressure to answer "what if" faster than a manual model can. Board, PE or investor reporting demand was the trigger for 6 of 55 buyer companies, and it rarely arrives with more time to build the model.
| The old way | The new way |
|---|---|
| The forecast gets rebuilt every month and is stale by the time it's finished. | A rolling forecast that takes new actuals and rolls forward without a rebuild. |
| Running a scenario means copying the file and breaking half the links. | Base, upside and downside cases on the same drivers, side by side. |
| Variance analysis is a weekend with two spreadsheets open. | Actual against budget, forecast and prior year, whenever you need it. |
From a CEO who used to dread the board meeting:
Forecasts hit consistently, with more confidence in front of the board
“As the CEO of Perkville, I've had a great experience working with MCC. They understand our business and have helped us achieve a strong forecast, boosting my confidence with the board. Thanks to MCC team, we now hit our forecasts consistently, enhancing our board meetings and overall performance.”
Sunil Saha
CEO, Perkville
NetSuite and the warehouse system in one consolidated model
“MCC connected NetSuite and the warehouse system into one consolidated data model, eliminating manual consolidation and saving time. Their templates enabled accurate seasonality planning and trailing 12-month analysis, making budgeting more reliable. Highly recommended.”
Mark Garcia
CFO, Arctic Cold
A budget is set once a year and becomes the target. A rolling forecast is updated regularly, usually monthly or quarterly, and always looks the same distance ahead, such as the next 12 or 18 months. The budget says where you planned to be. The rolling forecast says where you're actually heading.
Most companies do. The budget sets targets, bonuses and the plan the board approved. The rolling forecast shows where you're heading against it. Some companies drop the budget entirely, but for most finance teams the useful move is keeping both, built on the same drivers so they're easy to compare.
Usually three: a base case you expect, an upside and a downside, each driven by the few assumptions that actually move the business, like volume, price, hiring pace or churn. More scenarios than that tend to go unused. What matters is that switching between them takes minutes, not a rebuilt file.
Instead of forecasting every line of the profit and loss directly, you forecast the handful of business drivers behind it, such as units, price, headcount and hiring dates, and let the financials calculate from them. Change a driver and revenue, cost and cash update together, which is what makes scenarios quick to run.
Keep actuals, budget, forecast and prior year in the same model, on the same chart of accounts and dimensions. Then variance reports are views, not projects: they refresh when actuals load. The time goes into explaining the variances, which is the part the board actually wants to hear.
Last updated
Drivers and scenarios get built during tailoring, on top of a foundation that already holds your actuals. The forecast is only as current as the actuals feeding it, which is why the foundation comes first.
Not ready to talk yet? Save this page for later, or send it to your CFO. One email, not a newsletter you didn't ask for.
