Everyone predicted AI would shrink CS teams.

The companies actually building with AI are hiring them.

That's worth pausing on.

Something structural is happening across SaaS right now. Not in one category. In all of them.

The CEO of Microsoft said the traditional application layer — SaaS basically — is collapsing into agents. a16z has been writing about it. Bain has been writing about it. It is not a prediction anymore. It is a direction.

What it means in plain language: your customers are not buying software to configure, maintain, and operate themselves. They are buying outcomes. The product is increasingly invisible. The result is what they are paying for.

This is not news to CS people. We have been saying "we sell outcomes not software" for a decade.

The difference now is it is actually becoming true.

Here is what is changing.

For most of SaaS history, there was a ceiling on what a CS team could do. You could advise. You could guide. You could encourage. But at some point the customer had to do the work themselves.

They had to import the data into the CRM. They had to write the email sequence. They had to come up with the content ideas. They had to build the workflow. You could sit on a call and walk them through it. But you could not do it for them — not without a professional services budget and a six-week project.

That ceiling is gone.

A CS team with the right AI tools can now just do it. Not guide the customer through it. Not create a ticket for it. Not add it to the next success review agenda.

Do it.

The CRM import they have been putting off for three months. The onboarding email sequence that has been a blank doc since they signed. The content calendar, the campaign brief, the internal training material. Blockers that used to sit on the customer's to-do list forever can now be removed in a conversation.

That is not support. That is the outcome itself.

This is why AI-first companies are hiring CS people.

Not despite AI. Because of it.

Someone has to own what the customer is trying to achieve. Someone has to know the goal well enough to look at every blocker and ask: can we remove this for them? Someone has to make the judgment call about what matters and what doesn't.

That is CS. It has always been CS.

The difference is that CS teams now have the execution capability to match the strategic understanding they already had.

The advisor who used to watch the customer struggle can now remove the struggle.

Most CS teams have not figured out what to do with this yet.

They are still running the 2019 motion. Quarterly check-ins. Health score reviews. Renewal calls. Chasing customers to do things the customer will never prioritize.

The teams that move first will look completely different in 24 months. Not because they hired more people or bought a better tool. Because they redefined what CS actually delivers.

Not guidance. Outcomes.

Not advice. Execution.

Not "here is how you do it." Done.

A word to the founders and revenue leaders reading this.

The instinct to cut CS headcount is not wrong. If your CS team is running the 2019 motion — reactive support, renewal coordination, chasing customers to do things they never will — that version of CS probably is a cost center. That version deserves to be restructured.

But here is what most leadership teams are about to get wrong.

They are going to cut CS at exactly the moment CS becomes capable of generating revenue it could never generate before.

It costs five times more to acquire a new customer than to expand an existing one. A CS team that is removing execution blockers for customers — not monitoring them, actually doing the work — is the highest ROI revenue motion available to a SaaS company right now. Not sales. Not marketing. CS.

The old CS team was managing churn. Barely justifying its cost.

The new CS team is driving expansion, compressing time to value, and compounding NRR in a way no new sales hire can replicate. Because the relationship is already there. The goal is already known. The trust is already built.

You do not cut that team.

You stop asking it to be a cost center and start building it to be a revenue engine.

The question is not how do we reduce CS headcount.

The question is how do we make CS the most revenue-productive function in the company.

The tools to do that exist now. They did not two years ago.

The question worth asking your team this week:

What are the three things our customers keep not doing — the blockers sitting between where they are and the outcome they bought for — and can we just do those things for them now?

Start there.