How do you hire your first SDR?
Have a working process and real lead volume before hiring, or a good hire fails at a broken job. Define quota and ramp expectations before day one, not after.
The short answer
- A first SDR hire needs an existing process to step into. At least a rough sense of what a good lead looks like, what messaging works, and what the follow-up cadence should be. Asking a new hire to build the process while hitting quota sets them up to struggle.
- Lead volume matters more than headcount plans suggest. Hiring an SDR before there is enough volume to work leaves them idle. That produces poor performance that looks like a bad hire but is really a timing mistake.
- Define and communicate ramp-up time before the person starts. Judging a new SDR against full quota in month one, before they know the product, the tools and the process, is unrealistic and demoralizing.
- Decide up front whether the role is full-cycle, prospecting and working leads, or purely working handed-off leads. That changes what skills to hire for and how many qualified leads must already exist.
Why hiring often happens before the process is ready
A common pattern is hiring the first SDR as a reaction to feeling overwhelmed. The founder or an existing salesperson is buried in outreach and follow-up, and hiring feels like the obvious relief valve. The problem is that "we're overwhelmed" describes a volume problem, not necessarily a process problem. A new hire dropped into an undefined process, with no clear sense of what a qualified lead looks like or what messaging has worked, spends their early months guessing rather than executing something proven.
A first-SDR hire that works usually follows some evidence that the process itself works. A founder or early team member has generated leads and closed some deals by hand. They have a rough sense of what messaging and targeting produced results. They can hand that knowledge to a new hire as a starting point, rather than asking them to invent it from nothing while being judged on output.
Readiness checklist before hiring
| Question | Why it matters |
|---|---|
| Is there a proven process to hand off? | A new hire needs a starting point, not a blank page |
| Is there enough lead volume to keep them busy? | Idle capacity produces poor performance that looks like a bad hire |
| Is the role full-cycle or lead-working only? | Changes what skills to hire for and what volume is required |
| Is ramp-up time defined? | Prevents judging a new hire against an unrealistic early bar |
What to set up before the role is posted
Document what has worked so far, even informally: target criteria, message templates, objection patterns. The new hire then has something concrete to build from. Estimate the lead volume that will realistically flow to this person and confirm it is enough to fill their time. Set an explicit ramp-up period with reduced quota expectations. Communicate it clearly before their first day, not after a rough first month.
Disclosure: SalesCrew is our product. Quotas, a leaderboard, and forecast categories to track a new SDR's ramp against are on our roadmap and not shipped today. This page describes general hiring practice rather than a SalesCrew reporting feature available now.
A good hire fails fast in a broken or undefined process
Questions
- How much lead volume justifies a first SDR hire?
- There is no fixed threshold. If the founder or existing team can barely keep up with current outreach and follow-up, that is a stronger signal than a specific lead count. Hiring to fill idle capacity rarely works out.
- Should the first SDR do their own prospecting or just work handed-off leads?
- Both models exist. A full-cycle first hire who prospects and works leads gives more flexibility early on. A pure lead-working role needs a reliable stream of qualified leads already coming in to be worth the hire.
- How long should ramp-up take before judging performance?
- It varies by product complexity and sales cycle length. Judging a new SDR on full quota in their first month, before they have learned the product, the process and the tools, sets an unrealistic bar.