The Operationalization Gap Separating AI-Fluent Leaders from the Rest by James Kaikis
The leaders pulling ahead rebuilt the job before touching the tools. Here's their playbook.
The Gap You Can’t Close with a Better Tool
There’s a divide opening up in B2B revenue right now that most leaders are underestimating. The Haves have rebuilt how they work around AI. The Have-nots plugged in the tools and kept moving. The distance between them is widening fast.
I’ve seen both sides of it up close this year. A CEO at a B2B software company reached out to me recently. He was fluent in AI himself and frustrated that his GTM team wasn’t. They had access to everything he had. They just hadn’t internalized what to do with it.
Another team spent two months debating “ChatGPT vs. Gemini” before rolling out Claude — missing entirely that the argument itself was the problem. Same gap, different shape. The tools weren’t the issue. The thinking was.
Mindset is the performance differentiator in B2B revenue. McKinsey’s 2026 Global B2B Pulse draws the same line: deployment vs. operationalization. Deployment is a procurement event, whereas operationalization is a leadership decision about how the team works, what it measures, and what it’s allowed to rebuild. Almost every B2B revenue org has deployed AI. Very few have operationalized it.
The Haves changed how their teams think about the work before they changed what tools the team uses to do it. That order matters.
The AI-Fluent Leader Moves Differently
The signal I trust is what I’m seeing across the market. Here’s my version, sharpened for GTM: mindset first, workflow second, tools third. Curiosity precedes process change, which precedes tool change.
I spend a lot of time in rooms with revenue executives. The leaders getting this right are focused on one thing: what their teams can do now that they couldn’t six months ago. Pipeline coverage 2x’ing without new headcount. Reps managing 2–3x the opportunities. Higher deal velocity. Leads surfaced from sources nobody had time to work before. Specific people on their teams operating at a level the org chart didn’t anticipate.
Three Moves the AI-Fluent Leader Is Making
They open up a new tier of performance at the top.
Meet Meghan — your best AE three years running, the one everyone else shadows. She’s been compensating for a broken system with sheer volume of hours. She has more deals in motion than she can give real attention to, and more territory than she can cover. The org has been rewarding her heroics and call her a great performer because of them, without questioning whether the job itself is designed right.
The AI-fluent leader doesn’t look at Meghan and see a productivity gap. They see a system that needs to be rebuilt. The real question is which parts of her job should be AI-led, human-in-the-loop, or automated entirely.
Get the redesign right, and Meghan doesn’t burn out. She becomes the 10x AE — running 30 accounts with better judgment than she applied to 10. The job she’s operating in 12 months from now looks nothing like the job she’s grinding through today.
Most leaders are benchmarking AI against the old job definition. The leaders pulling ahead are watching their best people redefine the job, and protecting the conditions that let it happen.
They build the conditions before the playbook.
This is the move most leaders skip, because it’s the hardest one to put on a dashboard. Experimentation has to be protected time, owned by someone, with permission to fail visibly.
Sharon Martin (SVP of Solutions Engineering, Alteryx) stood up volunteer AI guilds at the team’s revenue kickoff. The pitch wasn’t “we need to hit an adoption number.” It was “grow your career, solve company-level problems, get CEO visibility.”
She got more volunteers than she had room for. Within their first few months, the guild’s work was showing up in deals, in customer outcomes, and in the team’s appetite for harder problems.
You don’t turn skeptics into believers by mandate. You let them experience what’s possible. The volunteer guild becomes the SWAT team. The SWAT team builds repeatable motions. The laggards don’t get dragged along. They get pulled by people who already cleared the path.
They redesign the org around the work AI now makes possible.
This is the move that separates the leaders pulling ahead from the ones running the old playbook faster.
Gartner’s 2025 CSO survey found 58% of reps will need reskilling by year-end, and 74% of CSOs believe seller skills will require significant evolution. The successful few are doing something harder: rewriting roles and consolidating functions so the work maps to how it’s actually being done — asking not “what does an AE do?” but “what jobs need to get done, and who’s best positioned to do them?”
It’s the same logic behind why every early-stage AI startup is hiring “GTM” instead of AE, SE, or CSM. They’re hiring around the duties that deliver measurable revenue outcomes, not an org chart from 1995.
The industry-scale signal that this is happening is now public. Salesforce is hiring thousands of Forward Deployed Engineers because the work of selling and delivering enterprise software is expanding into a category that didn’t exist 18 months ago — a massive structural acknowledgment that the work has shifted.
Kyle Norton (CRO, Owner) rewrote the BDR job description — lead research, account enrichment, and pre-call research came out of the JD entirely. Those tasks moved to a central AI system, which gave the BDRs their attention back to do what humans actually do best: building relationships, navigating buying committees, closing the conversion. The job got smaller in scope and bigger in impact.
Another leader, at a growth-stage revenue intelligence platform, oversaw SE, PS, and CS as a single function. His CS team had been stuck in “administrative jail,” firefighting, order-taking, passing information. He trained them on value realization: how to deliver it with every customer, how to recognize when they were creating it, and how to compound it.
I hear stories like these every week. Leaders are redrawing AE territories around pipeline coverage instead of account counts. They’re rebuilding comp models around outcomes the old job description never accounted for. They’re collapsing the lines between SE, AE, and CS because the work no longer respects the org chart.
Different starting points, same pattern: role definitions and functional boundaries are constraints, not givens. The leaders who see it early have a head start.
Before the Gap Is Visible, It’s Already Set
The GTM leaders I trust most are moving faster on adaptation, not procurement. They’re building teams where curiosity is the entry-level expectation, experimentation is protected, and the job description gets rewritten by the people doing the work.
The next 18 months will make this gap impossible to ignore. The Haves are going to look obviously different from the Have-nots — in revenue growth, in talent retention, in board confidence. By the time this is fully visible in the metrics, the divide will already be set.
The losers are still defending the org chart. The winners are rewriting it.
Which camp do you want to be in?
James Kaikis is the co-founder of SolutionExec, a private network for Solutions leaders in B2B SaaS, and the founder of GTMshift, a consultancy for GTM operators. He has spent his career across startups, scale-ups, and enterprise organizations including Salesforce, with experience spanning sales, solutions, and customer experience.
Explore More of Topline
Your Comp Plan Has a Zombie Liability — and Credits Just Made It Worse by Amy Konary
Credits Are Here. Is Your Comp Plan Ready?
What to Watch Next
 | A guest post by
|