He built something remarkable two and a half years ago.

Using AI tools that barely existed at the time, he automated a prospect enrichment database that his company had been running manually, slowly, expensively, and inaccurately for years. He was 20% more accurate than the human scrubbers. Ten times faster. A fraction of the cost. He did it before anyone at his company had approved "enterprise AI." He did it before most of his peers had even heard of the tools he was using.

Then he moved into a field sales leadership role. And he stopped.

Not because he lost interest. Not because the technology stopped mattering. He stopped because the job demanded everything, and there was no protected space to think, experiment, or build. The deep work that had made him a pioneer got crowded out by the urgent work of hitting a number.

I think about how that must feel.

You were ahead. You saw it coming before most people did. You did the hard, unglamorous work of figuring it out when there was no playbook. And then life, a promotion, a bigger team, a harder quarter, quietly moved you away from the thing you'd built. Not because you chose to leave it. Because the current just carried you.


Two and a half years later, he sat across from me and said something I haven't stopped thinking about: "I look back at that project and think, what have I done with AI since then?"

That question wasn't self-pity. It was honest reckoning. And I've heard versions of it from some of the sharpest leaders I work with.

They had a moment where they were genuinely ahead. A project, a breakthrough, a bet that paid off. And then the demands of the role took over, and the thing that made them distinctive went quiet. Not gone. Just quiet.

What makes it harder is that the world didn't slow down while they were busy. The pace of change in AI right now is relentless. New models, new tools, new applications, sometimes week over week. For someone who was early and then stepped away, catching up doesn't just feel like learning. It can feel like loss.


The Verdict vs. The Information

Here's what I want to say to that feeling: it's not a verdict. It's information.

The gap isn't about capability. The leaders I'm describing are often the most capable people in the room. They're not behind because they can't keep up. They're behind because they never built the infrastructure to keep going, and that's a very different problem with a very different solution.

Early advantage doesn't compound on its own. It requires maintenance. And maintenance requires protected time, personal systems, and a decision to treat your own development as a business requirement, not a nice-to-have, not a someday project, but a real requirement with real constraints and real design.

At an executive dinner recently, a senior leader described spending two and a half hours individually researching every guest before the event. Not skimming. Researching. Preparing specific questions. Curating the conversation. Logging everything into a personal knowledge system afterward.

My client's reaction wasn't admiration. It was recognition. That's the standard. And I'm not there.

That recognition, that honest, clear-eyed look at the gap, is actually the beginning of something. Not the end.


Three Things That Actually Move the Needle

  1. Name your use cases before you name your tools. The leaders pulling ahead aren't the ones with the most tools. They're the ones who got specific about what they need: I want to never miss a follow-up with a high-value relationship. I want to walk into every customer meeting better prepared than anyone else in the room. I want my action items from every meeting to surface automatically. Start there. The tools follow.
  2. Treat your own development as a business requirement. Not a goal. Not a resolution. A requirement, with the same rigor you'd apply to any deliverable. What are the constraints? What are the non-negotiables? What does "done" look like? When you frame it that way, the question stops being "do I have time?" and starts being "how do I design this to fit?"
  3. Protect against your own intensity. Some of the most capable people I coach are also the most prone to hyperfocus. They don't dabble, they go deep, stay up late, and come out the other side having built something real. That's a superpower. It's also a risk. Know your pattern. Build in the circuit breakers before you need them, not after.

The two-year gap is real. But it's not a measure of who you are. It's just the distance between where you were and where you're starting from again.
You were early once. That instinct didn't go anywhere.

Joelle Kaufman

More GTMFlow Blogs on AI and Leadership