16 Nov 2026
A sales playbook is your company's written guide to how the team handles each kind of sales conversation: who you sell to, what each call needs to achieve, which questions and objections come up, and what has to be true before a deal moves to the next stage.
You can build a solid first version in six steps: scope it, gather evidence from real calls, define stages by what buyers do, write plays with criteria you can observe, prepare those plays for live calls, and set rules for keeping them current.
The order matters. Writing everything at once is the quickest route to a long document nobody opens. Working step by step gives you something usable at each stage, and each step below ends with a deliverable you can share with your team. At the end you'll find a worked example and a template you can copy.
Step | What you do | Deliverable |
|---|---|---|
1. Scope | Choose one segment, a few call types and an owner | One-page scope statement |
2. Gather evidence | Review calls, deals and team input | Evidence log |
3. Define stages | Write exit criteria based on buyer actions | Exit-criteria table |
4. Write plays | Turn each call type into a play with observable criteria | Play cards |
5. Prepare for live use | Cut each play down to what a rep needs mid-call | In-call cards |
6. Govern | Pilot, review on evidence, retire what no longer works | Governance page and change log |
Before you start, it helps to agree on what "playbook" means, because teams use the word for at least four different things.
What it answers | Example | |
|---|---|---|
Sales methodology | What a well-qualified deal or a good discovery conversation looks like in general | MEDDIC, MEDDPICC, BANT, SPIN, the SPICED framework |
Sales script | The exact words to use at a specific moment | A cold-call opener or a voicemail |
Sales playbook | How your team applies its methodology to your buyers, call types and stages | "On a first discovery call with a mid-market finance leader, these four things must happen before we book a demo" |
Spiky's Sales Playbook feature | Whether a meeting covered the key topics of a supported framework (BANT, SPIN, MEDDIC or MEDDPICC) | A meeting with each MEDDIC topic marked as covered or missed |
A methodology is general and portable. Two companies can both run MEDDPICC and still need very different playbooks, because their buyers, deal sizes and objections differ.
A script lives inside a playbook. Scripts suit short, predictable moments like an opener or a voicemail. In open-ended conversations they get in the way, which is why the plays in this guide use short talk-track starters.
Software features add a fourth meaning. In Spiky, "Sales Playbook" is the name of a feature that checks meetings against a sales framework. It can help you verify part of your playbook, as the product section near the end explains. The playbook itself remains a document your team writes and owns.
The first version of a sales playbook should cover one segment and three to five call types. A playbook that tries to cover every product, region and deal size in its first version usually becomes too long to use and too slow to finish.
Pick the segment where a better playbook would make the biggest difference. Three questions help:
Where does most of your pipeline come from?
Where do results vary most between reps selling the same thing?
Where are new hires ramping, so a clear standard saves the most manager time?
If the answers point to different segments, start with the one you can gather evidence for fastest. A motion with plenty of recorded calls is easier to build from than one that runs mostly offline. If your scope is an outbound motion, keep it consistent with your existing outbound sales strategies rather than writing a parallel version.
List the conversations a rep in that segment actually has, then keep the three to five that account for most of the work. Typical candidates are a first discovery call, a product demo, a pricing or proposal conversation, a competitive evaluation and a late-stage procurement call. Leave the rest for version two.
One person owns the playbook. That is usually a sales enablement lead or a front-line sales manager. List who must approve changes: typically a sales leader, RevOps for stage definitions and product marketing for competitive claims. A playbook with several equal owners tends to have none.
Deliverable: a one-page scope statement that names the segment, the call types in and out of scope, the intended reader (new hires, experienced reps or both), the owner, the approvers and the date you plan to pilot.
With the scope agreed, the next job is finding out what actually happens in those calls today.
A playbook is only as good as the evidence behind it. Before writing any plays, collect what your team already knows from calls, deals and colleagues, and note where each piece of evidence is weak.
Source | What it tells you | Watch out for |
|---|---|---|
Recorded calls, won and lost | How buyers describe their problems, the objections they raise in their own words, where conversations change direction | Calls that were never recorded are missing from the picture |
CRM stage history | Where deals stall and how long each stage takes | It reflects what reps entered, which can lag what actually happened |
Closed-lost reasons | The reasons reps recorded for losses | Dropdown values like "price" or "timing" often hide the real reason |
Reps at different performance levels | What people do that the current process does not describe | Personal habits can be mistaken for rules |
Sales engineers and customer success | What buyers ask after a demo or after signing | Questions asked after the sale often show what discovery missed |
Product marketing and competitive notes | Positioning and known competitor claims | Vendor-written material should be checked against what buyers actually say |
For each call type in scope, pull a mixed sample of recent calls: some won, some lost, some from strong reps and some from newer ones. Listen for three things and write them down verbatim:
The questions buyers asked.
The objections buyers raised, in their exact words.
The moment the conversation moved forward or stalled, and what happened just before it.
Verbatim matters. Buyers rarely phrase an objection the way a slide deck does, and reps recognize an objection faster when the playbook uses the buyer's language. Conversation analytics can make this review faster when you have more calls than anyone can listen to.
Tag each observation as seen repeatedly, seen once or hypothesis. A hypothesis can still go into the playbook, but label it as something to test during the pilot. This keeps strong opinions from turning into rules without anyone checking them.
Deliverable: an evidence log with one row per observation: call type, what you saw, a verbatim quote where you have one, the source, how often it appeared and your confidence level.
The evidence log now tells you where deals move and where they stall. Step 3 turns that into stage definitions.
A stage exit criterion should describe something the buyer has said, done or agreed to, and it should be checkable from a call recording, an email or a calendar invite. Criteria based on rep activity, such as "demo delivered" or "proposal sent", record effort. They tell you little about whether the deal actually moved.
Stage | Weak exit criterion (rep activity) | Strong exit criterion (buyer evidence) |
|---|---|---|
Discovery | Discovery call held | The buyer described the problem and its business impact, and agreed to a next meeting with the people who own it |
Evaluation | Demo delivered | The buyer named the criteria they will use to decide and the people who will evaluate |
Proposal | Proposal sent | The person who approves the budget has seen pricing and agreed to a decision date |
Procurement | Contract sent | The legal, security and purchasing steps are known, each with an owner and a date |
If your team uses a methodology, this is where it plugs in. MEDDIC's decision criteria and decision process, or SPICED's critical event, become exit criteria at the stage where you expect to have confirmed them. Mapping them this way also shows where your current stages ask for something nobody ever checks.
Keep exit criteria to one or two per stage. They are gates for the deal: a manager or RevOps checks them before a deal moves forward, so a long list quickly turns into paperwork.
The detail belongs inside the plays you'll write in Step 4. Each play has its own three to five must-cover moments, which describe what should happen in a single conversation. Several must-cover moments usually add up to one exit criterion. In the worked example later in this article, four moments on a discovery call together satisfy a single discovery exit criterion.
Deliverable: an exit-criteria table listing each stage in scope, its exit criterion and the evidence a manager would look for to confirm it. Share it with RevOps before writing plays, since stage definitions usually live in the CRM too.
This is where the playbook becomes something reps can use. A play covers one situation: the outcome you want from the buyer by the end of the conversation, and the few things that must happen in the conversation to get there. Most playbooks need one play per call type, plus a few for recurring situations such as a competitor coming up.
Every play answers the same questions. When does it apply (the trigger)? What should the buyer have agreed to by the end (the buyer outcome)? Which three to five things must happen on the call (the must-cover moments)? Add a few talk-track starters, the objections reps are likely to hear in the buyer's own words, any disqualifiers, the next step that ends the play well, and an owner and version number. The template later in this article lays these out as fields you can fill in.
Of these, the must-cover moments take the most care, because they decide whether a play can be checked at all.
An observable criterion describes something you could point to in a recording or transcript. A useful test: would two managers, listening to the same call separately, agree that it happened?
Five rules make criteria observable:
Describe something that was said or agreed. "Built rapport" is a judgment. "Confirmed the buyer's goal for the call in the first few minutes" can be checked.
Prefer buyer evidence to rep activity. A rep can ask about impact without getting an answer. "The buyer described the impact in their own words" shows the question worked.
One behavior per criterion. "Covered budget, timeline and decision-makers" hides which part was missed.
Define what counts. If a criterion asks the buyer to describe a consequence, say whether a vague "it's annoying" is enough or whether you need a specific effect on time, money or risk.
State the condition when it only sometimes applies. "When the buyer raises price, the rep asked what they are comparing it to before responding" avoids counting every call without a price objection as a miss.
Vague criterion | Observable rewrite |
|---|---|
Do good discovery | The buyer described their current process and at least one consequence of it in their own words |
Qualify budget | The buyer said how purchases of this size are approved and by whom |
Handle objections well | When the buyer raised an objection, the rep asked a clarifying question before answering |
Create urgency | The buyer named an event or date that makes solving the problem matter now |
Close for next steps | Before the call ended, both sides agreed on a next meeting with a date, attendees and purpose |
Some things that matter resist this treatment, such as tone or how well a rep listens. Keep them off the must-cover list and handle them in coaching conversations, where a manager's judgment belongs.
Every must-cover moment competes for the rep's attention during the call. When everything is required, reps can't tell what actually matters. Put extra detail in the reference version of the play and keep the must-cover list short.
Deliverable: one play card per call type in scope, each with observable must-cover moments.
A play card that reads well at a desk can still be hard to use halfway through a call. That's the problem Step 5 solves.
Most playbooks are written to be read before a call. The moments that decide a deal happen during it, when a rep has a few seconds to remember the next question or the best answer to an objection. A play that works in a live conversation needs a second, much shorter version.
The reference version holds everything: the reasoning, the background, examples and links to supporting material. Reps read it while preparing and managers use it in coaching.
The in-call version fits on one screen. It holds only the must-cover moments, one-line responses to the likely objections and the next-step ask.
Keep each prompt to about ten words. A question works better than an instruction: "What happens if this waits until next quarter?" is easier to use mid-call than "Establish urgency."
Order prompts in the sequence the conversation usually follows, so the rep's eye moves down the card as the call progresses.
Start each objection line with the buyer's likely words, so the rep recognizes it the moment they hear it.
Leave out product detail and background. Link to it from the reference version instead.
Test the in-call card by giving it to a rep who did not help write it and asking them to use it on a practice call. If they need to stop and read, it is still too long.
Teams that want this guidance to appear automatically during conversations can look at real-time AI sales coaching, which surfaces prompts while the call is still happening. The card is still worth writing first: it defines what that guidance should say.
Deliverable: an in-call card for each play, one screen long, reviewed by at least one rep who did not write it.
At this point you have a complete first version. The last step keeps it accurate once real conversations start testing it.
A sales playbook starts going out of date the day it ships. Buyers raise new objections, competitors change their pitch and pricing moves. This step decides how the playbook gets tested, how it changes and how plays are removed.
Roll out version one to a single team for a few weeks before the rest of the sales org sees it. During the pilot, collect two kinds of feedback:
Where reps skipped a play, and why. If a play doesn't fit the conversation, the content needs fixing. More training won't help.
Where managers disagreed about whether a criterion was met. Disagreement usually means the criterion is still too vague. Rewrite it using the rules from Step 4.
In coaching sessions, pick one play and one must-cover moment, then look at a real call where it happened or where it was missed. Working on a single criterion gives the rep something specific to practice on the next call, and it keeps coaching tied to the playbook instead of a manager's general impressions.
A quarterly review is a reasonable default. These events should trigger a review sooner:
A new objection or competitor starts appearing across several reps' calls.
Pricing, packaging or the product changes.
Deals keep stalling at a stage whose exit criterion looked solid.
Most reps, including strong ones, keep missing the same must-cover moment.
The last trigger deserves a closer look. When nearly everyone misses the same criterion, check the criterion before you coach the team. It may describe something buyers in this segment don't need.
Remove or merge a play when its situation rarely comes up, when its must-cover moments are met on nearly every call and no longer separate strong conversations from weak ones, or when won deals regularly happen without it. Treat that last pattern as a prompt to investigate. A pattern in a small number of deals can be misleading.
Record every change in a change log with the date, what changed, why and the evidence behind it. Without one, the next owner inherits a set of rules with no explanation.
Deliverable: a governance page listing the owner, approvers, review triggers and default review date, followed by the change log.
To see how the six deliverables fit together, here is one play built end to end. Tallyhouse is a fictional company that sells accounts payable automation software to mid-sized businesses. Every observation below is invented for illustration.
Scope (Step 1): companies with 200 to 1,000 employees and an in-house finance team, arriving through inbound demo requests. Version one covers four call types: first discovery, product demo, pricing and proposal, and competitive evaluation. Owner: sales enablement lead.
Evidence (Step 2): in this fictional call review, buyers who booked a demo had usually walked through their invoice approval process on the first call. Buyers who went quiet had rarely mentioned a controller or CFO. "Our ERP already has an AP module" came up often enough to need a prepared response, which the team marked as a hypothesis to test.
Exit criterion (Step 3): discovery is complete when the buyer has described the approval process and its impact, and a demo is booked with the person who owns the AP process. The four must-cover moments in the play card below are how a rep gets there in a single call.
Field | First discovery call: inbound demo request |
|---|---|
Trigger | A finance leader at a company in the target segment requests a demo |
Buyer outcome | The buyer agrees the problem is worth solving this quarter and books a demo with the people who own the AP process |
Must-cover 1 | The buyer described how an invoice gets approved today, from arrival to payment |
Must-cover 2 | The buyer named at least one specific consequence of the current process, such as late payments, slow month-end close or time spent chasing approvals |
Must-cover 3 | The buyer said what prompted them to look now |
Must-cover 4 | The buyer named who else will be involved in choosing a tool and how a purchase of this size gets approved |
Talk-track starters | "Walk me through what happens to an invoice from the moment it arrives." "What made this a priority now?" "If this works, who else needs to be convinced?" |
Objection: "We're just exploring." | Ask what would need to be true for this to become a project this year; if the answer is "nothing yet", agree on a smaller next step |
Objection: "Can you just send pricing?" | Explain which factors pricing depends on and offer to walk through it on the demo with whoever approves the budget |
Objection: "Our ERP already has an AP module." | Ask what they have tried in it and where it falls short before describing any difference (hypothesis, test in pilot) |
Disqualifiers | No in-house finance team; invoice volume below the level where automation pays off (set your own threshold) |
Exit and next step | A demo is booked with a date, the AP process owner attending and an agreed goal |
Owner, version | Sales enablement lead, version 1.0, reviewed at the end of the pilot |
Walk me through an invoice, arrival to payment?
What does that cost you: time, late fees, close delays?
Why now?
Who else decides? How are purchases like this approved?
"Just exploring": what would make it a project this year?
"Send pricing": depends on volume and entities; cover it on the demo with the budget owner.
"ERP has AP": what have you tried, and where does it fall short?
Close: demo date, AP owner attending, goal agreed.
The pilot runs with one inbound team. A new objection heard across several reps, a pricing change, or must-cover 4 being missed by most of the team all trigger a review.
"We already use a competitor." The play triggers when the buyer names an incumbent tool. A good outcome is a clear answer either way: the buyer names a gap the current tool leaves, or the rep learns a switch isn't worth pursuing now. Must-cover moments: the rep asked what works well with the current tool before comparing anything; the buyer described a gap in their own words; the rep connected one specific difference to that gap; both sides agreed whether to continue. The play avoids criticizing the competitor, since the buyer chose that tool and may still defend it.
Late-stage security and procurement review. The play triggers when the buyer says the deal is "with procurement" or "with legal". The outcome is a shared plan for the remaining steps. Must-cover moments: the buyer named who signs and who reviews security and legal terms; each step has an owner on both sides; dates are agreed for each step; the rep confirmed which documents the buyer needs and by when. In the fictional Tallyhouse review, late-stage deals that slipped usually had no owner for the next step, so every moment in this play is about ownership and dates.
The template below follows the six steps in order, so you can fill it in as you work through them. It's written in Markdown, which pastes cleanly into most docs and wiki tools; anything in square brackets is a placeholder to replace.
Copy the whole block into your team's docs tool.
Fill in sections 1 to 3 first. The play cards should come from your evidence log and exit criteria, so write those before any plays.
Duplicate sections 5 and 6 once for each play, and give each copy the play's name. A first version usually has three to five.
Keep each in-call card short enough to read on one screen without scrolling.
Add a dated entry to the change log every time something changes, starting with version 1.0.
# \(Company\) Sales Playbook: \(Segment\)
## 1. Scope
Segment:Call types in scope:Out of scope (for now):Intended reader: new hires / experienced reps / bothOwner:Approvers:Pilot team and start date:## 2. Evidence log
| Call type | What we saw | Verbatim quote | Source | How often | Confidence (seen repeatedly / seen once / hypothesis) |
| --- | --- | --- | --- | --- | --- |
| \(\) | \(\) | \(\) | \(\) | \(\) | \(\) |
## 3. Stages and exit criteria
| Stage | Exit criterion (what the buyer has said, done or agreed) | Evidence a manager would check |
| --- | --- | --- |
| \(\) | \(\) | \(\) |
## 4. Ideal customer and disqualifiers
Who we sell to:Who signs:Who we walk away from, and why:## 5. Play card: \(Play name\)
Trigger:Buyer outcome:Must-cover moments (3 to 5, observable):\(\)\(\)\(\)Talk-track starters:Likely objections (in the buyer's words) and response approach:"\(objection\)": \(response approach\)"\(objection\)": \(response approach\)Disqualifiers:Exit and next step:Supporting material (links):Owner / version / last reviewed:## 6. In-call card: \(Play name\)
Prompt 1:Prompt 2:Prompt 3:"\(objection\)": \(one-line response\)Next-step ask:## 7. Competitor notes
| Competitor | When buyers mention them | What buyers like about them | Gap we can address | Proof we can share |
| --- | --- | --- | --- | --- |
| \(\) | \(\) | \(\) | \(\) | \(\) |
## 8. Coaching focus this quarter
Play and must-cover moment to coach first:Why (evidence):## 9. Governance
Owner:Approvers:Default review date:Review triggers: new recurring objection or competitor / pricing, packaging or product change / repeated stalls at one stage / a criterion most reps miss## 10. Change log
| Date | Version | What changed | Why | Evidence |
| --- | --- | --- | --- | --- |
| \(\) | 1.0 | First version | \(\) | \(\) |
Everything above works with a shared document and a manager's time. Software helps where that time runs out: keeping the evidence log current, supporting reps while the conversation is happening and seeing whether plays are followed across a whole team.
One naming note first. The playbook in this guide is a document your team writes and owns. Spiky's Sales Playbook is a product feature that checks meetings against a supported sales framework: BANT, SPIN, MEDDIC or MEDDPICC. The feature can verify the parts of your playbook that map to those frameworks. The rest of your playbook, such as company-specific must-cover moments, still needs a manager's review.
Spiky Signals analyzes sales conversations to identify recurring patterns, objections and behaviors across reps and calls. That supports Step 2, when you are building the evidence log, and Step 6, when you are watching for review triggers such as a new objection spreading across the team. Treat what Signals surfaces as patterns to investigate. The decision to change a play stays with the playbook owner.
Spiky Whisper provides real-time, contextual guidance during live sales conversations, which is the moment Step 5 prepares for. During live meetings, reps can open the Sales Playbook, choose one of the supported frameworks and see which key topics have been discussed so far. The view appears within about a minute and keeps updating through the meeting. The framework can't be switched once it has been chosen for a meeting, so pick the one that matches the call. According to Spiky's Help Center, the real-time playbook is available on Premium and Enterprise plans.
After a meeting, the Sales Playbook in Spiky Pulse evaluates it against the chosen framework. Each key topic is marked as covered or missed, with the transcript excerpts where it was discussed, and the results can sync to your CRM. If you map some of your must-cover moments to framework topics, managers can see where they were covered without listening to every recording, then coach on the specific moment, as described in Step 6.
To see how your own meetings compare against the framework topics in your playbook, book a Spiky demo.
A sales playbook should include the segment and call types it covers, your ideal customer and disqualifiers, the stages of your sales process with exit criteria based on buyer actions, one play per call type with observable must-cover moments, the objections buyers raise in their own words, competitor notes, an owner and a change log.
Long enough to cover the call types in scope and short enough that a rep can find the right play in under a minute. Many teams keep a full reference version and a one-screen in-call version of each play.
Review it on a regular schedule, such as quarterly, and sooner when something changes in the market: a new recurring objection or competitor, a pricing or product change, or deals repeatedly stalling at one stage. Log every change with the evidence behind it.
One named person, usually a sales enablement lead or a front-line sales manager. Sales leadership, RevOps and product marketing approve the parts they are responsible for, such as stage definitions and competitive claims.
A template saves time on structure, but the value of a playbook comes from what goes into it. Use a template like the one above to organize the work, and fill it from your own calls, deals, an,d buyers rather than from generic examples.
28 Sep 2026
The CRO role is moving beyond sales leadership. See why the next generation of revenue leaders needs analytical judgment, AI fluency and cross-functional operating skills.
Nisa Meray
19 Sep 2026
Not "which sales model is better?" but which model should own which part of your market—and why?
Nisa Meray
11 Sep 2026
What breaks as a sales organization grows? Learn how leadership, messaging and GTM structure change around the $5M, $25M and $100M stages.
Nisa Meray
Stay in the loop with everything you need to know.