A discovery call just ended. The buyer liked what they saw and mentioned two people they’ll want to bring in: their CFO and someone from IT. What your rep does in the next hour (the recap, the CRM update, whether those two get researched and an intro gets asked for) is your sales playbook. It just isn’t written down yet.

A sales playbook is that know-how, written for the whole team: who you sell to, the path a deal takes to close, and how your best reps handle the moments that come up on almost every deal. Written well, it answers the question every rep asks a dozen times a day: what should happen next on this deal?

Most playbooks are written like a manual: personas, talk tracks, a list of stages. The useful ones are written as judgment, one moment at a time. Judgment still fits after a deal changes. A manual doesn’t.

What goes in a sales playbook?

Most playbooks cover the same ground. What makes one useful is that each part settles a decision a rep faces on a live deal.

  • Who you sell to. Your ideal customer and the people who decide inside it. This settles which deals deserve the time, and who needs to hear from you before a deal can close.
  • The path a deal takes. The stages from first call to signature, and what proves a deal has really reached each one. Our MEDDPICC guide shows one way to map this with dates, and our post on the B2B sales process covers the stages.
  • The moments. What your best reps do when a call ends, a buyer goes quiet, someone new joins, a buyer pauses, or a competitor comes up. Most playbooks skip this part, and it’s the part reps need most.
  • Messaging and talk tracks. How you describe the problem and what you do about it, in the words that work with your buyers.
  • Discovery questions. What a rep needs to learn on the first calls, and how to ask. If you qualify with a framework like BANT or MEDDPICC, it lives here.
  • Objections and competitors. The pushback you hear most, the competitors that come up, and how your best reps answer each.
  • Rules that always hold. The few things that never change: who approves what before it reaches a buyer, what never goes in writing, when a deal gets marked lost.
  • Tools and the CRM. Where the work happens, and what gets written back to the CRM after each step.

A sales process is the path. A sales play is how you handle one situation, like re-engaging a deal that stalled. The playbook holds both, plus what a rep needs to run them.

How is a sales playbook different from a script or a workflow?

All three try to get reps doing the right thing. They break in different places.

A script says what to say. It gets a new rep through a first call. But buyers don’t follow scripts, so it runs out at the first unexpected answer.

A workflow says when something happens, do this: when a meeting ends, send the recap template; when a deal sits for 14 days, send the check-in. That’s fine for things that should always happen. The trouble is what happens in between. If the buyer replies before the follow-up goes out, a stakeholder changes, or the timeline slips, the next instruction is already wrong, because nothing re-reads the situation.

A playbook says what your best rep weighs at that moment, what they’d usually do, and when they’d do something different. It can still hold rules: if your process says reps send a mutual action plan after discovery, that goes in the playbook too.

Harvard Business Review made the case for judgment over process back in 2013. In Harvard Business Review’s “Dismantling the Sales Machine”, the authors argued that sales leaders had built formal processes “designed to help their team members replicate the approaches of star performers,” and that this fixation on process discipline had broken down now that buyers engage suppliers much later in their own buying process. They wanted managers coaching and reps using more judgment, and they didn’t say process was always bad. We agree. It’s a case against scripts and stage checklists, and for writing the judgment down.

How do you write a sales playbook?

Start small. A first version that covers five moments well is worth more than forty pages nobody opens.

  1. Start from deals you won. Pick your last few closed-won deals and ask the rep who closed each one what they did at each turn, and why. Push for what they did on instinct. Nobody has written that part down. You’re done when you have their answers in their own words.
  2. Name the moments. List the moments that come up on most of your deals. For most B2B teams, that’s after a discovery call, a buyer going quiet, someone new joining, a buyer pausing, and a competitor coming up.
  3. Write each moment as judgment. Under each moment, write three lines: what matters, the usual move, and when to do something else. The examples below show the format.
  4. Add the rules that always hold. Keep the list short. If a rule has exceptions, it’s a moment, not a rule.
  5. Keep one copy. One playbook for the whole team, changed in one place after won and lost deals.

What does a sales playbook look like? Four examples and a template

Here are four entries in that format. The quoted lines come from one of our own playbooks in Arrows.

After a discovery call

  • What matters: the buyer leaves knowing what happens next and when, and anyone they named gets found before the trail goes cold.
  • The usual move: a recap the rep sends that day, “with the next milestone and a date for it.” The CRM updated with what you learned. Research on everyone the buyer mentioned, and an ask for an intro. Our follow-up email builder gets the recap started.
  • When to do something else: if the buyer named a date to reconnect, time the next note to arrive just before it, not on a fixed day count.

A buyer goes quiet

  • What matters: why they went quiet. A deal waiting on someone else’s sign-off needs a different note than one that lost priority.
  • The usual move: a short nudge with something useful in it, like an answer to a question they raised or a proof point that fits their situation.
  • When to do something else: if the deal has a second contact, try them instead of sending a third note to the first. If two nudges go unanswered, make the ask smaller: one line, one question.

Someone new shows up on the thread

  • What matters: who they are, what they care about, and whether they decide. In one of our playbooks, the deal overview (the summary Arrows keeps on each deal) tracks “where it is on the path to close, what happens next, who decides and what goes on the quote.”
  • The usual move: research them before the next call, and give your contact an easy way to bring them in.
  • When to do something else: if the new person is senior to your contact, don’t go around your contact. Ask what the new person needs to see.

The buyer pauses the deal

  • What matters: the reason, and what would change it. “We’re pausing” usually comes with a condition.
  • The usual move: a reply that confirms the condition, and a CRM change to match: a later close date, lower confidence, a new next step.
  • When to do something else: if the condition is public, like a new hire or a funding round, watch for it and reach out when it happens, not on a calendar reminder. If nothing moves for a few weeks, ask whether to revisit later or close it out.

A template to copy. For each moment on your list, write four lines:

  • Moment: what just happened on the deal.
  • What matters: what your best rep is thinking about right now.
  • The usual move: what they’d do on most deals.
  • When to do something else: the signs that call for a different move, and what that move is.

What does a sales playbook do on a real deal?

Here’s a deal from our own pipeline, names taken out.

One discovery call on September 17, and nothing booked after it. The buyer named two people they’d bring in, so the after-call entry did its job: the recap and CRM update were drafted the same day, both people were researched, and an intro ask was drafted. The buyer had named early October to reconnect, so the next note, with a proof point that fit, was timed to arrive just before it.

On September 28, the buyer wrote that they were pausing until they hired a sales leader. That’s the pause entry: a reply confirming it, and a CRM change for the rep to approve, with a later close date, lower confidence, and a new next step. The condition was public, so Arrows checked for news of the hire, then drafted a re-engagement note with a short walkthrough to forward to whoever they hired. If that goes unanswered, the plan is to shrink the ask to a one-line question or try the other contact, and after that, to propose either a date to revisit or closing it out.

Arrows did that work, with nobody prompting it. It reads your team’s playbook every time something happens on a deal and keeps a gameplan for each one: a path to close built from the playbook and from what’s actually happening on that deal. Every piece is drafted for a rep to approve before it goes out. Dominique Rennell, Chief Customer Officer at Projectworks, put it this way: “It’s just a no brainer if you want to ensure that your sales process is consistent across your sales team.”

We build the playbook with your team in one kickoff call, and Arrows starts on your open deals that same day.