Teams building sales development for the first time hit the same problems in roughly the same order. Knowing the order is most of the value, because each one is far cheaper to prevent than to fix.
Before the first hire: no written ICP
The most expensive omission, and the easiest to miss because everyone believes they know who the customer is until three people write it down separately and disagree.
An SDR without a written ICP will invent one from whoever replies. That reverse-engineered profile then hardens into the target list, and a year later the team is efficiently pursuing the wrong market.
Fix before hire one. Write it with the disqualifiers, not just the fit criteria. See the ICP development workshop.
Hires one and two: no manager
The temptation is to have the VP of Sales manage two SDRs "for now". It works badly and predictably: the VP has a quota, the SDRs get attention when the forecast allows, and coaching stops entirely at quarter end, which is exactly when it is needed.
Hire or appoint the manager before the third rep. Two reps can survive neglect. Three cannot, and by five the lack of coaching is showing up as churn.
A fractional manager is a real option at this size. See fractional SDR manager and SDR manager training.
Month one to three: ramp with no curriculum
New reps get product training, a login, and a list. That is onboarding, not training. Product knowledge is the part they can look up; the parts they cannot are call mechanics, writing, and reading a signal.
The symptom is a rep who can explain the product fluently and cannot get past the first ten seconds of a call.
Fix: a 30/60/90 with a certification checkpoint at each. Curriculum in SDR training, verification in the training checklist.
Month four to six: activity theatre
The first reporting instinct is calls and emails per day, because it is easy to count. Reps optimise what is counted, so activity goes up and meetings do not.
The number that matters is meetings held, then whether they produced a next step. Activity is an input, and it is only worth watching when conversion is already understood.
Fix: report conversion by stage, not volume by channel. See pipeline velocity.
Month six to nine: the first churn wave
SDRs who joined together get restless together, especially the good ones, and especially where no promotion path was ever described.
The conversation to have in the first interview, not the exit interview: what this role leads to, on what timeline, and against what criteria. A rep who knows the AE path is eighteen months away with defined gates behaves differently from one who suspects it does not exist.
Fix: write the progression criteria down before you need them.
Ongoing: the handoff nobody owns
The seam between SDR and AE. It has no owner by default, so it degrades: context is lost, meetings get taken cold, AEs decide SDR meetings are low quality, and SDRs decide AEs waste their work. Both are right, and the cause is structural.
Salesforce frames the split as SDRs opening conversations and AEs closing them. Nobody owns the join.
Fix: name an owner, define what travels with a meeting, and measure meeting-held rate and next-step rate rather than meetings booked. See revenue alignment.
The compression
Two decisions prevent most of the list:
- Write the ICP before the first hire.
- Put a manager in place before the third.
Almost every problem after month three is one of those two arriving late, wearing a different costume.
Where this sits
Building the team spans Mastery and Motion in the Tenbound Pipeline Architecture Standard, and it fails most often at Market, which is the pillar people assume is already handled.
For where a new team lands on the automation ladder, the maturity model. New teams start at Manual and should not attempt Orchestrated before the process exists on paper.