A new planning system is a real investment: in money, in time, and in the attention of a finance team that already has a full plate. Before committing to one, a CFO can save the organization a great deal of pain by asking a few pointed questions. The goal is not to slow the project down. It is to make sure it is aimed at the right target before the spending starts. Here is what to ask.
What decision will this help us make better?
Start with the outcome, not the tool. A planning project should improve something specific: faster reforecasting when the market moves, clearer visibility into what drives the numbers, less time assembling and more time analyzing. If the honest answer is that the current system is old or that a vendor gave a compelling demo, that is not yet a reason. Anchor the project to a decision the business needs to make better, and every later choice becomes easier.
Do we understand our own process well enough to automate it?
Software does not create a planning process. It supports one. If your planning today is a loose collection of spreadsheets and tribal knowledge, automating it will simply produce a faster version of the confusion. Ask whether the team can clearly describe what drives the numbers, where inputs come from, and how everything rolls up. If they cannot, the first work is process design, not software selection.
Who will own this after go-live?
Every planning application needs an owner: someone accountable for its administration, its accuracy, and its evolution. If no one is named before the project starts, the system will drift the moment the implementers leave. Ask who that person is, whether they have the capacity, and whether they will have the knowledge to maintain and extend the application rather than depending forever on outside help.
How will actuals get in, and will they tie?
Plans are only meaningful against trustworthy actuals. The connection to your source of record is where many planning projects quietly fail, because if the actuals do not reconcile, people stop believing the system. Ask early how actuals will flow from the ERP, on what schedule, and how they will be validated. This is not a detail to leave for late in the build.
What are we willing to keep simple?
Ambition is where planning projects go to overrun. Every stakeholder wants their special case modeled, every dimension at full detail, every scenario available. Ask what the team is willing to leave out, at least at first. A focused application that launches and gets used beats a comprehensive one that never quite goes live. Deciding up front what to keep simple is one of the most valuable things a CFO can insist on.
How will we know it worked?
Before you spend the money, decide how you will judge whether it was worth it: faster close or reforecast, less manual effort, better adoption, more confident decisions. If you cannot describe what success looks like in advance, you will not be able to defend the investment afterward, and you will struggle to justify the next one. Define the measure of success while it can still shape the project, not after.
Why these questions matter
None of these are technical questions, and that is the point. Planning projects rarely fail on technology. They fail on unclear goals, unready processes, absent ownership, untrustworthy data, uncontrolled scope, and undefined success. A CFO who asks these six questions before the project starts does more to ensure it succeeds than any feature comparison could. The best time to steer a project is before it has momentum, and these questions are how you steer.