What a sales playbook should actually contain
The test is whether a rep can find a usable answer in under a minute on a Tuesday afternoon with a buyer waiting. Most playbooks fail that test.
Playbook · 7 min read
What belongs in a sales playbook template
A working sales playbook covers who you sell to and who to walk away from, the questions that surface a real problem, what has to be true to advance each stage, the objections you hear weekly with the answers your best rep gives, and what the manager does to enforce it. A downloaded template hands you the headings without any of the answers, which is why most of them go unread.
A sales playbook fails one of two ways. Either it was downloaded as a template and never made specific to your buyer, or it grew into a 60 page document that no rep opens with a deal in front of them.
The test is simple. A rep hits an objection they have not heard before, Tuesday afternoon, buyer waiting on a reply. Can they find a usable answer in under a minute? If not, you have decoration.
The sections that earn their place
Who you sell to, described honestly
Not a persona with a stock photo and a fake name. The company profile where your win rate is highest, the roles who feel the pain, the roles who quietly block, and the situations where you should walk away. The disqualification list is the most valuable page in the document and the one nearly every playbook leaves out.
Stage definitions and exit criteria
The same ones the CRM uses, written out in full. When the playbook and the pipeline disagree, reps follow the pipeline and stop trusting the playbook.
Discovery questions grouped by what they uncover
A flat list of 40 questions is useless. Group them: current state, cost of doing nothing, what they already tried, decision process, timeline pressure. Five or six per group. A rep needs a prompt, not a script.
The demo, mapped to problems
Not a feature tour. A few short paths through the product tied to problems you actually hear, so the rep shows the two things this buyer cares about instead of everything the product does.
Objections, with the real answers
Write down the six or seven you hear every week. For each: the concern underneath it, a response that has worked, and the question that reopens the conversation. Collect these from the reps who close. Not from marketing.
Competitive positioning
Where you genuinely win, where you genuinely lose, and what to do when the buyer already picked someone else. Overstating this section loses deals, because buyers usually know the market better than the playbook assumes they do.
The manager's cadence
Most playbooks stop at the rep. Include what the manager does: the weekly review format, the questions asked in deal inspection, what triggers a coaching session. Leave this out and the playbook has no enforcement mechanism at all.
Format matters more than length
- One page per section, searchable, wherever your team already works
- Written in the words your buyers use, not internal product language
- Dated, with a named owner, reviewed once a quarter
- Built with the reps who are already winning, so it describes something real
A playbook assembled from a template describes a company that does not exist. A playbook assembled from your own recorded calls describes yours.
How it gets adopted
Publishing it does nothing. Adoption comes from the manager referencing it in every deal review until the language is automatic, and from updating it the week a rep finds something that works better. A playbook that has not changed in a year is not in use.