Economy slows down. Cut CS. AI arrives. Replace CS with agents. Board wants efficiency. Reduce CS headcount.
It is always something. And the response is always the same: defend, justify, prove your worth. Write the business case. Show the NRR numbers. Explain why you need the headcount.
This cycle is exhausting. And it never really ends. Not because CS teams are failing, but because CS has always been positioned as a cost center waiting to be challenged rather than a growth engine that changes the math entirely.
That framing is the problem. And right now, for the first time, there is a real way out of it.
Why CS Is Always on the Chopping Block
The pattern goes back to the beginning of the discipline. When economic pressure hits a company, leadership looks for places to reduce cost. CS is visible, headcount-heavy, and notoriously difficult to tie directly to revenue. Preventing churn is real work, but it is hard to prove a negative. You cannot point to the renewals that happened because of what your team did. You can only point to the ones that did not.
That is why I have always argued that CS needs to be commercial. Not just focused on retention, but actively driving expansion, revenue, and growth. When CS contributes to NRR in a way that leadership can see, the conversation changes. You are no longer defending your existence. You are pointing to numbers.
But even that is not enough anymore. Because now the question is not just whether CS is worth the cost. The question is whether CS needs humans at all.
What AI Actually Changes
Here is what is getting lost in all the noise: AI agents are not here to replace your CS team. They are not a cheaper version of your CSMs. The companies treating them that way are going to find out the hard way that what they built is a very efficient failure.
Customers expect an appropriate experience. That means human contact, real relationships, and genuine attention. No chatbot in front of your customers is going to replicate that. And if your version of AI in CS is throwing automation between your team and your customers, you are solving the wrong problem.
The right question is not how do we do the same things with fewer people. It is what could we do for our customers that we simply could not do before.
That is a completely different question. And the answer to it is what makes CS genuinely untouchable.
What Becomes Possible
When you stop asking CS to be leaner and start asking it to be more capable, the math changes completely.
Agentic workflows can absorb complexity that used to land on the customer. Instead of spending hours trying to get customers to do things they do not want to do, cannot do, or are unlikely to do well, your team does it for them. The customer gets the outcome. Your CSM gets their time back. And that time goes toward deeper, more valuable engagement with more customers.
Your team is not spread thinner. It is working at a level it could never reach before.
That is not efficiency. That is capability. And capability is what changes the conversation about what CS is worth to the company.
The Better Response
CS is at a crossroads again. In March 2026, we have got economic pressure, AI hype, and leadership asking hard questions all at once.
The old response is to defend, justify, and prove your worth. The better response is to use this moment to build something that was never possible before and make sure leadership sees it.
That is what agentic workflows make possible. Not just doing the same things faster. Doing things that could not be done. For more customers. At a level of depth and quality that redefines what CS actually is.
The teams that figure that out are not going to be on the chopping block. They are going to be the ones everyone else is trying to catch up to.
