Abe Dearmer

The SDR Split Already Happened. The AE Split Is Next.

Portrait of Abe Dearmer
· 12 min read
A brass compass resting open on a weathered wooden surface, soft directional light from upper left casting a long shadow, deep earth tones and oxblood accents, painterly editorial illustration

The most common question I get from sales leaders right now is some version of: “Is AI going to replace my SDRs?” They are asking the wrong question, and the wrong question is expensive. What actually happened to the SDR role is not elimination. It is bifurcation. The role split in two. And the same split is now arriving for Account Executives, Customer Success managers, and engineers. The operators who see it first will have 18 months on the ones who don’t.

The Split That Already Happened to SDRs

The SDR role did not disappear when AI outbound tools became reliable. It separated into two distinct jobs with different required skills, different metrics, and different futures. One job manages the AI volume machine: sequences, domain reputation, delivery rates, intent-signal routing, and ICP scoring. The other does the work AI cannot do yet: specific account research, personalized first touches, video outreach, and the first conversation that requires a real human to read the room.

I saw this happen in slow motion, and then all at once. Teams kept the original SDR title, added AI sequencing tools, and watched their top performers leave within 12 months. What had happened was not a productivity improvement. It was a structural redesign that nobody named. The person who was excellent at nuanced first conversations found herself managing a volume machine she had no patience for. The person who was excellent at systems and throughput found himself on cold calls he had no talent for. Both were still called “SDR.” Both were measured on the same quota.

The first essay I wrote on the bifurcation thesis called this out for the SDR role specifically: AI Campaign Managers own the volume machine. Sales Development Specialists own the 20% AI cannot win. That post named the pattern in early 2026. Since then, I have seen more operators reach the same conclusion through retention problems than through intentional redesign.

The split is real. The title catch-up is slow. Teams are still calling both jobs “SDR” while measuring both on the same KPIs, which guarantees the volume-machine hire outperforms the relationship hire on every metric that can be tracked easily, and the relationship hire eventually leaves.

That was the SDR story. The same structural split is now arriving for the roles further up the funnel.

The 11x Signal Operators Are Misreading

Job seeker searches for AI roles on Indeed have grown 11x since ChatGPT launched in November 2022, according to Indeed’s Hiring Lab analysis. The growth came in two waves: the first right after ChatGPT, the second from mid-2024 onward following the releases of Claude 3, Llama 3, and GPT-4o. By early 2026, searches for AI-related roles were at all-time highs.

The signal is real. The interpretation most operators take from it is wrong.

The most common read is: “People are retraining because AI is replacing existing jobs.” The second most common is: “I should hire an AI specialist.” Both misread what the data is showing.

AI job searches are still under 1% of all job searches on Indeed, while AI skill requirements appear in roughly 5% of all job postings. The gap between what job seekers are looking for and what employers are listing is the real signal. Employers are not posting for new “AI jobs.” They are posting for existing roles with new skills embedded. The person who fills an AE role in 2027 needs to know how to work with AI tools for their function. But the job is still “Account Executive,” not “AI Sales Specialist.”

What the 11x growth shows is that the market has noticed something fundamental is shifting. What the market has not figured out yet is the correct frame. The correct frame is not elimination. It is bifurcation. The existing role is splitting into two halves, and the question is which half you are in, not whether there is a new job title to chase.

Most operators wait for the market to settle on the new titles before they redesign. That wait costs 18 months.

Where the AE Role Is Splitting Right Now

The AE bifurcation is underway, and it follows the same pattern as SDRs. One half of the AE role is being absorbed by AI: qualification scoring, demo preparation research, follow-up email drafting, proposal first drafts, CRM hygiene, and meeting summaries. The other half is becoming more human, not less: running discovery conversations that require genuine pattern recognition, navigating multi-stakeholder buying committees, and building the kind of trust that closes a $200K deal with a CFO who does not like salespeople.

Here is the AI side of the split in concrete terms. AI tools in 2026 can score an inbound lead against your ICP before a human touches it. They can pull a 3-page account research brief in 12 minutes. They can draft a personalized follow-up from meeting notes. They can generate the first version of a proposal from a template and prior deal data. This work took skilled AEs 2 to 3 hours a day. It now takes a tool and a 10-minute review.

Part of what makes this split visible is the time data. Research on what AI tools actually do to the sales day shows that a significant portion of the traditional AE role is already automatable with current tooling, but most teams are running it manually out of habit, not because it requires a human.

According to Harvard Business Review’s research on digital integration in sales, solution selling and account management still require the human capacity to navigate organizational politics, read buying committee dynamics in real time, and adapt a pitch to what a room is telling you mid-conversation. AI cannot replicate that within the 18-month horizon that matters for your current comp planning.

The AEs who will outperform in 2027 are not the ones who use AI tools the most. They are the ones who figure out which part of their current job is getting automated, hand that half to the tooling, and invest the freed time into getting much better at discovery and relationship work. The AEs who will struggle are the ones who add AI tools to an unchanged motion: running the same full-cycle process, just faster. Faster is not bifurcated. Faster is just faster.

