Sales Playbook

In a company with one strong seller, that person's method is written down nowhere. They can't explain it either. What they ask on a first call, when they bring up price, how they answer someone who says it's expensive — all of it is in their hands rather than in words.

So a new rep learns by sitting beside them. Listening to calls, joining meetings. After three months they can approximate it, but which parts of the approximation are the method and which are that person's personal habits is not something they can tell. Sent out alone in that state, even the parts that were working start drifting.

The arrangement holds at two reps and collapses at six. The person doing the teaching runs out of hours, and six people begin selling six differently learned ways. At that point there's no basis for telling a rep with a low win rate what to change. With no standard, the difference can only be called style, and style is not something a manager can coach against.

A sales playbook is that method moved into writing. Turn the strong seller's judgment into conditions and questions and a new rep finds their footing in a month instead of three, and a weak result can be traced to a specific stage.

Five things go inside.

1. Who you sell to — which companies, and which companies you don't sell to. The exclusions matter more. Written down that you don't take companies under twenty people, a rep stops spending hours on that part of the list.
2. Stages and advancement conditions — for each deal stage, the value showing how far a deal has come, one sentence on what has to be true to advance. To move from demo to proposal, technical questions have to be closed and the approval path known. Without those sentences, two reps will file the same deal at two different stages.
3. What to do and ask at each stage — specific enough to list the five questions that must come up in a discovery call, the conversation where you learn the customer's situation and problems. With the questions written, the quality of a first call stops varying by who ran it.
4. Common objections and answers — how to respond to too expensive, not right now, and we're looking at something else, written as actual sentences rather than tactics.
5. The handoff procedure — the sales handoff that passes a signed customer to the next owner is the last chapter, so one document spans first contact through life after the contract.

It has to be short. Nobody opens a hundred-page document twice. One page per stage across five stages, one page per objection type across four, and two pages front and back is enough. Length is the most common reason a playbook goes unread, and an unread playbook teaches nobody anything.

Revenue operations or a sales manager writes it, but the content comes from the field.

There are two ways to build it. One is listening to about twenty call recordings from the strongest rep and pulling out what's common. The other is laying twenty won deals next to twenty lost ones and counting which stage separated them. The first produces the language; the second produces the conditions. Build from only one and you end up with either plausible phrasing or bare numbers.

Three groups read it.

1. A new rep reads it front to back in their first month. For them it's a textbook, and how quickly they reach their first closed deal is the most direct measure of whether the document works.
2. An experienced rep opens one page when they need it — usually hunting for an answer to an objection they haven't met before.
3. A manager uses it sitting across from a rep, comparing a low win rate against the stage conditions instead of describing it by instinct.

The revision cadence gets fixed too, usually once a quarter, plus immediately whenever the product or the price changes. When internal enablement — training sales and customer success ahead of a launch — runs without this document being updated in the same pass, the training describes the new feature while the document still describes the old one.

"The playbook has the condition for moving to proposal. If the approval path isn't confirmed, it's still at demo."

Reversing a stage call on the basis of the document.

"I rewrote the objections chapter this quarter. More competitor talk than before."

The document changed because the market did.

"The new hire ran her first call off the playbook and got through all five questions."

Confirmation that the document actually taught someone.

At Pagedeck, Grace owns this document and has capped it at ten pages. Building the first version meant listening to twenty of Sofia's call recordings. The most useful thing that came out wasn't any clever explanation — it was the order of her questions on a first call. Sofia always asked what they do today and how before bringing up the product at all, which meant every later sentence had something of theirs to attach to.

Revisions happen in the first week of a quarter. Last quarter's lost deals get read together, and any reason that appears three or more times goes into the document. Last time the addition was when to ask about the customer's procurement process, after three deals slipped a quarter on that alone.

A common belief is that a playbook is a rule to comply with. It's written down, so breaking it looks like a violation. But the purpose of the document is to provide a starting point, not control. Start policing reps who reorder things to suit the person in front of them and two things happen: methods that work in the field never make it back into the document, and reps ignore it while recording their work as though they followed it. What's left then is a record that doesn't match reality.

The other belief is that a good playbook lasts. The work is heavy enough that it's tempting to think so. But everything in it was extracted from past deals. Change the price or gain a competitor and the objections chapter ages first; add features and the stage conditions fall out of true. A new hire reading a six-month-old playbook learns how to sell a product that no longer exists. Without a fixed revision cadence, having the document can be worse than not having it, because it carries authority its contents no longer earn.