The CFO has no desire to be sold to. But their signature is the single most important part of closing the deal. Here is how to build a case they will sign, and win the deals you keep losing to "no decision."
Most reps sell up to the point of value and stop. They run a great demo, win the champion, and then hand a price to a CFO who was never given a reason to spend it. The deal does not die because the product was wrong. It dies because nobody built the financial case for change. Selling to the CFO is the part of the deal that actually decides it, and it is the part most teams skip.
None of this is theory. It is the same sequence used to win eight-figure enterprise deals, stripped down to what you can apply on your next live opportunity.
The CFO is not comparing you to a competitor. They are comparing you to doing nothing. Put a number on what the current problem costs every quarter: wasted hours, lost revenue, risk carried. Make the status quo expensive in their own numbers, and the decision to change makes itself.
A CFO does not buy features. They buy cost reduction, revenue growth, and reduced risk. For each thing your product does, name the outcome it drives and the line on the P&L it touches. If you cannot connect a feature to money, leave it out of the CFO conversation.
Do not wait for procurement to demand an ROI model. Bring a one-page business case: costs, hard benefits, soft benefits, and net impact over three years. The champion who walks into the CFO's office with a finished case looks like a partner, not a supplier.
The fastest way to lose a CFO is a number they do not believe. Use conservative estimates, cite where each one came from, and show the math. Underpromise on the model so the result overdelivers. A defensible 3x beats an unbelievable 10x every time.
Answer the question the CFO is actually asking: when do we get our money back. Give a payback period and a net value figure. For most enterprise software, a payback inside 12 to 18 months with a strong net impact is a case worth signing.
The CFO conversation usually happens in a room you are not in. Give your champion a case they can defend alone: the assumptions, the competitive context, and the answers to the questions the CFO will fire back. If they can hold the line without you, the deal survives.
Every CFO decision comes down to three questions. Why change: the cost of standing still. Why you: the outcome only you deliver. Why now: what it costs to wait another quarter. Answer all three with numbers and the deal closes at full price.
Leading with features instead of financial outcomes. Bringing numbers you cannot source or defend. Introducing the CFO too late, once the framing is already lost. And handing the champion a case they cannot defend when you are not in the room. Fix these four and most stalled deals start moving again.
The one-page reference my clients keep open while they build the business case. Free.
A CFO cares about three things: the cost of the problem you solve, the return on the money they spend, and the risk of the investment. They do not evaluate features. They evaluate whether the business is better off financially after the purchase, and how quickly. Lead with the cost of the status quo and a defensible payback period, not a product tour.
Start with the financial baseline: what the current problem costs today. Add the costs of your solution, including implementation and change management. Then model hard benefits you can measure, soft benefits you can estimate, and net impact over three years. Use conservative, sourced assumptions, state a payback period, and put it on one page the champion can defend without you in the room.
Earlier than most reps think. If the CFO first sees your deal as a signature request at the end, you have already lost control of the framing. Surface the financial case while you still have access to the champion, so the numbers reaching the CFO are yours, built on their data, not a procurement summary of your list price.
A user buys capability: what the product does and how it feels to use. A CFO buys outcome: what changes on the P&L and when. The same product needs two different cases. For the CFO, translate every capability into cost reduction, revenue growth, or reduced risk, and drop anything you cannot tie to a number.
Expect it, and welcome it. Share your assumptions before they ask, cite the source of each one, and show a conservative and an aggressive scenario. When a CFO can see the math and pressure-test it, pushback becomes a working session instead of a rejection. A number you can defend under scrutiny is worth more than a bigger number you cannot.
Free guides that break down the frameworks behind the CFO conversation.
90 minutes. Your team. A business case framework they'll actually use.