Explained / SaaS / 24 July 2026

Sales playbook design: when to write one, when not to, and the page-count trap

Sales playbooks are routinely written and rarely used. The 90-page document everyone references at orientation and nobody opens after week 4 is the dominant pattern. A practitioner walkthrough of when a playbook is the right artefact, when something else is, and how to keep what you write below the page-count threshold where it stops being read.

Playbooks work when they are short (under 30 pages), maintained (quarterly review against actual deal patterns), and structurally embedded (referenced from CRM stage definitions, deal-walkthrough format, comp plan). Playbooks fail when they are long, written-once, and aspirational.

Sales playbooks are routinely written and rarely used. The 90-page document everyone references at orientation and nobody opens after week 4 is the dominant pattern in UK SaaS at growth-stage and beyond.

This piece is a practitioner walkthrough of when a playbook is the right artefact, when something else is, and how to keep what you write below the page-count threshold where it stops being read.

When a playbook is right

Three conditions:

The team needs to align on a non-obvious motion. A playbook articulates the answer to 'how does this team actually run a deal'. If the answer is obvious from CRM stages and standard methodology, a playbook adds little. If the answer requires explaining product-specific discovery, sector-specific buying patterns, or competitor-specific responses, a playbook is the right artefact.

The team is scaling. New hires arrive every quarter and need to ramp. The playbook is the onboarding artefact. Without it, every manager teaches the motion ad-hoc and inconsistency compounds.

The team is geographically distributed. Distributed teams can't absorb the motion through proximity. The playbook substitutes for the over-the-shoulder coaching co-located teams get.

When a playbook isn't right

Three signals that something else is the right artefact:

The team is small (under 10 sellers). At this scale, the manager IS the playbook. Documenting it formally usually adds bureaucracy without adding alignment.

The motion changes quarterly. A playbook is a static artefact; if the motion is in flux, the playbook is out of date the day it ships. Monthly stand-ups or quarterly off-sites carry the same information at lower bureaucratic cost.

The team is hiring slowly. Onboarding 1-2 hires per quarter doesn't justify a playbook investment; ad-hoc onboarding from the manager works.

In these cases, the right artefact is something smaller: a one-page deal-stage definition, a checklist for first calls, a competitive battlecard. Don't write a playbook because everyone else has one.

The page-count trap

The dominant failure mode: playbooks that are too long.

Reader research on internal-document engagement is consistent: documents over 30 pages get skimmed at orientation and never re-opened. Documents over 60 pages don't even get fully skimmed. The 90-page playbook everyone has is the playbook nobody uses.

The right page-count target: under 30 pages. Under 20 if you can manage it. The discipline to compress is the hard part; the temptation to add is constant.

What a 25-page sales playbook contains

A defensible structure:

Pages 1-3: ICP and buyer personas. Who are we selling to. What problems do they have. What roles in the buying centre matter.

Pages 4-7: The discovery framework (SPIN or MEDDPICC). Specific question banks for our product. What disqualifies a deal.

Pages 8-12: The deal stages. CRM-aligned. Specific exit criteria for each stage. What 'qualified' means at each stage.

Pages 13-17: Demo flow. Standard demo structure. What we never demo (why). Common objections and how to handle them.

Pages 18-21: Competitive landscape. Top 3 competitors. Where each wins. Where we win. How we differentiate.

Pages 22-25: Process: forecasting cadence, deal-walkthrough cadence, escalation paths, support resources.

This is a 25-page playbook. It can be written in 4-6 weeks of focused effort. It can be read in 90 minutes.

How to make sure it gets used

Five habits:

  1. Reference it from the CRM. Stage definitions in the CRM link directly to the playbook section. The playbook is reached through the workflow, not as a separate document.
  2. Cite it in deal walkthroughs. Manager: 'walk us through how you applied the discovery framework here'. The playbook is the reference standard.
  3. Update it quarterly. Mark each section with a 'last reviewed' date. Sections older than 6 months are red flags.
  4. Track engagement. If your tooling allows, watch which sections actually get accessed. Sections with zero access in 3 months are candidates for cutting.
  5. Onboard against it. New hires should have read it by day 3 and demonstrated comprehension by day 14. If onboarding doesn't reference the playbook, the playbook isn't being used.

What to operationalise

If you're writing a playbook from scratch:

  1. Set the 30-page ceiling before you start. Treat it as a binding constraint.
  2. Write the table of contents first. What sections are required. What can be left out.
  3. Draft section by section. Aim for tight prose; cut adjectives.
  4. Get manager sign-off before publishing. Playbooks that managers haven't endorsed get ignored.
  5. Plan the quarterly review. Owner named; calendar invite booked.

If you have an existing playbook over 60 pages:

  1. Don't rewrite. Cut.
  2. Identify sections that haven't been referenced in 6 months. Cut them.
  3. Compress remaining sections to half their current length. Most playbook prose is filler.
  4. Republish with a 'major revision' note. Re-onboard the team to the shorter version.

This is editorial coverage of public sales-playbook practice. For specific advice on what fits your team, talk to your sales operations and front-line managers.

Source: Editorial synthesis from UK SaaS sales operations practice.