Are Your SDRs Ready for AI?

Over the past year, every sales leader I have spoken to has asked some variation of the same question:

"How do we get our SDRs using Claude?"

Or more recently:

"Should we be building MCPs?"

They are sensible questions, but they are often being asked at the wrong time.

At Stakki, we have helped organisations introduce Claude, GPTs, Clay, MCPs and AI-powered workflows into their outbound teams. We have seen first-hand how transformative these tools can be when they are introduced correctly. We have also seen the damage they can do when companies mistake AI adoption for sales enablement.

In fact, across the organisations we have worked with, we have found something interesting. When we coach the fundamentals first, simplify the sales process and then introduce AI with clear use cases, around 85% of SDRs improve their performance.

That statistic is not because AI does not work.

It is because people do.

AI Isn't the Problem. Premature AI Adoption Is.

There seems to be a race to become "AI native." Sales leaders are encouraging SDRs to build Claude projects, experiment with MCPs and automate as much of their day as possible. The intention is good, but in many cases, the outcome is not.

We have watched teams become increasingly dependent on AI before they have mastered the fundamentals of outbound sales. Rather than improving prospecting, AI often becomes somewhere they disappear for hours each day, building prompts, refining workflows and chasing efficiency while the basics begin to slip.

The reality is simple. If an SDR struggles with account ownership, qualification, CRM discipline or consistent prospecting today, Claude is not going to solve those problems. More often than not, it simply amplifies them.

When Claude Becomes a Second CRM

One project we recently worked on highlighted this perfectly.

The company wanted to embrace AI across its sales organisation. Every SDR had access to Claude. Some were building increasingly sophisticated workflows, while others were experimenting with MCPs and conducting almost all of their research inside AI before eventually updating the CRM.

Individually, people felt more productive.

Collectively, the business became less efficient.

Knowledge was trapped inside personal Claude conversations instead of being captured in the CRM. Different SDRs developed different ways of working. Managers struggled to understand how decisions had been made. Opportunities reached Account Executives missing context, and the CRM slowly stopped reflecting reality.

Nobody intended for that to happen. It happened because Claude had quietly become the team's second operating system.

Even Your Best SDRs Can Accidentally Create Bad Habits

Interestingly, this is not usually driven by underperformers.

In one case, one of the strongest SDRs on the team passionately believed everyone should become "Claude native." Their workflow genuinely made them more productive, and there was no question they were getting value from AI.

The problem was that nobody else could replicate what they were doing.

The thinking happened inside Claude. The reasoning stayed inside personal projects. The process could not be coached because nobody could see it, and very little of that knowledge found its way back into the CRM where the wider team could benefit.

They were not doing anything wrong. They were simply optimising for their own productivity rather than the organisation's productivity.

Those are two very different things.

Your CRM Should Still Be Your Operating System

This is where many AI conversations lose their way.

The CRM should never become somewhere you update after you have finished working. It should remain where the work happens.

It is where account ownership lives. It is where qualification happens. It is where pipeline is measured. It is where marketing, SDRs, AEs and leadership all stay aligned around the same information.

Claude should enhance those workflows, not replace them.

If your SDR spends four hours inside Claude and fifteen minutes updating HubSpot at the end of the day, you have unintentionally created two systems of record. One works for the SDR, while the other works for everyone else. That disconnect creates friction across the entire revenue team.

Build the Skills Before You Build the AI

One of the first things we often do with new customers surprises people.

We reduce their reliance on AI.

Not permanently, and certainly not because we are against it. We do it because we want to establish the behaviours that great sales teams are built on before introducing technology that accelerates them.

That means focusing on calling confidence, prospecting discipline, CRM hygiene, account ownership, qualification, multithreading and consistent workflows. Once those habits become second nature, AI starts to deliver exactly what it promised.

Research becomes faster. Preparation improves. Admin reduces. Follow-ups become more consistent.

AI stops replacing thinking and starts supporting it.

That is why we have seen around 85% of SDRs perform better when AI is introduced after the fundamentals are in place.

Coach AI Like You Coach Cold Calling

Nobody gives a new SDR a dialler and expects them to become exceptional on the phone.

We coach them. We listen to calls. We review objections. We improve discovery. We reinforce good habits until they become second nature.

AI deserves exactly the same approach.

Simply handing someone Claude and telling them to "be more efficient" is no different from giving them Salesforce and expecting them to become a top salesperson overnight.

Technology has never replaced capability. It simply amplifies it.

Great salespeople become faster.

Weak habits become faster too.

When AI Becomes an Accelerator

If your SDR team already has strong fundamentals, AI becomes one of the biggest productivity gains available.

Teams that consistently hit activity targets, maintain excellent CRM discipline, understand account ownership, qualify opportunities well and collaborate effectively across SDRs, marketing and Account Executives are perfectly positioned to benefit from Claude and MCPs.

At that point, AI is not compensating for missing skills. It is removing repetitive work and giving your best people more time to sell.

The AI Stack We're Seeing Work Best

When those foundations are in place, we have seen several tools integrate brilliantly with Claude and emerging MCP workflows.

Surfe allows SDRs to create and enrich CRM records directly from LinkedIn, keeping the CRM accurate while removing manual administration.

Fathom captures meetings, summaries and action items, giving Claude structured context without relying on handwritten notes or memory.

Apollo combines prospecting and engagement data that Claude can use for research and preparation while ensuring activity still flows back into the wider sales process.

Final Thoughts

We are incredibly optimistic about AI. Claude is one of the most impressive products we have used in years, and MCPs have the potential to fundamentally change how sales teams work.

But they are not shortcuts.

The organisations seeing the biggest returns are not the ones telling every SDR to become AI native. They are the ones investing just as much time coaching AI adoption as they do coaching cold calling, qualification and prospecting.

Before asking whether your SDRs are ready for Claude, ask a simpler question. Are your SDRs ready for AI?

Because if they cannot consistently prospect, qualify, multithread and manage opportunities today, AI will not solve those problems.

It will simply hide them behind better prompts.

The future of sales is not SDRs spending all day inside Claude. It is SDRs with exceptional sales fundamentals, using AI to remove friction so they can spend more time building relationships, creating opportunities and doing the work that only humans can do.

Thinking about introducing AI into your sales organisation? Stakki helps businesses design practical sales technology stacks that reduce friction and improve adoption. Learn more at stakki.io