Every finance team produces reports. Good FP&A teams change outcomes.
FP&A exists to help the business improve its financial performance. That is it. Not to produce budgets, not to produce analysis, not to write board decks. Those outputs have no value in isolation. They only matter if they change decisions, align effort, or surface problems early enough to act on them.
That distinction sounds obvious. It rarely is in practice. Most FP&A functions justify themselves through activity — the number of models built, the thoroughness of variance commentary, the sophistication of the forecast. None of that is the measure. The measure is whether the business performs better because finance is in the room.
Core Processes
The FP&A cycle runs on five core processes. They are not independent. Each one feeds the next, and most failures in FP&A happen at the handoff between them.
Sets the strategic direction and long-term financial ambition. Year 1 of the LRP becomes the foundation for the annual budget. The purpose is strategic alignment, not precision.
The performance contract for the year. It sets targets, drives accountability, and aligns the organisation behind shared financial goals. A weak budget creates a weak year.
The truth of what happened. Actuals versus budget. The quality of management accounts determines whether performance reviews are grounded in reality or spend their time disputing the numbers.
The conversation between finance and the business. Not a readout of what happened, but a structured discussion about what to do next. This is where FP&A either earns its seat or becomes a reporting function.
An updated view of the full-year outlook. Not a revision of the contract — the budget holds. The reforecast tells you how the year is likely to end and surfaces where course correction is possible.
Where FP&A Fails
Most FP&A failures happen at the interlock points — where one process hands off to the next. The budget that inherits an unresolved gap from the LRP. The management accounts that can't support a clean variance discussion. The performance review that surfaces a problem two months too late.
Beyond the handoffs, the most common structural failures are:
Finance runs the FP&A processes instead of the business. Budget cycles, forecast updates, and performance reviews should be business processes facilitated by finance — not finance exercises that happen to involve the business. When finance owns the outputs without business ownership, the insights stay in the deck and nothing changes.
Wrong level of detail. Too granular and finance spends its time defending P&L lines rather than discussing what matters. Too high-level and the numbers lack credibility. Getting this right for each part of the cycle is harder than it sounds and depends heavily on the business context.
No exec buy-in. FP&A without a direct connection to the CEO and CFO's priorities is overhead. If the outputs of the cycle don't feed the decisions being made at the top, the function is performing for itself.
Better at cost than revenue. Finance teams typically know the cost model in detail and treat revenue as an input controlled by sales. The best FP&A teams understand the revenue model — including the conversion funnel, the unit economics, and the drivers of retention — better than anyone else in the building.
Disconnected from incentives. The real power of FP&A is connecting strategic goals to individual performance targets. If the FP&A cycle doesn't inform how people are measured and paid, it will never fully drive behaviour.
The 80/20 of FP&A
Good financial modelling is necessary but insufficient. By most estimates it contributes around 20% of what's needed for FP&A to work. The other 80% is people: building trust with business leaders, translating numbers into decisions, and maintaining the credibility to be heard when something is going wrong.
That is not a soft observation. It is the hard reality of why technically capable finance teams consistently underdeliver. The numbers are never the hard part. Getting the organisation to act on them is.