What the Customer Success Split Looks Like

Customer Success is the third role splitting along the same line, and the automation infrastructure is already furthest along. Health scoring, renewal alerts, onboarding sequences, product-usage nudges, and escalation routing are handled at scale by CS platforms at most growth-stage SaaS companies. The human CS work takes a different form: the conversation that saves a churning account, the QBR that changes a decision-maker’s mind, the expansion ask that requires knowing the customer’s Q3 priorities. None of that has been automated, and shows no signs of being automated soon.

What most CS organizations have not done is acknowledge that they have already bifurcated their function de facto, while continuing to call both halves “Customer Success Manager” and measuring them with the same NPS and renewal metrics.

The low-touch half needs different success criteria: how many accounts are receiving timely automated outreach, how quickly are risk signals being flagged, how clean is the health data. The high-touch half needs different criteria entirely: how many strategic accounts have a documented QBR conversation, what is the multi-year retention rate on accounts the specialist owns, what is the expansion rate per high-touch account.

Running both on the same NPS average measures neither. It guarantees you are underpaying the specialist for relationship results that don’t show up in the aggregate, and overpaying the automation operator for health scores that look good because the system is working, not because a person intervened.

The CS split is often the most sensitive conversation to have internally because it implies that some CSMs are being asked to do high-stakes relationship work they were never hired for, and others are doing automation work that could be owned differently. The organizational implications are real. So is the cost of not having the conversation.

The Two Questions Every Operator Should Run on Each Role

Before redesigning anything, answer two questions for each customer-facing role: what does AI already do better than a human in this function at scale, and what does the buyer or customer specifically need a human for in this function that AI cannot provide convincingly?

The automation boundary runs between the answers to those two questions. Everything to the left of that line belongs in the AI half. Everything to the right belongs in the specialist half.

RoleAI half (automation layer)Human half (specialist layer)
SDRSequences, domain health, ICP scoring, reply routing, volume cadencesPersonalized first-touch, video outreach, account-specific research, first conversations
AEQualification scoring, demo prep research, follow-up drafts, proposal assembly, CRM hygieneDiscovery conversations, multi-stakeholder navigation, deal closing, relationship trust
CS ManagerHealth scoring, renewal alerts, onboarding sequences, escalation routingStrategic QBRs, churn rescue conversations, expansion asks, champion development

The warning when running this exercise: do not outsource the diagnosis to your AI vendors. Vendors optimize for their tool, not for your org design. A sequencing vendor will tell you the tool handles everything on the left side of the table and can also reach some things on the right. They are telling you what they want to be true, not what is operationally true in your specific buying motion.

This is the same logic as building the no-list before the yes-list for any AI deployment. Define what AI cannot do in your function before you build the automation layer around what it can. The yes-list expands over time as the tools improve. The structure persists even as the line shifts. Doing the diagnosis once gives you a framework that stays useful even as the AI capability boundary moves.

The operators who have run this exercise on their own teams consistently find the same thing: the split is already visible in their performance data. Their top AEs have informally stopped doing the left-side work themselves. They just haven’t been given formal permission to stop, or the rest of the team hasn’t been redesigned around them.

The Hiring Implication No One Wants to Sit With

The volume-machine half and the high-stakes specialist half need different hiring profiles, different comp structures, and different development paths. We have been pretending otherwise because we call both halves by the same job title. That pretense is getting expensive.

The volume-machine hire is operations-minded, data-literate, comfortable with systems and process, and measured on throughput and coverage. They would be miserable in 6 high-stakes discovery conversations a week. Their value is in running the engine for 400 accounts a month with consistent quality and zero chaos. Sequence hygiene, domain reputation management, intent-signal routing. That is the work they find energising. Put them in a closing role and they underperform and eventually leave.

The high-stakes specialist is communication-brained, high-EQ, comfortable with ambiguity, and measured on relationship quality and ACV. They would underperform doing sequence management and domain health work. Their value is in the 6 conversations a week that close the $200K deal. Put them on volume-machine work and you have a bored, talented person who leaves in 8 months.

These have never been the same person. Every sales leader reading this can think of someone on their current team who fits one description and someone who fits the other. What they often cannot tell you is which job title each person holds, because right now, both titles are probably “Senior AE” with a territory.

The promotion problem is real too. The person who excels at the high-stakes specialist work is not necessarily the right manager for a team of them. The person who excels at the volume machine is often the one who gets promoted because their KPIs are easier to read. Both are being set up for roles that do not match what they are actually good at.

The founder lessons that survive a go-to-market redesign are almost all versions of the same hard insight: the org chart you built for the last phase of growth is wrong for the next one. This is one of those moments. The question is whether you redesign it intentionally now, or wait for the retention data to force your hand.

What the Next 18 Months Actually Look Like

The operators who redesign their go-to-market roles now will spend 6 months looking slower than their competitors. The headcount stays flat while the role design shifts. The team runs two slightly blurry motions for a quarter while the split becomes clear. Outside observers see a team “figuring things out.”

