How to Structure a B2B Outbound Sales Team

SDR-to-AE Ratios That Actually Work

The optimal SDR-to-AE ratio depends on your deal size and sales cycle. For SMB (€5–20k ACV, 30-day cycles): 3–4 SDRs per AE. AEs handle high volume, short cycles, and need a steady flow of meetings. For mid-market (€20–80k ACV, 60–90-day cycles): 2–3 SDRs per AE. AEs spend more time per deal, so they need fewer but higher-quality meetings. For enterprise (€80k+ ACV, 120+ day cycles): 1–2 SDRs per AE, often with named-account alignment where the SDR and AE co-own a target account list. Running a 1:1 ratio in SMB wastes AE capacity; running 4:1 in enterprise overwhelms AEs with meetings they cannot service.

These ratios assume SDRs are booking 12–18 meetings/month and AEs can handle 15–25 active opportunities simultaneously. If your SDRs book fewer meetings, you need fewer SDRs per AE. If your AEs manage longer cycles with more stakeholders, they need fewer meetings per month. Model the math: if an AE needs 8 new opportunities/month and your meeting-to-opportunity rate is 40%, the AE needs 20 meetings/month. If each SDR books 14 meetings/month, you need 1.4 SDRs per AE. Round to 1.5 and staff accordingly. Revisit every quarter as conversion rates shift.

Three Team Structures: Pools, Pods, and Islands

Pool model: all SDRs report to an SDR manager, all AEs report to an AE manager, and meetings are distributed round-robin or by territory. Pros: easy to manage, clear metrics per role, natural competition. Cons: handoff friction, SDRs optimize for quantity over quality because they have no relationship with the AE, finger-pointing between teams. Best for: teams with 10+ SDRs where standardization and scalability matter more than personalization.

Pod model: an SDR and AE (or 2 SDRs + 1 AE) form a pod with shared targets and shared accountability. The SDR books meetings specifically for their paired AE, and both are measured on pipeline generated and revenue closed. Pros: tight alignment, high meeting quality, strong feedback loops. Cons: if one person underperforms, the pod suffers; harder to benchmark individual contribution. Best for: mid-market and enterprise teams where meeting quality and SDR-AE chemistry matter. Island model: each rep does their own prospecting and closing (full-cycle). Pros: complete ownership, no handoff issues. Cons: expensive (AEs doing SDR work), hard to scale, AEs typically neglect prospecting when they have active deals. Best for: early-stage companies with 1–3 reps before specialization is justified.

Management Layers and Reporting Lines

Add your first frontline sales manager when you have 5–6 SDRs or AEs. The optimal span of control for a frontline manager is 6–8 direct reports. Below 5, the manager does not have enough coaching volume to justify the role — they should be a player-coach. Above 8, coaching quality degrades because the manager cannot listen to enough calls, run enough 1:1s, and manage enough pipeline reviews. For SDR managers: expect them to spend 60% of their time coaching (call reviews, email reviews, role-plays) and 40% on reporting, hiring, and process. For AE managers: 50% coaching (deal reviews, call coaching, strategy sessions), 30% forecasting and pipeline management, 20% reporting and hiring.

Reporting lines matter more than most leaders realize. SDR teams should report to the sales organization, not marketing — even though marketing generates the ICP definitions and content that SDRs use. Why? Because SDRs need to be calibrated to the AE's definition of a qualified meeting, not marketing's definition of an MQL. If SDRs report to marketing, incentives misalign: marketing celebrates meeting volume while sales complains about quality. In a pod model, the SDR and AE pod can report to the same frontline manager, which maximizes alignment but requires the manager to coach both prospecting and closing skills.

Scaling the Team — When and How to Add Headcount

Add SDR headcount when: (1) existing SDRs are consistently hitting 100%+ of meeting targets for 2+ consecutive months, indicating ceiling capacity, (2) AEs report they could handle more meetings/opportunities, and (3) your pipeline math shows a gap between required pipeline and current generation capacity. Do not add SDRs when existing SDRs are at 60% of target — the problem is productivity, not capacity. Adding people to a broken process scales the problem, not the solution.

Add AE headcount when: (1) AE pipeline is consistently 5x+ coverage (they have more opportunities than they can service, leading to dropped balls), (2) average deal attention is declining (fewer touchpoints per deal, longer response times), and (3) win rates are declining without other explanation (often a sign of stretched capacity). The hiring sequence for a scaling outbound team: hire 2 SDRs first, prove the outbound motion works (3 months), then hire 1 AE, then add SDRs to maintain the ratio. Never hire AEs before you have proven meeting flow — an AE without meetings is the most expensive problem in sales.

Before locking in a permanent headcount, [see when remote SDR capacity makes more sense than an in-house hire](/blog/build-in-house-sdr-team-vs-hire-remote-talent) to see which model fits your stage.

Still comparing hiring models?

This page gives you the cost/risk context. The next step is deciding which hiring model fits your situation: recruiter, agency, in-house SDR, EOR/direct employment, or structured remote capacity.

If you are choosing between [building an in-house SDR team versus hiring remote talent](/blog/build-in-house-sdr-team-vs-hire-remote-talent), it also helps to benchmark against [working with a recruitment agency](/blog/talentbridge-vs-recruitment-agencies) so the trade-off is explicit.

Frequently Asked Questions