Your CFO Is Questioning the CRM Spend. Here's How to Respond.

The CFO has asked the question you've been half-expecting. The CRM spend is rising, the business case feels intuitive rather than evidenced, and the request is clear: prove the ROI, or propose options to reduce cost.

The instinctive response is to pull together a presentation showing pipeline growth, deal velocity improvements, and forecast accuracy — framed to make the investment look justified. That presentation will satisfy a CFO who isn't looking too carefully. It will not satisfy one who is.

The approach that actually works — and that builds trust with a financially rigorous CFO — is a different one: an honest audit of what the CRM is and isn't delivering, with a clear-eyed explanation of why the gaps exist and a specific plan for closing them. CFOs respect candour paired with a plan far more than a defensive deck. And if the numbers genuinely hold up, an honest presentation makes them more convincing, not less.

First: Build the Actual ROI Case

A credible CRM ROI case has three components. Most organisations only attempt the third.

Component 1 — Productivity valueHow much time does the CRM save per rep per week, and what is that worth? This is calculable. If automated activity logging saves a rep 45 minutes a day of manual data entry, and you have 20 reps at an average fully-loaded cost of £80,000 per year, that's roughly £750,000 of recovered productive time annually — time that should be going into selling activity, not admin. You don't need to claim all of that as CRM value, but you can claim a credible proportion of it.

Component 2 — Revenue impactThis is harder to isolate cleanly but is the most compelling part of the case. You're looking for evidence that the CRM has changed commercial outcomes — not just recorded them. Specific examples carry more weight than averages: deals that were flagged as at-risk by the system and rescued, leads that were surfaced by scoring and converted that wouldn't have been contacted otherwise, forecast accuracy that allowed resource decisions to be made correctly. Build a list of these. Even three or four specific examples with attached revenue figures is more persuasive than a generic pipeline velocity chart.

Component 3 — Cost avoidanceWhat would the alternative cost? If you weren't using the current CRM, you'd need something — a simpler tool, a manual process, more headcount to compensate for what the system does. Estimating the cost of the next-best alternative, even roughly, gives the CFO a comparison point and makes the current spend look different than it does in isolation.

The ROI Metrics That Actually Hold Up

Metric	What it measures	How to calculate it
Forecast accuracy	Whether the system produces reliable revenue predictions	Compare system-generated forecast at start of quarter vs actual close. Target: within 10% consistently.
Deal velocity	Whether CRM workflows are accelerating pipeline movement	Average days from creation to close, trended over 6–8 quarters. A shortening trend after CRM adoption is meaningful.
Win rate by adoption cohort	Whether reps using the CRM properly close more deals	Split reps into high/low CRM adoption groups. Compare win rates. A meaningful gap is strong evidence of system value.
Rep ramp time	Whether the CRM accelerates new hire productivity	Time from start date to first closed deal, trended before and after CRM adoption. Playbooks and process embedded in the system measurably reduce ramp time.
Pipeline coverage ratio	Whether better lead visibility allows more accurate capacity planning	How often actual pipeline at quarter start accurately predicted the deals available to close. Erratic coverage ratios indicate forecast unreliability.

What to Do When the Numbers Don't Hold Up

This is the harder and more important conversation. If you pull these numbers and they're weak — forecast accuracy is poor, adoption is low, you can't point to specific revenue outcomes — the right response is not to find a better way to frame the weak numbers. It's to be honest about the gap and present a plan.

A CFO who has been in business for a while knows that enterprise software underdelivers regularly. What they're evaluating in this conversation is whether you know it's underdelivering and have a plan — or whether you're going to spend another year paying full price for partial value while pretending otherwise.

The structure that works: acknowledge the gap explicitly ("our current adoption rate is X, which means we're realising approximately Y% of the system's potential value"), explain why it exists (configuration incomplete, change management insufficient, wrong tool for the motion), and present three options with honest cost-benefit assessments for each.

The Three Options Worth Presenting

Option 1 — Stay and invest in adoptionCommit to a 90-day adoption improvement programme with specific targets: data completeness above a defined threshold, automated workflows activated, forecast accuracy measured against actuals. This option requires internal resource and genuine executive commitment — not another "CRM optimisation project" that gets deprioritised when a quarter gets difficult. Present the cost of the programme alongside the projected value recovery. If adoption doubles, what does that realistically mean for the metrics above?

Option 2 — Right-size the contractBefore the next renewal, conduct a capability audit: what features are you contracted for, which are activated, which are being used. Most enterprise CRM contracts include capability that was sold in the initial deal and never implemented. Renegotiating down to what you actually use — removing unused modules, adjusting licence tiers to match actual user activity — can typically reduce cost by 20–40% without changing anything about how the sales team works. This is worth doing regardless of which option you choose.

Option 3 — Evaluate alternativesIf the honest assessment is that the current platform's cost exceeds the value it's delivering, and the adoption gap is structural rather than fixable, a controlled evaluation of alternatives is the responsible recommendation. This doesn't mean committing to switch — it means doing the analysis properly before the next renewal rather than defaulting to the status quo. The output is either a stronger negotiating position with the current vendor or a genuine business case for change.

The Posture That Works

The CFOs who push on CRM spend are doing their job correctly. They're looking at a line item that grows every year, that's justified with commercial outcomes the business already expected to achieve, and they're asking a reasonable question: how much of that outcome is the system, and how much would have happened anyway?

The CROs who handle this conversation well are the ones who have already been asking themselves the same question. They come in with data, with candour about the gaps, and with options rather than defences. They treat the CFO as a partner in getting the investment right, not an obstacle to be managed.

That posture — accountable, specific, forward-looking — is more persuasive than any ROI deck. And it's the posture that gets you the budget, the resource, and the runway to actually fix the problem.

If you want to understand the specific questions your CFO is likely to ask, the companion piece covers that in detail: As a CFO, what should you be asking your CRO about CRM spend?