Sales playbook: stop writing PDFs nobody opens

A COO of a 60-person B2B software company sent me their sales playbook last spring. Fifty-two pages. Discovery questions, objection scripts, competitor positioning, three ICP definitions, an entire chapter on their sales methodology. Someone had clearly spent a month on it, and honestly the content was good.

Then I asked their four AEs when they last opened it.

Two said onboarding week. One said never. The fourth asked which document I meant, because there were three floating around and he was not sure which one was current.

That is the normal outcome, not the embarrassing exception. Forrester's estimate is that 60 to 70 percent of the sales content marketing produces goes untouched, mostly because reps cannot find it at the moment they need it. Other survey data puts the perception gap even more bluntly: around 85 percent of sales managers think they hand reps enough material, and about 15 percent of reps agree.

So the problem is not that your team lacks a playbook. Almost every team has one. The problem is that a playbook written as a document has to compete for attention with a live deal, and it loses every single time.

What a playbook is supposed to do

Strip away the formatting and a sales playbook answers one question: in this specific situation, what does a good rep do next?

That is it. Situation in, action out.

Which means the useful unit is not a chapter. It is a play: a named situation, a trigger that tells you the situation is happening, an action, and a way to tell whether the action worked. Four parts. If any one is missing you have written a blog post for your own team, not a play.

Here is a real one from a client running HubSpot:

• Situation: a deal has been in Evaluation for more than 21 days with a single contact attached.
• Trigger: HubSpot workflow fires when days-in-stage crosses 21 and associated contacts equals 1.
• Action: rep sends the "bring in your finance lead" email, which asks for a 20-minute call with whoever signs the contract, and attaches the one-page business case.
• Signal it worked: a second contact gets attached within 7 days.

Nobody has to remember that. It runs. The rep gets a task with the email template already loaded, and the report at the end of the month shows how many single-threaded deals got a second contact.

Compare that to page 34 of a PDF telling reps to "always multithread." Everyone agrees with page 34. Nobody does page 34. We wrote more about that specific failure in our guide to multithreading B2B sales deals.

Why the document version keeps failing

I have watched this fail in enough companies to name the pattern.

It is written for the wrong reader. Most playbooks get written by a founder or a head of sales who already knows the answer. They write down conclusions. A new AE needs the reasoning and the exact words, not the conclusion. "Qualify hard on budget" means nothing. "Ask: what did you spend on this problem last year, and who signed that off?" means something.

It has no expiry date. Your pricing changed in March. Your main competitor shipped a feature in April. The playbook still says what it said in January. Reps figure out within about six weeks that the document is stale, and once they decide that, they stop checking it forever. Trust is hard to get back.

It is too big to enter. Fifty pages has no entry point. A rep with a live objection needs 30 seconds and one answer, and instead has a table of contents.

Nobody measures whether it gets run. This is the one that actually matters. No team tracks playbook adherence, so no team knows which plays work, so the plays never improve. A playbook that never gets edited after launch is a document, whatever you call it.

Start with eight plays, not eighty

The instinct is to document everything. Resist it. Every play you add dilutes the ones that matter, and the tail of rare situations is infinite.

Pick the plays where the money actually moves. For most B2B teams doing five to fifty deals a quarter, that is a short list.

The qualification play. What has to be true for a deal to move out of your first real stage, written as observable facts rather than feelings. Not "prospect is interested." More like: we know the business problem in their words, we know roughly what it costs them, we know who signs, and we have a next meeting booked. If you are running a formal framework, our MEDDPICC walkthrough covers how to make the criteria observable instead of decorative.

The discovery play. The eight questions, in order, with the follow-up probes. Reps improvise the wording, never the sequence. Our discovery call guide has the structure we use.

The multithreading play. Triggered by contact count, as above.

The stall play. What a rep does when a deal goes quiet for two weeks. This is where most teams have nothing written and reps default to "just checking in," which is the worst email in B2B sales.

The top three objection plays. Price, timing, and whichever competitor you lose to most. One page each, with the actual language. If you sell against one dominant rival, this is where battlecards belong.

The handoff play. What gets written down and passed to customer success when a deal closes, and what happens in the first 14 days.

That is eight. Eight plays that get run beat eighty that get read once. Add more only when you can point at a deal you lost because the play did not exist.

Put the playbook where the work happens

This is the part that separates a playbook that changes revenue from one that decorates a wiki.

Reps live in two places: the CRM and their inbox. If a play is not in one of those, it is not in the workflow. So the playbook stops being a file and becomes a set of objects in your CRM.

How this looks in HubSpot

Concrete version, because vague advice is how playbooks die in the first place.

Deal stage exit criteria become properties. In HubSpot, you set required properties per stage so a deal cannot move to Evaluation without a documented business problem, an identified economic buyer, and a next step with a date. Reps grumble for two weeks and then it becomes normal. Your stage definitions have to be built around buyer behaviour first, which we broke down in the sales pipeline stages guide.

Triggers become workflows. Days-in-stage, contact count, email reply gaps, meeting outcomes. Each condition creates a task assigned to the deal owner, and the task description contains the play. Not a link to the play. The play.

Assets become snippets and templates. The stall email is a template, not something a rep writes from scratch at 6pm on a Thursday. The business case one-pager is attached to the task.

Reporting becomes one dashboard with two columns: how many times the trigger fired, and how many times the task got completed inside 48 hours. That second number is your adherence rate, and the first time you look at it you will be unhappy. Everybody is.

