You can have the right initiative, the right timing, and the right vendor and still lose the budget conversation. Not because the project isn’t worth funding, but because the proposal doesn’t answer the questions your CFO uses to evaluate capital requests.
This isn’t a criticism of finance teams. It’s how capital allocation is supposed to work. CFOs are paid to be skeptical. Their job is to pressure-test assumptions, challenge ROI projections, and protect the organization from investments that look better on paper than they perform in practice. If you walk in without answers to their standard questions, the proposal gets tabled. It’s not personal.
Here’s what those questions often look like and what you need to prepare before you’re in the room.
“What does it cost us to do nothing?”
This is the first filter. CFOs aren’t just evaluating the investment. They’re evaluating the risk of not investing. If your proposal doesn’t quantify the cost of staying where you are, you’re asking them to approve spending against a blank baseline. That’s a hard sell.
Most proposals skip this question entirely, which is why most proposals lose. The status quo has a price tag. You need to know what it is.
“Where are these numbers coming from?”
Estimates don’t survive budget reviews. Neither do directional claims like “we believe” or “industry research suggests.” CFOs want to see the methodology behind your numbers. How did you calculate labor inefficiency? What assumptions are built into your inventory cost projection? How did you arrive at your ROI estimate?
If you can’t show your work, the numbers aren’t credible. Be ready to defend every figure you put in front of them.
“What does payback look like?”
Not IRR. Not five-year NPV. Payback period. It’s the most common first question in capital allocation conversations because it’s the most intuitive. How long until this investment pays for itself? If you don’t have a clean, defensible answer, the conversation usually ends there.
Build your payback math before you walk in, and build it conservatively. CFOs notice when projections assume best-case scenarios across the board.
“Who else has reviewed this?”
When a CFO sees that operations and IT have both weighed in and signed off, it tells them the numbers have been pressure-tested by people close to the work.
A proposal that arrives from a single function reads like advocacy. A proposal with broad internal alignment reads like analysis. That’s a meaningful difference when you’re competing for capital against other priorities.
“What happens if we delay?”
This question doesn’t always get asked out loud, but it’s always in the room. If there’s no cost to waiting, there’s no urgency to approve. You need a clear answer to why now matters more than next quarter or next fiscal year. That answer usually comes back to the cost of inaction, including hidden margin loss, compliance exposure, and inefficiency accumulating while the decision gets deferred.
Getting these answers right before you walk in is what separates proposals that move forward from proposals that get tabled pending “further review.”
If you’re building a capital case for ERP modernization, “The High Cost of Doing Nothing” was built for this preparation. It gives you a financial tool for quantifying what your legacy system is actually costing you, with a cost-of-inaction worksheet, a KPI-to-dollar calculator, and a one-page executive summary your CFO can actually engage with.
