The read
What a forecast states
Financial forecasting is the corporate practice of stating where a period ends: revenue, cost, margin, and cash. It runs on a cycle, refreshing as actuals land, and it feeds the plan ahead of replacing it. Its output is a number the business acts on before the period closes.
Financial forecasting methods
The published treatment of this subject is a method inventory, and the top of the search results is a list of techniques. Four appear on almost every list.
Percent of sales
Cost and working-capital lines are expressed as a share of revenue and scale with it. Fast, and it inherits whatever error the revenue line carries.
Moving average
A trailing window smooths noise. It also smooths the turn, so an inflection arrives dampened and late.
Straight-line extension
Last period times a growth rate. The growth rate is where the whole forecast lives, and it is usually a single figure.
Regression on drivers
Revenue is modelled against price, shelf reach, and spend. Stronger and limited to drivers already present in the data.
Every one of the four takes a historical series as its input. The technique chosen changes how the past gets projected and leaves the evidence base untouched.
Financial forecasting models
A forecast model is the structure those methods run inside: driver logic, a scenario set, and a link into the ledger. The mechanics are well solved by software. What the model consumes for the revenue line is a demand assumption, and that assumption is where forecast error concentrates.
Forecasting and risk analysis
Risk analysis asks how wrong the forecast could be. Done properly, it needs a measured sensitivity, meaning how far volume moves when price, pack, or availability moves. Modelled from list-price history, that sensitivity reflects the price points already tried. Measured through the stated response, it covers the ones under consideration.
Financial forecasting software
Planning platforms hold the model, the version history, the workflow, and the audit trail, and they hold them well. The forward-looking consumer signal sits beyond every system such a platform connects to, because it exists only where somebody asks a shopper a question.
What the path read returns
| Output | What it settles | Where it goes wrong |
| Current demand base | What is selling this cycle. | Read from a closed quarter. |
| The turn | Whether choice is changing now. | Detected after the sales file. |
| Switch volume | How many shoppers would move. | Modelled from price distance. |
| Per-market error | Which country drove the miss. | Netted off into a regional average. |
Four inputs behind the path
The path read runs on four collected inputs, refreshed every cycle in every market.
| Input | What it answers |
| Receipts | What consumers bought this cycle, at what price. |
| Store captures | Whether the item was there to be bought. |
| Geo-verified photos | The shelf as it stood, dated and placed. |
| Stated preference | The change that shifts the next purchase, and its shopper count. |
The team's own numbers join separately. Ledger actuals, shipment history, price files, and the forecast model connect through 250+ integrations, so a projection meets recorded consumer choice.
What internal systems omit
Three questions sit outside any ledger, and each one moves the forecast.
- What happens next week. The file records closed transactions and holds zero rows on the next choice.
- Whether the shelf held stock. A volume shortfall reads as weak demand where the item was absent.
- How far a change would move volume. The sensitivity behind every scenario sits with consumers.
Where forecasting hands off
Three shipped pages carry the same verb against different subjects. Demand forecasting states the units a market will absorb. Sales forecasting states what the pipeline closes. Revenue forecasting states the money those closes produce at a given price. Sibling financial planning and analysis holds the cycle, and this forecast refreshes inside it.