The category
Sales Development: Building the Function That Feeds Your Pipeline
Sales development is the function responsible for identifying and engaging prospects before they’re ready to buy, and handing off qualified conversations to a closing team, structurally distinct from the sales team that runs those conversations to close. Median B2B SaaS teams run roughly one SDR for every 2.4 account executives, and 60% of sales development teams report into sales leadership rather than marketing (The Bridge Group, 2025 Sales Development Research Report). The function isn’t disappearing under AI, as some current headlines claim, but it is being restructured hard: 36% of surveyed B2B software companies cut sales development headcount in 2025, the sharpest cut of any sales role (Emergence Capital, “Beyond Benchmarks 2025”).
That’s the state of the function right now: real structural data, a real disruption underway, and a lot of noise in between. This is the version without the noise.
What sales development actually is, and where it came from
See the difference between BDR and SDR roles specifically if you’re trying to resolve title confusion rather than function structure. Sales development is the specialized function that finds and qualifies prospects before a closing rep ever gets involved. It’s a distinct discipline from “sales” broadly: a sales development rep researches, prospects, and starts conversations; an account executive runs the deal to close. The split exists because those are genuinely different skill sets, one is about volume, research, and opening a conversation with someone who wasn’t looking for you; the other is about navigating a buying process to a signed deal.
The discipline has a specific, well-documented origin. Aaron Ross split a single combined “sales” role into specialized prospecting and closing functions at Salesforce in the early-to-mid 2000s, a structural change he later formalized in his 2011 book Predictable Revenue (Predictable Revenue, “The History of Professional Selling,” 2015). That structural story, splitting prospecting from closing into two distinct roles, is consistent across every independent account of the function’s history. Ross’s book is also where the widely repeated claim that this approach helped generate “$100 million” in additional revenue at Salesforce comes from; that figure is Ross’s own account rather than an independently audited number, worth knowing if you see it cited elsewhere as a settled fact.
How the function is actually structured today
The most current, methodologically transparent data on sales development team structure comes from The Bridge Group’s 2025 Sales Development Research Report, its tenth edition, based on 351 B2B companies (78% North America, 83% B2B SaaS), published February 2025. A few load-bearing numbers from that research:
- SDR-to-AE ratio: 1:2.4 median, a ratio that’s held roughly steady since 2018. The single most common individual setup is 1:2 (31% of surveyed companies).
- Reporting structure: 60% of sales development teams report to Sales leadership, 26% to Marketing, and 10% to a C-level executive directly. That split has held roughly consistent since 2012, meaning the “should SDR report to sales or marketing” debate has a real, stable answer in practice: most of the time, sales.
- Manager span of control: 6.4 SDRs per first-line manager, down from around 8 in 2021 to 2023, suggesting managers are getting a tighter span as coaching demands increase.
- Average ramp time: 3.0 months, the fastest it’s been since 2010. Bridge Group’s own researchers hedge that this may partly reflect AI-assisted onboarding tools, not a firm causal claim, but it’s the lowest ramp figure in the report’s 18-year history.
This data comes from a single research house, albeit an authoritative and long-running one; no independent second dataset (from RepVue or LinkedIn’s own Talent Solutions research, for example) was found to cross-validate these exact ratios. Treat them as the best available structural benchmark, not an independently triangulated consensus number.
Is the sales development function dying?
This is the question actually driving traffic to this topic right now, and it deserves a direct, evidence-based answer rather than a hedge.
The honest answer: the function isn’t dying, but it’s being restructured harder than any other sales role right now, and the restructuring is real, not hype. Emergence Capital’s “Beyond Benchmarks 2025” survey of more than 560 VC-backed B2B software companies (April 2025) found 36% of respondents cut sales development headcount over the prior 12 months, the highest cut rate of any sales function measured, compared to 25% for AEs, 17% for professional services, and 14% for sales engineers. Only 19% of companies grew SDR headcount over the same period, the lowest growth rate of any function in the survey, while 44% held headcount flat.
That data is a real signal, but worth being precise about what it does and doesn’t show: it’s one primary survey, widely amplified across secondary sales-content sites, and hasn’t yet been independently replicated by a differently constructed study. It shows companies are cutting and restructuring sales development teams at a higher rate than other sales functions. It doesn’t, on its own, prove the function is being eliminated as a category.
The most visible real-world case cited across current practitioner discussion is Salesloft’s 2025 restructuring of its own SDR function, discussed at length on Reddit and LinkedIn. The debate over what actually happened is itself informative: one line of commentary frames it as evidence the SDR role is ending, while a competing, independently corroborated account argues it was driven by a private equity acquisition and cost-cutting mandate rather than a verdict on the function itself, with genuine practitioners on both sides of a real, unresolved argument (r/sales, “Why did Salesloft fire their SDRs?”, 2025; competing LinkedIn commentary from Collin Cadmus attributing the cuts to the PE acquisition specifically). Neither account is definitively settled, which is itself the honest state of the debate.
What practitioners actually closest to the function tend to agree on, across multiple independent sources, is that the role is evolving rather than disappearing. One SDR trainer, rebutting a reported claim from a sales-tech CRO that “the SDR role will be dead by 2026,” put it directly: “The SDR role isn’t disappearing. It’s evolving... SDRs will move deeper into the sales cycle, acting as a hybrid between pipeline generation and early deal support” (LinkedIn, Matt Firestone, 2025). A frontline enterprise AE, commenting independently on a different thread, described the practical shift: “The BDR and SDR job is now the hardest job in sales. The old way does not work” (r/techsales, 2025).
What’s actually changing inside the function
Two things appear to be driving the restructuring, based on the available evidence, not one:
AI is absorbing the lowest-value activity, not the whole job. Bridge Group’s data shows AI SDRs appearing as a distinct headcount category for the first time in 2025 (at 1% of surveyed teams), and faster ramp times that its own researchers partly attribute to AI-assisted onboarding. That’s consistent with the practitioner consensus above: the mechanical, high-volume parts of prospecting are increasingly automatable, while the judgment-heavy parts (research quality, message relevance, actually reading a conversation) aren’t, at least not yet.
Companies are questioning whether SDR needs to be a separate team at all, distinct from whether the work needs doing. This is a different question than “is AI replacing SDRs,” and it’s the one Salesloft’s own restructuring actually raised: the company reportedly folded its SDR function into what it calls an “Office of Pipeline Management,” a structural change in how the work is organized, not necessarily evidence the underlying work disappeared. That’s the more precise way to read the current wave of headcount cuts: some of it is real automation of specific tasks, and some of it is companies reorganizing who owns the same work, which shows up in the data as a “cut” without actually meaning less prospecting is happening.
Building the function: what the data suggests, in practice
If you’re structuring or restructuring a sales development function today, the current data points toward a few practical defaults, while leaving real room for judgment based on your specific stage and motion:
Start from a ratio, then adjust. A 1:2 to 1:2.5 SDR-to-AE ratio is the current median and the most common individual setup, a reasonable starting point rather than a rule. Deal size, sales cycle length, and how much of your pipeline needs to come from outbound versus inbound should move that number in either direction.
Default to reporting into sales, unless you have a specific reason not to. The 60/26/10 split toward Sales leadership isn’t an accident; it reflects that sales development’s core output (qualified opportunities) is measured and coached most naturally by the team that inherits them. The 26% reporting into marketing tends to correlate with companies running a more inbound-heavy, MQL-driven motion where sales development functions closer to lead qualification than outbound prospecting.
Plan for tighter management, not looser. The manager-to-rep ratio tightening from roughly 8:1 to 6.4:1 over the past several years suggests the function is being coached more closely, not left to run on volume alone, consistent with the broader shift toward research quality and message relevance over raw activity.
Decide deliberately whether AI belongs in the research layer or the writing layer. The available evidence (ramp times falling, AI SDR appearing as its own headcount category, and separate research on outbound specifically) points toward AI adding real value in targeting, research, and administrative overhead, and adding real risk when it’s used to mass-generate the actual outreach message. That’s a decision worth making explicitly rather than by default.
How a sales development team is actually organized
Ratios and reporting lines answer “how big” and “who owns it.” They don’t answer “who does what, day to day,” which is the gap most org-structure questions about this function are actually asking about.
At the individual-contributor level, the standard title is sales development representative (SDR), sometimes called a business development representative (BDR) depending on the company; some organizations split the two so one works outbound prospecting exclusively and the other works inbound follow-up, while others use the titles interchangeably for the same job. An SDR’s job ends at a qualified handoff, not a closed deal, which is the structural line that separates the function from sales broadly.
Above the individual-contributor layer, the common pattern is a first-line SDR manager, coaching and running the team day to day, at the 6.4-SDRs-per-manager span already cited above (The Bridge Group, 2025 Sales Development Research Report). Above that, in organizations large enough to need it, sits a Director or Head of Sales Development, who owns quota-setting, hiring, and the reporting relationship into whichever function the team ultimately reports to (sales, marketing, or a C-level executive directly, per the 60/26/10 split above). Smaller teams frequently collapse the manager and director layer into one person, often a working manager who still coaches reps directly; the two-layer structure tends to appear once a team crosses roughly 10 to 15 reps, though no methodologically disclosed source was found that pins that threshold to an exact headcount, so treat it as a directional pattern rather than a hard rule. [DATA NEEDED: a disclosed-methodology source for the specific headcount at which a second management layer typically gets added.]
The career path most commonly runs SDR to AE, not SDR to SDR manager, which matters for how you structure the team: most reps are optimizing for the sales floor, not for people management, so promotion criteria and comp should be built around readiness to carry a closing quota rather than tenure alone.
The KPIs that actually connect sales development to pipeline
Ratios and reporting lines describe the org chart. They don’t show how the function’s daily activity actually turns into the number a CRO cares about: qualified pipeline. That requires tracing the funnel the function runs, stage by stage, with real conversion data at each step.
The funnel has three connection points worth measuring separately, because a problem at one stage looks identical to a problem at another if you’re only watching the top-line number:
Marketing-qualified lead (MQL) to sales-qualified lead (SQL). This conversion has been declining industry-wide: roughly 13% in 2024, down from about 18% in 2022, per Salesforce’s State of Sales research (Salesforce, “5th Edition State of Sales,” 2024, based on a survey of 5,500 sales professionals). That’s a market-wide trend, not a single-company diagnosis, worth knowing before assuming a declining number inside your own funnel means the SDR team is underperforming.
SQL to opportunity. Once a lead is qualified and handed to an AE, roughly 47% convert into a formal sales opportunity, according to Ebsta and Pavilion’s B2B Sales Benchmark Report (Ebsta/Pavilion, “B2B Sales Benchmark Report,” 2024, drawing on more than 4 million opportunities across 700 B2B revenue teams). This is the number that most directly measures whether the sales development function is handing off leads that are actually ready, as distinct from leads that are merely willing to take a meeting.
Opportunity to closed-won. This stage sits mostly outside sales development’s control, since it’s the AE’s execution being measured, but it’s the number that ultimately validates whether the qualification bar upstream was set correctly. A high SQL-to-opportunity rate paired with a weak win rate downstream is a sign the qualification standard is too loose, not that AEs are underperforming.
Activity metrics (calls, emails, touches per day) still matter operationally, but they’re leading indicators for the SDR manager, not proof of pipeline contribution on their own. The three conversion rates above are what actually connects sales development’s day-to-day work to a number finance and the CRO both track.
A worked example: sizing a sales development team to a pipeline target
Take a company that needs 40 new sales opportunities a month and wants to know how many SDRs that requires.
Alleyoop’s own cost model for a mid-market US SDR assumes roughly 8 qualified meetings per SDR per month once a rep is past ramp (alleyoop.io/true-cost-of-an-sdr, 2026), a figure consistent with the ramp and productivity assumptions in The Bridge Group’s research cited throughout this piece. At the Ebsta/Pavilion SQL-to-opportunity rate of roughly 47%, each of those 8 meetings converts to opportunities at:
8 meetings × 0.47 ≈ 3.8 opportunities per SDR per month.
To reach 40 opportunities a month: 40 ÷ 3.8 ≈ 10.5, rounding up to 11 SDRs at full productivity.
Two adjustments matter before treating that as a hiring number. First, it’s a steady-state figure: it assumes every SDR is past the roughly 3.0-month ramp window (The Bridge Group, 2025), so a team built from scratch will underproduce this number for its first quarter or two. Second, at the Bridge Group’s 40% median annual SDR turnover (The Bridge Group, 2025 Sales Development Research Report), an 11-person team should statistically expect to lose more than 4 reps a year, which means the realistic number to plan around is closer to 12 to 13 seats to keep 11 producing at any given time, the same turnover-buffer logic detailed in Alleyoop’s in-house SDR cost modeling.
Layer the SDR-to-AE ratio on top: at the median 1:2.4 (The Bridge Group, 2025), 11 SDRs imply roughly 4 to 5 AEs to carry the resulting opportunity volume through to close. That’s the structural link between the ratio benchmark cited earlier in this piece and an actual pipeline target, rather than a ratio treated as a rule of thumb in isolation.
Sales development vs. business development: a related but different split
“Sales development” and “business development” get used interchangeably often enough that the distinction is worth stating plainly, separate from the sales-development-vs-sales split covered above.
Sales development focuses on identifying leads, researching and developing them, and moving them along the sales cycle toward a closing, work that happens on a daily, quarterly, and annual cadence tied directly to current products and current pipeline. Business development involves finding new growth opportunities and forming strategic partnerships that open up new markets, work that’s inherently longer-horizon and doesn’t necessarily produce revenue this quarter (Indeed, “Sales vs. Business Development: What’s the Difference?”, updated June 15, 2026).
In practice, some companies use “business development representative” (BDR) as a synonym for SDR, with no functional distinction between the two titles, while others draw the line described above: sales development owns qualifying and booking meetings against an already-defined ICP, while business development owns exploring new markets, channels, or partnership structures the company hasn’t sold into yet. When you see the titles used identically at a company, it’s almost always the first pattern; when a company has both titles with genuinely different job descriptions, it’s the second.
Frequently asked questions.
What is sales development?
Sales development is the specialized function that identifies and engages prospects before they’re ready to buy, then hands off qualified conversations to a closing team. It’s structurally distinct from sales broadly: sales development researches and opens conversations; sales (account executives) runs deals to close.
Where did the sales development function come from?
Aaron Ross split a single combined sales role into specialized prospecting and closing functions at Salesforce in the early-to-mid 2000s, later formalized in his 2011 book Predictable Revenue. That structural split, prospecting separated from closing, is the origin of sales development as a distinct discipline.
What’s a typical SDR-to-AE ratio?
The current median is 1:2.4, with 1:2 as the single most common individual setup, per The Bridge Group’s 2025 Sales Development Research Report (351 companies surveyed). Deal size and sales cycle length are the main reasons to move away from that median in either direction.
Should sales development report to sales or marketing?
Most commonly, sales: 60% of surveyed teams report to sales leadership, 26% to marketing, and 10% to a C-level executive directly, a split that’s held roughly steady since 2012 (The Bridge Group, 2025).
Is the SDR/sales development role dying because of AI?
Not dying, but being restructured harder than any other sales function right now. A 2025 survey of 560+ B2B software companies found 36% cut sales development headcount over the prior year, the highest cut rate of any sales role, though only 19% grew it. The available evidence points to AI absorbing the mechanical parts of the job (research, targeting) while the judgment-heavy parts remain human, alongside some companies restructuring how the function is organized rather than eliminating the underlying work.
What KPIs actually connect sales development to pipeline?
Three conversion rates matter most: MQL-to-SQL (around 13% in 2024, down from about 18% in 2022, per Salesforce’s State of Sales research), SQL-to-opportunity (roughly 47%, per Ebsta and Pavilion’s 2024 B2B Sales Benchmark Report), and opportunity-to-closed-won, which sits mostly outside sales development’s control but validates whether the qualification bar upstream was set correctly. Activity metrics like calls and emails are useful leading indicators for a manager, but these three conversion rates are what actually link the function’s daily work to pipeline.
How many SDRs do I need to hit a specific pipeline target?
Work backward from a per-rep opportunity rate: at roughly 8 qualified meetings per SDR per month (Alleyoop’s cost model) and a 47% SQL-to-opportunity conversion rate (Ebsta/Pavilion, 2024), each SDR produces about 3.8 opportunities a month once fully ramped. A target of 40 opportunities a month works out to roughly 11 SDRs at full productivity, though real-world turnover (40% median annually, per The Bridge Group) means budgeting closer to 12 to 13 seats to keep 11 producing at any given time.
What’s the difference between sales development and business development?
Sales development identifies, researches, and qualifies leads, moving them toward a closing on a day-to-day and quarterly cadence tied to current products. Business development finds new growth opportunities and forms strategic partnerships that open new markets, work that’s longer-horizon and doesn’t necessarily produce revenue this quarter (Indeed, “Sales vs. Business Development: What’s the Difference?”, updated June 15, 2026). Some companies use the titles interchangeably; others draw this line deliberately.
Done reading? Start measuring.
Twenty minutes, your numbers, and a straight answer on whether a program fits. If we’re the wrong fit, we’ll say so.
The assist is ours. The win is yours.