Sales Playbook: Writing One People Actually Use

A sales playbook records how selling is done in this business. Its value is in two specific places. It shortens the time a new joiner takes to become productive, because they inherit accumulated practice rather than rediscovering it. And it gives a manager something to coach against, so feedback is about a shared standard rather than about personal style.

Most playbooks fail for the same reason: they are written as documents rather than as tools. A long, thorough document satisfies its author and is read once. A short one that a seller opens before a first call, or when a particular objection appears, changes behaviour. Length is the most common substitute for usefulness.

Ideal customer profile, and who you decline

Describe the organisations you serve well in observable terms: sector, size, how they operate today, what makes the problem acute for them. Then describe who you should not pursue and why. The second half is the part usually omitted and the part that saves the most time, because the fastest way to improve a pipeline is to stop filling it with deals that were never winnable.

Personas

For each role involved in a decision, record what they are measured on, what they are worried about, and what they need to see before they will agree. These are frequently different people with conflicting definitions of success, and a seller who knows that in advance handles a multi-stakeholder deal very differently from one who discovers it in week three.

Stages with exit criteria

Define each stage by what the buyer has done. Compare two versions of the same stage. The weak one: proposal sent. The strong one: the buyer has confirmed the requirement in their own words, named who will approve it, and agreed a date to review the proposal. The first can be achieved by pressing send. The second cannot be achieved without the buyer participating, which is exactly why the pipeline built on it is worth forecasting from.

Discovery questions

Keep a bank rather than a script. Group the questions by what they establish: the problem, its cost, who owns it, what has been tried, what happens if nothing changes, and how a decision would be made. A seller draws from the bank as the conversation goes; a seller working through a list in order produces an interview, and buyers can hear the difference immediately.

Messaging

Write problems and outcomes in the customer's language. Features are documented elsewhere and are rarely what a buyer is trying to establish. The most useful format is a short set of statements of the form: this is the situation we see, this is what it costs, this is what changes. If the statements do not survive being read aloud to an actual customer, they belong to marketing rather than to selling.

The right-hand column is not worthless material. It is material that belongs somewhere else and is linked from the moment it becomes relevant. Putting it in the playbook is how a usable twelve-page document becomes an unread eighty-page one.

The most effective method is observational. Listen to recorded calls from the people who sell well and write down what they actually do, particularly in discovery and when handling resistance. Most strong sellers cannot articulate their own method accurately when asked directly, because much of it is habitual, and a playbook built from interviews alone tends to capture what people believe they do.

Equally useful is a loss review discipline. When deals are lost for the same reason three times, that reason belongs in the playbook, either as a qualification criterion, a discovery question or an objection response. A playbook assembled this way grows from evidence rather than from opinion, and sellers can see that it describes their world.

Assign an owner and a review cycle, and date every section. Tie revisions to events as well as to the calendar: pricing changes, product releases, a new competitor appearing in deals, or a pattern of losses. The reason for discipline here is asymmetric. A current playbook helps; an out-of-date one damages, because the first wrong section a seller finds gives them a rational reason to distrust everything else in it.

A battle card is a single-competitor reference that a playbook may point to. A call script is a written call flow for one specific type of conversation. A talk track is the flexible spoken version of a message rather than a document. Sales enablement is the function that usually owns the playbook. The connection that matters most operationally is to the CRM, since stages defined in a document and stages configured in the system need to be the same stages.

Related pages on running a sales process and the system underneath it:sales automation, lead management software, what a CRM is, CRM versus Excel, AI CRM, and features overview.