The Sales Script
for SDRs
(Book Qualified Meetings,
Don't Try to Sell)

The most important thing to understand about an SDR script is that the SDR's job is not to sell — it is to prospect, qualify, and book qualified meetings for the account executives who close. An SDR (sales development rep) sits at the top of the sales process: their role is to reach prospects, establish enough relevance and qualification to know a meeting is worthwhile, and book that meeting for an AE, who then runs discovery, demo, and close. So an SDR script should be built around the SDR's actual goal — booking a qualified meeting — not around selling, which is the AE's job later. Yet many SDR scripts fail precisely by trying to sell: the SDR pitches the product, attempts to make the case, tries to advance the deal — doing the AE's job badly at the wrong stage, when their job was simply to establish relevance and book the meeting. This guide is an SDR script framework built around the SDR's real role: the SDR's specific job, the framework for the SDR conversation, the qualification and handoff to the AE, the common SDR script mistakes, and how to run it as a framework. The throughline is that the SDR's job is to book qualified meetings, not to close — and an SDR script that reflects that goal succeeds where one that tries to sell fails.

The reason getting the SDR's role right matters so much is that the SDR and AE roles are specialized for good reasons, and an SDR doing the AE's job (trying to sell) does both jobs badly. The SDR role exists to do the top-of-funnel work — prospecting, initial relevance, qualification, booking — efficiently and at volume, so the AE can focus on the deeper work of discovering, demonstrating, and closing qualified opportunities. When an SDR tries to sell on the prospecting call, they fail at their own job (booking efficiently) by getting bogged down in a sales conversation they are not positioned to win (they do not have the discovery or the deal context to sell well), and they often burn the opportunity by pitching prematurely to a prospect who is not yet ready. The specialization works when each role does its part: the SDR establishes relevance and qualifies and books, the AE takes the qualified meeting and sells. So the SDR script should keep the SDR in their lane — establishing enough relevance to book a qualified meeting, then handing off — rather than tempting them into the AE's job. This is not a limitation on the SDR but the design of an efficient sales process: the SDR's focused job (book qualified meetings) is valuable precisely because it is focused, and a script that keeps them focused on it is what makes the SDR role work. An SDR script built for selling misunderstands the role and undermines the specialization that makes it effective.

The SDR's Specific Role

The SDR's role is the top-of-funnel work of the sales process: reaching prospects, establishing relevance, qualifying enough to know a meeting is worthwhile, and booking that meeting for an AE — not selling, which the AE does later. This role exists because separating the top-of-funnel prospecting and qualification (the SDR's job) from the deeper selling (the AE's job) lets each be done well: the SDR focuses on efficiently generating qualified meetings at volume, the AE focuses on converting those meetings into deals. The SDR's specific deliverable is a qualified meeting — a prospect who fits, has enough relevance and potential need to be worth the AE's time, and has agreed to a meeting — handed to an AE who takes it from there. Understanding this deliverable shapes everything about the SDR script: it should be built to produce qualified meetings efficiently, which means establishing relevance, doing enough qualification to confirm the meeting is worthwhile, and booking — not selling, over-qualifying, or trying to advance the deal. The SDR is the front of the sales process, and their job is to feed qualified opportunities into it, not to run the whole process themselves. This focused role is valuable precisely because it is focused: an SDR who efficiently books qualified meetings is doing exactly what the role is for, while an SDR who gets drawn into selling or over-qualifying is drifting from the role into work it is not designed for. The SDR script keeps the SDR focused on their deliverable — the qualified meeting — which is what makes the role and the specialized sales process work.

The SDR Script Framework

An SDR script framework is built around booking a qualified meeting.

• Open and earn the moment. An honest, relevant opening (as in any cold outreach) that earns the prospect's attention — the SDR still has to get past the dismissal reflex.
• Establish relevance. Quickly establish why this is relevant to them — a problem they likely have — giving them a reason to engage, without pitching the product.
• Qualify lightly. Ask enough to confirm the prospect fits and the meeting is worthwhile — fit, a plausible need — without a full discovery, which is the AE's job.
• Book the meeting. The SDR's actual goal — secure a meeting with the AE, framed as a worthwhile next step for the prospect, once relevance and basic qualification are established.
• Set up the handoff. Capture what was learned (the relevance, the qualification) to hand to the AE, so the AE walks into the meeting with context.

The framework keeps the SDR focused on booking a qualified meeting — open, establish relevance, qualify lightly, book, hand off — rather than selling, which is the AE's job after the meeting is booked.

Qualification and the Handoff

A crucial part of the SDR's job is qualifying enough — and handing off well — so the AE receives a worthwhile, contextualized meeting. The SDR qualifies lightly: enough to confirm the prospect fits the ICP and has a plausible need worth the AE's time, but not a full discovery (which is the AE's job in the meeting). This light qualification is a balance: qualify too little and the SDR books meetings that waste the AE's time (unqualified prospects who were never worth meeting); qualify too much and the SDR drifts into the AE's discovery work and bogs down the efficient meeting-booking the role is for. The right level is enough to confirm the meeting is worthwhile — fit and plausible need — leaving the deeper discovery to the AE. Then the handoff: the SDR captures what they learned (the relevance that resonated, the qualification confirmed, any context about the prospect's situation) and passes it to the AE, so the AE walks into the meeting informed rather than starting cold. A good handoff makes the AE's meeting far more effective, because the AE builds on the SDR's groundwork rather than re-establishing everything; a poor handoff (booking a meeting with no context) wastes the SDR's work and starts the AE from scratch. So the SDR's deliverable is not just a booked meeting but a qualified, contextualized one — a meeting with a fitting prospect, plus the context the AE needs to run it well. The qualification confirms the meeting is worth booking; the handoff makes it worth more. Both are part of the SDR doing their job well, which is producing qualified meetings that convert, not just meetings that fill the AE's calendar.

The SDR Script Mistakes to Avoid

A few SDR script mistakes recur. The biggest is trying to sell — pitching the product and attempting to advance the deal, which is the AE's job done badly at the wrong stage; the SDR's job is to book a qualified meeting, not sell. The second is over-qualifying — doing a full discovery on the prospecting call, which bogs down the efficient meeting-booking the role is for and duplicates the AE's work; qualify lightly, leave the deep discovery to the AE. The third is under-qualifying — booking any meeting regardless of fit just to hit a meeting quota, which fills the AE's calendar with unqualified prospects and wastes everyone's time; qualify enough to confirm the meeting is worthwhile. The fourth is the bad handoff — booking a meeting with no context for the AE, who then starts cold; capture and pass the context. The fifth is the canned, robotic delivery that fails on any call — an SDR reciting a script sounds exactly like the outreach prospects dismiss; run the framework naturally. And the sixth is being so focused on the meeting-booking goal that the SDR pushes for a meeting before establishing relevance, which feels pushy and fails — establish relevance first, then book. Each mistake either confuses the SDR's role (selling, over-qualifying), undermines the deliverable (under-qualifying, bad handoff), or fails on delivery (canned, premature). Avoiding them comes back to the role and the framework: establish relevance, qualify lightly, book the qualified meeting, hand off the context, delivered naturally — which is the SDR doing their actual job well.

Among these, the sell-versus-book confusion is the root mistake from which several others grow: an SDR who thinks their job is to sell over-qualifies (doing discovery to sell), pitches prematurely, and loses sight of the booking goal. Clarifying the role — the SDR books qualified meetings, the AE sells — resolves the root confusion and prevents the downstream mistakes. The SDR script's most important job is to keep the SDR focused on booking qualified meetings rather than drifting into the selling that is not their role, which is why understanding the role is the foundation of using the script well.

Run It as a Framework, Not a Recited Script

As with every script, the SDR script works as an internalized framework delivered naturally, not a recited script — and SDRs are especially prone to robotic delivery because they make many calls and the repetition can turn the script into a rote recitation. An SDR reciting the same script robotically on call after call sounds exactly like the canned outreach prospects dismiss, which fails at the SDR's job of earning the moment and booking the meeting. The SDR who internalizes the framework (open, establish relevance, qualify lightly, book, hand off) and runs it naturally — adapting the relevance to each prospect, sounding like a real person — books far more qualified meetings than the one reciting a rote script. This matters especially for SDRs because the volume of calls makes rote recitation tempting, and because the SDR's whole job depends on earning the moment and the meeting, which a robotic delivery forfeits. So the SDR framework must be internalized and run naturally, with the relevance tailored to each prospect, rather than recited identically every time. The same framework-not-script principle that governs every sales conversation applies with particular force to the high-volume SDR role: internalize the framework, deliver it naturally, tailor the relevance — because the SDR making many calls especially needs to sound like a person rather than a recording to earn the moments and meetings that are their entire deliverable. A framework run naturally, even at volume, books meetings; a script recited robotically, however many times, mostly gets dismissed.

FAQ: Sales Script for SDRs