What is a sales playbook? (and what actually goes in one)

What is a sales playbook?

Short answer: a sales playbook is the operational handbook a new salesperson uses to do the job — and the document a senior salesperson refers to when a deal goes sideways. Not a strategy deck. Not a marketing artefact. A working manual. If a new hire cannot pick it up on day 1 and know what to do by day 5, it is not a playbook. It is documentation.

Most B2B companies say they have a playbook. Most of those playbooks are slide decks last updated 14 months ago, full of taglines, missing the parts the reps actually need. This post is about the version that works.

TL;DR — what a playbook contains

This is the modal table of contents. Some teams cut one or two; the strong ones keep all ten.

Why most sales playbooks fail

Three failure modes:

Failure 1: Written for marketing, not for reps. The playbook is a brand document — full of mission statements, taglines, customer logos. None of it tells a rep what to do on a Tuesday morning. Reps ignore it.

Failure 2: Written once, never updated. A founder spends a weekend in 2023 writing a playbook. Nobody updates it. By 2025 it references defunct tooling and an old ICP. The playbook becomes a historical artefact.

Failure 3: Lives in the wrong place. The playbook is a 60-page Google Doc that takes 8 minutes to load. Reps cannot find anything in it during a call. The playbook is consulted before a hire arrives and never again.

The fix for all three is structural — write the playbook for reps using it during actual sales activity, version it explicitly, and host it somewhere navigable in under 30 seconds.

Section 1 — ICP & positioning

Every rep should be able to answer, in under 30 seconds:

• Who do we sell to? (ICP — firmographic, technographic, behavioural)
• Why us? (positioning vs. competitors)
• Why now? (trigger events that make this quarter relevant for the buyer)

This section is short — typically 2–4 pages. It does not need to be long. It needs to be exact.

A strong version:

ICP: B2B service firms (consultancies, agencies, IT services, system integrators) headquartered in the UK or UAE, 30–250 employees, £3–25M ARR, currently using HubSpot or Pipedrive, founded 4–15 years ago, that have hired or are hiring a Head of Growth or Sales Director in the last 6 months.

>

Why us: We install the sales OS, not just train the team. The system stays after we leave.

>

Why now: The recent hire of a sales leader is a forcing function. They have 90 days to show progress. Our 90-day installation timeline aligns with that.

Compare to a generic playbook:

Our customers are mid-sized B2B businesses looking to grow.

The first version is operational. The second is decorative.

Section 2 — Process

The named stages, the exit criteria for each stage, the qualification framework.

A typical structure:

Each stage has a single sentence definition + 2–4 exit criteria. Reps cannot move a deal forward without satisfying all exit criteria. This is the heart of pipeline hygiene.

This section is also where the qualification framework lives — MEDDPICC, SPICED, BANT, whichever you have chosen. Document the framework's fields, the questions that surface them, and the CRM fields they map to.

Section 3 — Discovery

The discovery section is where most playbooks under-invest. Reps run discoveries badly, and the playbook should fix that.

What belongs here:

Call structure — the standard discovery agenda (intro, pain exploration, impact quantification, next-step setting). 30 or 45 minutes, broken into named segments.

Question bank — at least 20–30 discovery questions, organised by category:

• Situational questions (where is the buyer now?)
• Pain questions (what is broken?)
• Impact questions (what does the broken thing cost?)
• Vision questions (what would success look like?)
• Decision questions (who decides? how? when?)

Each question should have notes on when to use it and what answer to listen for.

Recording and review process — reps record discoveries (Gong, Chorus, Fathom). The playbook specifies which discoveries are reviewed and on what cadence.

A working discovery section is 8–15 pages on its own. Most playbooks dedicate 1–2 pages. This is the single biggest under-investment in most B2B playbooks.

Section 4 — Demo / pitch

For service businesses, "demo" means "the pitch meeting" — typically a 45–60 minute presentation tailored to discovery.

What belongs here:

• The standard pitch flow (problem → approach → outcomes → proof → ask).
• The customisable elements (which slides change per buyer, which stay constant).
• The standard decks (general pitch, vertical-specific pitch, technical deep-dive).
• Customer stories — 5–8 short case studies, organised by industry and pain.
• The post-pitch close — how to end the meeting with a clear next step.

For tech B2B with product demos, the same structure plus: which features to show, in what order, with what talk track. Demo scripting is critical at scale because rep variance in demos is one of the highest sources of variance in close rates.

Section 5 — Objections

The single most under-built section in most playbooks, despite being where reps spend the most time live.

The structure that works:

1. List the top 20 objections you hear in real deals.
2. For each, write a 2–3 sentence response that has been tested live.
3. Categorise them: pricing, timing, fit, competition, no-budget, no-authority, no-pain, no-trust.

Example:

Objection: "We are already using {Competitor}."

>

Response: "That makes sense — most of our customers were using one of three tools before us. The question is whether what they have is actually getting the outcomes they wanted. Mind if I ask what specifically pushed you to look beyond {Competitor}? Even if you decide to stay, I'd love to understand what triggered the search."

Objections are easier to write after a rep has lived them. The playbook should be a working document — every time a rep encounters a new objection, it gets added with a tested response.

Section 6 — Sequences

The cold + warm + follow-up + breakup templates.

A modal sequence library:

Each sequence has the actual templates — subject lines, body copy, send schedule, variations.

