What a CFO Should Ask Before Approving Any Technology Spend

Technology requests arrive at a CFO's desk with enthusiasm and optimism attached. The business case promises efficiency gains, competitive advantage, and future-proofing. The numbers look reasonable. The vendor references are impressive.

And yet, a significant number of technology investments fail to deliver the return they promised. Not because the technology was bad - but because the business case was incomplete, the total cost was understated, or the expected outcome was never defined precisely enough to be measured.

Here are five questions to ask before you sign. They are not about the technology. They are about the money.

1. What is the total cost of ownership over three years?

The proposal in front of you shows the licence cost or the development cost. It does not show the full picture.

Add implementation and configuration. Add data migration from existing systems. Add training for the team - not just the initial session, but the ongoing learning curve as people adapt. Add internal administration time - someone has to manage the tool, handle updates, resolve issues, and maintain the integrations.

For SaaS: add projected annual price increases. Most vendors raise prices by eight to fifteen percent per year. Your year-one cost and your year-three cost are materially different numbers.

For custom development and build: add ongoing maintenance, hosting, and the cost of change requests as requirements evolve.

The question is not "can we afford the subscription?" It is "what does this cost us fully loaded over thirty-six months, and is that number still attractive?"

2. What is the measurable outcome and when will we see it?

Efficiency, productivity, and competitive advantage are not outcomes. They are categories. An outcome is specific: "reduce month-end close from ten days to three." "Eliminate forty hours per week of manual data entry through business automation." "Reduce invoice processing errors by eighty percent."

If the business case cannot state a specific outcome with a number attached, it is not a business case. It is a wish.

Ask when the outcome will be measurable. Not when the system goes live - when the metric changes. If the answer is "six to twelve months after implementation," ask what happens during those months and how you will know whether the project is on track.

3. What does this replace and what happens to the cost of the thing it replaces?

Every new technology investment should replace something - a manual process, an existing tool, or a workaround. If nothing is being replaced, you are adding cost, not improving efficiency.

Ask whether the existing tool or process will be decommissioned. Ask when. Ask who is responsible for the transition. In many cases, the old system runs in parallel for months or years after the new one is implemented - and you pay for both.

The net cost of the investment is the new cost minus the old cost. If the old cost does not go away, the ROI calculation is wrong.

4. What is the cost of doing nothing?

This is the question that separates genuine needs from nice-to-haves. If you do not make this investment, what happens?

If the answer is "nothing changes and we continue operating as we are" - that is not necessarily a reason to reject, but it does mean the urgency is lower than the proposal suggests.

If the answer is "we continue losing X hours per week, Y pounds per month, or Z percent accuracy on critical data" - now you have a cost of inaction that can be compared directly to the cost of the investment.

The best business cases are the ones where doing nothing is more expensive than doing something. If the cost of inaction exceeds the cost of the project within twelve to eighteen months, the decision is straightforward.

5. Can we start smaller?

Large technology investments carry large risks. Configuration takes longer than expected. Adoption is slower than planned. Requirements change during implementation. Scope creeps.

Ask whether the project can be broken into phases. Can you start with the highest-value component, prove it works, and then expand? A phased approach reduces risk, accelerates the first measurable return, and gives you real data to inform the next investment decision.

If the vendor or the internal team insists on an all-or-nothing approach - the entire platform, fully configured, across the business - that is a risk signal. Independent tech consultancy will usually say the same thing: the best technology projects start small, deliver quickly, and scale based on evidence.

The CFO's role in technology decisions

The CFO is not a gatekeeper. The CFO is the person who ensures that technology investment is measured with the same rigour as every other capital allocation decision.

The answers to these five questions will not tell you whether the technology works. They will tell you whether the investment makes financial sense - and whether the team has done the work to define what success looks like before the money is spent.

That is not being difficult. That is being responsible.