The Sales Playbook: Write It for the Moment a Rep Is Stuck

Most companies have a sales playbook, and most reps cannot tell you what is in it. It was written carefully, presented at a kickoff, saved to a shared drive, and opened a handful of times since, usually by new hires in their first week.

The common explanation is that reps are busy, or do not value documentation. The better explanation is that most playbooks are written to be read, and nobody reads a playbook. They consult it, briefly, at the moment they are stuck: the buyer just said they already have a supplier, the champion has stopped replying, procurement has sent back a contract covered in changes. A document organised like a company handbook is no help in those thirty seconds.

This guide covers why playbooks go unread, how to structure one around the moments reps actually get stuck, what belongs in it, and how to tell whether it is working.

Why sales playbooks go unread

Look at the contents page of a typical playbook and it follows the seller's org chart: company overview, products, ideal customer, personas, competitors, pricing, sales process, tools. Every section is accurate. Together they form a reference manual, organised by topic, written to be read front to back.

People do not use manuals that way, and this is well established outside sales. Research on how people use documentation found long ago that readers skip the introduction, jump in at the point where they are stuck, and want to know what to do next rather than how the system works. A reference structure answers "what do we know about competitor X?" A stuck rep is asking "they just mentioned competitor X, so what do I say?"

There are three other reasons playbooks go unread, all following from the first.

• They are too long to use in the moment. A thirty-page section on objections is useless thirty seconds before a call.
• They describe instead of instruct. "Our differentiation is our integration depth" tells a rep what is true. It does not tell them what to say when a buyer asks why they should switch.
• They go stale quietly. Pricing changes, a competitor launches something, the best answer to a common objection improves. Nobody updates the document, reps notice it is out of date, and they stop trusting all of it.

Nobody reads a sales playbook. They consult it, for thirty seconds, when they are stuck. Write it for those thirty seconds.

Structure it around moments, not topics

The fix is to change the unit of the playbook. Instead of topics, organise it around moments: the specific situations in a deal where a rep needs to decide what to do next.

Topic-based	Moment-based
Competitors	"They already use a competitor"
Pricing	"They want a price on the first call"
Sales process	"My champion has gone quiet"
Personas	"Finance just joined the call"
Legal	"Procurement sent a redline"

The information in both columns overlaps heavily. What changes is the way in. A rep searching in the words they would use to describe their problem finds a page written for exactly that situation.

Where do the moments come from? Not from a planning workshop. They come from calls and lost deals: the points where conversations stall, the objections heard every week, the stages where deals sit for too long. A good first version has fifteen to twenty-five moments. That number is not a rule, but it is enough to cover most of what goes wrong and small enough to keep current.

What a good entry looks like

Every moment gets one short page, the same shape every time, so a rep knows where to look:

1. The moment, in the words a rep would use to search for it.
2. What is usually going on. One or two sentences on what the buyer probably means.
3. What to say first. A short talk track, written the way people talk.
4. What not to do. The common, instinctive mistake.
5. The next step to aim for. What a good outcome of this moment looks like.
6. Proof to use. One customer story or fact that fits this moment.
7. Owner and date. Who maintains this entry and when it was last checked.

Here is an example. The product and wording are invented.

That entry fits on one screen. A rep can read it in the corridor before a call. For the full version of this particular objection, see we already have a vendor.

The sections that earn their place

The moments are the core, but a playbook needs a few pages of context around them. These are the ones worth writing, each kept short.

1. Who we sell to, and why they buy. One page: the customer we win with, the problem they have in their own words, and what usually triggers a purchase. Not a persona deck.

2. How our buyers decide. The stages of the buyer's decision, defined by what the buyer does at each one, with what has to be true to move forward. We explain why stages should follow the buyer in our guide to the B2B sales funnel, and the shared plan that keeps a deal moving in the mutual action plan template.

3. Discovery. The handful of questions that tell you whether a deal is real, and what to listen for in the answers. If your team uses a qualification method such as MEDDIC, map it here rather than re-explaining it.

4. The moments. As above: fifteen to twenty-five entries, each one screen.

5. Competitive situations. Written as moments too: "they're also talking to X". What X is good at, where it is weaker for buyers like ours, and the question that helps the buyer see the difference for themselves.

6. Pricing and negotiation rules. What a rep can offer without approval, what needs approval and from whom, and what never to give away. A rep who has to ask about every discount loses momentum; a rep with no rules gives away margin. Our negotiation frameworks cover the conversation itself.

7. Talk tracks and proof. Short scripts for the conversations that repeat, and a library of customer stories sorted by buyer type and problem. See what a talk track is and the collateral worth building.

8. Handoffs. What happens when a deal moves between people: from the person who booked the meeting to the account executive, and from sales to the team that onboards the customer. Most lost context is lost at a handoff.