For the plays that need external data, this is where automation earns its keep. We run enrichment through Clay and glue the rest together with n8n so a trigger can check a funding round or a hiring signal before the task ever reaches a rep. That work sits in our AI and automation practice, and it is the difference between a play that fires on time and a play that fires on Tuesdays because that is when someone runs a report.

Measure adherence before you measure outcome

Here is the mistake I see teams make right after they build something good: they go straight to "did win rate improve?"

Too early. If only 30 percent of triggered plays get run, you are measuring nothing except your own rollout.

Track two numbers separately.

Adherence. Of the times the trigger fired, how often did the play get run inside the window? Track it per play and per rep. A play at 20 percent adherence across the whole team is a broken play, not a discipline problem. Usually the trigger is too noisy or the action takes too long.

Outcome. Of the deals where the play ran, what happened compared to the deals where it did not? Stage conversion, cycle length, win rate. You need maybe 30 to 40 instances before this means anything, which for most SMB teams is a quarter.

The pairing matters. High adherence with flat outcome means the play is wrong and you should kill it. Low adherence with strong outcome on the few times it ran means you have a good play and a delivery problem. Those need opposite fixes, and a single "did revenue go up" number cannot tell them apart.

One client, a services business with six reps, found their stall play sitting at 71 percent adherence and their competitor objection play at 12 percent. Same team, same month. The objection play required reps to fill in a four-field form before they got the response language. We deleted the form. Adherence went to 64 percent in three weeks. The content had never been the problem.

The maintenance loop nobody builds

A playbook is a living thing or it is dead. There is no third state.

Give every play a named owner and a review date. Once a month, someone spends 45 minutes looking at the adherence dashboard and asking three things: which play has the worst adherence, which play has not fired at all, and what situation came up in a real deal that no play covers.

Feed it from win-loss conversations too. When you lose four deals in a row to the same objection and the response language is two years old, the playbook told you. You just have to be reading it.

Call recordings help here. Tools like Gong will tell you which reps actually asked the discovery questions, which is a much harder number to argue with than a manager's impression from a pipeline review.

What to leave out

A few things that keep ending up in playbooks and should not be there.

Your company history. Your funding story. The org chart. Product feature lists that go stale the moment engineering ships. Aspirational values statements. Anything a rep would only read once.

Those belong in onboarding material, which is a different artifact with a different job. We covered that split in the sales onboarding guide. Mixing them is how a 12-page playbook becomes a 52-page one, and the length is what kills it.

Also leave out any play you are not willing to measure. If you cannot say what "the rep ran this" looks like in data, do not write it down. It will sit there as decoration and quietly teach everyone that the playbook is optional.

A 90-day rollout that works

Weeks 1 to 2: sit in on eight to ten live deals and write down the situations that actually come up. Do not design from theory. Ask the two reps who consistently hit quota what they do differently, and write that down word for word. Most of your best plays already exist inside one person's head.

Weeks 3 to 4: build four plays. Only four. Stage exit criteria plus the four highest-frequency situations. Build them in the CRM with triggers and tasks, not in a doc.

Weeks 5 to 8: run them with two reps, not the whole team. Watch the adherence number weekly. Expect to rewrite at least one play completely, because the first version of a trigger is almost always too noisy.

Weeks 9 to 12: roll out to everyone, add the remaining four plays, and put the monthly review on someone's calendar as a recurring meeting with an owner. If nobody owns the review, you have built a document again, just a more expensive one.

If your CRM is a mess going in, fix that first. Plays that trigger off bad data create bad tasks, reps learn to ignore tasks, and now you have made adoption worse than before you started. Our CRM and RevOps work usually starts there, and it is the least glamorous and highest-return part of any of this. The same logic applies to why reps stop updating the CRM in the first place.

FAQ

What is the difference between a sales playbook and a sales process?

The process is the sequence of stages a deal moves through and what has to be true to advance. The playbook is the set of plays reps run inside those stages. Process tells you where a deal is. The playbook tells a rep what to do about it. You need the process defined first, because plays trigger off stage and deal data.

How long should a sales playbook be?

Length is the wrong measure, because the working version is not a document. Aim for 8 to 12 plays, each one short enough to read in under a minute. If you insist on a written companion doc for onboarding, keep it under 15 pages and treat it as a reference, not the playbook itself.

Do we need a sales enablement platform to do this?

Usually no, if you have fewer than about 20 reps. HubSpot or Salesforce plus workflows, tasks, templates and snippets covers most of it. Dedicated platforms start to pay off when you have content versioning problems across multiple products or regions. We wrote a longer take in the sales enablement platform guide.

Who should own the sales playbook?

One named person, usually the head of sales or whoever owns RevOps. Committees produce playbooks nobody edits. The owner does not have to write every play, but they do have to run the monthly review and be allowed to delete things. Deletion rights matter more than writing rights.

How do we get reps to actually use it?

Deliver the play as a task inside the CRM rather than as a document to consult, make the action take under five minutes, and show the team the adherence numbers openly. Then act on what those numbers say. The fastest way to lose adoption is to publish a play, see 15 percent adherence, and blame the reps instead of fixing the play.

Where to start

If you have a playbook nobody opens, do not rewrite it. Pull the four situations that cost you the most money, turn each into a trigger and a task in your CRM, and watch the adherence number for a month. That single change does more for your win rate than another rewrite ever will.

If you want help building it, get in touch. We do this work as part of our go-to-market engagements, and it usually takes about six weeks to get the first four plays running properly.