Customer Success Platform business case: how to win over your CFO

You've sat through three demos, your CSMs have fallen for one of the platforms and the quote is waiting in your inbox. You walk into the leadership meeting with your arguments: 360° view, churn alerts, automated playbooks... Then your CFO stops you in your tracks: "Fine. And how much will it bring in?" If you can't answer in euros, the project goes back in a drawer for six months. Here's how to build a business case that stands up to a finance team!

Your CFO's job is to arbitrate between dozens of requests that all claim to be "strategic". Marketing wants budget for campaigns, Product is asking for two more developers, Sales wants a new prospecting tool. And you turn up with a platform whose benefits are described in terms of "visibility" and "proactivity".

Measuring the ROI of Customer Success as a function is one thing. Defending a specific investment in front of a finance team is quite another. A business case isn't a plea on behalf of your team: it's a decision document, one that lets someone who doesn't know your job say yes (or no) with full knowledge of the facts.

Why most CS business cases get rejected

The first mistake is arguing on comfort. "My CSMs waste hours piecing together an account's history", "we have no visibility on usage"... All true. But what a CFO hears is: you want a tool to make your work more pleasant. Your team's comfort is not a budget line.

Tom Carnewal describes a typical case: a former CS director had tried to sell a platform on team efficiency and failed to convince the CFO, until the project was refocused on financial indicators. That's no coincidence. Efficiency is a means, not an outcome.

The second mistake is more insidious: maximising the gains and minimising the costs. A CFO spots it straight away, and from that moment on, they stop believing any figure in the document. Even the sound ones.

The third is promising gains that can never be verified. A business case that doesn't say how the result will be measured in six months commits nobody to anything.

Step 1: put a figure on the cost of the status quo

Your best argument isn't what the platform will deliver. It's what not deciding is already costing you, every month, without anyone noticing. So before you talk about tools, lay out the numbers for the current situation:

ARR lost to churn over the past twelve months;
ARR lost to contraction (downgrades, licences removed);
expansion opportunities that slipped through;
the number of salespeople busy replacing lost customers rather than growing ARR;
the time your CSMs spend exporting, cross-referencing and piecing together information;
the hires planned to absorb portfolio growth.

Then do something few teams ever do: go back over your last ten churned accounts and ask yourself how many you saw coming. For each one, check whether there were signals in your data (falling usage, a champion leaving, late invoices) and whether anyone picked them up in time. Departures flagged by signals nobody saw are exactly where a Customer Success Platform earns its keep. It's also your strongest argument, because it rests on your own data rather than on a vendor's promise.

One last point, often overlooked: strong growth tends to mask churn, which only becomes visible when growth slows. If your leadership team isn't worried about retention yet, that doesn't necessarily mean everything is fine.

📍 Churn doesn't just cost you ARR: it also ties up your salespeople replacing the customers you've lost. Work out what churn is really costing you with our calculator (anonymous, no form to fill in).

Step 2: calculate the full cost before your CFO does

Your CFO knows the difference between a subscription price and total cost of ownership. Don't give them the satisfaction of finding the missing lines themselves! Your full cost should include:

the annual subscription and how it scales (number of licences, add-ons...);
set-up and implementation fees;
internal technical time for integrations (CRM, product, support, billing);
ongoing admin time: who maintains the health score and the playbooks?
training and change management;
foreseeable annual price increases and exit costs.

The gap between vendors is considerable. According to Vendr purchasing data compiled in our Customer Success Platform pricing comparison, a mid-market deployment typically costs between $10,000 and $60,000 a year, almost always with set-up fees on top. By way of comparison, Skalin's pricing is public (from €569 a month), doesn't depend on customer volume and includes deployment.

Whatever you choose, the rule is the same. A CFO will forgive a cautiously estimated gain. They will never forgive a forgotten cost.

Step 3: the three sources of gain (and how to make them credible)

Avoided churn: your main argument

Churn doesn't just cost you the ARR that walks out of the door. Simply to stand still, you have to sign new customers to replace the ones you've lost. In other words, part of your sales team isn't working to grow the company: it's filling a leaky bucket.

The real cost of churn is the ARR lost plus the salaries of the salespeople tied up replacing it. The calculation takes two lines. Divide churned ARR by the ARR an average salesperson signs in a year: that gives you the number of salespeople working purely to offset departures. Multiply that number by their fully loaded cost.

