You can't build an SDR org by throwing bodies at it

Sales development is getting smaller. In the last year, 36 percent of B2B software companies reduced their SDR and BDR headcount, according to Emergence Capital's Beyond Benchmarks survey of more than 560 companies, reported by SaaStr. Most of that came not from layoffs but from open roles left unfilled. The high-volume, low-touch, throw-more-reps-at-it model is quietly being wound down.

I spent about seven years leading sales development, and I think the shrinkage is mostly healthy, because the model that is dying deserved to. You could never actually build a durable SDR org by throwing bodies at it. You could inflate activity for a couple of quarters, but the moment hiring slowed the whole thing sagged, because the output was tied to headcount instead of design. What replaces it is smaller, more skilled, and built on purpose. Here is what that actually takes.

Headcount was hiding the design problem

When you can always hire another rep, you never have to fix the system. Ramp too slow? Hire ahead of it. Reps burning out at ten months? Backfill. Conversion mediocre? Add volume until the raw number of meetings looks fine. Every structural weakness has a headcount patch, so none of them ever get solved.

Take the headcount lever away, which is exactly what this market has done, and the design problems surface all at once. Now the only way to grow output is to make each rep more effective, and that forces the questions a growing headcount let you avoid: why does ramp take this long, why do good reps leave at the same point, why does the same coaching not stick. Those were always the real questions. Cheap hiring just let you postpone them.

Ramp is a system, not an orientation

The first place the design shows is ramp. Most teams treat onboarding as an event: a week of orientation, some certifications, then thrown onto the phones. Then they are surprised that reps take six months to get productive and some never really do.

Ramp that works is a system, not an event. It is a defined path from day one to full productivity with checkpoints along the way, each one a specific competency a rep has to demonstrate before moving on. Not "attend the training" but "run a live discovery and here is what good looks like." The point of the checkpoints is that they make ramp legible: you can see where a rep is stuck instead of waiting six months to find out they never got past a step three weeks in. When you cannot hire your way around slow ramp, fixing ramp becomes the highest-leverage thing you do.

A skill ladder beats an activity quota

The second place is how you define the job. The lazy version is an activity number: make the calls, send the emails, book the meetings. Activity quotas are easy to manage and they produce exactly what they measure, which is activity, not necessarily pipeline.

A skill ladder is harder and far more durable. It defines the role as a progression of capabilities, research and account selection, opening a conversation, running discovery, handling the objection under the objection, qualifying honestly, and it makes advancement about climbing that ladder rather than hitting a dial count. Reps know what they are getting better at and why. It gives coaching something to attach to. And it turns the SDR seat into the start of a career instead of a burnout station people flee at month ten, which is the single biggest fix for the retention problem that quietly wrecks these teams.

Smaller teams need better coaching, not less

Here is the trap in a shrinking model. Fewer reps can mean less coaching, because the manager is now covering more ground with less time. That is backwards. A smaller, more skilled team is more coachable and more worth coaching, because each rep matters more and the ceiling on each one is higher.

The teams that come out of this period strong will be the ones that used a smaller headcount as a reason to coach deeper, not an excuse to coach less. Structured coaching against the skill ladder, real call review, specific and repeated, is what compounds a small team into a good one. You cannot buy that with headcount. You have to build it.

Design is the moat now

The companies cutting SDR headcount are not all making the same bet. Some are just cutting cost and hoping. The ones that win will be the ones that treat the smaller team as a forcing function to finally design the role well: a real ramp system, a skill ladder instead of an activity quota, and deeper coaching per rep.

That was always the better way to build sales development. A hiring boom let a lot of teams skip it. The correction is making it mandatory again, and the teams that internalize it will be far harder to compete with than the ones that just had more bodies. You could never throw bodies at this and win for long. Now you cannot even pretend to.

I led sales development for about seven years, and I write about building revenue teams that hold up under pressure. I also run a productized Revenue Engine Audit for revenue leaders who want the engine underneath the team to be as well-designed as the team itself.