53% of GTM Teams See No ROI From AI. The Problem Is Not the Tools.
June 8, 2026
A recent survey of 30+ GTM leaders found that 53% are seeing little to no impact from their AI investments. Not because they picked bad tools. Not because they lack budget. Most of them are running the same tools as the teams that are seeing results.
The difference is how they managed the change.
If you are in RevOps, Sales Ops, or Marketing Ops and you have rolled out an AI tool that reps are not using, this post is for you. Here is what is actually going wrong, and what operators who are getting results are doing differently.
The Real Adoption Gap: It Is Not Technical
Here is the failure pattern most GTM teams fall into. Leadership buys a tool, IT configures it, someone runs a lunch-and-learn, and then the tool sits unused while reps go back to doing things the way they always have.
The problem is that we treat AI rollouts like software rollouts. Flip the switch, send the training link, track license utilization, and wonder why nothing changed.
AI tools require a different kind of adoption. They demand behavior change, not just feature awareness. And behavior change in a quota-carrying environment is hard. Reps have a number to hit. They are not going to experiment with something unfamiliar when the cost of failure is a missed quarter.
The teams seeing real results understand this. They do not ask reps to figure out where AI fits. They make the use case obvious, the workflow frictionless, and the value immediate.
Start With One Workflow, Not a Platform Strategy
The instinct when rolling out AI is to go broad. "Let us get everyone using it for prospecting, call prep, deal summaries, and follow-up emails." That is a recipe for zero adoption everywhere.
The operators who are winning start with exactly one workflow. They pick the use case where:
- The current process is visibly painful (reps complain about it)
- The output is easy to evaluate (you can tell immediately if it is good)
- Success is measurable in a way reps care about (time saved, meetings booked, pipeline generated)
A common starting point: AI-assisted account research before outbound calls. A rep spends 20 minutes manually pulling together context before a prospecting call. An AI workflow cuts that to 3 minutes and produces a better output. That is a win a rep can feel on day one.
Get that one workflow humming. Get reps talking about it. Then expand.
The Manager Layer Is the Real Bottleneck
Here is something most RevOps teams miss: the frontline manager is the make-or-break variable in any GTM change initiative.
You can train every rep in the org. But if their manager is not reinforcing the new behavior in 1-on-1s, pipeline reviews, and deal calls, the behavior will not stick. Managers shape what reps pay attention to. If a manager never asks "did you use the AI research before this call?", reps learn fast that it does not matter.
Before you roll out anything to reps, get the managers on board first. Not just informed, actually using the tool themselves. A manager who has personally felt the value of a workflow will enforce adoption naturally. A manager who only got a slide deck will not.
This is the same principle that governs any process change in GTM: leadership behavior sets the floor for rep behavior. AI is no different.
Practically, this means:
- Run your manager enablement session two weeks before rep rollout
- Give managers a short checklist of behaviors to reinforce (specific questions to ask in 1-on-1s)
- Include AI tool usage in your CRM hygiene or process compliance checks so it shows up in data managers already review
Build a Feedback Loop Into the Rollout
Most AI rollouts are one-directional. Ops builds the workflow, trains the team, and then waits to see if utilization goes up.
The teams getting durable results treat rollout as a two-way conversation. They set up a lightweight feedback mechanism from day one: a Slack channel, a biweekly 15-minute sync, a simple form. The goal is to surface what is actually happening when reps use the tool.
Is the AI output accurate enough to use, or are reps spending more time editing it than they would have spent doing it manually? Is the workflow embedded in the tools reps already live in (CRM, Slack, email), or is it a separate tab they have to remember to open? Are there edge cases the workflow breaks on, like enterprise accounts, or certain verticals?
This feedback is gold. It lets you iterate quickly before bad habits form. It also signals to reps that ops actually cares how the workflow performs in the real world, not just on a slide.
The teams that are crushing it with AI are not running perfect workflows from the start. They are running good-enough workflows that they improve based on real usage data. That is a discipline, and it starts with building the feedback loop on day one.
What Actually Moves the Number
The GTM leaders seeing big returns from AI share a few things in common. They are not waiting for vendors to hand them a turnkey solution. They are building lightweight workflows themselves using tools like Clay, n8n, or Zapier layered on top of general-purpose LLMs like Claude or ChatGPT.
More importantly, they measure the right things. Not "are reps using the tool?" but "did the workflow change an outcome we care about?" Meetings booked. Time spent on research. Pipeline from targeted accounts. Conversion rate from outbound sequence to call.
If your AI rollout metrics stop at utilization, you will never know if it is working. Tie the workflow to a downstream number, and review that number in the same cadence you review any other GTM metric.
The 47% of GTM teams with no AI agents in production are not behind because they lack tools or budget. They are behind because they have not made the change management investment to turn a tool into a habit, and a habit into a result.
That gap is closeable. It just takes a different kind of work.
If you are working through an AI rollout on your GTM team and want a second set of eyes on your change management approach, let us talk.