Bottleneck calculator
On the Table

What your first SDR needs from you before day one

You've decided to hire an SDR. The plan makes sense: get outbound off your plate, fill the top of the funnel, stop being the only person generating pipeline. Before you post the role, though, there's a harder truth worth sitting with. When a first SDR flames out, the person usually wasn't the problem. They were dropped into nothing to work with.

An SDR is one of the easiest early hires to get wrong, because it looks like you're buying pipeline when you're really buying execution. And execution needs something to execute.

An SDR runs a motion, they don't invent one

A good SDR runs outbound: builds lists, sends the sequences, books the meetings, keeps the top of the funnel moving. What they don't do is figure out who your buyer actually is, why that buyer cares, or how a booked meeting turns into a closed deal. If those things don't exist yet, a new SDR will do the only thing they can, which is push more volume into the void, and burn through your best-fit accounts while they're at it.

What they actually need before day one

  • A defined ICP. Who exactly they should be reaching, and who to leave alone, specific enough that they're not guessing.
  • Messaging built on real buyer pain. Not your feature list, the actual problem your buyers feel, in words that sound like something a human would say.
  • A motion to hand meetings into. When they book a qualified conversation, someone and something has to be ready to run it to a close. Otherwise the meetings they worked so hard to book die on the vine, and nothing drains an SDR's morale faster.
  • A follow-up rhythm and the tooling to run it. The sequences, the CRM, the cadence, set up before they arrive rather than improvised in week three.
  • Someone to coach them. Especially in the first month, they need real feedback and course-correction from someone who knows what good looks like.

The handoff seam is where it usually breaks

Here's the failure I see most. The SDR does their job, they book meetings, and then the meetings land on a founder who's too slammed to run them well, or into a sales process that doesn't really exist yet. The pipeline the SDR built leaks straight back out, everyone concludes the SDR isn't working, and a good hire gets blamed for a gap that was never theirs to fill.

Set them up to actually ramp

The fix is sequence, again. Get the motion built first, define the outbound together with the person who'll run it, and make sure there's a real place for their meetings to go. When an SDR lands in a working motion instead of chaos, they ramp fast, because the hard part was done before they arrived.

It's why, on a Revenue Engine, I don't hand a founder an SDR and wish them luck. The SDR is recruited into a motion that already runs, with the outbound strategy shaped and the deals being handled, so their pipeline plugs into something real from the start.

If a first SDR is on your near-term list, it's worth getting clear on what needs to exist before they start. The free strategy session is a good place to map that.

If this reads like where you are, it's worth a conversation.

Get your free strategy session