How Do You Bring Your Team With You When AI Arrives and the Stack Is Shrinking?

computer server graphic
November 17, 2026
orange stacks graphic

This is Part 2 in a short series answering the questions CROs and RevOps leaders raised at the CRO networking event in London

In This Series

  • Part 1: Can We Trust Our Data Enough to Let AI Act On It?
  • Part 2: How Do You Bring Your Team With You When AI Arrives and the Stack Is Shrinking? (You are here)
  • Part 3: How Do You Explain Your Value When You Sell More Than One Thing, and Through Partners? (Coming soon)

Most revenue leaders are being asked to do two things at once. The board wants AI adopted across the team. Finance wants fewer tools and a smaller software bill.

On paper these are separate projects. To the people doing the work, they feel like one long disruption. The tool a rep finally learned last year is being switched off, and in the same quarter they're told to start working with an AI assistant they didn't ask for.

It's worth remembering how the tool creep happened. Every one of those tools was bought to solve a real problem. Someone needed better call notes, cleaner contact data or a faster way to build a proposal. Remove the tool without moving that job somewhere else, and the problem comes straight back as a spreadsheet nobody can see.

So before anything is switched off, write down what each tool actually does for the people using it. Not what it was sold to do. What it does on a Tuesday afternoon. That list tells you where each job needs to land after consolidation, and it gives you an honest answer when someone asks why their favourite tool is going.

Order matters here. Consolidate first, then introduce AI on the simpler stack. AI is only as useful as the data it can reach, and an assistant working across eight disconnected tools will give patchy answers. Patchy answers in the first month are how a team decides AI doesn't work and quietly stops using it.

Then start with your managers, not your reps. If sales managers still run pipeline reviews from their own spreadsheets, reps will read that as the real signal, whatever the launch email said. When managers use the new view in every one-to-one, and ask questions the AI helped them prepare, the team follows without being told.

Enablement also needs to be about the work, not the feature. A training session on what the assistant can do is forgotten by Friday. Showing a rep how to prepare for tomorrow's renewal call in five minutes instead of thirty is remembered, because it gives them something back that same week.

Finally, measure the right thing. Logins tell you people opened the tool. They don't tell you whether anything changed. Better signals are whether call preparation time has dropped, whether forecast calls are shorter and calmer, and whether managers are coaching from shared data rather than chasing updates.

None of this needs a large change programme. It needs leaders who are honest about what's going away, clear about what replaces it, and visibly using the new way themselves.

People rarely resist change itself. They resist losing something that works without being shown what takes its place. Answer that for every tool you remove and every AI capability you add, and adoption stops being a campaign.

‍

Want to find out more?

Has this triggered any questions, and want to keep the conversation flowing? We'd love to talk.

Contact us
chevron right

Experience the difference

Firms that respond within an hour are nearly 7x more likely to have
a meaningful conversation than those that wait longer.
loupe logo on image of people

Simplify and accelerate your document management

See how T4S can automate your records and document archiving
from Salesforce to OpenText Content Manager.
T4S call to action