Framed this way, churn looks very different to a CFO. "We lose 10% of our customers every year" stays abstract. "Almost two salespeople spend the whole year just helping us tread water" is a lot less so!

You then need to estimate how much of that cost the platform will help you avoid. And no, that doesn't mean writing "the platform will halve our churn". Start from your analysis of the last ten departures: if three of them showed visible signals several weeks beforehand, and you reckon you could have saved one, you have a defensible assumption. A modest, well-sourced assumption beats a spectacular promise.

Finally, remind them that saved ARR is recurring: a customer retained this year pays next year too. To stay conservative, count it only once in the first-year calculation, but do mention it.

Expansion: only count what you can trace

A platform that spots accounts with growing usage generates upsell opportunities. The trap is attribution: the day a deal is signed, Sales, Account Management and CS all claim credit for it.

Hence a simple rule: only count opportunities you will log in the CRM as CSQLs (Customer Success Qualified Leads), with an identifiable source. And if your CFO thinks in margin rather than revenue, apply your gross margin rate. They'll appreciate that you did it before they had to.

Capacity: an hour saved is not a euro saved

This is the objection every CFO will raise, and they'll be right. If your CSMs save five hours a week, payroll doesn't go down by a single penny. A CFO doesn't pay for hours, they pay salaries.

Time saved only becomes a financial argument if it translates into a hire avoided or postponed, or into a bigger portfolio per CSM. At Karnott, Anne Gaillard reckons the Customer Success Platform replaces the equivalent of one or two CSMs, and the customer portfolio grew 2.5 times with a CS team of almost the same size, thanks to automated customer journeys. Now that's an argument your CFO will understand!

One word of caution, though: only count this gain if the hire was genuinely in the budget. Otherwise it's an imaginary saving.

📍 A CSP works on two levers: it spots at-risk accounts to reduce churn, and it automates follow-up so each CSM can manage more customers. Estimate the ROI of a Customer Success Platform with our calculator.

Worked example: a SaaS company with €3M ARR

Let's take a fictional case to illustrate:

€3M ARR spread across 250 customers, so €12K per customer;
10% annual gross churn, so €300K ARR lost every year;
5 salespeople plus 1 planned hire, each signing 15 new customers a year, so €180K ARR each;
fully loaded cost of a salesperson: €112.8K (€80K gross, bonuses included);
fully loaded cost of a CSM: €67.7K (€48K gross);
a team of 4 CSMs: as the portfolio grows, a 5th CSM will be needed within the year;
total first-year cost of the platform: €20K (subscription, integrations, internal time, training). With a platform that includes deployment, such as Skalin, the first-year cost is considerably lower.

Let's start with the cost of churn. Replacing €300K ARR takes the equivalent of 1.7 full-time salespeople, or around €188K in fully loaded salaries. So churn costs this company almost €490K a year, not €300K.

On the gains side, with deliberately conservative assumptions:

Avoided churn: saving one departure in ten, so €30K ARR retained and €18.8K of sales capacity freed up;
Expansion: five extra CSQLs at €4K, so €20K;
CS capacity: with each CSM covering 10% more customers, almost half a hire avoided, so €31K.

Net ROI is calculated as (gains − total cost) / total cost. You can also present it as a multiple, meaning what each euro invested brings back. That gives three scenarios:

Conservative (retained ARR only): €30K in gains, 50% ROI, or €1.50 for every €1 invested, with payback in 8 months;
Central (full avoided churn + expansion): €68.8K in gains, 244% ROI, or €3.40 for every €1 invested;
Ambitious (all three levers): €99.8K in gains, ROI of almost 400%, or €5 for every €1 invested.

Don't lead with the ambitious scenario. It's the conservative one that should carry the decision. Build your business case so it still holds even if the CFO crosses out two lines out of three. If it's still profitable on retained ARR alone, the conversation changes completely: you're no longer debating whether the project is worthwhile, but how fast to roll it out.

To work with your own figures, you can estimate the real cost of your churn with our calculator, sales capacity included. It's pre-filled with this example: just replace each assumption with your own.

Leadership objections (and how to answer them)

"Our CRM can already do that"

