An SDR playbook is a written system that tells sales development people who to target, how to reach them, how to qualify what they find and when to pass a lead to an account executive. A good one fits in a few pages and gets used every day.
This guide gives you a template with ten sections that you can copy and fill in. It is a situation-specific part of the wider sales playbook, and it belongs to the overview of sales enablement.
What is an SDR playbook?
Sybill defines an SDR playbook as a repeatable, execution-first system that defines how sales development people identify, engage, qualify and convert prospects into qualified pipeline (Sybill, read November 11, 2026). The word that matters is "execution". A playbook that teaches concepts is training. A playbook that tells someone what to do at 9:15 on a Tuesday is a playbook.
The guide from Vouris makes a useful point about length. Its author recommends keeping the document tight, and leaving out anything an SDR will not eventually know by heart (Vouris, read November 11, 2026). We follow the same rule below.
How is an SDR playbook different from a BDR playbook?
It is the same kind of document. Companies use the two titles differently, so the useful question is what your own team's job is. If your SDRs work inbound leads, the playbook leans on speed to lead and qualification. If your business development people work outbound, it leans on target lists and cadences. Write the playbook for the job you actually have, and keep one document per job if the two differ a lot.
What goes into an SDR playbook?
Use these ten sections. Together they cover the day from the first list to the handoff.
| # | Section | What it answers |
|---|---|---|
| 1 | Goal and numbers | What does a good month look like? |
| 2 | Ideal customer profile | Who are we looking for, and who do we skip? |
| 3 | Lead tiers | Which leads come first? |
| 4 | Daily rhythm | What do I do in each part of the day? |
| 5 | Outreach cadence | Which touches, on which days, in which order? |
| 6 | Message starters | What do I say in each situation? |
| 7 | Qualification | What must be true before I book a meeting? |
| 8 | Objections | How do I answer the common ones? |
| 9 | Handoff | What does the account executive need from me? |
| 10 | Metrics and coaching | How is it measured, and who reviews it? |
The sections of the Vouris template overlap with this list: company and team information, the industry and the prospect's problem, a short product and pricing section, the sales process and the SDR workflow (Vouris, read November 11, 2026). We moved company background into the onboarding plan and put the ICP, tiers and handoff first, because they decide who gets contacted and when.
Section 1: how do you set the goal and the numbers?
State the monthly goal in one line and the activity behind it. Keep the numbers as your own, taken from the last three months.
| Line | Example for a team of five | Where the number comes from |
|---|---|---|
| Meetings held per person | 12 per month | Average of the last three months |
| Meeting-to-opportunity | 40% | Opportunities created over meetings held |
| Opportunities per person | 5 per month | The two lines above multiplied |
| Working days | 20 | Calendar |
| Daily activity target | 40 touches | Set from your conversion data |
The numbers above are examples, so replace them. If you have fewer than three months of data, say so in the playbook and revisit the numbers when you do.
Section 2: how do you define the ICP and the exclusions?
Write who you want and who you skip. Define the negative criteria too, since they save the most time. A useful ICP fits in a table.
| Field | Fill in | Example |
|---|---|---|
| Company size | Employee or revenue range | 50 to 500 employees |
| Industry | Two or three, in order | B2B software, business services |
| Buyer titles | The person who feels the problem, and who signs | VP Sales, Head of Revenue Operations |
| Trigger events | Things that signal need | New sales leader, hiring surge, new funding |
| Fit signals | What makes a company a good match | Team of ten or more sellers, CRM in place |
| Exclusions | Who to skip | Agencies, companies under 20 people |
Marketbetter's template makes the same point: define the profile in specific criteria and add negative criteria, so the team does not chase leads that will never close (MarketBetter, read November 11, 2026). Apply our 80/20 rule: look at your closed-won deals, find the two or three traits most of them share and build the ICP from those.
Section 3: how do you set lead tiers?
Tiers tell people where to start. Three are enough.
| Tier | Who | Action | Speed |
|---|---|---|---|
| Tier 1 | Inbound requests for a demo or contact, and target accounts showing intent | Call first, then email | Within one hour |
| Tier 2 | Content downloads from the ICP, replies to earlier outreach | Email and a call attempt | Same day |
| Tier 3 | Cold accounts that match the ICP | Planned cadence | Per the cadence |
Marketbetter's template uses a similar three-tier order and puts the hottest leads at the top of the day (MarketBetter, read November 11, 2026). Choose your own speed targets from your data. Many teams find that the first hour after an inbound request matters most, so check yours: compare the meeting rate of leads reached within an hour with the rate of those reached later.
Section 4: what does the daily rhythm look like?
Give people a default day, so they spend less time deciding what to do. Treat it as a starting point that each person can adjust.
| Block | Work |
|---|---|
| 8:30 to 9:00 | Review overnight leads and replies; set the day's top five |
| 9:00 to 11:00 | Tier 1 and Tier 2 calls and emails |
| 11:00 to 12:00 | Follow-ups from yesterday |
| 1:00 to 3:00 | Tier 3 outbound, with the cadence tasks due today |
| 3:00 to 4:00 | Research and list building for tomorrow |
| 4:00 to 4:30 | Log notes, update the CRM, flag deals that need a manager |
Keep two blocks sacred: the morning calls and the end-of-day logging. A day without them goes to inbox work and the pipeline notes fall behind.
Section 5: what does an outreach cadence look like?
A cadence is the schedule of touches for one prospect. Keep the first version simple and change it with data. This one runs fourteen days across three channels.
| Day | Channel | Touch |
|---|---|---|
| 1 | Short note tied to a trigger event | |
| 1 | Connection request with no pitch | |
| 3 | Phone | Call, and a voicemail of fifteen seconds |
| 5 | A useful asset, such as a one-page benchmark | |
| 8 | Phone | Call at a different time of day |
| 10 | A question about the problem, in two lines | |
| 14 | A closing note that offers to stop contacting |
Write down what each touch is for. The first earns a reply, the call earns a conversation and the last one removes the pressure. Review reply and meeting rates by day and cut the touches that produce nothing.
Section 6: what message starters should the playbook include?
Give two or three starters for each situation and tell people to change the words. Lines that sound written by a team of one hundred get ignored. Treat them as patterns to adapt.
| Situation | Starter pattern |
|---|---|
| Inbound demo request | "You asked about [topic] today. What prompted that?" |
| Trigger event | "I saw [event] at [company]. Teams in that spot often run into [problem]. Does that match?" |
| Content download | "You looked at our guide on [topic]. What are you trying to fix?" |
| Cold, by title | "I work with [title] leaders on [problem]. Is that on your list this year?" |
| Follow-up after no reply | "Sending this once more in case it slipped. Should I close it out?" |
Every starter has the same shape: a reason you are writing, a question about the buyer's situation and a low ask. For spoken lines that fit other stages, see the sales talk examples in our library.
Section 7: how do people qualify?
List the facts that must be true before a meeting is booked, and the ones to note but not require. A short checklist beats a long form.
- Problem: the person can describe a problem we solve, in their words.
- Impact: they can say roughly what it costs, or why it matters now.
- Role: they own the problem or can bring in the person who does.
- Timing: something is driving a decision in the next two quarters.
- Fit: they match the ICP table, or have a stated reason to be an exception.
Add a line for the notes the account executive will want: who else is involved, what they use today and what they said in their own words. A meeting booked without these notes costs the account executive the first ten minutes.
Section 8: how do people handle objections?
Write one short answer for each of the four or five most common objections. Each answer follows three moves: acknowledge, ask, answer.
| Objection | Acknowledge | Ask |
|---|---|---|
| "Not interested" | "Fair enough." | "Is it the topic, or the timing?" |
| "Send me information" | "Happy to." | "What would you want it to answer?" |
| "We use a competitor" | "Good to hear." | "What would make you look at an alternative?" |
| "No budget" | "That is common this time of year." | "When do plans for next year start?" |
| "Bad timing" | "Understood." | "What would need to change for it to be a priority?" |
The ask is the part people skip. It turns a brush-off into information. Our post on common sales objections has more answers to adapt.
Section 9: what does a good handoff include?
A handoff is a short note and a meeting invite. Agree the format with the account executives, and make it the same every time.
- Who and where: name, title, company and the CRM link.
- Why now: the trigger or the words they used.
- The problem: one or two lines in their own words.
- Who else: other people named, and their roles.
- What was agreed: the meeting time and what the buyer expects to see.
- What to avoid: anything the buyer said they dislike.
Hold a monthly fifteen-minute review where account executives say which handoffs were good and which missed something. Add the lessons to the section.
Section 10: how do you measure and coach?
Pick a small set of numbers and a regular review. Mix output numbers with a quality score from calls.
| Measure | Type | Review |
|---|---|---|
| Meetings booked and held | Output | Weekly |
| Meeting-to-opportunity rate | Quality | Monthly |
| Reply rate by touch | Output | Monthly |
| Time to first touch on inbound | Speed | Weekly |
| Call score on a qualification scorecard | Skill | Weekly, two calls per person |
Volume numbers tell you whether people are working. They say little about whether people are good at it, which is why a call score matters. Listening to two calls per person each week and scoring them on the qualification checklist shows which part of the playbook people skip. Tools that score every call against your own playbook automate this, and our guide to sales playbook software covers what to look for.
How do you build the playbook in a week?
Day 1
Pull your last twelve closed-won deals and write the ICP.
Day 2
Set the tiers, the daily rhythm and the first cadence.
Day 3
Write message starters and objection answers from real calls.
Day 4
Write the qualification list and the handoff note with account executives.
Day 5
Run a one-hour session, hand it out and book the first review.
Do not wait for it to be perfect. A version one with ten sections and ten pages gets used and improved. A perfect draft that arrives in March arrives too late.
How do you use the playbook to ramp new SDRs?
A new SDR can use the playbook as the spine of the first thirty days. Week one: read it and shadow calls. Week two: practice the starters and objection answers in role play with a manager. Week three: run the cadence on a small list with daily feedback. Week four: work the full day, with a call score each week. Pair it with a dated plan such as our 30-60-90 day plan for sales, which sets goals by phase.
Role play matters most in week two. People who rehearse the objection answers aloud say them better on live calls than people who only read them.
Where does the SDR playbook fit with other playbooks?
It is the front of the funnel. The account executive's sales playbook takes over where the SDR handoff ends, and the GTM playbooks set the wider plan for the market, segment and message that the SDR playbook turns into daily work. If you see a conflict, such as an ICP in the GTM plan that differs from the one in the SDR playbook, resolve it at the higher level first.
SDR work also feeds forecasting. The handoff notes and meeting data flow into the pipeline view described in our guide to revenue intelligence platforms, so keep the CRM fields in the handoff consistent.
What mistakes should you avoid?
- Writing a manual. If it takes an hour to read, nobody will read it twice.
- Scripting every word. People sound like robots and buyers can tell. Give patterns and let people adapt.
- Ignoring the account executives. The handoff section only works if they help write it.
- Skipping the exclusions. The ICP without a skip list sends people to the wrong accounts.
- Never reviewing. A cadence that worked last year may not work now. Check the data every month.
Frequently asked questions
What is a BDR playbook?
A BDR playbook is the same kind of document as an SDR playbook, written for business development people. It defines who to target, how to reach them, how to qualify and when to hand the lead to an account executive. Companies use the two titles differently, so write the playbook for the job as your team defines it.
How long should an SDR playbook be?
Short enough that people read it, usually five to ten pages. Include only what a new person should know by heart after a few weeks. Link out to deeper material instead of pasting it in.
How often should you update an SDR playbook?
Review it every quarter and update the messaging and cadence monthly if results move. Change one section at a time, so you can tell what caused a change in results.
Where to start
Pull your last twelve closed-won deals and write the ICP table. Then fill in the tiers and the daily rhythm and give the draft to two SDRs and one account executive for a week. Return to the sales playbook guide to see how the SDR playbook fits the full document, and to the sales enablement overview for the wider program.