BDR versus SDR does not have one universal answer. Both titles commonly describe early-pipeline sales development work: researching, prospecting, qualifying, nurturing, and creating meetings or opportunities for account executives. Some companies split inbound and outbound. Others reverse the labels, divide by segment, use one title for seniority, or merge the roles.
The practical question is not “Which acronym is correct?” It is “Who owns each source, decision, queue, handoff, and outcome?” This guide uses official Salesforce descriptions as examples of title variation, not as rules every team must copy.
The short answer
A BDR and an SDR may be the same job or different jobs. Salesforce says the terms are often used interchangeably. In Salesforce’s own published pipeline model, BDRs focus on outbound prospecting and SDRs qualify inbound demand. Treat that as one operating pattern, then write your own role contract.
For candidates, ask about lead source, activity mix, quota, opportunity credit, account ownership, handoff, pay, and promotion criteria. For leaders, publish those answers before hiring. A familiar title cannot repair ambiguous work.
Why the titles conflict
The labels evolved inside different organizations, so their boundaries are local. Salesforce’s BDR explainer says BDR and SDR are often interchangeable and sometimes differ by inbound or outbound work, career progression, or company convention.
Salesforce Trailhead’s description of its own pipeline engine is more specific: BDRs focus on outbound calls and pass opportunities to AEs, while SDRs qualify inbound website, chat, and phone demand. Another company may use “SDR” for all development reps or assign BDRs to partnerships and new markets.
That variation makes title-based benchmarks fragile. Before comparing headcount, compensation, activity, or performance, compare actual job definitions and denominators.
Choose an organization pattern
Pick the split that reduces queue conflict and creates a clear learning path.
| Pattern | BDR | SDR | Main risk |
|---|---|---|---|
| Source split | Outbound accounts and cold prospects | Inbound leads and hand-raisers | Arguments over mixed-source accounts and attribution |
| Segment split | New markets, enterprise, or strategic accounts | SMB or scaled qualification | Different difficulty hidden under one quota |
| Seniority ladder | More complex accounts or later development step | Entry-level qualification | Title inflation without changed authority |
| Unified team | One title owns inbound and outbound within a territory or account book | Priority conflict unless queues and service levels are explicit | |
A source split works when inbound volume is steady and routing is reliable. A segment split works when research, stakeholders, and qualification differ materially. A unified role fits a small team when one person can own a coherent account set without being pulled between an unlimited inbound queue and outbound targets.
Write the role operating contract
A one-page operating contract is more useful than a long job description. Include:
- Purpose: the pipeline decision this role owns.
- Sources: inbound forms, events, partners, target accounts, product activity, signals, or recycled leads.
- Queue: routing rules, priority, ownership conflicts, and reassignment.
- Qualification: required evidence, disqualifiers, uncertainty, and who can override.
- Channels: permitted email, phone, LinkedIn, events, and account research behavior.
- Handoff: the artifact, destination, service level, rejection reason, and recycling path.
- Credit: meeting, accepted opportunity, sourced pipeline, influence, and rules for duplicates.
- Development: skills, observed evidence, coaching cadence, and progression criteria.
Do not write “qualified meeting” without defining both words. A booked calendar event, held meeting, accepted AE handoff, and created opportunity are distinct states.
Design the AE handoff
The handoff should let an AE accept or reject the work using visible evidence. Include account and contact identity, source, relevant context, problem or goal in the prospect’s words, stakeholders identified, timing evidence, prior interactions, promised next step, consent or channel state, open questions, and the development rep’s confidence.
The AE must respond with accepted, rejected, needs clarification, duplicate, already owned, or recycle—plus a reason. Silence should not become acceptance. Set a service level for review and automatically return stale items to a named queue.
Use the sales call qualification guide to define evidence without converting a development rep into a form-filler. Qualification should reduce uncertainty enough for the next decision; it should not require every enterprise buying answer before the first AE conversation.
Measure the system, not the label
Measure each stage with a denominator the team can reproduce. Track assigned records, attempted records, reached people, meaningful conversations, meetings booked, meetings held, handoffs submitted, handoffs accepted, opportunities created, sourced pipeline, recycle reasons, duplicates, and time in queue.
Segment results by source, territory, account fit, tenure, and channel before comparing reps or roles. An outbound BDR and an inbound SDR do not operate the same population. Activity count without eligibility and outcome state rewards busy queues, not useful pipeline.
For career context, use the sales careers map; for day-to-day detail, use the BDR workflow and SDR role guide. Then make the internal role definitions discoverable to candidates, reps, AEs, managers, and RevOps. Clear work beats a standard acronym that does not exist.