After this lesson you will be able to
- Write a one-page summary a CFO will read, in finance language rather than product language.
- Present total cost of ownership, including the costs your quote does not show.
- Answer the five questions CFOs most often ask without getting defensive.
- Coach your champion to carry the case into rooms you are not in.
Know what a CFO is actually deciding
Your champion is deciding whether Salesforce will make their team better. The CFO is deciding whether this is the best use of a limited amount of cash compared to every other request on their desk this quarter. That comparison is the real competition, and it is usually not another CRM.
A CFO also carries risk the champion does not. If the project runs over budget, slips a year or fails to get adopted, it shows up in their forecast and their credibility with the board. Expect questions about downside before upside.
So your goal in a CFO meeting is not to excite. It is to make the decision feel understood, bounded and reversible where possible. Calm and specific beats enthusiastic.
Write for what the CFO reads
Many CFOs will not read your deck. Most will read one page if it is written for them. That page should answer, in order: what problem this solves, what it costs over the contract term, what return the business expects and when, what could go wrong, and what the company is committing to.
Use their units. Talk in dollars, months, margin points and headcount, not in features or clouds. "Sales Cloud with Revenue Cloud" means little to finance. "Shortens quote turnaround so reps spend more time selling, which the sales team estimates is worth X in gross margin" is something they can test.
Put assumptions where they can see them. A CFO who finds a hidden assumption stops trusting the rest of the page. A CFO who sees a conservative assumption clearly stated often relaxes. Build the numbers with the customer using the method in the business case lesson and our ROI calculator at /salesforce-account-executives/roi-calculator/.
Frame cost against value, not against discount
When a CFO pushes on price, the reflex is to discount. Resist leading with that. A discount answers a question the CFO has not asked yet, and it tells them your first number was soft.
Instead, put the cost next to the value and the cost of doing nothing. For example, a 150-person services firm whose project managers spend hours each week rebuilding status reports by hand is already paying for that work in salary. The CFO's question becomes whether the software costs less than the waste it removes, plus a margin for risk.
Value has to be in terms finance recognizes: margin, cash timing, avoided cost or reduced risk. Revenue alone is not enough, because revenue without margin does not pay for software. If the case rests on revenue, convert it to gross margin before the meeting.
Present total cost of ownership before they find it
Your quote is not the total cost. The CFO knows that. If you only show license cost, they will assume you are hiding the rest, or they will ask IT, and IT will give a bigger number than reality.
Lay out the full cost over the contract term in one table. Being the person who shows the complete picture first is one of the fastest ways to earn credibility with finance.
- Subscription cost over the full term, including any planned ramps
- Implementation services, with a range and what drives the range (see /resources/salesforce-consulting-pricing-guide/)
- Data migration and cleanup, which customers routinely underestimate
- Integrations and any middleware or AgentExchange (formerly AppExchange) apps
- Internal time: project lead, subject matter experts, testing, training
- Ongoing administration, either an internal admin or a managed services contract
- Usage-based costs, such as Flex Credits for Agentforce, if relevant
Talk about risk before the CFO does
Every CFO has seen a software project go badly, and many have seen a CRM project go badly. Raising risk yourself signals that you have done this before and are not hiding anything.
Name the three biggest risks for this deal specifically: adoption, data quality, scope growth, integration, or internal capacity. For each one, say what reduces it and who owns that. A phased plan with a defined first release and a decision point before the next phase is usually the strongest risk answer you can give, because it limits how much money is exposed before results are visible.
If the customer has had a bad implementation before, do not avoid it. Ask what went wrong and show how this plan is different. Our list at /resources/salesforce-implementation-mistakes/ is a useful checklist for that conversation.
Prepare your champion to carry the case
Much of the final decision happens in meetings you will not attend: budget reviews, executive staff meetings, a hallway conversation. Your champion carries the case there, so arm them.
Give your champion the one-page summary, the TCO table and short answers to the hardest questions. Rehearse with them. Ask, "When the CFO asks what happens if adoption is low, what will you say?" If they cannot answer comfortably, the deal is not ready for that meeting.
When implementation cost or timeline is the open question, bring a delivery partner in before the finance review so the services number is grounded. Abstrakt can provide scoped estimates through the deal desk at /salesforce-account-executives/deal-desk/.
Talk tracks
Opening a meeting with a CFO
“I know you see a lot of requests for budget. I'd like to spend this time on the cost, the expected return, and the risks, and then answer whatever you need to make a call.”
It shows you understand their job and puts risk on the agenda before they have to raise it.
When the CFO says "this is expensive"
“It's a real investment. Can I show you how it compares to what the current process is costing, and what we assumed? If the assumptions look wrong to you, I'd rather fix them now.”
It moves from price to value and invites the CFO to test the numbers rather than reject them.
When the CFO asks for a discount early
“Before we talk price, let me make sure the scope is right. If there's anything in here you don't think you need in year one, that's a better way to lower the number than a discount on things you'll use.”
Right-sizing protects value and is more credible than a reflexive discount.
When the CFO asks what else this will cost
“Here's the full picture over the term: subscription, implementation, data work, integrations, your team's time and ongoing admin. The ranges are honest, and I can tell you what moves each one.”
Showing total cost first builds trust that the rest of the case is accurate.
When the CFO asks what happens if it doesn't work
“That's the right question. The plan is phased, with a first release and a review point before the next phase, so most of the spend comes after you've seen results.”
It answers downside risk with structure instead of reassurance.
When the CFO wants to wait until next year
“That may be the right call. Can we look at what waiting costs? If the current process costs about the same each month, a six-month delay has a price too, and you should see it before deciding.”
It respects the decision while making the cost of inaction visible.
CFO meeting prep checklist
Use it on a live deal. Tick items off as you go; nothing you tick leaves this page.
Common mistakes
Bringing the product deck
Feature slides waste a CFO's time and signal you do not understand their role. Bring the one-pager and the TCO table.
Leading with a discount
An early discount teaches the CFO that your numbers are soft and invites more pressure. Right-size scope before you touch price.
Showing only license cost
Finance will find the implementation, data and internal costs anyway. If they find them first, they discount everything else you said.
Using revenue as the return
Revenue is not profit. A case built on top-line growth without margin math looks naive to a finance reader.
Overstating certainty
Precise-looking projections with no stated assumptions read as sales math. Ranges with clear assumptions read as honest.
How you will know it is working
- The CFO questions specific assumptions instead of dismissing the case.
- Finance asks for a version of the one-pager for their own internal review.
- Your champion answers the hard questions in their own words without you.
- Price conversations focus on scope and phasing, not percentage discounts.
Questions
Should I ask to meet the CFO directly?
Yes, when the deal size or the customer's process means finance will decide. Ask your champion how finance usually reviews purchases like this, and offer a short meeting focused on cost, return and risk. If a direct meeting is not possible, invest in preparing your champion.
How precise should the ROI numbers be?
Less precise than you think. Use ranges and round numbers, and label every assumption. A CFO trusts a conservative range they can check far more than a precise figure they cannot.
What if the customer will not share internal cost data?
Use clearly labeled estimates and ask them to replace them with their own numbers before the finance review. Even a rough cost of the current process is more persuasive than none.
How do I handle a CFO who is skeptical of CRM projects in general?
Ask what they have seen go wrong. Their answer tells you which risks to address. Then show how the plan limits exposure, usually through phasing, a named internal owner and a clear first-release scope.