ExplainedSaaS/ 24 July 2026/ 4 min read
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.
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.
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.
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 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.
A defensible structure:
: ICP and buyer personas. Who are we selling to. What problems do they have. What roles in the buying centre matter.
Snapshot
UK B2B outbound channel mix has shifted materially from 2022 to 2026: LinkedIn first, phone returning, cold email lower-volume but more personalised, direct mail seeing a small revival in enterprise. The relative effectiveness ranks have inverted from the 2022 hierarchy.
Explained
Account-based sales (ABS) was promoted heavily across UK SaaS through 2018-2023 as a structural answer to broad-volume outbound. By 2026 the picture is more nuanced: ABS works at specific deal sizes and team scales, fails predictably outside those, and many UK mid-market teams adopted it for the wrong reasons. A practitioner walkthrough.
Explained
UK enterprise buyers in 2026 increasingly run ESG due diligence on vendors as part of procurement: documented sustainability commitments, modern-slavery statement, supply-chain transparency, and (depending on the buyer) climate-disclosure alignment. The UK Sustainability Disclosure Standards regime has tightened the buyer-side disclosure obligations, which cascades down to vendor expectations.
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.
Five habits:
If you're writing a playbook from scratch:
If you have an existing playbook over 60 pages:
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.