What Is the Difference Between an SDR and a BDR?
An SDR qualifies demand that already exists, and a BDR creates demand that does not. The sales development rep works the inbound side. Form fills, content downloads, trial signups, webinar registrations, routed leads from the marketing system. Someone on the buyer's side has already moved, and the job is to find out whether the movement is real, whether the account fits, and whether a seller should spend an hour on it.The business development rep works the other direction. Named accounts, target lists, cold sequences, referrals into companies that have shown no intent at all. Nobody raised a hand. The job is to manufacture a first conversation out of nothing.
Plenty of companies invert the two labels, and a few use them as synonyms for the same queue. The title is a local naming choice. The distinction that survives across companies is which side of the demand line the rep sits on, because that is the thing that changes how the resulting pipeline behaves.
Why Does the SDR vs BDR Split Change the Forecast?
Because inbound-sourced and outbound-sourced pipeline close on different curves, and one blended rate hides both. A buyer who filled out a pricing form has already done part of the qualification work internally. A buyer who answered a cold call has not. The two opportunities enter the same pipeline, sit in the same stage, and carry the same close date field, and then they behave nothing alike.This is why source-level segmentation matters more than most teams treat it. ORM groups every opportunity with a machine learning model and predicts a close curve for each group. Those curves run from one week to eighty weeks, with most of the expectation landing before week twelve and very few groups carrying expectation past fifty-two weeks. The curve belongs to the group. Apply the average of the whole pipeline to a single deal and you have described a deal that does not exist.
When SDR and BDR pipeline get merged into a single "sales development sourced" bucket, you lose the ability to answer the only question that matters in a coverage review: which part of this number is likely to happen, and when. For the broader method, see how to create a sales forecast.
How Do the Two Roles Compare Side by Side?
The SDR job is speed and disqualification, and the BDR job is research and access. Everything else in the comparison follows from those two mandates.| Dimension | SDR (inbound) | BDR (outbound) |
|---|---|---|
| Demand | Already exists, needs qualifying | Does not exist, needs creating |
| Trigger | Form fill, trial, routed lead | Target account list, research, referral |
| First touch | Response to a signal | Cold sequence |
| Speed pressure | Minutes to first touch | Weeks of patterned follow-up |
| Primary skill | Fast disqualification | Account research and message construction |
| Volume profile | Higher meeting count, mixed fit | Lower meeting count, tighter fit |
| Ramp | Faster, the queue teaches the job | Slower, requires account knowledge |
| Core output metric | Accepted meetings from inbound | Accepted meetings from named accounts |
| Failure mode | Queue worked shallow, good leads burned | Activity theater with no account penetration |
| Comp emphasis | Throughput and speed to lead | Meeting quality and account coverage |
Which Metrics Should Each Role Be Held To?
Hold both roles to accepted meetings and surviving opportunities, never to raw activity. Dials, emails, and touches measure effort. Effort inflates the moment you pay for it. The honest measure is the meeting a seller accepted, then the opportunity that survived a stage gate, then the revenue that closed.Two rules keep the measurement clean. First, define acceptance in writing and enforce it in the CRM, so a meeting that a seller rejects never counts for anyone. Second, stamp the source on the opportunity at creation and never let it be overwritten, so the SDR curve and the BDR curve stay separate for the life of the deal.
The second rule breaks more often than teams realize. A deal that started as a BDR-sourced conversation gets re-attributed to marketing when the champion later downloads a report, and the outbound motion silently loses credit for the pipeline it built.
Should You Hire SDRs or BDRs First?
Hire against the gap in the pipeline, not against the org chart. If inbound volume is arriving faster than the team can respond and leads are aging in the queue, an SDR converts demand you already paid for. If the inbound queue is worked to the bottom every day, adding SDR headcount produces nothing, and the gap is coverage of accounts that will never find you on their own.There is a second diagnostic, and it is the more useful one. Ask how much of next quarter has to be created inside next quarter. Across ORM customers, roughly 20% of the pipeline carrying in-quarter close dates on day one of the quarter actually closes in that quarter. That means a large share of the value dated into the quarter on day one never lands in it, so the gap has to come from deals created inside the quarter or pulled forward from later periods.
If your in-quarter creation engine is thin, no amount of pipeline inspection saves the number. That is a BDR capacity question, and it needs to be answered a quarter early. It is also why pipeline coverage alone is a poor read on the quarter.
What Breaks When You Merge Both Roles Into One Title?
Outbound decays first, and the activity dashboard stays green while it happens. Give one rep an inbound queue and an outbound list, and the inbound queue wins every time. It converts faster, it produces meetings this week, and it pays sooner. Nobody makes a decision to abandon outbound. It just loses every hour it competes for.The reporting damage is worse than the coverage damage. Once both motions live under one title with one target, the source field stops describing anything, the conversion rate is an average of two populations, and the forecast loses the ability to explain where next quarter's pipeline comes from.
If you do combine the roles for headcount reasons, give outbound its own target, its own block of protected time, and its own line in the pipeline report. Track the two motions separately even when one person runs both. When you review win rate by source, the split is the only thing that makes the number readable.
Frequently Asked Questions
What is the difference between an SDR and a BDR?
By the most common convention, an SDR qualifies demand that already exists and a BDR creates demand that does not. The SDR works inbound signals such as form fills, trial signups, and routed leads. The BDR works cold target accounts that have never raised a hand. Some companies swap the two labels, so the title tells you less than the question of which side of the demand line the rep sits on.
Do SDR and BDR pipeline convert at the same rate?
No. Pipeline created from a hand raise and pipeline created from a cold sequence behave differently on cycle length, average value, and the odds of the close date holding. A blended conversion rate describes an average deal that does not exist in your pipeline. Track the two sources separately or your coverage math inherits the error.
Should I hire SDRs or BDRs first?
Hire against the gap in the pipeline rather than the org chart. If inbound volume is arriving faster than anyone can work it, an SDR converts existing demand and pays back sooner. If inbound is thin or already worked to the bottom of the queue, more SDR capacity produces nothing and you need outbound coverage of named accounts.
Can one person do both the SDR and BDR job?
One person can hold both queues, and almost every one of them will work the inbound queue first because it converts faster and pays sooner. Outbound then decays quietly while activity metrics still look healthy. If you combine the roles, protect outbound time with a separate target and a separate scoreboard.
Which metrics should an SDR or BDR be held to?
Hold both roles to accepted meetings and to opportunities that survive a stage gate, not to raw activity. Dials and emails measure effort, and effort is easy to inflate. The honest number is how much pipeline the rep created that a seller kept and that later closed, measured at the source level so the two motions never get averaged together.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo