Seven Board Questions Your FP&A Tool Cannot Answer

Your FP&A platform produces the report. It consolidates, it formats, and it delivers the numbers on schedule. Then a director asks why gross margin fell two points, and you are back in Excel for the rest of the week.

That is not a defect in the platform. Reporting and investigation are different problems, and a tool built for the first is not badly built for failing at the second. But it does mean the gap is structural rather than something a better dashboard closes.

Board questions arrive in chains

The single most useful thing to understand about board questions is that the first one is never the real one. They come in a predictable sequence:

1. What happened? The report answers this.
2. Why? The report does not.
3. Does it repeat? This is the actual question.
4. What are you doing about it? This is what determines whether the meeting ends well.

A pack that answers only the first question guarantees a follow-up you will answer by email a week later. Answer question three explicitly, structural or one-off, and most of the chain collapses, because the board's underlying concern is always whether the forecast still holds.

The seven questions

1. Why did gross margin drop?

The report shows the margin fell. Explaining it means decomposing the movement into price, volume, input cost, and mix, then testing each against the transactions. Mix is the one that catches people: revenue can hit plan exactly while the product mix shifts toward lower-margin lines, producing a margin decline with no revenue variance to point at.

What you need: revenue and COGS by product line for both periods, unit volumes and average selling price, input cost per component, and any cost reclassification made during the period.

2. Where did the cash go?

Profit was positive and the bank balance fell. The answer is almost always working capital, and almost never already decomposed before the meeting.

You need a bridge from net income to the change in cash, in no more than five steps: profit, non-cash adjustments, working capital movement split into receivables, payables and inventory, capital expenditure, and financing. Then name the largest driver in plain language and say whether it reverses.

3. Does the pipeline support the forecast?

Raw coverage looks adequate in almost every board pack. The question behind the question is about quality.

Bring weighted coverage alongside raw coverage, using historical conversion by stage rather than a single blended rate. Disclose how much pipeline is older than one full sales cycle and should be discounted. Show whether new pipeline creation is keeping pace with consumption: a coverage ratio that is stable because nothing is closing is not a healthy one.

4. What is the plan if revenue lands below forecast?

This is a preparedness question, and an unprepared answer is very obvious.

Have the downside scenario already modelled, with runway under it. Have cost actions identified and ordered, with the lead time each requires. Most importantly, have the trigger: the revenue level and the date at which you would act. Boards are reassured far more by a named decision point than by optimism.

5. How has customer concentration changed?

Usually asked before a fundraise or an acquisition conversation. Two details are routinely missed: measuring concentration at entity level when several accounts belong to one parent, and reporting the revenue impact without the profit impact. Losing your largest customer may remove 12% of revenue and 25% of EBITDA if they are a high-margin account.

Bring the renewal dates on the top accounts too. That is the follow-up, every time.

6. What does this hire actually buy us?

A headcount request framed as capacity relief rarely survives the meeting. Framed as a return, it usually does.

Lead with the fully-loaded annual cost: base plus taxes, benefits, and tooling, not base salary. Name the specific outcome and when it lands. Give the payback period. Then answer the question that always follows: what happens to the plan if it is deferred a quarter.

7. Why does the close take this long?

A slow close delays every decision downstream of the numbers, so this is a question about the reliability of the whole finance function rather than about the calendar.

Name the specific bottleneck rather than describing the process. Give the current days-to-close and the trend. State the target, the date, and what is required to reach it: system, process, or headcount. Vagueness here reads as not having looked.

Why the platform cannot answer these

Every one of these questions requires three things a reporting tool is not built to provide.

Data joined across systems. Margin decomposition needs the ledger joined to product and pricing data. Concentration analysis needs revenue joined to the CRM's account hierarchy. Reporting tools consolidate for presentation, not for arbitrary investigation.

The question was not known in advance. A report is built to answer a question someone specified. These questions follow from whatever actually happened this quarter, which nobody specified in advance.

Company-specific rules. Which customer is excluded and why, which quarter is not comparable, how commissions are recognised. These live in someone's head and get applied automatically by the person building the analysis, and are invisible to any tool that has not been told.

The eighth question

The seven above recur, and you can prepare for them. The one that costs you a week is the eighth: specific to your business, asked without warning, requiring data joined in a way nobody has joined it before.

Preparing for every possible question is impossible. The realistic goal is different: being able to answer any of them in minutes rather than days, so the eighth question stops being expensive. That is a question about how fast you can assemble and interrogate your own data, not about how good your reporting is.

Practical preparation

• Work backwards from the question to the analysis, not forwards from the data to a report.
• For every number in the pack, know the one-sentence explanation of why it moved.
• Classify every material movement as timing or structural before the meeting.
• Put detail in an appendix so the main pack stays readable and the follow-ups are still answerable.
• Bring a recommendation with every problem. A problem without one becomes an action item assigned to you.
• When you do not know, say so, state what you would need, and commit to a date. That costs far less credibility than an improvised answer that proves wrong.

What these seven questions have in common

Every one of them shares three properties, and the three together are why a reporting platform cannot answer them:

• They span systems. The answer needs the ledger joined to the CRM, the product catalogue, or headcount data. A tool scoped to financial consolidation cannot see two of the three.
• Nobody knew they were coming. A report answers a question someone anticipated. These are, definitionally, the ones nobody anticipated: that is why they get asked out loud.
• They need a decision attached. "Margin fell four points" is a fact. The board wants to know whether it recurs next quarter, which requires knowing the cause.

Preparing without trying to predict

You cannot pre-build the answer to an unanticipated question, but you can remove most of what makes answering one slow:

1. Keep the joins standing. Customer names reconciled across the ERP and CRM, once, permanently. This single thing accounts for a large share of the delay in most follow-ups.
2. Keep last year's same-period build. Most board follow-ups are comparative, and rebuilding the comparison is often longer than the new analysis.
3. Keep the definitions written down. When someone asks about retention live in a meeting, the argument about which definition to use costs more than the calculation.
4. Know your top-10 concentration cold. It precedes half of these questions and takes ten seconds to have ready.

What to say when you do not know

The instinct in the room is to answer. The better move is a bounded commitment: what you know now, what you do not, and when you will have it.

"Revenue is down 6%; I can see two-thirds of it in the two renewals that repriced, and I do not yet know what the remaining third is. You will have it Thursday" is a stronger answer than a confident guess, and it survives the follow-up email in a way the guess does not. Boards remember the finance lead who was wrong once with confidence far longer than the one who was precise about uncertainty.

The pattern underneath

These seven are not exotic. They are the ordinary consequence of a board doing its job: reading the report, and asking the obvious next question. Any finance function will face some version of them every quarter.

The useful conclusion is not that FP&A platforms are inadequate: they solve consolidation and recurring reporting well, and that is a real problem worth solving. It is that the report is the beginning of the conversation, not the end of it, and most finance stacks are built as though it were the end. The gap between shipping the pack and answering what the pack provokes is where mid-market finance teams actually lose their month.

One thing to do this quarter

Pick the question from this list your board is most likely to ask next, and build the answer before they ask. Not the report: the answer, with the joins already made and the comparison already standing.

You will learn two things: how long it actually takes, and which part of the delay was analysis and which was assembly. That second number is the one that should drive whatever you buy next.