Decisions
FP&A: a forecast the board can hold, without killing ops
Finance needs a slower, cleaner number than a warehouse. The mistake is either ignoring the operational forecast or forcing it into a 12-month line that cannot be true. FP&A should consume a reconciled path, plus scenarios, plus an interval.
Updated Aug 26, 2026·8 min read
FP&A is a consumer
Finance needs a slower, cleaner number than a warehouse. The mistake is either ignoring the operational forecast or forcing it into a 12-month line that cannot be true. FP&A should consume a reconciled path, plus scenarios, plus an interval — not maintain a shadow model that always wins the board meeting and loses the quarter.
Guidance is a scenario
The plan is a decision. The statistical path is an estimate. Guidance is often a scenario on top (“we hire 40, we cut a product”). Do not train the model to reproduce last year’s sandbag. Put the plan in as a scenario and show the delta.
- Grain: board wants quarters; ops wants weeks. Reconcile. Do not stretch.
- Revenue, cash, and cost are different nouns. Separate goals.
- Construction cost, commodity, energy price: drivers or sibling forecasts, not a guess.
Boards hate bands and need them
A fake-precise 7.42% growth is how you get a confident miss. p10/p90 in money, with the grain stated, is the adult version. If the band is too wide to plan, that is information: you do not have enough signal, or the horizon is vanity.
Same workspace, different horizon
Keep the operational goal and the FP&A goal in Predict.ai, on the clocks each meeting uses. The analyst explains why the path moved without a packet. Scenarios are how guidance stays honest. You are not asking SageMaker for a board pack. You are asking a prediction OS for the same object ops already serves — rolled up, with a treaty on top.
FAQ
- Should FP&A run its own model?
- They can. They should not silently diverge. If they override, measure FVA. A shadow model that always wins the board meeting and loses the quarter is expensive.
- How do I present uncertainty upstairs?
- p10/p90 as a range around the plan, in money, with the grain stated. A fake-precise 7.42% growth is how you get a confident miss.
Keep going
Guide
Revenue forecasting
Revenue is not one series. Bookings, billings, recognized revenue, and pipeline coverage all have different clocks. SaaS, usage, and store sales only look alike in a board deck. Pick the definition the decision uses, then forecast that.
Guide
S&OP and the forecast
Sales and operations planning wants a number the company can staff, buy, and book against. It fails when each function brings a private forecast. The work is not a prettier chart. It is one grain, one horizon per decision, and a cadence that matches the meeting.
Guide
Hierarchical forecasting
You rarely forecast one series. You forecast stores that must sum to a region, and SKUs that must sum to a brand. Hierarchical forecasting predicts at more than one grain and reconciles so finance and ops are not holding two official numbers.
Use case
Revenue forecasting
Maintain a current revenue outlook grounded in bookings, pipeline, usage, renewals, pricing, and seasonality.
Use case
Cash-flow forecasting
Project cash receipts, payments, and liquidity with ranges that reflect timing uncertainty.