What to leave out

Company history, organisation charts, product documentation, everything marketing has ever published, and long methodology explanations. All of it can be linked from the playbook. None of it belongs inside it.

Keep it alive

A playbook decays from the day it is published. Markets move, products change, and the best answer to a common objection keeps improving as reps try new things. Three habits stop the decay.

• Every section has a named owner. Not "enablement" or "sales leadership": a person, whose name is on the page.
• New moments come from calls. When call reviews or lost deals keep turning up the same difficult moment, it gets an entry. When a rep finds an answer that works better than the documented one, the entry changes. A playbook that only enablement writes will drift away from what happens on calls.
• Review on a schedule, and delete. Once a quarter, check each entry's date, update what is stale, and remove what nobody uses. A smaller playbook people trust is worth more than a complete one they do not.

We wrote about why the gap between what is documented and what reps actually do is the central problem of enablement in sales enablement strategy.

How to tell whether it's working

Page views tell you almost nothing. A playbook can be opened often by new hires and ignored by everyone else. Better signals:

• When it is used. Searches and views just before calls, by experienced reps as well as new ones, mean it is being consulted at the moment it was built for.
• What people search for and do not find. Searches with no matching entry are the best source of new moments.
• Whether the moments go better. If an entry covers a common objection, calls where that objection comes up should more often end with a next step than before. This is the only signal that the playbook changed behaviour rather than knowledge.
• Whether reps contribute. When reps start suggesting changes, they trust it.

A playbook is not learned by reading it

Even a well-structured playbook has a limit. Reading the right answer to "we already have a supplier" does not mean a rep can say it smoothly when a real buyer says it, slightly differently, in a hurry. The words have to be practised out loud a few times before they come naturally under pressure.

So the most useful thing to do with a new or updated entry is to rehearse it: a few minutes in a team meeting where someone plays the buyer and each rep tries the moment two or three times. We described how to fit that kind of short, repeated practice into a working week in inside sales training.

Where our tool fits

We build an AI practice tool, so read this with that in mind.

The moments in a playbook are exactly what SalesArmor is built to rehearse. A rep can practise a call against a realistic AI buyer who raises the objections your playbook covers, try the documented answer, and get scored afterwards. If a call goes wrong at a particular moment, they can replay it from just before that point and try again. See objection handling practice.

Common questions about sales playbooks

What is a sales playbook? A sales playbook is a guide that tells reps what to do in the situations they meet while selling: who to sell to, how buyers decide, what to ask, what to say when specific objections or problems come up, what they can offer on price, and how deals move between people. The useful ones are written for quick use at the moment a rep needs help.

What should be included in a sales playbook? A short description of who you sell to and why they buy, how your buyers make decisions, the key discovery questions, a set of common difficult moments with what to say in each, competitive situations, pricing and negotiation rules, talk tracks and customer proof, and how handoffs work. Company history and product documentation should be linked rather than included.

Why don't sales reps use sales playbooks? Usually because the playbook is written as a reference manual, organised by topic and meant to be read in full, while reps only consult it briefly when they are stuck. It is also often too long to use before a call, describes rather than instructs, and goes out of date, which makes reps stop trusting it.

How long should a sales playbook be? Short enough that any single answer fits on one screen. A good first version has a few pages of context plus fifteen to twenty-five specific moments, each with its own short page. Length matters less than whether a rep can find the right page in a few seconds.

What is the difference between a sales playbook and a sales process? The sales process describes the stages a deal moves through and what has to be true to move between them. The playbook is broader and more practical: it includes the process, but mostly tells reps what to do and say in specific situations within it.

How do you create a sales playbook? Start from real calls and lost deals rather than a template. List the moments where deals stall or reps get stuck, write a one-screen entry for each with what is going on, what to say, what to avoid and the next step to aim for, then add short sections on buyers, decisions, discovery, pricing rules and handoffs. Give each section an owner.

How often should a sales playbook be updated? Continuously for individual entries, whenever a better answer or new situation emerges, plus a scheduled review about once a quarter to update stale pages and delete unused ones. An out-of-date playbook loses reps' trust quickly.

How do you measure whether a sales playbook works? Look at whether experienced reps consult it before calls, what they search for and fail to find, and above all whether the moments it covers start going better on real calls, for example more conversations continuing after a common objection. Overall page views say very little.

A note on sources

This guide publishes no figures on how much of a playbook reps use, how often it is opened or how much content goes unread. The widely shared numbers come from vendor surveys whose questions and samples are not public.

The argument that people consult documentation at the point they are stuck, rather than reading it in order, draws on research into how people use manuals, most notably John M. Carroll's work on minimalist instruction in The Nurnberg Funnel. The example entry uses an invented product and invented wording. The moment-based structure, the entry format and the measurement signals are ours.