SDR vs BDR vs AE: Sales Roles Explained (And When You Need Each)

Sales job titles are a mess. SDR, BDR, AE, AM, plus a dozen company-specific variations — and different organizations use the same acronym to mean different things. For a founder building a first sales team, the alphabet soup makes a genuinely important decision look more confusing than it is.

Underneath the titles, B2B sales breaks into three core jobs: find opportunities, qualify opportunities, and close opportunities. SDR, BDR, and AE are the conventional names for who owns which job. Understanding the split — and, crucially, when not to split it — is one of the more consequential structural decisions an early sales org makes.

This guide defines the three roles cleanly, explains the full-cycle alternative, lays out when to specialize, how to fix the handoff problem, how comp differs by role, and which role to hire first.

Definitions: SDR, BDR, AE

An SDR — Sales Development Representative — owns outbound prospecting. They identify target accounts, run cold outreach across email, calls, and LinkedIn, and work to turn cold strangers into qualified meetings. The SDR's product is a booked, qualified opportunity handed to a closer. They generate pipeline; they do not close it.

A BDR — Business Development Representative — is, by the most common modern convention, the inbound counterpart to the SDR. BDRs work leads that have already raised a hand — demo requests, content downloads, trial signups — qualifying them and routing the good ones to a closer. The honest caveat: many companies use SDR and BDR interchangeably, or flip the definitions entirely. What matters is not the acronym but the function: outbound-sourced versus inbound-sourced qualification.

An AE — Account Executive — is the closer. The AE takes qualified opportunities, runs discovery, demos, proposals, and negotiation, and carries the number — a revenue quota. The AE owns the deal from qualified opportunity to signed contract. SDRs and BDRs feed the pipeline; the AE converts it into revenue.

The full-cycle rep: when one person does everything

At an early-stage company, the SDR/BDR/AE split usually does not exist, and that is correct. The role is the full-cycle rep — one person who prospects, qualifies, and closes the entire deal end to end. Most B2B sales motions begin this way, often with the founder as the original full-cycle rep.

Full-cycle has real advantages beyond just being cheaper. There is no handoff, so no opportunity leaks between roles. The rep owns the whole relationship, so context is never lost in a transfer. And full-cycle reps learn the entire sales motion deeply — which makes them excellent future managers and gives the company a complete, first-hand understanding of how its sales actually work before it commits to a structure.

The downside is focus. A full-cycle rep is constantly context-switching between cold prospecting and active closing, and those two modes demand different energy and different headspace. The near-universal failure pattern: when closing gets busy, prospecting stops, because closing is urgent and prospecting is not. Pipeline dries up, then closing dries up a quarter later. Full-cycle is the right model early, but this whipsaw is exactly the pain that eventually justifies specializing.

When to split roles

There is no exact headcount that triggers specialization, but there are clear signals. The clearest is the one just described: your full-cycle reps are consistently sacrificing prospecting to handle closing, and pipeline creation has become lumpy and unreliable. When the cost of that inconsistency outweighs the cost of another hire, it is time to split.

The usual first split is to separate prospecting from closing — add SDRs so AEs can focus entirely on working and closing qualified pipeline. The economic logic is specialization: an AE's time is expensive and best spent closing, so handing cold prospecting to a more junior, lower-cost SDR is simply better leverage. A focused SDR also out-prospects a distracted AE, so total pipeline goes up.

Splitting inbound qualification into a dedicated BDR role typically comes later, and only once inbound volume is high enough to warrant a full role. If inbound is a trickle, AEs can field it directly. When it becomes a meaningful, steady stream, a BDR ensures inbound leads get a fast, consistent response — and speed-to-lead on inbound is a major win-rate lever. Specialize when the volume justifies the role, not before, and not as cargo-culting of how big companies are structured.

The handoff problem and how to solve it

The moment you specialize, you create handoffs — and handoffs are where opportunities go to die. An SDR books a meeting and passes it to an AE; a BDR qualifies a lead and routes it. Every transfer is a chance for context to be lost, for the ball to be dropped, for the prospect to feel the seam between two people who do not share a brain.

Bad handoffs do real damage. The AE walks into a meeting cold because the SDR's notes were thin or buried in another tool. The prospect re-explains everything they already told the SDR, which is annoying and erodes trust. Or the lead simply sits in limbo because nobody is clearly accountable for the next step. Specialization gains nothing if the handoffs leak away the advantage.

