CS teams spend years building champions. But in 2026, the renewal decision has moved to finance - and your champion can't save you if they can't answer a CFO's ROI question. Here's what changed, and what the CS motion needs to look like now.
The call came three weeks before renewal. The CS team had done everything right - regular touchpoints, solid adoption metrics, a QBR six weeks prior where the champion had been genuinely enthusiastic. The account looked green. Then the champion called and said she'd been trying to get the renewal approved for ten days, and finance kept pushing back. They wanted to know what the platform had actually delivered to the business. Not usage numbers. Not satisfaction scores. A financial answer.
She couldn't give them one. And neither could we.
I've watched versions of that conversation happen more times than I can count, across different companies and different account sizes. And over the past two years, the frequency has accelerated sharply. The renewal motion that worked reliably in 2021 and 2022 - build the champion relationship, keep NPS high, show up for the QBR - has a structural problem now. The person who loved your product is no longer the person who controls the renewal.
The Budget Scrutiny That Changed Everything
Sometime in late 2023, enterprise finance teams got serious about SaaS spend in a way they hadn't been before. The combination of rising interest rates, tighter growth expectations, and two years of post-pandemic software over-procurement meant that CFOs started paying attention to contracts they'd previously rubber-stamped. The process became: find every SaaS renewal over a certain threshold, put it in front of finance, and ask the question your CS team wasn't prepared for.
What is this software actually doing for the business?
Research by Zylo and others tracking enterprise SaaS portfolios has found that significant portions of enterprise software spend are on tools with low or unmeasured utilization. That number varies widely by company, but it doesn't matter whether it's 20% or 40% in any given organization - what matters is that finance now knows these numbers exist, and every renewal is subject to the same scrutiny. Your contract is not presumed innocent until proven otherwise. It's presumed a cost until proven an investment.
This is the environment your champion is walking into when they try to get your renewal approved. They believe in the product. They've been advocating for it internally for years. But when the CFO asks for a business case, they're often working from adoption dashboards and NPS scores that don't translate to financial language. The champion is stuck defending the product they believe in with evidence the finance team doesn't speak.
Why Your Champion Can't Save You Anymore
This is the part that's uncomfortable to say but important to understand: a champion's enthusiasm is no longer sufficient. It was never supposed to be the primary defense at renewal - it just functioned as one because CFOs weren't paying attention. Now they are.
I spent years at Zendesk watching enterprise account teams work the champion relationship with genuine skill. The best CSMs I worked with had champions who would go to the mat for them - call in political capital, push back against procurement timelines, escalate to their own leadership to protect a vendor they believed in. And in most cases, that worked. Because the renewal decision lived at the operational level, where relationship and trust carried real weight.
What I've watched shift since 2024 is that the renewal decision no longer lives there. Finance involvement isn't limited to large enterprise anymore - it's pushed down to mid-market accounts, to contracts that two years ago would have auto-renewed without a conversation. The approval chain has lengthened, the scrutiny has risen, and the champion who once had authority to sign off is now more of an internal advocate than a decision-maker.
An advocate needs evidence. Evidence they often don't have - because the CS team built the relationship, not the economic case.
The CS Motion That's No Longer Fit for Purpose
The traditional enterprise CS motion goes something like this: land the account, onboard successfully, drive adoption, run QBRs quarterly, manage executive relationships, secure the renewal. It's a solid motion. It produced strong results for years. The problem is that it is optimized for managing the champion layer, not for building the financial case that's now required at renewal.
Most QBRs cover adoption metrics, product utilization, roadmap previews, and relationship maintenance. Almost none of them, in my experience, regularly build and maintain a running calculation of what the platform has delivered in financial terms. The economic story gets assembled retroactively, usually in a panic, when a renewal is in jeopardy and someone in finance has started asking questions.
By then, it's too late. Not because the value isn't there - it usually is - but because you're asking a CFO to accept a business case you wrote under pressure, three weeks before the contract expires. No financial decision-maker worth their title signs off on that. They've seen vendor-constructed ROI analyses before. They're skeptical of them on a good day, and deeply skeptical when the analysis appeared only after scrutiny began.
The value needs to be visible continuously. Built incrementally. In language that finance actually speaks.
What the CS Motion Needs to Look Like Now
The shift isn't complicated to describe, though it takes real discipline to execute. The CS team's job is no longer just to make the champion happy. It's to ensure that at any point during the contract - six months in, twelve months in, three weeks before renewal - there is a clear, defensible answer to the CFO's question.
That means redefining success metrics from the start of the engagement, not at the end. Adoption rate is a proxy. The metric that matters to finance is what changed in the business because of the adoption. Faster ticket resolution is a proxy. The metric that matters is what that deflection translated to in cost terms, or what the headcount would have looked like without it. Revenue influenced by the platform. Cost avoided. Time recovered and reallocated. These are the numbers that hold up in a budget review.
It means building those numbers into the customer's language, using their internal benchmarks where possible, and updating them regularly - not just when renewal pressure appears. A running value summary, maintained by the CS team and reviewed with the champion quarterly, means the champion walks into their internal approval conversation armed rather than scrambling.
And it means expanding the relationship beyond the champion. Not replacing it - the champion relationship still matters enormously. But the CS team needs at least a working relationship with whoever in finance or operations will be asked to evaluate the renewal. That person doesn't need to be a product advocate. They need to understand what they'd lose if the contract went away.
The Conversation Your Champion Needs to Be Able to Have
Here's a practical test for any CS team right now. Take your top five accounts up for renewal in the next six months. For each one, answer this question: if a CFO asked your champion tomorrow to justify the spend in financial terms, could they? Not with enthusiasm - with numbers. With a business case that would hold up to a 20-minute finance review.
If the answer is no, you have three to six months to build it. That is enough time, if you start now. It is not enough time if you wait until the renewal conversation is already happening.
The champions who save renewals in 2026 are the ones who can walk into their internal review and say: here is what we paid, here is what we got, and here is what we'd have to do differently to replace it. That's not a relationship argument. It's an economic one. And the CS team's job is to put that argument in their champion's hands long before they need it.
