SDR (Sales Development Representative)

# SDR (Sales Development Representative)

An SDR is a Sales Development Representative, the role traditionally responsible for the first stage of the outbound sales motion. The work spans researching accounts, building prospect lists, sending cold messages across email and LinkedIn, following up on the sequences they ship, and qualifying responses into meetings for an Account Executive (AE) to take. The job is heavy on coordination, repetition, and persistence. It is also the entry-level path into B2B SaaS sales for most companies, and the position most directly affected by the shift to agent-driven outbound.

The role took its modern shape in the late 2000s and early 2010s alongside the rise of inside sales and tools like Outreach and SalesLoft. By 2026 the average SaaS company has reduced SDR headcount relative to the 2022 peak, as the coordination work that justified the role has moved to agents and automation. The remaining work, judgment, voice, reply triage, concentrates in fewer reps each running larger books.

Why it matters

The SDR role is the canary for how AI is restructuring sales work. The job decomposes cleanly into tasks that an agent can do (list build, draft, follow up, schedule) and tasks that require human judgment (account selection, voice, reply nuance). Watching how companies split this work tells you more about the future of sales operations than any vendor roadmap will.

The historical model, twelve SDRs supporting six AEs, each SDR running 100-150 prospects in active sequences, is uneconomic for most companies in 2026 unless the gross margin and ACV are very high. The math broke when reply rates fell from the double-digit percentages of 2018 to the low single digits of 2023, because the same throughput now produces fewer meetings.

The replacement model is not zero SDRs. It is fewer SDRs, each operating more like an editor than a sender. The agent builds the list, drafts the messages, runs the sequences. The SDR reviews, approves, edits, handles non-trivial replies, and owns the relationship with the AE for handoff. The job becomes higher-skill and higher-stakes per message, with much less of the repetitive coordination work that defined the previous version.

This is good for the better SDRs and bad for the role as an entry-level rotation. The skill floor goes up. The volume goes up per rep. The ceiling on what a great SDR can produce is meaningfully higher than before.

Common pitfalls

The first is treating the SDR role as a pure activity quota in 2026. "Send 100 cold emails a day" was a coherent measurement when sending was the work. Now sending is mostly agent work and the SDR's value is in the judgment around it. Companies that keep measuring on activity tend to keep producing low-quality activity.

The second is failing to invest in the ICP work the SDR depends on. An SDR cannot fix a bad ICP at the message level. Companies that under-invest in ICP definition and then blame SDRs for low pipeline are pointing at the wrong layer.

The third is bad SDR-to-AE handoff. The handoff is the conversion point that determines whether the SDR's work translates into pipeline or evaporates. Most companies treat the handoff as informal calendar coordination. The cleaner version is structured handoff with explicit context, recent activity, and qualification notes.

The fourth is over-rotating SDR comp to meetings-booked. The metric is gameable. SDRs optimize for meetings that look good on paper but do not convert. Comp that includes pipeline progression or pipeline-sourced revenue (with a long enough measurement window) keeps the incentive aligned with the company's actual outcome.

How it shows up in agent-driven workflows

In Coil specifically, the SDR persona is one of the primary users alongside the founder doing their own outbound. The product is designed for both. An SDR using Coil does not send fewer messages. They send the same volume with much less coordination work, because the agent handles the list building, the sequence cadence execution, the dedup, and the follow-up scheduling. The SDR reviews drafts, approves sends, and handles the replies that need a human touch.

The interesting workflow change is the review queue. A traditional SDR spent a few hours a day on list-build and a few hours on sequence execution. The Coil-using SDR spends most of their time in the review queue, approving drafts, editing messages that need a sharper angle, and routing replies to the right next action. The work is more concentrated and more cognitively engaging per minute.

The revops function plays a larger role in this model because the SDR's effectiveness depends on the upstream artifacts (ICP, automations, suppression lists, sequence templates) being well-configured. The SDR cannot easily compensate for upstream weakness by working harder.

Related concepts

Cold outreach is the activity an SDR's job is built around. The activity continues. The operator changes.

Agent-driven outbound is the operating model that is reshaping the SDR role. Both are evolving at the same time.

RevOps is the function the SDR depends on for the operating environment. A good RevOps team makes the SDR effective. A bad one makes the role impossible.

Sequence cadence is the structured artifact that defines the SDR's daily work pattern. The cadence has not changed much. Who executes it has.

For more on how Coil thinks about the role transition, see the agent-driven lead gen pillar.