SDR Team Setup: The RevOps Infrastructure You Need Before You Hire Your First Rep

One of the most common and expensive mistakes growth-stage companies make is hiring SDRs before the RevOps infrastructure is ready to support them. The SDRs arrive, they're given a list, they start making calls, and nothing works the way anyone expected. The sequences aren't set up. The routing is manual. The reporting doesn't exist. The playbook is one person's brain. Three months in, two SDRs have already quit and the CRO is wondering why the hire wasn't working.

This is almost always a setup failure, not a talent failure. Here's what needs to exist before SDR hire day.

The ICP and Targeting List

SDRs need to know who to call. That means a defined ICP (see the ICP guide), a list of target accounts that fit it, and contact data for the right personas at those accounts. Without this, SDRs spend a significant portion of their time on research and list-building — work that should be done before they arrive, or offloaded to a data tool.

Build the target account list before day one. Use your ICP criteria and a data enrichment tool (Clay, Apollo, ZoomInfo) to pull accounts that fit. Prioritize by intent signal if you have access to intent data. Give each SDR a defined territory or account set so there's no overlap and clear ownership from the start.

Sequencing and Outreach Infrastructure

SDRs shouldn't be doing one-off emails from their inbox. They need a sequencing tool — Outreach, Salesloft, or Apollo — configured with your approved email and call sequences. Those sequences need to be written before SDRs start. Not by the SDR. By someone who understands your ICP and your value proposition well enough to write credible outbound messaging.

Configure at minimum: a new prospect sequence (multi-step, email + call + LinkedIn), a reactivation sequence for cold leads, and a post-event or post-meeting follow-up sequence. Make sure the sequences are set up in the tool, connected to the CRM, and logging activity automatically before the SDR's first day.

The sequencing mistake: Many teams buy the tool and let the SDRs write the sequences themselves. New SDRs don't know your ICP, your value proposition, or your best-performing messaging. They write generic outreach that performs poorly, the SDR concludes outbound doesn't work, and the team gives up on the channel. Write the sequences for them based on what your best-performing outbound actually looks like.

Lead Routing and CRM Configuration

Inbound leads that come in while SDRs are working need to be routed to them quickly and cleanly. Build the routing rules before you hire: inbound MQLs route to SDRs by territory or round-robin, assignment happens automatically within the CRM, the SDR gets a notification with the lead's context, and there's an SLA for how quickly they respond.

The CRM also needs to be set up for SDR workflows: what objects they create, what fields they fill in, what stage an SDR-sourced lead enters when converted to an opportunity, and how their activity is logged. If the CRM setup isn't ready, SDRs will work around it and your data quality will be compromised from day one.

Reporting: How Will You Know If It's Working?

Before SDRs start, define what success looks like at 30, 60, and 90 days. Common SDR metrics: calls/emails per day, connect rate, meeting booked rate, SQL conversion rate, and pipeline sourced. Build the reports that track these metrics before the SDR starts — not after, when you're trying to figure out whether the hire is performing.

The most important early metric is meeting booked rate: of the prospects an SDR contacts, what percentage book a meeting? This is your primary leading indicator of SDR effectiveness. If the rate is too low, the problem is either the list, the messaging, or the activity level — and your reports should help you distinguish between them.

The Playbook

SDR playbooks cover: the ICP (who to target and why), the sequences (how to reach out), the objection handlers (what to say when prospects push back), the qualification criteria (what makes a meeting worth booking), and the handoff process to the AE. Without a written playbook, SDR behavior varies dramatically between individuals and from one week to the next.

Write the playbook before hire. Give it to the SDR in their first week. Review it together. Update it quarterly based on what you're learning from win-loss data and call recordings. A living playbook is one of the highest-leverage tools in your SDR infrastructure — and one of the easiest things to skip because it feels like it can always be done later. It can't.

For the broader process documentation framework, see the sales process documentation guide.

Building your outbound motion and want the infrastructure right from the start?

I help RevOps teams set up the systems, routing, reporting, and playbooks that make SDR hires productive from week one instead of month six.

Talk to Gage →