The two titles sit at the top of the sales funnel. The pay is usually similar. The career ladder is nearly identical. What changes is who starts the conversation: the prospect, or the rep.
The most common split is that an SDR (sales development representative) qualifies inbound leads that come in from marketing, while a BDR (business development representative) runs outbound prospecting into accounts that have never heard of you. Terminology varies by company, so some orgs flip the definitions or use the titles interchangeably. The real difference is motion: inbound reactive versus outbound proactive.
Six things to know before you post a job req, accept an offer, or build a team around either role. The titles blur in practice. The work does not.
In the most widely cited convention, SDRs qualify leads that marketing generated. BDRs cold-prospect into named accounts that have never raised a hand. The SDR works a queue of warm requests. The BDR builds a list, writes sequences, and dials strangers. Same funnel, opposite starting point.
HubSpot often uses SDR and BDR interchangeably. Salesforce historically split them along inbound and outbound lines. Outreach and other sales-tech vendors use yet another convention where BDR is the senior title and SDR is the junior one. Before accepting a job or writing a scorecard, read the job description, not the acronym.
When two titles exist on the same team, the practical difference is motion. One person reacts to signals (form fills, demo requests, chat sessions, trial starts). The other creates signals (cold email, cold call, LinkedIn, event follow-up). The skills do not fully transfer, which is why some companies hire specifically for each.
For the two roles at the same company, base salary and on-target earnings tend to land in the same band. Quota structure can differ (SDRs are often paid on meetings held and opportunities created, BDRs on sourced pipeline and sometimes closed-won revenue), but the headline comp number is rarely the thing that distinguishes them.
Both roles are the standard on-ramp to a closing seat. The next step for either title is usually AE (account executive), followed by senior AE, team lead, and eventually sales manager or RevOps. Lateral moves between SDR and BDR are common. The path to the top of the org chart does not care which badge you wore first.
Picking a title matters less than picking a model. Does your team specialize inbound from outbound, or does one group do both? Does one person own an account end to end, or does the lead hand off at the meeting-held stage? The org chart answer determines how you staff, pay, measure, and tool the function.
The reason reasonable people disagree about SDR versus BDR is that the sales-tech category grew up with no shared dictionary. Different vendors wrote different playbooks, each company hired based on whichever playbook its first head of sales had read, and the titles diverged. Here is where the main conventions come from, and why nobody is wrong.
HubSpot has treated the two titles as near-synonyms for most of its history. Their content and certifications use SDR and BDR as alternative names for the same role: the person at the top of the funnel who qualifies interest. Teams that grew up on HubSpot often hire for just one of the two titles and do not split by motion.
Salesforce and the broader enterprise sales world have historically used SDR for inbound qualification and BDR for outbound prospecting. This is the split most industry reports cite. Teams coming from the enterprise world usually run two queues, two sets of SLAs, and two coaching tracks that mirror the split.
A third convention, used by some sales-engagement vendors and their customers, treats BDR as the more senior title focused on strategic outbound into named enterprise accounts, with SDR as the entry-level role handling volume at the top of the funnel. The job families are distinct, with different quotas and different coaching models.
Each head of sales brings the convention they learned to the next job. If the first three sales leaders at your company came from Salesforce, your org chart uses the Salesforce split. If they came from HubSpot, the titles are synonyms. Over a decade the industry ended up with three self-consistent conventions that disagree with each other.
Industry surveys from the SDR research firms show that both the inbound-outbound split and the junior-senior split are widely used, and that a meaningful share of companies use the titles interchangeably. There is no single modal definition. Any article that says the distinction is "well-defined" is reading only one of the three playbooks.
When you see SDR or BDR on a job post, read the responsibilities. Does it describe booking meetings off marketing-sourced inbound, or building target-account lists and cold-prospecting into them? That tells you the motion. The two-letter title is just whatever the first VP of Sales preferred.
When a company does split the two roles, the division of labor is almost always about motion. One person works from signals that already exist. The other person creates signals that did not. These two jobs feel different hour to hour, require different skills, and benefit from different tooling, which is why organizations with the scale to specialize usually do.
An inbound rep lives on a queue of form fills, demo requests, chat sessions, and trial sign-ups. The core metric is speed-to-first-touch, measured in minutes, because conversion drops sharply after the first few minutes. The work is reactive, high-volume, and rewards strong qualification and routing more than cold-call bravery.
An outbound rep starts with a target account list, builds a contact list inside each account, and runs multi-touch sequences across email, phone, and social. The core metric is sourced pipeline per rep per quarter. The work is proactive, slower-cadence, and rewards research, personalization, and the ability to open conversations from a cold start.
Inbound reps need fast qualification, strong product knowledge, and the discipline to work a queue without cherry-picking. Outbound reps need patience, strong writing, research instincts, and the resilience to call strangers for forty hours a week. Few reps are equally strong at both, which is one of the reasons the roles get split as teams scale.
An inbound team needs great lead routing, a fast queue view, and tight integrations with marketing forms, chat, and calendar. An outbound team needs sequence tooling, dialer integration, data enrichment, and account-list management. The two tech stacks overlap, but the critical tool for each is on the other side of the funnel from the other.
Inbound reps are usually measured on meetings held and opportunities created, often with a conversion-rate floor to keep volume honest. Outbound reps are measured on sourced pipeline dollars, with closed-won revenue sometimes layered on as a secondary metric. The quota shape follows the motion.
Despite the differences, the end of the job is the same for both titles. A qualified prospect gets handed to an account executive, with context attached, for the discovery and demo cycle. The role ends at the hand-off. What differs is how the conversation started, not where it ended up.
A sales team of five rarely has two separate titles for the top of the funnel. A sales team of fifty almost always does. Between those two points is the question every revenue leader eventually faces: when should one role become two? The answer depends on volume, skill specialization, and the shape of the business.
In the first ten hires, one rep usually owns both inbound and outbound. The volume on either side is not high enough to justify a specialist, and the learning benefits of running both motions make the eventual AE a better closer. Early-stage teams almost always combine, under whichever title the founder learned first.
When the majority of pipeline comes from product sign-ups and self-serve usage, the top-of-funnel role becomes mostly inbound by default, with a thin outbound layer for expansion into enterprise segments. One title, one playbook, one queue is often enough. Splitting the role prematurely creates coordination cost without specialization benefit.
A content-heavy marketing engine that reliably generates qualified volume rarely needs a dedicated outbound team until much later. The sales motion becomes a conversion funnel, not a sourcing funnel. One combined role with great routing and great speed-to-lead often outperforms two specialized roles at the same headcount.
The clearest signal to split is simple: one of the two motions is getting shortchanged. Inbound queues are stacking up because reps are chasing outbound dials, or outbound sequences are dying on the vine because every form fill interrupts. When specialization starts to beat generalism on the margin, the split pays for itself quickly.
As a team grows, hiring reps who are strong at both motions gets harder, and the dilution shows up in results. Teams at scale typically find they can hire specialist outbound reps at a lower cost per sourced pipeline dollar than they can hire generalists, which is often the economic argument that forces the split.
When a business starts selling into named enterprise accounts with a six-to-nine-month cycle, outbound becomes a different discipline from inbound. Account research, multi-threading, and executive outreach require a dedicated person with the time and the quota structure to work the account over a quarter, not a day.
Whichever convention your team uses, the modern CRM should not care. Both roles work the same records. Both roles need the same timeline, the same tasking, and the same handoff to the AE. What has to change is who sees what, which queue each rep works, and how new leads route in. Strkr handles both roles out of one tenant with role-based permissions, shared pipeline stages, and configurable routing.
Strkr ships role-based permissions that let you define an inbound-rep role and an outbound-rep role with different field access, different queue visibility, and different reporting scopes. Both roles work from the same contact and account records, so handoffs do not lose context, but each one only sees the queue it is paid to work.
Inbound form fills, chat sessions, and demo requests route by rule to the inbound queue with a speed-to-lead SLA attached. Outbound reps work from account lists tied to territory, segment, or tier. Routing rules are set once in Admin and run on every new record, so no manager is dragging rows between queues on Monday morning.
Each role gets its own board view. Inbound reps see the triage queue sorted by newest and SLA remaining. Outbound reps see their account list sorted by sequence stage and last-touched. Both boards live on top of the same underlying contact and account records, so a conversation started by one role is instantly visible to the other.
Opportunities created by either role flow into the same pipeline, with a source field that marks inbound or outbound origin. Reporting splits sourced pipeline by role automatically, so you can see which motion is producing without maintaining two separate pipelines and reconciling the totals in a spreadsheet every month.
Both roles get the same email and calendar sync, so cold outbound touches and inbound replies land on the same contact timeline. Reps type less, managers see more, and the AE opening a handed-off opportunity sees the full conversation history regardless of which top-of-funnel role started it.
Leadership can read pipeline coverage per rep, per role, per source segment. If inbound is overheating and outbound is underperforming, the chart shows it. If one specific outbound rep is sourcing twice what the team average does, that shows too. The data is the same whether you call the roles SDR, BDR, or both.
Strkr runs inbound queues, outbound sequences, routing rules, and role-based permissions out of a single platform. Whether your team splits the top of funnel or combines it, the data model, the pipeline, and the reporting line up. Pricing is published and the feature pages show exactly what ships today.
Neither is categorically better. For reps who are strong on the phone and energized by cold conversations, outbound-focused roles usually produce faster skill growth and more autonomy. For reps who thrive on fast reaction and high-volume qualification, inbound-focused roles tend to feel more sustainable. The ladder to AE is the same from either seat, so the choice is about day-to-day motion, not career ceiling.
At the same company, base salary and on-target earnings are usually comparable. Quota structure differs: inbound-focused roles are often paid on meetings held and opportunities created, while outbound-focused roles are paid on sourced pipeline, sometimes with a closed-won kicker. Headline comp bands are usually set by level (associate, mid, senior) rather than by which of the two titles the rep carries.
It depends on the company. In some organizations BDR is explicitly a more senior role focused on strategic outbound into named accounts, with SDR as the entry-level title. In others the two titles are interchangeable, or the inbound-outbound split applies and seniority is independent. Read the job description, not the acronym, when evaluating seniority.
Yes, especially at smaller companies. Early-stage teams routinely run a single generalist role that handles inbound qualification and outbound prospecting. The split usually appears as volume grows and one of the two motions starts getting shortchanged. Below roughly ten reps on the top-of-funnel team, one combined role tends to work. Above that, specialization usually wins.
An SDR qualifies interest and books meetings. An AE (account executive) runs the discovery, demo, proposal, and close. The SDR hands the qualified prospect to the AE at the top of the sales cycle. Both roles work the same records in the CRM, but their quotas and skill profiles differ: the SDR is measured on meetings and opportunities created, the AE on closed-won revenue.
In the modern sales-tech world, "sales development" usually refers to top-of-funnel qualification, whether inbound or outbound. "Business development" originally meant partnerships, channel, and strategic deals, but has drifted in many companies to mean outbound prospecting into named accounts. The terms overlap, which is why the SDR versus BDR title question is tangled in the first place.
Both roles need a CRM with strong contact and account records, email and calendar sync, task management, and a shared activity timeline. Inbound roles also need fast lead routing, a queue view with SLA tracking, and tight integrations with marketing forms and chat. Outbound roles also need sequence tooling, dialer integration, data enrichment, and account-list management. A modern CRM like Strkr ships all of the above in one platform.
Inbound-focused reps are usually measured on meetings held, opportunities created, and speed-to-first-touch, with a conversion-rate floor to keep volume honest. Outbound-focused reps are measured on sourced pipeline dollars per quarter, often with closed-won revenue as a secondary metric. Both roles share leading indicators like activity volume and sequence completion, but the primary quota should match the motion the rep actually runs.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
