Skip to content

SDR playbook: what goes in it, and how to keep it alive

What belongs in an SDR playbook, why agencies need one per client project, and how to keep it current with an FAQ the whole team writes to.

Updated 12 October 20266 min readTypeGuide
script test · Northgate Ltdrunning
VariantLeadsCalledMeetingsLeads to meetings
AOpener · cost angle21016494.3%
BOpener · renewal timing208159157.2%

Tip · "We just renewed"

Ask when the next review is, then offer a short call before it.

posted by Shelley L. · project FAQ

Illustrative example — sample data, not a customer screenshot.

An SDR playbook is the written answer to “how do we call this market”. Most teams have one. Most of those were written before the first call, saved as a PDF, and not opened since. The reps who have been on the team a while do not need it; the new ones cannot trust it.

A useful playbook is short, specific to one offer, and changed every week by the people making the calls.

What goes in an SDR playbook

Who to call

Ideal company profile, target titles, and who not to call.

Why they care

The two or three problems the offer solves, in the prospect's words.

The call script

Opener, discovery questions, the ask, and a voicemail.

Objections

The ones that come up most, with short answers that end in a question.

Qualification

What makes a meeting worth booking, and what does not.

After the call

Outcomes to log, follow-up rules, and when to stop calling a lead.

Leave out company history, a full product feature list and anything a rep would not use during a call. If a section has not been read in a month, cut it.

Qualification belongs in the playbook

The most expensive gap in most playbooks is qualification. If reps do not know what a good meeting looks like, they book what they can, the client’s sales team sits through meetings that go nowhere, and the no-show rate climbs. Write down the minimum: right role, right company size, a real problem, and agreement to a specific time. Then review booked meetings against it.

One playbook per client project

In-house teams usually sell one offer, so one playbook is enough. Agencies are different. Each client has its own product, buyer, market and language, and a rep may call for three of them in a day. A shared agency playbook covers how you work; each client project needs its own short playbook for what to say.

The per-client playbook should sit where the rep works that client’s leads. If it lives in a shared drive, it will not be open during the call.

Keep it living with a project FAQ

The real playbook is learned on the phone. A new objection on Tuesday, a better answer on Wednesday, a discovery that the target title is wrong by Friday. If that only lives in a chat thread, the next rep starts from zero.

Keeping a playbook current

  1. 1

    Capture on the call

    New objection or question? A one-line post in the project FAQ.

  2. 2

    Answer within the week

    The account manager or a senior SDR adds the answer.

  3. 3

    Promote what repeats

    An FAQ entry that keeps coming up moves into the script.

  4. 4

    Test the script

    Run a new version against the old one and keep the one that books.

  5. 5

    Prune monthly

    Remove lines nobody uses and answers that are out of date.

Static playbook

  • Written once at kickoff
  • Saved in a shared drive
  • Objections learned again by each rep
  • Script changes argued in meetings

Living playbook

  • Changed weekly by the people calling
  • Open next to the lead during the call
  • New objections added to the FAQ the same day
  • Script versions compared by meetings booked

Who owns the playbook

Someone has to. On an agency team that is usually the account manager for the client, because they hear from the client what changed and see which meetings the client valued. On an in-house team it is the SDR team lead. Everyone on the roster writes to the FAQ; the owner decides what goes into the script.

How to tell if it works

Watch three things per client project: how long a new rep takes to book their first meeting, how many held meetings the roster produces per working hour, and how often the same question gets asked twice. The first two should improve as the playbook improves; the third should fall.

Where Dialbrew fits

Dialbrew keeps call scripts and a tips/FAQ board inside each client project. Scripts are grouped by category (openers, objection handling, voicemail and more), and versions can be A/B tested by meetings booked. Only SDRs rostered on the project and its account manager see it, which matters for agencies running many clients and for freelance SDRs who should only see their own projects.

Related guides: cold call script, objection handling for SDRs and sales enablement for SDR teams.

Book a walkthrough

Put every client on one floor

A walkthrough on your own roster, clients and commission model — from an imported list to a sent invoice. Judged on your operation, not a demo dataset.

One booked meeting pays for an SDR's seat for the month.

EU-hosted · eu-central-1 · integrates the CRM, calendar and telephony you already run