Your CRM was built to run a sales pipeline. Customer Success signals, on the other hand, are scattered: product usage, support tickets, billing, conversations with the customer. Don't answer on features, answer on cost: who will build and maintain the scoring in the CRM, with which product data, and how long will it take? That time has a cost, and it needs to appear in the comparison.

"We can build it in-house with AI"

This objection has become common, and it's a fair one. But plugging an LLM into your customer data doesn't remove the complexity: it shifts it onto your teams. Integrations to write and maintain, prompts to recalibrate with every new model version, data governance, dependence on the one person who built it all... Anthropic's own data team found that without structured business context, Claude got no more than 21% of answers right on their analytical evaluations. Simply ask whoever raised it to cost the engineering time over two years. The answer is usually enough to settle the question.

"How will you know it was the tool that reduced churn?"

This is the best objection, and it deserves a proper answer. Propose the measurement protocol before anyone asks for it: a baseline churn rate calculated over the past twelve months, a pilot on one segment or region, and a comparison point at six months. Tom Carnewal describes exactly this approach: a test in a region equipped with the platform showed retention up by 5%, worth €56K in barely six months. A CFO who sees you're willing to be measured immediately trusts you more.

"You're counting the same churn twice"

The objection is logical, and a good CFO will raise it. If your salespeople are already in post, their salaries are paid regardless: reducing churn pushes ARR up, but doesn't lower any payroll line.

There are two parts to the answer. First, sales capacity spent replacing lost customers is capacity that produces no growth: it's a genuine opportunity cost, even if it doesn't show up as an expense. Second, that cost becomes very concrete as soon as your sales hiring is sized to compensate for churn. If a sales hire in the budget becomes unnecessary, the saving is very real.

That's why the sales component isn't included in the conservative scenario. You show that you know the limits of your own calculation, and your other figures become more credible as a result.

"Now isn't the time, budgets are frozen"

In our fictional example, €300K ARR walks out every year, or €25K a month, while the equivalent of 1.7 salespeople works to fill the gap. Every month of waiting has a cost, and it far exceeds the monthly price of most mid-market platforms. It's precisely when growth slows that retention becomes the main revenue lever. Waiting costs money too.

"Will your CSMs actually use it?"

The risk is real: everyone knows of a tool that was bought, rolled out, then abandoned after three months. Answer with concrete commitments: CSMs involved in the choice, a short deployment timeline, and adoption metrics written into the business case (alerts handled, active playbooks, accounts reviewed each week). Plan a 90-day review. If adoption isn't there, you'll be the first to say so.

"In two years, the bill will have doubled"

With many vendors, pricing is tied to the number of accounts tracked: it rises automatically with your portfolio, at the very moment you're trying to keep costs under control. Get ahead of the question by presenting the projected price at 24 months based on your expected growth, any caps on price increases, and the exit cost. An honest projection is far more reassuring than an introductory price.

Present it on one page, not fifteen

Tom Carnewal warns against endless presentations: fifteen slides means fifteen pieces of ammunition handed to leadership to pick holes in your case. One page is enough, structured like this:

the problem, costed in euros (the cost of the status quo);
the solution and its full cost;
the three gain scenarios, with visible assumptions;
the measurement protocol and the review date;
the cost of waiting.

Two tips on presentation. First, tailor your angle to the leadership team's priorities: if this year's goal is growth, open with expansion; if it's profitability, open with avoided churn and capacity. Second, never present a figure on your own that Finance hasn't validated. Have Finance review your assumptions before the meeting: a CFO rarely challenges numbers their own team has already checked. Do the same with Sales for the CSQL and sales capacity assumptions. That's what turning your colleagues into internal champions is all about: when they back your numbers alongside you, the conversation is no longer CS versus the rest of the company.

Conclusion

If you remember just one thing: your business case isn't there to prove the platform is brilliant. It's there to show you've done the CFO's work for them, with full costs, conservative gains and measurement planned in advance.

There's another benefit that's often forgotten. This document will become your roadmap: in six months, you'll present your results against the assumptions you set yourself. If you hit them, your next budget request will be much easier. A Head of CS who delivers on their numbers stops being a cost centre and becomes a trusted counterpart for Finance.

And it's that credibility that will make all the difference from then on!

Want to test your assumptions against a real case? Book a Skalin demo.