By month twelve, the picture is different. The volume machine is running at higher throughput, operated by people who are good at it and measured on what matters for it. The specialist work is running at higher quality, done by a smaller group with more time and more of the right conversations. The AI in B2B sales organizations that reach this state fastest are not the ones with the best AI tools. They are the ones with the clearest definition of what the human is supposed to be doing inside the motion.

This is the same compounding dynamic I wrote about in the disciplined AI manager piece from May: the first six months look like slow progress because the institutional advantage is not visible until month twelve, when competitors are still running undifferentiated full-cycle teams on the same motion they used in 2024.

The AI 2027 research on the junior engineer turmoil documents the same split happening in engineering: junior engineers are bifurcating into automation orchestrators and high-judgment specialists. The frame holds across functions because the dynamic is structural, not specific to any one role. Anthropic’s research on what AI agents can reliably do explains why the high-judgment work is the last to go: the capability ceiling for AI on tasks requiring contextual human trust is not moving as fast as the capability ceiling for AI on tasks requiring throughput and pattern matching.

The 11x surge in AI job searches tells me the market has noticed something is changing. The operators who act on the bifurcation frame now, not by hiring AI specialists but by redesigning existing roles, will be the ones the market is catching up with in 2028. The ones who wait for the job titles to settle before they redesign will be the ones catching up.

There is a version of this where the hesitation is reasonable. Role redesign is disruptive. Conversations about who belongs in which half of a job are uncomfortable. Changing comp structures mid-year is a headache. I understand the instinct to wait for more signal.

The problem is that more signal arrives as retention problems, not as a polite market update. The AE who is excellent at the specialist work figures out their role has changed before management does, and goes somewhere that has already named what they are.

The right time to have the redesign conversation is before that person walks. Explore more essays on this thread at dearmer.com.au.

Which half of your AE team’s current job description is still pretending the split hasn’t happened?

Frequently asked questions

Is AI eliminating SDR and AE jobs in B2B sales companies?

No. The observed pattern is bifurcation, not elimination. AI automates the high-volume repeatable parts of each role: sequences, scoring, research, follow-up drafts. The specialist work — personalized first conversations, multi-stakeholder navigation, high-ACV deal closing — is still done by humans. The job is splitting into two distinct roles, not disappearing.

What does the AI half of an SDR role look like in practice?

The AI half of SDR work covers sequence management, domain health monitoring, ICP scoring, reply classification, and outreach volume. One person can manage ten times the pipeline touchpoints through AI tooling. The remaining work — specific account research, personalized video, first conversations requiring real human judgment — belongs to the specialist half.

How should operators decide which part of each sales role to automate?

Answer two questions per role: what does AI already do better than a human at scale in this function, and what does the buyer specifically need a human for that AI cannot provide convincingly? The automation boundary runs between those answers. Build the no-list for each role before you build the automation layer.

Why do most operators redesign sales roles too late?

Most operators wait for a retention signal — high performers leaving because the role no longer matches their skills, or consistent underperformance because headcount is structured for the wrong work. By the time that signal arrives, competitors who redesigned earlier have already built 12 to 18 months of institutional advantage.

What profile should I hire for the specialist half of an AE role?

Look for communication depth, multi-stakeholder pattern recognition, and a track record of closing complex deals through relationship quality rather than volume. These hires are uncomfortable doing 50 light discovery calls a week, and should be. Their value is in the 6 conversations a week that require genuine judgment and human trust.

Will bifurcating sales roles require more total headcount?

Not necessarily. Most operators who run this exercise find both profiles already exist within their current team, titled and measured identically. Splitting the role clarifies expectations, improves retention on both sides, and typically holds headcount flat while improving output quality. The volume machine gets more throughput. The specialist gets more of the right conversations.

How does role bifurcation in sales connect to AI agent deployment strategy?

The same logic applies to both. Just as every agent needs a no-list before a yes-list, every role needs a clear split before you add AI tooling. Operators who deploy AI into an undefined role end up with neither good automation nor good human judgment. Define the split first, then build the tools around it.

Sources & references

  1. Indeed Hiring Lab — AI Job Search Growth Report · Primary source for the 11x growth in job seeker searches for AI roles since ChatGPT's launch, with data on the two major surge periods and the gap between job seeker searches and employer AI skill requirements.
  2. AI 2027 Forecast · Research-backed scenario that introduced the 'scatterbrained employee who thrives under careful management' frame for AI agents, and documents the junior engineer turmoil as the parallel role split happening in engineering.
  3. Harvard Business Review — Integrating Digital Tools into Sales Strategy · Research on how solution selling and account management still require human capacity for organizational politics and buying committee navigation, even as AI tools absorb the repeatable preparation work.
  4. Anthropic — Alignment and Capability Research · Published research on what AI agents can reliably do at scale versus where human judgment remains the irreplaceable input, informing the boundary between the automation and specialist halves of each split role.