A BDR playbook is the written plan every outbound channel works from: who to target, what to say, how to say it on the phone, by email and on LinkedIn, and how to judge whether it's working. Without one, each rep invents their own targeting and message, and nobody can tell what's actually driving meetings.
Here's what to put in a BDR playbook, section by section, with a template you can copy and the mistakes that make most playbooks go stale.
What a BDR playbook is, and what it isn't
A good playbook is a short, living document. It's the shared source of truth for strategy, data, calling, email and LinkedIn, and it changes as buyers tell you what works.
It isn't a 60-page binder nobody opens, and it isn't a script to read word for word. If your team can't find the answer to "who do we call this week and what do we say?" in a few minutes, the playbook is too long.
The ten sections of a BDR playbook
| # | Section | Questions it answers |
|---|---|---|
| 1 | Goals and targets | How many qualified meetings a month, by when, and how we'll judge the first 90 days |
| 2 | Ideal customer profile | Which industries, company sizes, regions and tech stacks, plus who we never contact |
| 3 | Buyer titles | Who feels the problem, who signs, who else sits on the buying committee |
| 4 | Problems and proof | The three problems each title cares about, in their words, and the proof that we solve them |
| 5 | Campaigns | Three to five ranked campaigns, each with an angle and a reason to reach out now |
| 6 | List rules | Data sources, how contacts are verified, list size per channel, and exclusions |
| 7 | Channel plays | The call opener and talk track, the email sequence, the LinkedIn sequence, and the cadence across them |
| 8 | Objections | The most common objections and how to answer each one |
| 9 | Qualified meeting and handoff | The written definition, what goes in the meeting notes, and who owns no-shows |
| 10 | Review and changes | The weekly scorecard, who decides what to scale or stop, and how changes are logged |
How to fill in each section
1. Goals and targets
Write the meeting goal as a range for the first 60 days, then a firm monthly target once you have real data. Judge the first quarter on qualified meetings and pipeline, not closed revenue. More in why outbound takes 90 days.
2. Ideal customer profile
Be specific enough that a GTM engineer can turn it into filters: industry, employee count or revenue band, region, and any technology that signals fit. Add the exclusions too: current customers, open deals, competitors and anyone who asked not to be contacted.
3. Buyer titles
List the primary title (who feels the problem most), the economic buyer (who signs) and the other people who usually join the deal. Enterprise deals involve several stakeholders, so plan to reach more than one person per account.
4. Problems and proof
For each title, write the three problems they'd describe in their own words, not your product's features. Next to each one, add a proof point: a customer result, a number or a short story.
5. Campaigns
Rank three to five campaigns, each with a clear angle and a reason to reach out now. Good campaigns are often built on signals, like a new leader in the buyer's seat, a hiring spree or a funding round. Our outbound signals playbook has 50 ideas. Launch the top-ranked campaign first, and keep the rest ready as fallbacks.
6. List rules
Write down which data sources to use, how contacts are verified, and how big each channel's list needs to be to sustain its volume for at least four weeks. See what a GTM engineer does.
7. Channel plays
Keep one message and adapt it to each channel:
- Phone: a 15-second opener, two or three questions that qualify, and the ask for a meeting. For example: "Hi Sam, it's Alex from Acme. I'll be quick. We help finance teams at companies like yours cut month-end close from ten days to five. Is close time something you're working on this year?"
- Email: a short sequence of three to five emails, each with one idea and one ask.
- LinkedIn: a connection request and two or three follow-up messages, ideally sent from an executive's profile.
- Cadence: how the three channels line up over two to three weeks. See cold calling vs cold email vs LinkedIn for a sample pattern.
8. Objections
List the five to ten objections your team hears most, with a short answer for each. A few common ones:
| Objection | A good answer |
|---|---|
| “Just send me an email.” | “Happy to. So I send something useful, what's the biggest priority for you on this right now?” |
| “We already have a vendor.” | “Most teams we talk to do. If you could change one thing about it, what would it be?” |
| “There's no budget.” | “Understood. Is it worth 20 minutes now so you have a plan ready when budget opens up?” |
| “Not interested.” | “Fair enough. Is that because it's not a priority, or because you've already solved it?” |
Update this table every week with what callers actually hear.
9. Qualified meeting and handoff
Write the definition down: the titles, company size and need the buyer has to confirm. Then define the handoff: the calendar invite, the notes your AE gets, and who reschedules no-shows. See what counts as a qualified meeting.
10. Review and changes
Hold one 30-minute review every week. Each channel reports its numbers and one thing buyers said. Decide what to scale, what to stop and what to test next, and log every change in the playbook. Our BDR metrics scorecard shows what to track.
How to roll it out
- Draft it before launch. The strategy owner writes the first version.
- Get it approved in writing. The client or your sales leader signs off on the targeting, scripts and lists before anything goes out.
- Share one version. Every channel works from the same document.
- Change one thing at a time. Then you can tell what made the difference.
At BizDev Labs, the playbook, target accounts, scripts and lists are approved in writing during the first 14 days, before any outreach starts.
Mistakes that make playbooks go stale
- Too long to use. If it takes an hour to read, nobody will.
- Written once, never updated. Buyers change, and the playbook should change with them every week.
- No exclusions. Contacting current customers or open deals damages trust fast.
- No written definition of a qualified meeting. Every disagreement about results traces back to this.
- One message for every title. A CFO and a VP of Operations care about different problems.
- No owner. Someone has to be responsible for keeping it current.
FAQ
What should a BDR playbook include?
Ten sections: goals and targets, the ideal customer profile, buyer titles, problems and proof, ranked campaigns, list rules, channel plays, objection handling, the qualified meeting definition and handoff, and the weekly review process.
How long should a BDR playbook be?
Short enough to use daily. For most SaaS teams, a few pages plus the scripts and sequences is enough.
Who should write the BDR playbook?
Whoever owns outbound strategy, usually a sales leader, founder or strategist, with input from the callers who hear objections and the AEs who take the meetings.
How often should a BDR playbook be updated?
Review it weekly and change it whenever the data says to. Log every change, so you know what moved the numbers.
The short version
A BDR playbook turns outbound from a set of individual habits into a system: one target, one message, adapted to each channel, reviewed every week. Keep it short, get it approved before launch, and change it as buyers teach you what works.
At BizDev Labs, a strategist writes the playbook for every program, and five specialists run it across strategy, data, calling, email and LinkedIn. Book a call and we'll show you what a playbook for your market would look like, and tell you straight if we're not the right fit.