What CFOs Actually Want to Hear in a Demo

Early in my career I made the same mistake most solutions consultants make the first time they get in front of a CFO. I showed the product. I walked through the features. I explained how the platform worked. I even had a beautiful slide deck with ROI projections and a competitive comparison matrix.

The CFO looked at me across the table, waited for me to finish, and said: "That's interesting. What problem does it solve for my business specifically, and what does it cost me if I don't do anything?"

I did not have a crisp answer. The meeting ended politely. The deal stalled for eleven weeks and eventually went to a competitor who had done the work I had not — they had built a business case anchored in the CFO's own language, the CFO's own numbers, and the CFO's own risk framework.

That meeting reoriented the way I approach every executive conversation I have had since. What follows is the framework I have built over many years and hundreds of enterprise deals — including engagements at Dun & Bradstreet, Conversica, and Leadspace where the CFO or VP of Finance was either the economic buyer or a decisive voice in the final approval.

The fundamental misunderstanding about CFO demos

The phrase "CFO demo" is itself part of the problem. A CFO does not want a demo. A demo is a product experience. It shows capability. It answers the question "can your platform do X?" — and that is not the question a CFO is asking.

A CFO is asking three questions, in this order. First: what is this going to cost me, fully loaded, including implementation, training, and any ongoing professional services? Second: what is the quantified value — not the theoretical value, the realistic, conservative, defensible value — of solving the problem this platform addresses? Third: what is the risk that this does not deliver, and how would I know early enough to course-correct?

Everything else — the UI, the integrations, the AI features, the roadmap — is supporting evidence for those three answers. If your presentation does not lead with those three questions and answer them credibly, you are giving a demo to the wrong audience.

The four things CFOs actually respond to

After years of executive selling, I have reduced what moves a CFO to four categories. They are not complicated. They are simply not what most solutions consultants prepare for.

The critical discipline here is picking one or two of these as your primary argument and building the business case around them with your prospect's own numbers. A presentation that tries to claim all four simultaneously reads as inflated. A presentation that makes one compelling, conservative, well-documented claim reads as credible.

How to build the business case before the executive meeting

The work that determines whether an executive meeting goes well happens weeks before the meeting itself. It happens in discovery — specifically in the discovery conversations with your champion and with the operational stakeholders who understand where the money is actually leaking.

The goal of those conversations is to build a financial model that uses the prospect's own numbers. Not industry benchmarks. Not your vendor's published ROI statistics. The prospect's actual conversion rates, their actual cost per sales rep, their actual contract values, their actual churn rate. When a CFO sees a business case built from their own data, the credibility shifts dramatically. They are not evaluating a vendor's claim. They are reviewing their own math.

This requires asking questions in discovery that most solution consultants avoid because they feel presumptuous. How many leads does marketing generate per month? What percentage convert to qualified pipeline? What is the average deal size and average sales cycle? What does it cost to onboard and ramp a new sales rep? How many customer success managers do you have, and what is your current net revenue retention rate?

These are not aggressive questions. They are the questions of someone who is serious about building a real business case rather than a polished slide deck. Champions who believe in you will answer them. The answers are the foundation of everything that follows.

Structuring the executive conversation

Once you are in the room — or on the call — the structure of the conversation matters as much as the content. CFOs are time-constrained and analytically oriented. They will respect a presentation that gets to the point quickly and supports its claims with evidence. They will disengage from a presentation that builds slowly toward a conclusion or relies on emotional storytelling without financial substance.

The structure I use, refined across many executive engagements, has four parts:

Notice what is not in that structure: a product tour. The product is not the point of an executive conversation. If the CFO wants to see the product, they will ask — and that is the right moment to show it, briefly, in the context of how it delivers the value you have just described. Showing the product before establishing the value frame is backwards.

The assumptions slide is your most important slide

This is the single most underused tool in enterprise sales, and it is the one that has saved more of my executive presentations than anything else. Before presenting your financial model, show a slide — or a section of your document — that explicitly lists every assumption you made in building it.

The assumptions slide does three things simultaneously. It demonstrates intellectual honesty — you are not hiding the levers in your model. It invites the CFO to engage — they will correct your assumptions if they are wrong, and in doing so they are co-authoring the business case rather than evaluating yours. And it protects you when the numbers get challenged, because you can say: "That number is based on the assumption that your close rate is currently at X — if that is not accurate, let us update the model together right now."

I have had CFOs spend fifteen minutes on an assumptions slide, correcting figures and running updated calculations in real time. Those are fifteen of the most valuable minutes in any enterprise sales process. By the end of it, the business case belongs to them as much as it belongs to me.

What to do when the CFO pushes back

Pushback from a CFO is not a bad sign. It is a sign of engagement. A CFO who is not interested does not push back — they end the meeting early or delegate follow-up to someone junior. Pushback means they are taking the business case seriously enough to stress-test it.

The right response to almost any CFO pushback follows the same pattern: acknowledge the concern directly, identify the specific assumption or data point being questioned, and offer to revise the model with their number instead of yours. Do not defend your assumption. Replace it. A business case that survives a CFO's scrutiny because you updated it with their inputs is far more powerful than one that survives because you argued for it.

The one thing most solutions consultants never do

After the executive meeting, most solutions consultants send a follow-up email with a summary and next steps. That is table stakes. What very few do — and what I have found to be one of the highest-leverage actions in an enterprise sales process — is send a written version of the business case document within 24 hours of the meeting.

Not a slide deck. A document. Two to three pages, written in prose, that restates the problem, presents the financial model with the assumptions you agreed on in the meeting, summarizes the evidence, and lays out the implementation path and payback period. A document that a CFO can share internally with their finance team, their board liaison, or their procurement lead without you in the room to explain it.

The deals that stall after an apparently successful CFO meeting almost always stall because the business case did not survive the internal circulation process. The CFO was persuaded but could not persuade others, because the case existed in a slide deck that required you to present it rather than a document that could stand on its own. A well-written business case document closes that gap. It gives your champion something they can circulate, and it gives the CFO something they can defend.