did ai kill sdr's?

You’ve seen the why — three launches in thirty days, the dialling factory closing. This is the how. No theory. The exact system I’d build if I were retraining for this seat starting Monday.

01 The role, in one line

You own the system, not the activity

The SDR was paid to run the motion — dials, emails, follow-ups. The AI GTM Engineer is paid to build and supervise the system that runs the motion, and to apply judgement at the few points where judgement decides the deal. Volume is now the machine’s job. Yours is targeting, offer, judgement, and governance.

Everything below is organised around one principle: automate the motion, gate the judgement.

02 The stack

Every stage, mapped to its engine

This is the whole motion, stage by stage — what now runs it, and the checkpoint where you stay in the loop. Tool names are examples; the categories are what matter.

ICP & targeting

Firmographic + intent signals (Clay, Apollo, intent feeds) piped into an agent that scores fit and surfaces accounts.

Your gate: you set and revise the ICP hypothesis. An agent can rank accounts; it can’t tell you who’s worth winning.

List build & enrichment

Agentic enrichment — Clay tables, scrape + LLM cleanup, dedupe, role mapping — built once, run continuously.

Your gate: QA the segments and kill the garbage before it sends. Bad data at scale is just faster damage.

Messaging & offer

AI drafts angle variants, personalises at the line level, A/Bs copy.

Your gate: you own the offer and the angle. This is the one thing the agents can’t originate — and the highest-leverage thing you do.

Sequencing & send

Outreach platform (Smartlead, Instantly, Apollo) running multi-channel cadence on autopilot.

Your gate: set the guardrails — volume caps, deliverability, domain health, brand rules.

Reply triage

An agent classifies replies (interested / objection / not now / referral) and drafts the response.

Your gate: you take every real conversation. Discovery is human. Always.

Booking & CRM hygiene

An in-CRM agent (Agentforce Coworker–style) books, logs, updates fields, sets next steps.

Your gate: mostly hands-off — you audit hygiene weekly, not daily.

Orchestration & governance

A governed workflow layer (Camunda ProcessOS–style) or a lead-agent / sub-agent setup (Claude multiagent, or build it yourself in Claude Code) ties the stages together.

Your gate: you’re the supervisor. You approve at the gates and own the audit trail.

03 The orchestration logic

How to wire the agents

Don’t build one mega-agent. Build a lead agent that delegates to specialist sub-agents — one for research, one for enrichment, one for drafting, one for reply triage — each with a narrow job and a clear output. The lead agent sequences them and hands the result to you at defined supervision points.

There are exactly four gates a human must hold:

The ICP gate — before a single list is built.
The offer gate — before any sequence goes live.
The conversation gate — the moment a reply becomes a human discussion.
The governance gate — deliverability, data, brand, and compliance, reviewed on a cadence.

Everything between those gates is the machine’s. That’s the whole design: a small number of high-leverage human decisions, wrapped around a motion that otherwise runs itself.

A small number of high-leverage decisions, wrapped around a motion that runs itself.

04 The 90-day path

From SDR to GTM Engineer

Days 1–30

Foundations — rebuild one play end to end

Map your current motion on one page — every stage from ICP to handoff.
Pick one orchestration tool and learn it deeply (Clay is the fastest on-ramp; Claude Code if you want to build).
Rebuild a single play end-to-end with agents — one ICP, one offer, one sequence, fully run by the stack with you on the gates.
Instrument it — track reply rate, qualified-meeting rate, and cost per booked meeting from day one.

Days 31–60

Leverage — multiply the motion

Add multi-agent orchestration — split research, enrichment, drafting and triage into specialist sub-agents.
Write the SOPs — document each gate so the system is repeatable, not in your head.
Shift your own metrics from activity to outcome — qualified pipeline and influenced revenue, not dials.
Run two or three plays in parallel across segments and compare unit economics.

Days 61–90

Own it — prove the math, claim the role

Run the full motion at the output of a small team with you plus the stack.
Prove the pipeline math — qualified pipeline per head and cost per meeting vs the old model.
Package it as a system — a documented, transferable playbook (this is your promotion case).
Make the role official — take the numbers to your leader, or to market. Don’t wait for a title; build the evidence and name the seat.

05 The judgement layer

What you never automate

The 20% that’s now the whole job. Run it through MEDDPICC and these stay human, permanently:

Economic buyer & champion — building trust with the signer and a champion who sells when you’re not there.
Identify pain & decision criteria — discovery that surfaces the unspoken pain is a conversation, not a form.
Reading intent live — knowing when a prospect is stalling, bluffing, or quietly on your side.
Owning the number — accountability doesn’t delegate to an agent.

Automate toward these moments. Never through them.

Start Monday — your first week

Write your ICP hypothesis in two sentences. If you can’t, that’s task one.
Open a Clay (or Claude Code) workspace and rebuild your enrichment for one segment.
Draft three offer angles by hand — then let an agent generate fifteen variants from them.
Wire one sequence to send through the stack with you holding the offer gate.
Set up tracking for reply rate, qualified-meeting rate, and cost per meeting. Baseline today.

One last thing

I break down a live build of this stack — agents, gates, the lot — in the newsletter. If this was useful, that’s where the next one goes deeper.

Subscribe to Automate & Hustle →