Every sales team has a playbook. Most of them are useless.

Not because the content is wrong — usually it’s reasonable. But because a playbook that lives in a shared Notion doc is not a playbook that gets used during a call. It’s a document that managers point to during onboarding and reps forget exists by week three.

The problem isn’t the information. It’s the format and the integration into the actual workflow.

What a playbook is supposed to do

A good sales playbook does one thing: it reduces the cognitive load on the rep during the call.

It does that by answering three questions in advance:

What is the structure of this call?
What am I listening for?
What do I say when things go off-script?

If your playbook answers those three questions in a format the rep can reference during the call, it’ll be used. If it doesn’t, it won’t.

The parts that actually matter

1. Call structure (sections)

Break the call into distinct phases with a clear purpose for each. This is not a script — it’s a sequence.

For an SDR inbound call, that might look like:

Warm opener — acknowledge what brought them in, make it feel natural
Context and intent — why now? What are they actually looking for?
Qualification — BANT or MEDDIC lightly; don’t interrogate
Solution teaser — one or two sentences, not a demo
Objection handling — the two or three they’ll definitely hit
Book the meeting — a specific time, framed around what they’ll get

Six sections. Each with a purpose. That’s a structure a rep can hold in their head and reference on screen.

2. Tone and intent (not a script)

The biggest mistake in playbook design is writing word-for-word scripts. Reps don’t use them because they don’t sound like humans when they read them, and prospects notice immediately.

Instead, write the intent of each section:

What does the rep need to accomplish here?
What does a good answer from the prospect look like?
What are the failure modes? (e.g., talking too long, not listening, skipping ahead)

Let the rep find their own words within the structure.

3. Discovery questions (per section)

Three to five questions per section, written in plain language. These are starting points, not a checklist to read through.

Good discovery questions for a current-situation section:

“How are you handling [problem] today?”
“What’s working well about that approach?”
“Where does it break down?”
“How long has that been the case?”

Bad ones:

“What is your current stack?” (too tactical too fast)
“Have you evaluated other solutions?” (puts them on the defensive)
“What’s your budget?” (too early)

4. Objection handlers (per likely objection)

List the four or five objections that come up most often for this specific call type, and write a short response for each.

The response shouldn’t be a counter-argument. It should be a question that keeps the conversation going.

Objection	Response
”Send me an email."	"Happy to. Before I do — is there a specific aspect you’d want me to focus on, or is this more of a general ‘not now’?"
"We already have something."	"Helpful to know — is it solving the problem well, or are there still gaps?"
"Not the right time."	"Got it — is the timing a budget thing, or is the problem not a priority right now?"
"Talk to my colleague."	"Of course — who would be the right person, and what context should I give them?”

Four responses. Each one keeps the conversation moving rather than ending it.

5. Next step definition

Every call has one good outcome. Define it explicitly in the playbook.

For an SDR call: the outcome is a booked meeting with the right stakeholder, at a specific time, with a clear agenda. Not “I’ll send you some information.” Not “let me know if you want to chat.” A calendar invite before the call ends.

If the rep doesn’t know what they’re trying to achieve, they’ll accept a vague commitment and call it a win.

What to leave out

Product feature lists. That’s the pitch deck’s job.
Long background sections about the company. Reps don’t read them.
Generic “be confident” or “listen actively” advice. It doesn’t change behavior.
More than five discovery questions per section. Too many becomes paralysing.

Building it in a format that works during a call

The biggest shift from traditional playbooks to useful ones is format.

A Google Doc is not a call interface. A Notion page is not a call interface. A 40-slide deck is not a call interface.

A useful call-time playbook is:

Scannable — the rep can find the right section in under three seconds
Expandable — detail is available but hidden until needed
Note-friendly — the rep can capture what the prospect says, tied to the relevant section
Live — it stays open during the call without needing to switch tabs

Some teams build this in their CRM. Others use a dedicated tool. The format matters more than the tool — what matters is whether the rep actually has it in front of them when the conversation is happening.

A simple template to start with

If you’re building a playbook from scratch, here’s a starting structure for an outbound cold call:

Section 1 — Opening angle (30 seconds)

Specific reason for calling. Signal-based. One sentence.

Section 2 — Permission and framing (30 seconds)

Brief framing of the purpose. One or two sentences. Don’t pitch.

Section 3 — Discovery (3–5 minutes)

Three to five open questions about the current situation, pain, and priorities.

Section 4 — Value connection (1–2 minutes)

Connect one pain point to what you do. Use their words.

Section 5 — Objection handling (as needed)

The three objections specific to your situation.

Section 6 — Next step (30 seconds)

Propose a specific time for a follow-up. Name what they’ll get from it.

You can download this structure as a ready-to-import playbook from the Tahaak Playbook Library, or build it from scratch in the Template Builder.

The test

Before publishing your playbook to the team, run this test: put it in front of a rep mid-call and ask if they can find the right section in under five seconds.

If they can’t, simplify the structure. If they can, you have a working playbook. Everything else is refinement.