The ROI of CS isn't invisible — it's being measured wrong, reported wrong, and framed wrong.
Have a question about this? Bring it to Aurelius.
Only 15% of executives consistently incorporate customer insights into strategic decisions — yet companies that do achieve more than 2x the revenue growth of those that don't. If you lead Customer Success and you feel the invisible weight of that gap every time you walk into a board meeting, you are not imagining it. The problem is real, the frustration is legitimate, and the cause is not your team's performance. It is a translation failure.
Snowflake's CFO did not say Customer Success doesn't matter. He said CS teams are "not accountable for anything." That is a measurement and framing problem. It is also, if you are willing to sit with the discomfort, one of the most useful things a financial leader has ever said about this function.
Most guidance on this problem tells CS leaders to build a better dashboard, find a compelling NPS story, or hire a RevOps analyst to construct a customer lifetime value model. The instinct is defensible but the diagnosis is wrong. The problem is not that you lack data. The problem is that you are presenting outcomes in a language your CFO did not ask to hear.
Financial leaders live in a world of causal claims, direct attribution, and hard-dollar figures with clear time horizons. When CS leaders show retention rates, health scores, and CSAT trends, they are showing correlational evidence to an audience trained to demand causation. No amount of polishing that presentation fixes the underlying mismatch.
Conventional advice also encourages CS teams to fight for credit — to argue that expansion revenue and low churn "belong" to Customer Success. This is a losing political contest. It creates friction with Sales, alienates RevOps, and positions CS as a department defending its budget rather than a function serving the company's growth. The better move is not to claim credit. It is to become undeniably legible in financial terms.
In Meditations 5.8, I wrote: "Confine yourself to the present." This sounds simple. It is not. Most CS leaders, when pressed by a CFO, reach backward into the past — past renewals, past saves, past NPS improvements — or project forward into a speculative future of compound loyalty effects. Neither move lands. The CFO is asking about now: what does this quarter's spend in Customer Success produce in this quarter's measurable outcomes?
This reveals something worth sitting with: the difficulty of proving CS ROI is partly a temporal discipline problem. We have built the function around lagging indicators — satisfaction scores that arrive after the moment has passed, health scores that turn red only when the risk has already compounded — and then we are surprised when financial leaders cannot see the value in real time.
Epictetus taught that we must distinguish between what is up to us and what is not (Enchiridion, 1). What is not up to you: the CFO's prior beliefs about CS, the board's mental model of customer work as cost rather than growth, the inertia of how SaaS companies have historically categorized CS spend. What is up to you: the metrics you choose to track, the frequency at which you report them, the causal logic you construct between CS activity and hard-dollar revenue outcomes.
This means the examined path forward requires a kind of radical honesty about your own measurement infrastructure. If you cannot draw a direct line from a specific CS motion — an onboarding intervention, a health score trigger, a QBR conversation — to a retained dollar, an expanded contract, or a recovered at-risk account, you do not yet have a financial story. You have a faith claim dressed in charts.
The Stoic discipline here is not to argue harder. It is to rebuild the foundation with more precision. Track saved ARR at the account level. Assign a dollar value to every churn intervention that succeeded. Quantify the expansion revenue influenced by CS-led adoption milestones. Present the cost of inaction — what would have been lost without the intervention — rather than the cost of the CS function. CFOs understand avoided loss. It is real money.
McKinsey's research makes the economic case starkly: 80% of value creation for the highest-growth companies comes from unlocking new revenue from existing customers. That is your frame. CS is not a retention cost center. It is the operating infrastructure of your highest-margin growth channel.
Begin with one cohort and one motion. Do not try to prove the ROI of all of Customer Success. Prove the ROI of one intervention — a 60-day onboarding program, a health-score-triggered save conversation, a QBR with a specific account segment — in one quarter, with hard-dollar outcomes attached.
Build a simple attribution model: accounts that received the intervention versus a comparable set that did not. Measure retention delta, expansion delta, and time-to-value delta. Bring those three numbers to your CFO before you bring anything else.
Then instrument the function so that this is not a one-quarter exercise. Turn Customer Health Scores Into Retention Decisions Your Exec Team Trusts is the operational architecture this requires. Equally, AI Renewal Execution: Reduce Churn by 25% gives you the tactical layer for connecting CS activity to renewal outcomes in measurable terms.
Finally, stop reporting to your CFO in CS language. Translate every metric into one of three categories: revenue protected, revenue expanded, or revenue accelerated. Those are the only three categories that belong in a board conversation.
Before you close this tab, open your CRM and identify the last five accounts your CS team actively saved from churning. Assign each one a hard-dollar ARR value. Calculate the total. Then calculate what percentage of your CS team's fully-loaded quarterly cost that number represents. That is your minimum demonstrable ROI for one quarter from one motion alone — and it is almost certainly a ratio your CFO will find defensible. Write that number down, format it as "$X in ARR protected against $Y in CS investment this quarter," and bring it — not a deck, not a dashboard, just that sentence — to your next conversation with your finance partner. One clear causal claim, one quarter, one motion. That is how the translation begins.
If you want to build the operational infrastructure that makes this measurement sustainable and scalable, Build a CS Operations Stack That Scales Beyond Your Headcount addresses the systems layer directly.
For the QBR conversations where financial framing matters most at the account level, Turn Your QBR Into a Retention Tool Your Customers Actually Value provides the structure.
And when you need to test whether your current retention playbook is producing signal or noise before you present it upward, Distinguish Signal From Noise: Is Your Retention Playbook Working is the right place to stress-test your logic before it faces a CFO.
Go deeper with Aurelius
Apply this to your actual situation. Aurelius will meet you where you are.
Start a session