AE vs SDR in one sentence
Direct answer. A sales development representative owns prospecting, initial engagement, and qualification; an account executive owns discovery, solution alignment, commercial progression, and close. The boundary is the accepted sales conversation—not a calendar event with missing context.
Salesforce describes SDRs as top-of-funnel specialists and AEs as middle- and bottom-funnel sellers. That is a useful starting point, but job descriptions do not prevent duplicate outreach, poor meetings, or arguments over credit. The operating system needs an explicit state change, an evidence packet, and a rejection path.
This comparison owns the general role boundary. If the decision is specifically whom a founder should hire first, use first sales hire: AE or SDR. If one person will own the whole motion, see the full-cycle AE role.
Compare responsibilities and measures
| Dimension | SDR | AE |
|---|---|---|
| Primary job | Create and qualify credible sales conversations | Turn qualified conversations into a buyer decision |
| Typical entry state | Target account, inbound inquiry, or sourced prospect | Accepted meeting or qualified opportunity |
| Core activities | Research, outreach, response handling, initial qualification, routing | Discovery, stakeholder mapping, evaluation, proposal, negotiation, close |
| Evidence produced | Identity, source, observed need, timing clue, meeting purpose, touch history | Problem, impact, decision process, stakeholders, next step, commercial status |
| Useful measures | Accepted conversations, show rate, acceptance quality, suppression defects | Stage conversion, qualified pipeline, win/loss, cycle movement, forecast quality |
| Primary failure | Optimizing booked meetings regardless of fit or readiness | Repeating qualification, ignoring handoff context, or accepting false pipeline |
Company titles vary. Some “BDRs” perform outbound SDR work; some SMB AEs prospect and close. Use the work and state ownership above, not the label on a business card.
Separate qualification from discovery
Qualification asks whether the conversation is worth routing: is the person real, the account eligible, the issue relevant, the timing plausible, and the meeting purpose understood? Discovery asks what the buyer is trying to change, how the current process works, who is affected, what evidence will support a decision, and what happens next.
The same call can contain both, especially in a founder-led or full-cycle motion. Keep the records separate anyway. A lightweight qualification result might be “eligible account, security leader requested a workflow review this quarter.” Discovery should preserve the buyer’s own problem statement, impact, stakeholders, constraints, and agreed action. Treating the first sentence as complete discovery creates shallow opportunities.
Practical exit test. The SDR state ends when the AE can explain why the conversation exists and decide whether to accept it without asking the buyer to repeat the entire prior exchange.
Build the SDR-to-AE handoff contract
A useful handoff is a small, sourced packet, not a paragraph of enthusiasm. Require only fields that change the AE’s next action:
- Identity: account and contact IDs, role, verified channel, territory, and current owner.
- Origin: inbound source or outbound selection basis, observed signal, URL or system event, and timestamp.
- Interaction history: messages sent, replies, call notes, objections, and explicit preferences.
- Qualification: why the account is eligible, the prospect’s words about the issue, timing clue, and known disqualifiers.
- Meeting contract: scheduled time, attendees, stated purpose, preparation promised, and desired next decision.
- Governance: consent or lawful-basis record where applicable, suppression result, recording expectations, and CRM authority.
The AE must return one of four dispositions: accepted, rejected with a reason, needs more evidence, or rerouted. “No response” should trigger an escalation queue, not leave both people assuming the other owns follow-up.
Set the accepted state before deciding attribution. An accepted conversation can earn SDR credit even if the AE later discovers no opportunity. That keeps the SDR from being judged on facts only a deeper discovery could reveal. It also prevents the AE from being forced to create pipeline to reward good top-of-funnel work.
Route common edge cases
| Event | Next owner | Required action |
|---|---|---|
| Prospect does not attend | SDR until an agreed limit | Record no-show, send contextual reschedule, then recycle or close |
| Wrong person, useful referral | SDR | Preserve referral source, verify new contact, restart qualification |
| Existing open opportunity | Current AE or opportunity owner | Suppress parallel outreach and append new evidence to the active record |
| Existing customer asks about expansion | Named account or customer owner | Route by customer-account rules; do not create a net-new lead |
| Meeting occurs but no relevant problem | AE disposition, then recycle | Record discovery result without manufacturing an opportunity |
| Prospect asks to stop | System authority | Apply suppression before any role can schedule another touch |
These branches belong in the sales workflow, not in a private spreadsheet. The system should make current ownership visible and block a second sequence when an opportunity or suppression record has higher authority.
Measure the system, not just each role
Meeting count and closed revenue are too far apart to diagnose the handoff. Track the transition itself:
- Acceptance rate by source: accepted handoffs divided by reviewed handoffs.
- Show rate: held first conversations divided by scheduled first conversations.
- Evidence completeness: accepted packets containing every required handoff field.
- Rejection reasons: mutually exclusive codes such as ineligible account, wrong role, no evidence, duplicate, or timing.
- Post-acceptance progression: accepted conversations that reach the team’s qualified-opportunity exit criteria.
- Buyer restart rate: calls where the buyer must repeat context already captured upstream.
Review these by source and segment. A low acceptance rate may indicate poor SDR qualification, but it can also reveal inconsistent AE standards. Sample rejected packets together before changing targets or compensation.
Choose a split or full-cycle model
Split SDR and AE roles when prospecting volume, research, response routing, and qualification are enough continuous work to support specialization—and when AEs have sufficient accepted demand to spend their time on discovery and close. The handoff cost must be lower than the focus gained.
Use full-cycle AEs when the market is still being learned, deal volume is low, founder context matters, or the sale requires deep expertise from the first interaction. One owner reduces handoff loss, but prospecting must remain a protected responsibility rather than work performed only when pipeline falls.
Use a hybrid when SDRs source and research accounts but the AE sends the first high-context message, or when SDRs qualify inbound while AEs self-source named accounts. Define separate entry rules so hybrid does not mean “everyone owns everything.” For role-specific rep workflows, see Gangly for AEs and the detailed SDR role guide.
AE and SDR operating checklist
- One role owns each prospect or opportunity state.
- Qualification and discovery have separate evidence requirements.
- The handoff packet preserves source, history, buyer words, and governance state.
- The AE returns an explicit disposition.
- No-shows, duplicates, customers, and suppressions have defined routes.
- SDR credit does not require the AE to create false pipeline.
- Leaders review transition health alongside role-level output.
The role choice matters less than the boundary quality. A clean SDR-to-AE transition carries the buyer’s context forward, makes ownership unambiguous, and lets each specialist do the work the role exists to perform.