From the CFO Seat: Five FP&A Demo Answers That Tell You More Than the Product
In my last post, From the CFO Seat: Five Questions to Ask in Your Next FP&A Demo, I focused on the questions finance leaders should bring into the room.
This piece is the other half of that conversation.
What I have learned over time is that demos rarely fail because of the questions in the room. They fall apart in the answers. Not the rehearsed ones, but the off script moments when a finance leader asks how something actually works under pressure.
After years as a Controller and CFO, and many more years sitting alongside finance teams as a consultant, I have seen the same pattern repeat. Most demos look polished on the surface. Dashboards load quickly. Forecasts roll forward on command. Everything feels smooth.
The cracks show up in the answers. The issue is rarely the tool itself. It is how well the tools in the stack stay connected, governed, and honest as complexity grows.
With that lens, here are five demo responses that should give you pause.
1. “Most customers don’t need that level of detail.”
This answer usually appears when you ask about edge cases. Multi entity complexity. Mid cycle reforecasts. Adjustments that do not follow clean, prescribed templates.
What it really tells you is this: the system is optimized for the average case, not your case.
From the CFO seat, averages are rarely the problem. Exceptions are. Timing gaps. Partial data. Scenarios that do not fit neatly into a predefined workflow. When a vendor dismisses complexity instead of exploring it with you, that complexity does not disappear. It shows up later, under deadline, and usually lands back on your team.
Takeaway: A strong platform does not avoid detail. It is designed to operate inside it.
2. “You just need to clean up your data first.”
Yes, data quality matters. Every finance leader knows that. The concern with this answer is not the sentiment, but the implication. It suggests that value only arrives after a future cleanup that somehow happens outside of normal operations.
In reality, finance systems are adopted while work is already in motion. During closes. During budget cycles. During reorganizations and leadership changes. There is rarely a clean pause where data suddenly becomes pristine.
When I hear this response, I always ask a follow up question: “What happens while the data is still imperfect?”
The most effective tools acknowledge that reality and help teams move forward with controls, visibility, and incremental improvement, not waiting for an ideal state that never quite arrives.
Takeaway: Good systems support progress. They do not require perfection as a prerequisite.
3. “That’s handled outside the system.”
This often comes up around allocations, adjustments, scenario comparisons, or reporting variations for different audiences.
Let’s be clear. Using Excel is not the problem. Excel is often where finance teams do their best thinking. It is flexible, fast, and deeply understood. Most organizations rely on it for very good reasons.
The risk appears when critical logic lives outside the system without connection or visibility. When assumptions, allocation drivers, or adjustment logic sit in standalone files, the organization loses a shared source of truth. Changes become harder to trace. Review becomes harder to scale. Knowledge becomes harder to transfer.
From the CFO seat, the real question is not “Is this done in Excel?” It’s “Is this connected, reviewable, and repeatable?”
A strong platform respects Excel’s role and supports it with live data, structure, and governance, instead of pushing important decisions into isolated workarounds.
Takeaway: Excel is a strength. Disconnection is the risk.
4. “You can always customize that later.”
This is one of the most expensive sentences in software. Customization usually means time, consulting cost, and ongoing maintenance. More importantly, it often signals that the core product does not naturally support how finance teams actually work.
In my experience, the capabilities that matter most are not exotic. They are flexibility, transparency, and the ability to adjust logic without rebuilding everything from scratch. If something central to your process is positioned as a future customization, it is worth asking why it is not part of the standard workflow today (and perhaps, why you are in this discussion to begin with).
Takeaway: Core finance behaviors should feel native, not bolted on.
5. “That’s not really an FP&A problem.”
This response tends to surface when questions cross functional lines. Reporting meets planning. Actuals meet forecasts. Finance meets operations.
But from the CFO seat, those boundaries are artificial. FP&A does not operate in isolation. Forecasts feed board discussions. Reports inform decisions across the organization. Adjustments ripple through teams whether systems acknowledge that or not.
When a vendor narrows responsibility instead of embracing those connections, it often reflects a product built around modules rather than outcomes.
Takeaway: Finance leaders live in the intersections. Their tools should as well.
Listening Matters More Than Asking
Strong demos are not about perfect, scripted answers. They are about honest ones.
The best vendors do not pretend finance work is clean or linear. They acknowledge how much thinking still happens in Excel, how often assumptions evolve mid cycle, and how frequently leaders need answers before structures are fully settled. Then they show how their platform supports that reality instead of fighting it.
If the first post was about asking better questions, this one is about listening for where responsibility lives once the demo ends. From the CFO seat, the goal is not fewer tools. It is better connections between them. Clarity beats polish every time.