Claim
The sales development function isn't a hiring problem or a script problem — it's a precision operating system with six interdependent elements: Strategy, Specialization, Recruiting, Retention, Execution, Leadership. Optimizing any one without the others produces local improvements but systemic mediocrity. The Bridge Group's industry-benchmark SDR data shows the failure modes statistically — most are preventable with system-level design.
Mechanism
Hire great SDRs but skimp on training (Execution failure) and they leave (Retention failure). Build great training but lack a defined ICP (Strategy failure) and they generate noise. Define ICP cleanly but skip role specialization (Specialization failure) and reps fall back to mixed prospect-and-close hybrids that erode predictability. Six elements form a cycle; weakness in any breaks the system. Bertuzzi's prescription: design all six together, with named owners and named metrics, before hiring the first SDR.
Conditions
Holds when:
- The company is at scale where building an SDR function makes sense (post-PMF, ≥$1-2M ARR).
- Leadership commits to building all six elements, not just the visible ones.
Fails when:
- Pre-SDR-stage startups where founder-led sales is still right.
- Productized-services or pure-PLG companies where SDRs aren't the right model.
Evidence
"The sales development function is a precision operating system with six interdependent elements; optimizing any one without the others produces local improvements but systemic mediocrity."
— Trish Bertuzzi, The Sales Development Playbook (synthesized from operator's published work)
Signals
- Each of the six elements has a named owner and named KPI.
- New SDR hires don't begin until all six elements are documented at minimum-viable level.
- Bridge Group benchmarks (or equivalent) are tracked against the team's actuals.
Counter-evidence
Modern intent-data + AI-personalization tools are partially absorbing functions traditionally done by SDR teams (Nick Abraham's hyper-personalization model). The six-element prescription may over-engineer for early-stage teams that need scrappy iteration first.
Cross-references
- ins_specialization-creates-predictability — adjacent operator (Aaron Ross)