What should a sales playbook include?
The short answer
A working sales playbook has six parts: an ideal customer profile with disqualifiers, the messaging and the five objections you hear most, a sales process with an exit criterion for every stage, the sequences and call scripts reps actually run, pricing and packaging, and the operating cadence that keeps it alive. Everything else is an appendix.
The six parts, and what each one is for
A sales playbook is the written answer to four questions: who do we sell to, what do we say, how does a deal move, and how do we know it is working. Every section earns its place by answering one of those. The six below do; most of what gets padded into a playbook does not.
| Section | The question it answers | What "done" looks like |
|---|---|---|
| Ideal customer profile | Who do we sell to, and who do we refuse? | Firmographic filters a researcher could run as a search, plus a disqualifier list |
| Messaging | What do we say? | Positioning, a one-sentence value proposition, proof, and responses to the five most common objections |
| Sales process | How does a deal move? | Five to seven stages, each with an exit criterion and an owner |
| Sequences and scripts | What does a rep actually do today? | Email and LinkedIn steps, call and voicemail scripts, discovery questions |
| Pricing and packaging | What do we charge and how do we present it? | Tiers, what is included, the discount rules, the assemblies a quote is built from |
| Operating cadence | How do we know it is working? | The weekly pipeline review, the scorecard numbers, the monthly and quarterly rhythm |
The ideal customer profile comes first because every other section is downstream of it. Messaging written before the ICP is settled talks to everyone and lands with no one. A process designed before you know who buys has the wrong stages. If you only fix one part of an existing playbook, fix this one.
Messaging is where most playbooks over-invest. You need the positioning statement, the value proposition in one sentence, two or three pieces of proof a rep can cite, and honest responses to the objections that actually come up. You do not need the brand story, the mission, or four pages of competitor analysis. A framework like StoryBrand is useful here for what it forces: the customer is the character, you are the guide, and the message is a plan that gets them from a problem to a result. Use it for discipline, not for length.
The process section is the one reps use on live deals, so it has to be precise. "Discovery" is not a stage; "Discovery complete: pain, budget owner and decision timeline confirmed" is. Each stage needs an exit criterion, a named owner, and the artifact that proves it happened — a call summary, a scoped quote, a signed order. If you use a qualification framework such as MEDDIC (metrics, economic buyer, decision criteria, decision process, identified pain, champion), it lives here as the checklist for the qualification stage, not as a chapter of its own.
Sequences and scripts are the part that turns the document into work. If the playbook says "reach out with a value-led message" and the rep still has to write the email, the playbook stopped one step short. Write the actual steps: day 1 email, day 3 LinkedIn connect, day 5 call with this voicemail, day 8 follow-up with this proof point. Pricing and packaging belongs in the playbook because reps quote what they understand; a pricing page that lives only in finance produces discounts nobody approved. The cadence closes the loop — it is how the playbook gets read every week instead of once.
What to leave out
Most playbooks fail by inclusion, not omission. A useful test for any section is whether a rep could open it in the middle of a live deal and get something they can use in the next ten minutes. Company history, org charts, the CRM field glossary, HR policy and the full product catalog all fail that test. They can exist; they do not belong in the playbook.
The reason to be strict is time. Salesforce's fifth State of Sales report, built on 7,775 responses from sales professionals across 38 countries, found that reps spend just 28% of their week actually selling — the rest goes to deal management, data entry and internal work (Salesforce). A 60-page playbook does not fix that; it competes with the 28%. The document should reduce what a rep has to think about, not add a reading assignment.
Two other things to leave out. First, any process step you are not going to inspect. If nobody will check that the discovery summary was written, do not make it an exit criterion — a playbook with rules that are not enforced teaches reps that none of the rules are. Second, aspirational content. Write the process you can run this quarter with the people you have, and revise it when the team changes.
How long should it be?
Length should track the number of people who need to run the same play without you in the room. The table is a guide, not a rule; a two-person company with a genuinely complex sale can need more, and a 30-person team selling one product can need less.
| Team | Playbook length | What matters most |
|---|---|---|
| Founder plus one | 8–12 pages | ICP, the objections, the sequences. The process is in the founder's head; write down the exit criteria anyway |
| 3–10 sellers | 15–25 pages | Stage definitions, scripts and pricing rules, because this is when deals start being run differently by different people |
| 10–50 sellers | 25–40 pages, often split by role | BDR and closer playbooks diverge; add onboarding paths and the cadence in detail |
Whatever the length, the playbook has to be revised. A version that describes the ICP you sold to two years ago, with the pricing from before the last increase, is actively harmful because reps will follow it. Put a review on the quarterly calendar and treat the document as a living system, not a launch deliverable.
Where SalesARC fits
SalesARC Playbook is built with a strategist from your own calls, documents and pricing, and it covers the six sections above. The difference from a document is what happens next: the ICP you define becomes the filter ArcClaw™ searches against, the messaging becomes the email and LinkedIn steps your reps send from Prospect, the call and voicemail scripts become the tasks that pop up in front of them, and the product tables and pricing become the line items in your quotes. Section Studio lets you rebuild any section from your own files and regenerate the sequences underneath it. Basic is $999 one-time for one ICP with the BDR and full sales playbooks; Standard ($2,499) covers up to three ICPs and all six playbook types. If what you need is a document to read, any competent consultant can write one. Playbook exists for the case where the document has to run something.
See SalesARC Playbook or build a plan.