What a sales playbook should contain

A sales playbook fails for one of two reasons. Either it was downloaded as a template and never made specific to the company's buyer, or it was written as a 60 page document that no rep opens during a live deal.

The test is simple. A rep gets an objection they have not heard before, on a Tuesday afternoon, with the buyer waiting for a reply. Can they find a useful answer in under a minute? If not, the playbook is decoration.

The sections that earn their place

Who you sell to, described honestly

Not a persona with a stock photo. The company profile where your win rate is highest, the roles who feel the pain, the roles who block, and the situations where you should walk away. The disqualification list is the most valuable page and the one most playbooks omit.

Stage definitions and exit criteria

The same definitions the CRM uses, written out. If the playbook and the pipeline disagree, reps follow the pipeline and ignore the playbook.

Discovery questions grouped by what they uncover

A flat list of 40 questions is useless. Group them by purpose: current state, cost of the status quo, what has been tried, decision process, timeline pressure. Five or six per group is plenty. Reps need a prompt, not a script.

The demo, mapped to problems

Not a feature tour. A short set of paths through the product tied to the problems you actually hear, so the rep shows the two things that matter to this buyer rather than everything the product does.

Objections, with the real answers

Write down the six or seven objections your team hears every week. For each one, the underlying concern, 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 how to handle it when the buyer is already committed to someone else. Overstating this section costs deals, because buyers know the market better than the playbook usually assumes.

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. Without this the playbook has no enforcement mechanism.

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 an owner, and 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 becomes automatic, and from updating it whenever a rep discovers something that works. A playbook that has not changed in a year is not being used.