Generic sequences (the ones the sequencer tool ships with) do not count. Real sequences are written for your ICP, your value prop, and your voice.

Section 7 — Pricing & commercials

What belongs here:

• The price list (or pricing logic if custom).
• Discounting rules (who can approve what discount, with what justification).
• Standard contract terms (term length, payment schedule, exit clauses).
• The MSA template + the negotiation playbook for common redlines.
• Approval thresholds (which deals need senior sign-off; how to route them).

This section sounds boring. It is also the section that prevents reps from accidentally giving away 20% of margin in negotiations. Write it explicitly.

Section 8 — Operating rhythm

The recurring meetings, who attends, what they cover, and how long they take.

Reps need to know what meetings they are in, what is expected from them, and what gets reviewed when. The playbook documents the meeting cadence so onboarding is predictable.

Section 9 — Tooling

How to use each tool in the stack, with screenshots and short walkthroughs.

This is mostly maintenance-heavy operational content:

• CRM — how to create accounts, opportunities, contacts. How to use the qualification framework fields. Required fields per stage.
• Sequencer — how to enrol prospects in sequences, how to read open/reply data, how to handle replies.
• Dialer — how to log calls, how to take notes that other reps can use.
• Calendar — how to send meeting invites, how to use scheduler links.
• Documentation tool — where to file customer notes, where to find the playbook itself.

This section is often 20+ pages because of screenshots. That is fine — reps consult it once, internalise it, and stop needing it. The playbook is the safety net.

Section 10 — Onboarding plan

The 90-day plan for a new hire.

A new rep follows this plan, with explicit checkpoints. The plan also doubles as the manager's coaching guide.

How to actually maintain the playbook

The single biggest failure of playbooks is staleness. Three rituals to keep it alive:

Monthly playbook updates. One hour a month, the sales leader or enablement person walks through the playbook and updates 1–3 sections. Even small updates signal that the document is alive.

Embed updates in pipeline reviews. When a rep encounters a new objection or wins a deal in a novel way, the pipeline review captures it and adds it to the playbook.

Annual full refresh. Once a year (typically early Q1), block half a day for a full review. Rewrite outdated sections, add new ones, archive obsolete sequences.

Version the document. A simple v1.0 → v1.1 → v2.0 versioning at the top of the playbook tells everyone how recent it is.

Where the playbook lives

The tool matters less than the discipline. Common homes:

For most B2B service firms at £500K–£5M ARR, Notion is the right answer. Strong navigation, easy to update, cheap.

For UAE & KSA teams

Regional adjustments to the playbook structure.

Bilingual content where needed. Discovery question banks and objection responses in both English and Arabic. Front-line reps facing Saudi family-business buyers benefit from having objection responses they can recite verbatim in Arabic. Senior playbook sections can stay English-only.

Regional case studies in the demo section. Western customer logos do not carry weight in the GCC. Build the case study library with at least 2–3 regional references (UAE/KSA companies the buyer recognises) before launching outbound. This single change frequently doubles late-stage conversion.

Procurement playbook addendum. A separate section covering KSA government procurement (vendor registration steps, tender response template, technical evaluation typical questions) and UAE government procurement (ADGM, DIFC variants where applicable). Most foreign-built playbooks omit this; it is essential for serious GCC selling.

Relationship strength as a CRM field. Add it to the process section explicitly. Cold / introduced / met / dined / multi-meeting. Coverage and forecast eligibility flow from it.

Calendar nuance. The operating rhythm section should specify Sunday–Thursday vs. Monday–Friday work weeks for the relevant team(s). Forecast call timing aligned to local week boundaries.

Cultural-fluency notes for non-local reps. A short section in the onboarding plan covering Ramadan etiquette, prayer time awareness, dress code expectations for in-person meetings, dietary norms for client lunches. Small section; high impact on whether a foreign rep avoids early credibility damage.

What MAVEN does about it

Playbook installation is part of the Sales Process Program — by week 8 of the engagement, the team has a living playbook covering all 10 sections, hosted in Notion (or the client's preferred tool), with the maintenance rituals defined.

The Sales OS Blueprint covers the broader architectural place of the playbook in the sales operating system.

If your current playbook is more decorative than operational, book a virtual coffee. 30 minutes, no slides — we look at what you have and tell you which two sections to rewrite first.

Frequently asked

How long is a working sales playbook?

40–80 pages for a B2B service firm at our typical client size. Less than 40 and it is probably missing sections. More than 100 and reps stop reading it.

Should marketing or sales own the playbook?

Sales. Marketing contributes the positioning section and the case studies. The rest belongs to the people running deals.

Can AI write the playbook?

AI can draft sections (objection responses, sequence variants, discovery question banks) usefully. AI cannot write your ICP, your pricing rules, or your operating rhythm — those require your own data and decisions.

What is the most important section?

Discovery, usually. Most teams under-invest in it. A good discovery section lifts close rates more than any other single section.

How often should we update the playbook?

Small updates monthly. A full refresh annually. If you go 6 months without any update, you have stopped using it.

Should the playbook include comp plans?

Reference, not detail. Comp plans usually live in their own document because of confidentiality and HR handling. The playbook can link to "see comp plan" without including the specifics.

---

Post 17 of our outbound + sales OS series.

Related reading

• When should a startup hire its first sales rep?
• What is a fractional VP of sales?
• What is a sales playbook?
• How to write a sales commission plan
• How to run sales 1:1s
• How to coach a B2B sales team