Selling to a CFO or economic buyer means answering one question: what does this do to the number they are accountable for. A defensible range with its assumptions named beats a single flattering figure, because the CFO has to repeat it upward without getting picked apart. Here is that conversation, handled badly and well.
The person who joins late and can end it
Somewhere in the deal, a new person joins the call who was not in the first three meetings. They did not sit through the product walkthrough. They do not care which features shipped last quarter. They have one question, usually unspoken until the second or third exchange: what does this do to the number I am accountable for. This is the economic buyer, and on most B2B deals that person sits in finance, often the CFO or a VP of Finance who signs off on anything above a certain spend threshold.
The champion who has been nodding along for weeks cannot approve the deal alone. They can want it, budget for it internally, and still watch it die in a five-minute conversation with someone who was never in the room for the pitch. That conversation runs on a different currency than the rest of the sales cycle. Features, workflow, "our customers love it," all of that lands as noise to someone whose job is to protect the P&L. The rep who walks in with the same deck they used for the champion is bringing the wrong argument to the only person in the building who can actually kill the deal or clear it.
Three ways a good product loses a finance room
Leading with product instead of the number it moves. A rep who has spent weeks building rapport with a champion around workflow improvements tends to keep pitching workflow when the CFO joins. The CFO is not asking "does this work well," they are asking "what does this return, over what period, and how confident should I be in that estimate." A pitch that never answers that question in plain terms reads as a rep who has not thought about the business case, whatever the product actually does.
Treating the ROI number as a slide instead of a claim to defend. Many reps arrive with a return-on-investment figure already built into the deck, often supplied by marketing, and present it as settled fact. A finance leader's job is to stress-test assumptions for a living. The first follow-up question is almost always about the inputs behind the number, and a rep who cannot walk through how it was built, whose numbers, over what period, against what baseline, loses credibility in the same breath that was supposed to build it.
Not addressing risk as its own line item. Cost is not the CFO's only concern. Implementation risk, the chance the tool sits unused, the switching cost if it fails, all weigh on a finance leader's decision the same way a bad hire weighs on a hiring manager. A rep who only talks about upside and never acknowledges what happens if the rollout underperforms is leaving the CFO to imagine the downside unassisted, which they will do, and usually worse than reality.
How does a CFO read your ROI claim?
They are converting everything into a number they can defend to someone above them. A CFO rarely has final, unaccountable authority. Most are defending a spend decision to a board, a CEO, or a budget committee. Every claim you make gets mentally translated into "can I repeat this number in that meeting without getting picked apart." Vague enthusiasm does not survive that translation.
They assume the vendor's ROI number is optimistic until proven otherwise. Vendor-supplied return estimates have a well-earned reputation for being built on best-case assumptions. A CFO's default posture is to discount whatever number you bring by some margin before doing their own math. A rep who volunteers the conservative case, not just the best case, is doing the discounting the CFO was going to do anyway, which reads as more trustworthy, not less impressive.
They are weighing this decision against every other claim on the same budget. The deal is not being evaluated in isolation. It is one line competing with headcount, other tools, and whatever the CFO is already worried about this quarter. A rep who frames the ask only in terms of the product's value, and never in terms of what it is being weighed against, is arguing a case the CFO has already reframed in their own head.
What a defensible number sounds like out loud
The rep sells a fleet-routing optimization platform for regional trucking companies. Denise is the CFO at Callenwood Logistics, a fifty-truck regional carrier evaluating three vendors after two straight quarters of fuel and overtime costs eating into margin. She joins the call after her VP of Operations has already run two demos.
Answering with adjectives:
Denise: I've seen the demo. What I need to understand is what this actually does for us financially.
Rep: Absolutely, so the platform reduces empty miles through smarter routing, and customers typically see meaningful savings on fuel and driver overtime within the first few months.
Denise: What's "meaningful," and whose numbers are those?
Rep: We've seen carriers save quite a bit, it really depends on the fleet, but the feedback has been very positive across the board.
Denise: I'll need something more concrete than that before I can take this upstairs.
The rep answered a financial question with a features-adjacent claim, "reduces empty miles," dressed up as an outcome. Pressed for a real figure, the rep retreated into vague reassurance, "quite a bit," "very positive," neither of which Denise can put in front of her own boss. She is left to build the business case herself, which she will not do on the vendor's behalf.
Answering with a defensible range:
Denise: I've seen the demo. What I need to understand is what this actually does for us financially.
Rep: Fair question, and I'd rather give you a number you can defend than one that just sounds good. Based on your fleet size and the mileage data your VP shared, a conservative estimate is 6 to 9 percent reduction in fuel and overtime spend in year one, that's the low end of what similar-sized carriers have seen, not the best case.
Denise: Why the range, and what would move you toward the low end versus the high end?
Rep: The low end assumes a slower rollout, drivers still adjusting to new routes for the first two months. The high end assumes full adoption by month two. Either way, the platform pays for itself inside the first year at your fleet size, and I can walk you through the exact math behind both numbers so your team can check it independently.
Denise: Send me the model. If the assumptions hold up, I can bring this to the board next month.
The rep gave a range instead of a single flattering figure, and explained what moves the number in either direction, which is what a finance leader actually needs to defend it upward. Naming the conservative case first, unprompted, did more for credibility than a bigger number would have. Offering the underlying model, rather than just the conclusion, let Denise verify the claim instead of having to trust it, which is the only way a number survives contact with a board.
Drilling the number until it survives questioning
Set up a discovery or negotiation call against an economic buyer persona and treat every financial question as a request for a defensible number, not an opportunity to sound confident. Goals for the practice run:
- Lead with the number the buyer is accountable for, not the product feature that produces it. Translate every capability into its financial effect before you say it out loud.
- Bring a range and explain what moves it, rather than a single polished figure. A number you can defend under questioning is worth more than one that only survives if nobody asks.
- Name the conservative case yourself before the buyer forces you to. Volunteering the discount they were going to apply anyway builds trust instead of costing it.
- Offer to show the model behind the number, not just the conclusion. A buyer who can check your math is a buyer who can repeat it to someone else.
Run it once against a CFO who accepts a well-built range, and once against one who keeps pushing on the assumptions underneath it. Knowing which parts of your business case hold up under real scrutiny, and which ones only sounded solid in the deck, is what this drill is for.
