Sales org design is where a lot of growth quietly leaks. The team is full of good people, the number still misses, and no one can say exactly why. Usually it’s structure: the wrong roles, the wrong ratios, or specialization that came too early or too late.
Here’s how high-growth B2B SaaS teams are actually structured, and how the shape should change as you scale.
What roles does a modern SaaS sales team need?
A fully specialized revenue team separates four jobs that founders often blur into one:
- SDR / BDR — creates pipeline (outbound prospecting and inbound qualification). Two flavors: outbound SDRs hunt cold; inbound BDRs work marketing-sourced interest.
- Account Executive (AE) — owns the deal from qualified opportunity to closed-won.
- Sales Engineer / Solutions — owns technical validation in complex or technical sales.
- Account Manager / CSM — owns retention and expansion after the close.
The insight behind specialization: prospecting and closing are different skills, energized by different people. Forcing one person to cold-call all morning and run executive demos all afternoon means they do both at 70%.
When should you specialize vs. keep full-cycle reps?
Don’t specialize on day one. Early on, full-cycle AEs (who prospect, close, and often onboard) are the right call — they give you full visibility into the whole motion and there isn’t enough volume to keep specialists busy.
Specialize when:
- AEs are spending more time prospecting than closing, and pipeline is the bottleneck.
- Deal volume is high enough that a dedicated SDR stays fully utilized.
- The sales cycle is complex enough that handoffs are worth the coordination cost.
Specialize too early and you’ve got an SDR with nothing to do and an AE starved of context. Too late and your best closers are wasting half their day on tasks a junior could own.
What is the right SDR-to-AE ratio?
There’s no universal number, but useful starting points by motion:
- High-velocity SMB: roughly 1 SDR per 1 AE — AEs close fast and need a steady feed.
- Mid-market: about 1 SDR per 2 AEs.
- Enterprise: 1 SDR per 2–3 AEs, sometimes fewer, because cycles are long and AEs do more of their own strategic prospecting.
The ratio is an output, not a goal. Tune it by watching where the constraint is: if AEs have capacity to close but no pipeline, add SDRs; if they’re drowning in pipeline they can’t work, add AEs.
How should structure change as you scale?
Seed: founder + 1–2 full-cycle founding AEs. No specialization.
Series A: first sales leader, 3–6 AEs, the first SDRs. Begin separating prospecting from closing. Introduce a real pipeline process and forecasting.
Series B: segment the team. Split by market (SMB / mid-market / enterprise) or by motion (new business / expansion). Add sales engineering. First-line managers own pods of 5–8 reps.
Series C and beyond: multiple segments, dedicated enablement, RevOps owning the data and tooling, and a CRO orchestrating sales, SDRs, partnerships, and often CS as one revenue engine.
What’s the most common structural mistake?
Too many reps under one manager. A first-line sales manager can coach 5–8 reps well. Push past 10 and coaching collapses into status-checking — and coaching is the entire job. When you’d cross that line, you need another manager before the next batch of reps, not after.
A close second: no clear ownership of the handoff. When it’s fuzzy who owns a lead between SDR, AE, and CSM, deals stall in the cracks. Write the handoff rules down and make them part of the comp plan.
The bottom line
Good structure is just matching the org shape to the motion and the stage. Keep reps full-cycle until volume justifies specialists, let the bottleneck tell you the right ratio, and add management capacity before spans of control break. Structure won’t make a bad team good — but bad structure will make a good team miss.
When we run leadership searches, org design is the first conversation — because the right VP for a 5-person full-cycle team is rarely the right VP for a 30-person specialized one.