A proposal tells the CFO what you cost. A business case proves the company is better off buying it, and when. Here is how to build one they will actually sign.
Most deals reach the CFO as a price with a product attached. No baseline, no return, no payback, nothing that answers the only question finance asks: what does the business get for this, and when. A business case is not a nicer proposal. It is a financial argument built on the customer's own numbers, and it is what turns interest into a signature.
Build it in this order. Each step is something you can apply to a live deal this week, using numbers your buyer already has.
Start with what the problem costs today, before you mention your solution. Quantify the wasted hours, the lost revenue, the risk carried, the money leaking every quarter. This baseline is the reference point the CFO measures every benefit against. No baseline, no case.
A CFO trusts a number that includes the uncomfortable parts. Add implementation, integration, training, support, and change management to the license fee. Total cost of ownership over three years, stated plainly. Hiding costs is the fastest way to lose credibility in the review.
Hard benefits are anything you can measure: hours saved times fully loaded cost, direct cost reductions, avoided spend, revenue you can attribute. These are the numbers the CFO reads most carefully. Keep each one tied to a source they can check.
Faster decisions, better experience, reduced risk: real value, harder to measure. Include them, but label them clearly and keep them out of the headline ROI. A case that separates hard from soft looks honest. A case that blends them looks inflated.
Bring it together: total benefit minus total cost, the ROI as a ratio, and the payback period. Answer the question the CFO is actually asking, when do we get our money back. For most enterprise software, a payback inside 12 to 18 months is a case worth signing.
Before the CFO does it for you, run a conservative case and a sensitivity analysis. Show what happens if the benefits land at 70 percent. A case that survives its own worst scenario is far stronger than a bigger number that collapses under one hard question.
The business case is read in a room you are not in. Summarize it on a single page: baseline, cost, net impact, payback, and the assumptions behind each. If your champion can present and defend it without you, the case does its job when it matters most.
Skipping the baseline, so there is nothing to measure benefits against. Hiding costs, which destroys trust the moment they surface. Blending soft benefits into the headline ROI, which reads as inflation. And numbers with no source, which a CFO cannot defend even if they want to. Remove these four and your case gets stronger the harder it is examined.
The one-page reference my clients keep open while they build the business case. Free.
A CFO-ready business case starts from a financial baseline, includes the full cost of ownership rather than just the license, separates hard benefits from soft ones, and states a clear ROI and payback period. Every assumption is conservative and sourced, and the whole thing fits on one page a champion can defend without the seller in the room. It answers when the company gets its money back, not what the product does.
Total the benefits you can measure over three years, subtract the total cost of ownership over the same period, and express the result as a ratio and a net figure. Hard benefits are measurable: hours saved times fully loaded cost, avoided spend, attributable revenue. Keep soft benefits separate and out of the headline number. Then state the payback period, which is the month the cumulative benefit passes the cumulative cost.
A proposal describes what you will deliver and what it costs. A business case proves the company is financially better off buying it, and when. A proposal is about your solution. A business case is about the customer's numbers: the cost of their problem, the return on the spend, and the payback. CFOs approve business cases, not proposals.
One page for the summary the CFO reads, backed by the detail behind it. The one-pager carries the baseline, cost, net impact, payback, and headline assumptions. The supporting model holds the full math and sources. The discipline of fitting the case on one page forces you to lead with the numbers that decide the deal.
Conservative ones, stated up front, with a source for each. Use pilot data, the customer's own figures, or credible benchmarks, and underpromise so the result overdelivers. Show a conservative scenario alongside the expected one. A defensible case built on numbers the CFO believes beats an ambitious case they cannot verify.
Free guides on the CFO conversation and the frameworks behind it.
90 minutes. Your team. A business case framework they'll actually use.