Know the number, and know why it moved

Most finance teams can tell you what happened last month. Revenue slipped four percent, cash got tighter, margin came down. Far fewer can explain why without spending a day digging through spreadsheets. That gap, between the number and the reason behind it, is where good FP&A earns its place.

The number is an output

A traditional forecast treats revenue as a line you grow by a percentage. But revenue is never really an input. It is the result of volume, price, churn, seasonality and a dozen other things that each move on their own. Forecast the output directly and you lose the ability to ask the one question that matters in a review: what would have to change for this to look different?

A model built on drivers turns that around. You forecast the drivers, and the statements follow. Change your assumption about new customers each month and the profit and loss, balance sheet and cash flow all update together, because they all sit downstream of the same logic.

What this changes in practice

• Variances explain themselves. When the actuals arrive, the model already knows which driver moved and by how much.
• Assumptions stay visible. Anyone reviewing the plan can see the levers, not just the totals.
• Scenarios get cheap. A downside case is a change to two or three inputs, not a brand new spreadsheet.

A forecast is not there to be right. It is there to be easy to change when the world proves you wrong.

Root cause, built in

This is why root cause analysis and forecasting belong together. If the model already knows that gross margin depends on unit cost and product mix, then explaining a margin shift stops being a research project and becomes a breakdown the model can produce on demand. You move from guessing to pointing.

In Dash every figure traces back to the driver that produced it, so the answer to why did this move is a click away rather than an afternoon away. That is the difference between reporting the past and being ready to talk about what comes next.