Why Most FP&A Gaps Are Structural
When leadership teams bring us in for planning and analysis, they usually expect us to add capability. More often, the bigger issue is how the underlying data isorganized and how finance connects to the rest of the business.
The conversation tends to start the same way. Leadership has a budget, monthly financials and some form of forecast, but when they try to use them to make a decision, the analysis doesn't go deep enough. They can see that margin moved. They can't see which customers, services or lines of business moved it, or whether it was a pricing issue or a delivery cost issue. The forward view covers the totals and not much underneath them.
The usual assumption is that this is a capability gap, and the answer is an analyst or a planning tool. Capability is often part of it. In most of the organizations we work with, though, the larger gap sits underneath. The general ledger and the reporting built on it were set up to close the books and produce general financial statements. They weren't set up to show how the business actually makes money. Operational data such as jobs, hours, units or customer activity may live in other systems, maintained by other teams, and nothing ties it back to the financials consistently.
The larger gap usually sits underneath the capability.
There is also usually no process holding it together. Finance, operations, and saleseach work from their own numbers and their own definitions. The budget is builtonce and rarely revisited, and when results differ from plan, nobody owns the work of figuring out why.
This is why adding a tool rarely fixes the problem on its own. A planning platform, a dashboard or an AI model will work with whatever structure it is given. If the data isn't organized around what drives the business, and finance isn't connected to operations and sales, the output looks more polished but answers the same surface-level questions.
We spend the early part of most engagements on that structure: mapping transaction-level data to the drivers that matter, agreeing on definitions across teams, and setting up a regular review of plan against actuals with clear ownership.
That structure is also what makes a bottom-up forecast possible: instead of applying a growth rate to last year’s totals, the outlook is built from the drivers themselves, such as customer volume, pricing, staffing and delivery cost.Because each assumption ties back to actuals, a miss can be traced to the specific assumption that caused it.
Accounting still has to come first. The close needs to be accurate and on time, because forward-looking analysis is only as reliable as the record it starts from. FP&A builds on that record. Its job is to explain what drove results and to help leadership decide what to do next.
Once the structure is in place, the change shows up quickly, usually within the first quarter. Clients may use it to reprice work once they can see what each service actually cost to deliver, and to move effort toward the customers and lines producing margin rather than just revenue. It also makes it easier to take what is working in one part of the business and repeat it elsewhere, and to trace underperformance to a specific cause instead of writing off a bad month.
None of this requires an enterprise system or a large finance team. It requires the numbers to be organized around how the business runs, and a process that keeps finance, operations and sales working from the same picture.
If your leadership team wantedto understand what drove last quarter's margin, how far down could your current reporting take them?
Connect with Adrian at Lyt to talkthrough FP&A.