How to Write a Sales Playbook People Actually Use

Salesforce's State of Sales research found that reps spend just 28% of their week actually selling ↗. Every minute a playbook asks a rep to spend reading it comes out of that 28%. So a playbook has to earn its place by saving more time than it costs.

Our opinion is that most founder-led teams need five one-page plays and not a manual. The rest of this post is the case for that, and a method for writing them.

A playbook fails by size and by distance#

The usual story starts with good intentions. Someone spends weeks writing a long document that covers the whole sales process. It is shared once, praised once and then forgotten.

Two things kill it. The first is size: a document that covers everything is hard to search in the middle of a deal. The second is distance. If the playbook lives in a folder, and the rep lives in the CRM and the inbox, the playbook loses.

One that gets used has three properties. It is short, it is built from deals you actually won, and it sits where the rep is working when the need arises. Anything that adds reading and reporting on top of the rep's week will lose, and anything that removes guesswork and rewriting will win.

Five plays are enough to begin#

Pick the situations that cost you the most when they go wrong. For a founder-led B2B team these are usually the first discovery call, the "we already use a competitor" conversation, a pricing or budget objection, writing and presenting a proposal, and a deal that has gone quiet. Write one play for each. If the team is a founder and one or two sellers, that is plenty. Add a sixth only when the same question comes up for the third time.

Write down what already won#

The best content is what has happened in deals you won, so start there. Pick three to five recent closed-won deals. For each, sit with the person who ran it and walk through the deal in order, using the real artifacts: the first email, the discovery notes, the proposal, the follow-ups.

Ask specific questions, not "how did you win?". What did you know about the account before the first call, and where did you find it? Which question did the buyer react to most? When did you first meet someone other than your main contact, and how? What was the hardest objection, and what did you say? What did you send after the call, and why that?

Frame the session as learning and not review, because people share more when nobody is judging them. Include steady performers as well as stars. A top performer's habits often rest on personal style or a strong network and are hard to copy, while a steady performer's habits turn into steps more easily. Interview both, and look for what they share.

Memory is unreliable, so back each interview with evidence. If calls are recorded, listen to the first discovery calls of your best deals. If not, read the email threads and proposals. The patterns worth writing down tend to be few and simple: two or three questions that open the buyer's problem, a standard way to bring in a second stakeholder, one short document sent after every call. The goal is not to find a secret. It is to write down what already happens and make it repeatable.

What to write and what to skip#

Not every habit belongs in the playbook. Leave out anything that depends on one person's contacts, anything that only worked once, anything with no clear link to a better outcome, and anything you cannot explain in a sentence. A short playbook that is trusted beats a complete one that is ignored.

One page per play#

A play answers a single question: what do I do when this happens? Use the same four parts every time. The trigger is an observable event, such as "the buyer names a competitor" or "no reply seven days after the proposal". The goal is what you want to be true afterwards. The steps are a short numbered list of what to do and say. The assets are links to the exact materials the play uses.

Play: Buyer mentions a competitor
 
Trigger: The buyer names a vendor they already use or are evaluating.
 
Goal: Understand what they like and what is missing, without attacking
the competitor.
 
Steps:
1. Ask what made them choose or consider that vendor.
2. Ask what they would change if they could.
3. Match the answer to a strength you can show, with an example.
4. Send the one-page comparison, if they ask for it.
 
Assets: comparison one-pager, two customer examples, objection notes.

Keep the language plain. Write exact words only where wording matters, such as one key discovery question, and leave the rest to the rep's judgment. We would advise against full scripts. A rep who reads a script word for word usually sounds worse than one who knows the aim.

Win/loss interviews feed plays like this one directly, because they tell you what buyers said about the alternatives. The same goes for the late-stage plays in proposal to signature.

Put it where the work happens#

Distribution decides adoption. In the CRM, link the relevant play from the deal stage or the opportunity record. Where the CRM supports it, show required fields at each stage, so the questions the play asks are also the fields the rep fills in. That makes the playbook the easiest path. If your CRM cannot hold documents, use one pinned page in your team workspace with a short index, and name plays after the situation they handle, so people find them by what they face.

Some plays can later trigger tasks. When a deal enters the proposal stage, for example, the system can create a task to confirm the buyer's legal and procurement steps. Wiring processes into tools this way is the core of pipeline automation. Do not build it all at once. Start with a shared page and a CRM link, and add automation once the plays are stable.

Use it in coaching as well as onboarding#

A launch email does not make a playbook live. Three habits do. Ask each rep to review the play drawn from their own deal, so they correct mistakes and feel ownership. In one-to-ones and deal reviews, ask which play applies and what happened, because reps who never hear a manager mention the playbook will conclude it does not matter. And role-play one key play in a team meeting, since fifteen minutes of practice teaches more than reading.

In a very small team the founder is the manager, so the founder has to follow the plays too. A founder who runs deals from memory teaches the team to do the same.

New hires benefit most. Give them a path: read the five plays, role-play two, join three live calls, then run a call with feedback. They also show you which plays are unclear, because they ask the questions veterans stopped asking.

Measure use first, then results#

Check use first. Are the CRM fields the plays require filled in, and do sampled deals show the plays being followed? A rarely used play is hard to find, written for the wrong situation, or not useful.

Then check results the play aims at. A discovery play should lift conversion from first call to proposal, and a follow-up play should shorten idle time. Pipeline velocity gives you the measures to compare before and after. Be careful about causation. Other things change when you launch a play, so treat the data as evidence, not proof, and keep asking reps what helps.

Give the playbook one owner, usually the founder or whoever runs the sales process. Unowned documents decay. Once the first version exists, the job takes an hour or two a month: retire plays nobody uses, update plays where buyers now say something different, add a play for any situation that keeps coming up, and refresh the assets.