Two things solve it. First, a defined process: explicit qualification criteria so everyone agrees what "qualified" means, a clear SLA on response time, and unambiguous ownership at every step. Second, shared context that travels with the opportunity. When the SDR's notes, the engagement history, the lead score, and the deal record all live in one platform that the AE already uses, the handoff is seamless — the AE inherits the full picture, no re-keying and no lost detail. Revnator is built this way: contacts, deals, sequences, and tasks share one system, so a handoff is a status change, not a risky data migration between tools.

Compensation structures by role

The three roles are compensated differently because their jobs are different, and getting comp right is how you actually drive the behavior each role exists to produce. AEs are paid on a roughly even base-plus-commission split, with commission tied to closed revenue and quota attainment. Because the AE directly controls the number, their pay should swing meaningfully with it — that is the whole point of the role.

SDRs and BDRs carry a higher base relative to variable pay, because they do not close deals and so cannot be fairly held to a revenue number. Their variable comp is tied to the outputs they do control — qualified meetings booked, or qualified opportunities accepted by an AE. The single most important design choice here: pay SDRs on qualified opportunities, not raw meetings. Pay on raw meetings and you get a flood of low-quality meetings that waste AE time. Pay on accepted, qualified opportunities and you align the SDR with what the business actually needs.

The principle across all three roles is to pay for the outcome the role controls. AEs control closed revenue, so pay them on it. SDRs and BDRs control qualified pipeline, so pay them on that — and define "qualified" tightly so the metric cannot be gamed. Comp is not just cost; it is the steering wheel for each role's daily behavior.

How a Sales OS supports all three roles in one platform

A practical worry when specializing is tooling: do SDRs, BDRs, and AEs each need their own software? The old stack pushed teams that way — sequencers built for SDRs, a CRM oriented to AEs, separate inbound tools for BDRs — which fragmented the data and made every handoff a cross-tool migration. That fragmentation actively works against a specialized team.

A unified Sales OS supports all three roles in one place, which is exactly what a specialized team needs. The SDR runs outbound from AI-Native Sequences with email, LinkedIn, and call steps. The BDR works inbound from Lead Capture Forms that AI-score hot leads at submission and auto-create contacts. The AE works the pipeline with AI win-probability scoring on every deal. And because it is all one platform, an opportunity flows from SDR to AE — or BDR to AE — without leaving the system or losing context.

Revnator is designed for exactly this. Contact Intelligence scores every lead 0 to 100 so SDRs and BDRs can prioritize; AI-Native Sequences power outbound; Lead Capture Forms handle inbound; the AI Sales Pipeline gives AEs scored deals; and the Sales Operations module coordinates tasks across all of it. One platform, every role, no handoff tax — and AI on every plan, so even a small specialized team gets the scoring and automation that used to require an enterprise budget.

Building your hiring sequence: which role to hire first

So which role do you hire first? For almost every early-stage B2B company, the answer is an AE — or more precisely, a full-cycle rep who can prospect, qualify, and close. Until you have proven that someone other than the founder can run the entire motion and close deals, hiring SDRs is premature. SDRs generate pipeline, and pipeline with nobody proven to close it is just expensive activity.

So the typical sequence: the founder sells first and establishes a repeatable motion. Then hire one or two full-cycle AEs and confirm the motion transfers to non-founders. Once those AEs are consistently closing but visibly capped by the time prospecting takes, add SDRs to feed them. Add a dedicated BDR later still, when inbound volume genuinely justifies a full role.

The mistake to avoid is hiring for specialization before you have product-market fit and a proven sales process. A specialized team is an optimization — it makes a working motion more efficient. It cannot create a working motion that does not yet exist. Hire full-cycle first, prove the motion, then specialize step by step as volume and pipeline pressure demand it. And give the team one platform that supports every role, so each split makes the org faster instead of more fragmented.

Structure your team around the work, not the titles

SDR, BDR, and AE are just names for three jobs: find, qualify, close. Early on, one full-cycle person does all three, and that is the right call. As you grow and prospecting starts losing to closing, you specialize — SDRs for outbound, BDRs for inbound, AEs to close — but only when volume justifies it, and only with comp and handoffs designed so specialization actually pays off.

Whatever structure you choose, the team works best on one platform. Revnator gives SDRs AI-Native Sequences, BDRs AI-scored Lead Capture Forms, and AEs an AI-scored pipeline — all unified, so opportunities flow between roles with no handoff tax and no lost context. AI is on every plan, setup is self-serve, and there is a free tier to start. Structure your team around the work, and give that work a Sales OS built to carry every role.