AI makes much of traditional sales and marketing work obsolete. At the same time, it makes GTM Engineering exponentially more important. Here's how agents, MCP, and LLM orchestration are changing the role, and what AI will never replace.
Over the past two years much nonsense has been written about "AI replaces sales." The reality is nuanced. AI makes large parts of sales and marketing work cheaper and faster. But the work that remains — strategic thinking, orchestration, building the systems that deploy AI — becomes more valuable, not less.
This is part 7 in the series. For the basics read What is GTM Engineering?. Here I dig into the specific implications of the AI era: which technologies actually change the work, where the data moat sits, and what AI won't solve.
The three waves of AI in GTM
To understand where we stand, mapping the three waves of AI adoption in GTM helps.
Wave 1 (2020-2023): Generative AI as writing assistant. Marketers used GPT-3 and GPT-4 to write copy, generate emails, and draft blog posts. Real but limited impact — 20-30% productivity gain for some tasks, but no fundamental change in how work was done.
Wave 2 (2024-2025): AI as personalization engine. Tools like Clay, Cargo, and countless AI-SDR platforms enabled personalized outreach at scale. Digital Applied's analysis of 100,000 emails showed AI-SDRs nearly matching human SDRs on reply rate (4.1% vs 5.2%). Work shifted: no longer "writing," but "orchestrating what AI writes."
Wave 3 (2026 onwards): Agentic AI with MCP. This is where we are now. Agents that don't just generate text but take actions — fetch data, update CRM, make decisions, call other agents. This is the transformation that's really changing GTM Engineering in 2026.
MCP: the missing protocol
The most important technical event in GTM-AI since GPT-4 is MCP — Model Context Protocol. Introduced by Anthropic in November 2024, adopted by OpenAI in April 2025, followed by Microsoft in July 2025 and AWS in November 2025. By March 2026, according to research, there were 10,000+ active public MCP servers and 97 million monthly SDK downloads, writes Truto in their MCP overview.
What is MCP? An open standard prescribing how AI models connect to external tools, data sources, and applications via JSON-RPC. For GTM it means: AI agents can talk directly to your CRM, email tool, enrichment providers, and data warehouse, without you having to build a separate integration for every combination.
Warmly's MCP guide for sales teams describes it: "MCP acts as a universal connector replacing dozens of point-to-point integrations between your CRM, email, chat, visitor identification, and outreach tools."
For GTM Engineers this changes everything. Before MCP, integrating an AI agent with a CRM was a weeks-long project — setting up webhooks, managing API tokens, writing data mapping, handling edge cases. With MCP it's hours of work. The effect: the barrier to "AI at production level" drops dramatically.
Five real AI use cases in GTM in 2026
Enough theory. Five use cases now running in production at B2B SaaS companies that I'm building for clients myself.
1. The sales call prep agent
An agent that automatically compiles a briefing for every scheduled call: company overview, recent news, organizational changes, tech stack, possible pain points, three strategic conversation openers. Input: the calendar event. Output: a Slack message 12 hours before the call with a PDF briefing.
Implementation: an orchestration layer (Claude or GPT-5 with MCP connectors to Google Calendar, HubSpot, BuiltWith, LinkedIn, news APIs). Build time: 5-10 days for functional V1. ROI: 200+ hours per AE per year reclaimed.
2. The inbound lead classifier
An agent classifying every new inbound lead within 30 seconds: fits ICP yes/no, urgency score, intent signals, suggested routing. The agent reads the form, enriches data, compares against historical conversion patterns, and makes a recommendation. RevOps approves the rules, GTM Engineering builds the system.
Implementation: a serverless function triggered by the CRM event, MCP calls to enrichment providers and the AI model, write back to the CRM. Build time: 2-4 weeks. ROI: response time drops from hours to seconds; high-intent leads served within 1 minute.
3. The churn predictor
An agent that weekly evaluates all existing customers: product usage patterns, support tickets, email sentiment, payment behavior, contract data. Output: a ranking with top-20 at-risk customers and suggested interventions. CSMs automatically receive a prioritized list.
Implementation: a daily-running workflow combining data from three to five sources and running it through an AI model for patterns. Build time: 6-10 weeks. ROI: 30-50% reduction in unexpected churn.
4. The outbound content personalizer
An agent that for every outgoing sequence step automatically adapts copy to the prospect: company-specific openers, industry-specific examples, personal triggers from recent behavior or news. Templates are no longer "merge field"-filled but contextually re-written.
Implementation: integration between your sequencer (Smartlead, Instantly), an LLM, and your enrichment layer. Build time: 1-3 weeks. ROI: reply rates that, in our measurements, are 2-4x higher than template-based sequences.
5. The RevOps QA bot
An agent continuously scanning the CRM for data issues: missing fields, duplicate records, invalid email formats, deals without owner, accounts without lifecycle stage. Output: a daily report and automatic fixes for obvious cases.
Implementation: a scheduled job traversing the CRM, evaluating rules (partly deterministic, partly via LLM for edge cases), and making changes or generating alerts. Build time: 4-8 weeks. ROI: data quality that, instead of degrading, automatically improves.
The data moat: where the real value sits now
The painful truth of 2026: AI models themselves are no longer the differentiator. Claude, GPT-5, Gemini, and open-source alternatives deliver comparable quality for most GTM tasks. The win sits elsewhere.
Digital Applied's research put it sharply: "Layers two and three are commoditized. Every sequencer does follow-ups. Every AI writes passable copy. Layer one — the data — is where campaigns live or die. Get that wrong and nothing downstream can save you."
That means: in 2026 the moat sits in data. Specifically:
- First-party data about your market: what do you know about your ICP competitors don't? Which signals have you encoded in your system that others miss? Which historical deal data has unique predictive value?
- Enrichment quality: how deep and how fresh is your enrichment? A waterfall with eight providers has better coverage than one. Vanderbuild's waterfall research documents lifts from 20% to 80% coverage.
- Signal velocity: how fast do you detect relevant buying signals? Companies reacting within 24 hours to a new Head of Sales hire win many deals that companies reacting after a month never even see.
The GTM Engineer's role in 2026: build the data moat. Not just connecting AI tools, but creating the fundamental asset AI runs on. That's not a one-week project. That's an investment over years.
What AI doesn't replace — and never will
With all enthusiasm about AI, it's important to honestly call out what AI doesn't replace. Three things still purely human work even in 2030.
Strategic positioning. Which ICP do you choose? Which message do you carry? Which markets do you enter? These are decisions requiring context, judgment, and vision LLMs don't have. AI can show you options, but the choice remains a leadership decision.
Deep customer relationships. In high-ACV deals (say, $100K+ ARR), trust wins, not speed. An AI agent can prep a conversation, but the conversation itself — the subtle moments of mutual understanding, empathy at a setback, hearing what isn't said — remains human work. Anyone who thinks AI agents will close enterprise deals has never closed an enterprise deal.
Creative breakthroughs. The positioning that wins your market, the GTM experiment turning the wheel, the insight opening a new category — that remains human work. AI sees patterns in what is. Humans see what doesn't exist yet.
For GTM Engineers: these three domains aren't your turf. Your job is building tools making strategists, AEs, and visionary founders more effective. Not replacing them.
Three stubborn misconceptions
Finally, three misconceptions about AI-in-GTM I hear weekly and that need clearing up.
Misconception 1: "With AI we don't need a sales team anymore." Nonsense. What changes is what sales people do. Less repetitive work, more strategic work. Less volume, more quality. A six-person sales team with good AI tools often performs better than a twelve-person team without. But 0 sales people consistently underperforms in B2B with serious deal sizes.
Misconception 2: "AI-SDR tools do all outbound work." Half true. Digital Applied's research showed AI-SDRs nearly matching humans on reply rate but landing in spam three times more often. The message: AI output without GTM Engineering foundation (deliverability, data quality, signal detection) isn't an improvement. It's automated mediocrity.
Misconception 3: "We buy an AI tool and we're done." The biggest misconception of all. An AI tool is an ingredient, not a recipe. What really matters is how you integrate the tool with existing systems, what data you feed it, and what you do with the output. That's not a tool choice, that's engineering work.
The GTM Engineer's role in 2026: orchestrator, not builder
An interesting shift I see: the GTM Engineer's role itself changes in 2026. Before 2024 it was "someone who builds integrations." Now it's "someone who orchestrates AI agents and systems."
Concretely: less Python writing, more prompt engineering. Less API mapping, more MCP server choices. Less ETL pipelines, more agent workflows. The work stays technical but shifts up one level of abstraction.
For those learning the trade: SQL and basic Python remain essential. But what's increasingly important is understanding LLM behavior (why a model hallucinates, how to steer it, how to measure quality), agent design (designing multi-day workflows where multiple agents collaborate), and evaluation (knowing an AI system does what it should).
How do you start with AI in GTM Engineering?
Practical advice: don't start with "let's set up an AI strategy." Start with one problem.
Which repetitive task takes most of your sales/marketing team's time? Briefings prep? Lead classification? Email personalization? Pick one. Build an AI solution for that one problem. Measure the effect. Only after that works, add a second use case.
Many companies try five AI projects simultaneously. None work well, nothing delivers ROI, and after six months everyone's cynical about AI. Better: one project per quarter, fully developed and measured.
In the final post of this series I cover what needs to be in place before you begin with GTM Engineering — including the AI components — and how we help you get there.