Reps defend tools that make them money.They tolerate tools that report on them.

Every sales leader has lived this sequence. You evaluate carefully, buy the tool, run the training session, announce it in the team meeting. Three weeks later, usage is a ghost town, and you're in 1:1s asking people to please log in.

The standard diagnosis is that salespeople resist change. It's wrong, and it's worth killing, because it leads leaders to buy the wrong things and then blame the wrong people.

Reps adopt new tools instantly when they want to. Nobody had to mandate ChatGPT. Nobody ran an enablement session for the rep who found a notetaker, or built their own prompt library on their own time, on their own card. Salespeople are arguably the fastest adopters in the building when the thing in front of them passes one test.

The test is simple: does this make me money, or does it report on me?

Every sales tool lands on one side

Reps run this evaluation in the first week, and they're almost never wrong.

Tools that report on them exist so someone else can see their work: activity dashboards, call scoring leaderboards, forced fields whose only output is a cleaner report for a meeting the rep isn't in. The rep does extra work; someone else gets the value. Every CRM field that exists purely for management reporting is a small tax with no receipt. Reps comply with these tools at the minimum viable level, game them where convenient, and quietly abandon them the moment enforcement blinks.

Tools that make them money shorten the path to commission: the prep that surfaces the thing that wins the meeting, the follow-up that goes out while the deal is warm, the nudge that catches a going-quiet champion before the quarter dies. The rep does less work; the rep gets the value. These don't need enforcement. They spread rep to rep, faster than any rollout plan, because the best marketing in a sales org is one rep asking another how they did that.

Here's the uncomfortable part for leaders: most of the sales stack of the last decade sat on the reporting side. Not because vendors were malicious, but because the buyer was the leader, so the value was pointed at the leader. The rep was the data source, not the customer. An entire generation of sellers learned that "new tool" means "new surveillance," and that's the prior your next rollout walks into.

Why this matters more in the AI wave

AI raises the stakes on both sides of the line.

Pointed the wrong way, AI is the most powerful reporting-on-you technology ever built: every call scored, every email graded, every minute accounted for. Reps can smell this instantly, and they will treat it exactly like they treated the last decade of surveillance tooling, with compliance theatre and quiet sabotage. If your AI rollout feels like a camera, adoption is dead on arrival no matter what the demo looked like.

Pointed the right way, AI is the first technology that can genuinely sit on the rep's side of the line at scale: doing the after-call admin nobody gets paid for, prepping them before every meeting, drafting the follow-up in their voice, watching their deals for risk while they sell. Not observing the work. Doing the work.

Same underlying technology. Opposite reception. The difference is purely who the value points at.

The dual test a sales system has to pass

Here's the thing though: leaders do need visibility. The forecast has to be real, coaching needs to be grounded in what's actually happening in deals, and the team's best way of working should run across everyone. None of that is surveillance. It's the job.

So the real bar for any AI system in sales is a dual test:

The rep test: does each rep get paid back, personally and immediately? Less admin, better prep, faster follow-up, deals that don't slip. If the rep's honest answer is "this thing works for me," you pass.

The leader test: does the leader get the truth without taxing the reps for it? Clean CRM, visible pipeline, one standard running across the team, without a single extra field for anyone to fill in.

Most tools pass one test and fail the other. Rep-side copilots make individuals faster and leave the leader blind. Reporting suites give the leader dashboards and make every rep's day slightly worse. The trick, and it's the entire design brief, is that the visibility has to be a byproduct of work the rep already wanted done. When the system does the rep's admin, the clean data the leader needs simply falls out the back. Nobody was reported on. The work just got done, and the truth became visible on its own.

The tell: what happens when you take it away

You can't detect any of this in a demo. You detect it by watching what reps defend.

When a tool is surveillance, removal is met with relief. When a tool makes reps money, removal is met with a fight. We've watched a rep mid-deal on the biggest opportunity of his year message us directly when a pilot lapsed because he didn't want to run the deal without it. One of our customers' AEs describes it as "we're basically married to Grw at this point." That's not what compliance sounds like. That's what a tool on the rep's side of the line sounds like.

It's also, for what it's worth, the strongest evaluation signal a buyer can get. Run the pilot, then watch what happens when it's time to turn it off.

Buy for the people who carry the quota

The adoption fear that haunts every sales software purchase, "will my team actually use this?", has a clean answer: they'll use what pays them.

So before your next rollout, ask the only question that predicts adoption: within the first week, what does each individual rep get out of this? If the honest answer is "better data for me," you're buying a reporting tool and you should expect reporting-tool adoption.

Grw was built to pass both tests: it does the work behind every deal for the reps, and the visibility leaders need falls out as a byproduct. Book a demo, and if you want the real evaluation, put it in front of your most skeptical rep first.