What is a sales playbook?
A sales playbook is the written record of how your team wins deals: who you sell to, how a deal moves from first meeting to signature, what a rep should do in common situations, and which approved words and content to use. A sales playbook template is the fixed outline behind it, so a new rep, a manager and an enablement lead all find the same answer in the same place.
The core of a playbook is its plays. A play is a repeatable response to a specific situation, such as "a new executive joins the buying group" or "the deal goes quiet after the demo", with a trigger, the steps to run, the content to send and a definition of done. A playbook that only describes the product, with no plays, reads like a brochure and is rarely opened twice.
The practical case for a playbook is time. Salesforce's fifth State of Sales survey of more than 7,700 sales professionals found that reps spend just 28% of their week actually selling (Salesforce, State of Sales research, 2022-12-08). That is Salesforce's survey result, not Revspire data. A playbook does not fix it on its own, but it puts the answers reps would otherwise ask around for in one place.
When do you need a sales playbook?
- You are hiring several reps in a quarter and need ramp to rely on a document, not on who sits next to whom.
- Top performers sell very differently from the rest of the team, and you want to write down what works.
- You are launching a product, entering a new segment or moving upmarket to larger buying groups.
- Your CRM has stage names, but no one agrees what has to be true for a deal to move forward.
- Partners or a channel team sell your product without your reps on the call.
- Skip a full playbook if two or three reps sell one product to one buyer type; a one-page process and a battlecard may be enough.
Sales playbook vs sales play vs sales process vs battlecard
These terms are often mixed up. The playbook is the container; the others are parts of it or tools that sit beside it.
| Asset | What it is | Who uses it | Scope |
|---|---|---|---|
| Sales playbook | The full guide to how your team sells | Reps, managers, new hires, partners | Every stage, persona and common situation |
| Sales play | One repeatable response to a trigger, with steps, content and a definition of done | Reps in a live deal | A single situation, such as "champion leaves" |
| Sales process | The stages a deal moves through and the exit criteria for each | Reps, managers and RevOps for forecasting | The backbone the playbook hangs on |
| Battlecard | A one-page card on how to win against one competitor | Reps facing that competitor | One competitor |
| Messaging framework | The approved value proposition, pillars and proof by persona | Product marketing first, then reps | What you say, not what you do |
| Talk track | Suggested words for one moment, such as a cold-call opener | Reps | A single conversation moment |
The sales playbook template
Work through the sections in order: the first four define who you sell to and how deals move, the rest tell reps what to do and say. Replace everything in brackets. Keep each section short and link to long documents, such as demo scripts and battlecards, rather than pasting them in.
1. Playbook header
| Field | What to write |
|---|---|
| Playbook name and scope | [e.g. "Mid-market new business, North America"; one playbook per sales motion] |
| Owner | [Enablement lead who keeps it current] / [sales leader who signs it off] |
| Contributors | [Two or three top reps, a sales engineer, product marketing, RevOps] |
| Last reviewed / next review | [Date] / [date, at least once a quarter] |
| Where it lives | [One link reps can bookmark; no attached copies] |
2. Who we sell to
| Field | What to write |
|---|---|
| Ideal customer profile | [Industry, company size, region, tech stack and the trigger events that make an account a fit] |
| Disqualifiers | [Signals that a prospect is not a fit and should be passed on or closed out] |
| Problems we solve | [The three to five business problems buyers describe, in their words] |
| Value proposition | [One or two sentences, copied from the messaging framework] |
| Typical buying group | [Economic buyer, champion, technical evaluator, end users, procurement, legal] |
3. Buyer personas
| Persona | Goals | Pains in their words | What they need to see | Question to ask |
|---|---|---|---|---|
| Economic buyer (e.g. CFO, COO) | [The business result they are measured on] | [Pain, quoted from calls] | A business case in their numbers and a credible plan to get value | "What happens if this stays as it is for another year?" |
| Functional leader (e.g. VP Sales, VP Operations) | [Goal] | [Pain] | Proof that teams like theirs reached the outcome | "How are you measured this year, and where are you behind?" |
| Champion (often a director or operations lead) | [Goal] | [Pain] | Material they can reuse internally and a clear plan | "Who else needs to believe this before it gets approved?" |
| Frontline manager | [Goal] | [Pain] | How it saves them time every week | "Walk me through how you prepare for your weekly team review." |
| End user | [Goal] | [Pain] | A hands-on demo of their daily workflow | "Which part of your week would you happily never do again?" |
| Technical evaluator (IT, security) | [Goal] | [Pain] | Security documentation, integration detail and an expert to talk to | "What does your review process look like, and who runs it?" |
| Procurement | [Goal] | [Pain] | Complete vendor paperwork early and predictable terms | "What do you need from a new vendor, and how long does onboarding take?" |
| Legal and data protection | [Goal] | [Pain] | Standard contract and data terms, with known fallback positions | "Which terms usually take your team longest to review?" |
4. Sales process and exit criteria
| Stage | Goal of the stage | Rep actions | Exit criteria (confirmed by the buyer) | Content to use |
|---|---|---|---|---|
| 1. Prospect | Earn a first meeting with an ideal-fit account | Research trigger events; run the outbound sequence; contact more than one person from day one | Meeting booked with someone who owns the problem | [Outbound sequence, one-page overview] |
| 2. Discover | Confirm a problem worth solving and a reason to act | Run the discovery questions; quantify the cost of the problem; identify the buying group | Buyer agrees on the problem, its cost and a target date | [Discovery guide, industry point of view] |
| 3. Qualify | Decide whether to invest in the deal | Check budget path, decision process and competition with your qualification framework (e.g. MEDDICC) | Economic buyer and decision process known; deal meets the qualification bar | [Qualification checklist] |
| 4. Solution and demo | Show how the buyer's problem gets solved | Tailor the demo to discovery notes; bring in a sales engineer | Evaluators confirm their use cases were covered | [Demo script, customer story by industry] |
| 5. Evaluate and validate | Remove technical and business risk | Run the pilot against agreed criteria; arrange references; answer the security review | Pilot criteria met and security review signed off | [Pilot plan, security pack, reference list] |
| 6. Business case | Make the decision easy to approve | Co-write the business case with the champion; meet the economic buyer | Economic buyer confirms priority and budget | [ROI model, business case template] |
| 7. Propose and negotiate | Agree commercial terms | Send the proposal; trade concessions within guardrails; run procurement and legal in parallel | Final terms agreed by both sides | [Proposal template, discount guardrails] |
| 8. Close | Get the contract signed | Confirm the signer, signature route and dates on the mutual action plan | Contract signed | [Mutual action plan, order form] |
| 9. Hand off | Start the customer well | Run an internal handoff to onboarding with goals, stakeholders and promises made | Kickoff held and success criteria handed over | [Handoff checklist] |
5. Discovery questions
| Topic | Question to ask | What a good answer tells you |
|---|---|---|
| Current state | "Walk me through how you handle [process] today." | The workflow, the tools and who is involved |
| Problem | "What is not working about that?" | The pain in the buyer's own words |
| Impact | "What does that cost you in time, money or risk?" | Whether the problem is worth solving |
| Urgency | "Why look at this now rather than next year?" | The compelling event and the real deadline |
| Desired outcome | "If this works, what is different in six months?" | Success criteria you can write into the plan |
| Decision process | "How have you bought something like this before, and who signed off?" | The steps, approvers and how long they take |
| Buying group | "Who else will weigh in, and who could stop this?" | The stakeholders you have not met yet |
| Budget | "How would this be funded: existing budget or a new request?" | Whether a budget path exists |
| Alternatives | "What other options are you considering, including changing nothing?" | The competitors and the status quo you are up against |
| Next step | "What would you need to see to take this to [economic buyer]?" | The agreed next step and the evidence it needs |
6. Plays
| Play | Trigger | Steps | Content to send | Done when |
|---|---|---|---|---|
| New executive in the account | A new leader joins in a role that touches the decision | Send a short, relevant insight; ask the champion for an introduction; book a 20-minute alignment call | [Executive brief] | Meeting held and their priorities recorded |
| Deal goes quiet after the demo | No buyer reply for [10] business days after a demo | Send a recap with one new insight; call the champion; offer a short working session with the evaluators | [Demo recap, customer story] | Buyer confirms a next step and date |
| Single-threaded deal | Only one buyer contact engaged at stage 3 or later | Ask the champion who else is affected; offer something useful to each new person; bring in a peer from your side | [Stakeholder map, persona one-pagers] | Three or more engaged contacts, including the economic buyer |
| Competitor enters late | A rival is named after discovery | Re-confirm decision criteria; open the battlecard; ask its landmine questions; offer a reference | [Battlecard, comparison page] | Decision criteria confirmed in writing |
| Champion leaves | Your main contact changes role or leaves the company | Ask for a handover introduction; re-map stakeholders; re-confirm the problem with the new owner | [Deal summary, business case] | New champion identified and engaged |
| Budget pushed to next quarter | Buyer says there is no budget right now | Quantify the cost of waiting; check for other budget lines; offer a phased start | [Cost-of-delay worksheet] | A new decision date agreed, or the deal qualified out |
| Security review stalls | Questionnaire open for more than [two] weeks | Send the security pack; offer a call between their reviewer and your expert; ask what is blocking | [Security pack, data processing terms] | Reviewer signs off |
| Discount request at signature | Buyer or procurement asks for a lower price late in the deal | Trade price for term, volume or a reference; check discount guardrails before offering anything | [Discount guardrails, approval route] | Approved terms in the final proposal |
7. Objection handling
| Objection | What is usually behind it | Response approach | Proof to share |
|---|---|---|---|
| "It is too expensive." | Value is not yet clear, or the budget holder is not involved | Return to the cost of the problem and compare it with the cost of doing nothing | [ROI model, customer story] |
| "We already have a tool for that." | Switching feels risky and the current tool is "good enough" | Ask what the current tool does not do for them; show coexistence or a migration path | [Migration plan, integration overview] |
| "Now is not a good time." | No compelling event, or competing priorities | Ask what would make it a priority and tie the decision to a date they care about | [Cost-of-delay worksheet] |
| "We will build it ourselves." | An internal team thinks it is simple | Compare the full cost of building and maintaining it; ask who owns it in two years | [Build vs buy guide] |
| "Just send me some information." | A polite brush-off, or unclear value | Ask what they want to learn and agree a short follow-up call | [One-page overview] |
| "We need to involve IT and security." | A real step, not always an objection | Welcome it; offer the security pack and an expert call now | [Security pack] |
| "Your competitor is cheaper." | Comparing price, not outcomes | Open the battlecard; reframe on outcomes and total cost | [Battlecard] |
| "I need to talk to my boss." | The champion lacks authority or confidence | Offer to help them prepare, and ask to join the meeting | [Business case, executive summary] |
8. Competitors, tools and metrics
| Field | What to write |
|---|---|
| Top competitors | [Two or three rivals, each linked to its battlecard; include "do nothing"] |
| Content library | [Link to approved content, organized by stage and persona] |
| CRM rules | [Required fields per stage and what reps must log after each meeting] |
| Metrics to watch | [Stage conversion, cycle length, win rate and ramp time; owned by RevOps] |
| Feedback route | [Where reps suggest changes, and who reviews them] |
Prefer a file? Both downloads are free and ungated.
Sales playbook example
Example: fictional company
Here is part of the template filled in for an invented software company. A real playbook completes every section; the example shows the level of detail that works.
Ferncastle Analytics sells revenue-forecasting software to mid-market sales teams. Its sales enablement lead, Nadia Brennan, wrote this playbook for new account executives selling to companies such as Marlow & Finch Logistics.
Header and who we sell to
| Field | Example entry |
|---|---|
| Playbook scope | Mid-market new business, North America: companies with 50 to 300 sellers. |
| Owner | Nadia Brennan, Sales Enablement Lead; signed off by the VP Sales. |
| Ideal customer profile | B2B companies with 50 to 300 sellers, a RevOps team of at least two and a forecast still run from spreadsheets. |
| Trigger events | A new CRO or VP Sales, a missed forecast quarter, a funding round or a CRM migration. |
| Disqualifiers | Fewer than 20 sellers, or a forecast owned entirely by finance with no frontline manager use. |
| Value proposition | Run a forecast call your managers trust, without waiting for an analyst. |
Sales process (stages 1 to 7)
| Stage | Goal of the stage | Rep actions | Exit criteria (confirmed by the buyer) | Content to use |
|---|---|---|---|---|
| 1. Prospect | Meeting with a sales leader or RevOps owner | Trigger-based sequence to the VP Sales and RevOps lead | Meeting booked with the person who owns the forecast | Trigger-event email sequence |
| 2. Discover | Confirm the forecasting pain and its cost | Run the ten discovery questions; ask to see last quarter's forecast process | Buyer agrees on hours lost each week and a target date | Forecasting maturity checklist |
| 3. Qualify | Decide whether to invest | MEDDICC check in the CRM; confirm who owns the forecast budget | Economic buyer named; decision process written down | Qualification checklist |
| 4. Solution and demo | Show the weekly forecast call view | Rebuild one of their forecast calls in the demo environment | Two managers confirm it matches how they work | Demo script, logistics customer story |
| 5. Pilot | Prove it in two regions | Four-week pilot with written success criteria | Two forecast calls run without RevOps help | Pilot plan, security pack |
| 6. Business case | Make the decision easy for the CFO | Co-write it with the champion using pilot results | CFO confirms budget for the next fiscal year | ROI model |
| 7. Propose and close | Agree terms and sign | Proposal within discount guardrails; procurement and legal run in parallel on the mutual action plan | Contract signed | Proposal template, mutual action plan |
Three plays from the playbook
| Play | Trigger | Steps | Content to send | Done when |
|---|---|---|---|---|
| New CRO in a target account | News or LinkedIn shows a new CRO or VP Sales | Send a short note on first-quarter forecasting priorities; ask any existing contact for an introduction; offer a 20-minute forecast review | New-leader forecast checklist | Meeting booked within 30 days of their start date |
| Finance wants to keep forecasting in its BI suite | The CFO or a finance systems lead joins and mentions Harborview Metrics | Open the Harborview battlecard; position Ferncastle as feeding the BI suite, not replacing it; offer the integration demo | Harborview battlecard, integration overview | Finance agrees to evaluate Ferncastle for the sales forecast |
| Pilot without a manager champion | Pilot week 2 and no frontline manager has logged in | Call the RevOps champion; book 30-minute sessions with two managers; rebuild their own forecast view with them | Pilot quick-start guide | Two managers run a forecast call in Ferncastle |
Objections new reps hear most
| Objection | What is usually behind it | Response approach | Proof to share |
|---|---|---|---|
| "Our spreadsheet works fine." | Fear of losing a familiar model | Ask how long forecast preparation takes each week and who maintains the model; show how the model maps into Ferncastle | Logistics customer story |
| "Harborview already does forecasting." | Finance owns the tool decision | Agree that finance should keep Harborview for company reporting; show the integration that feeds it | Harborview battlecard |
| "We are in the middle of a CRM migration." | Worry about timing and workload | Offer to start after cutover, and use the migration as the moment to fix the forecast process | Implementation plan |
Example: fictional company. Ferncastle Analytics, Harborview Metrics, Marlow & Finch Logistics and every person named in this example are invented for illustration. Any resemblance to real companies or people is coincidental.
How to write a sales playbook with this template
Start from your best deals, not a blank page
Pull five to ten recent wins and a few losses. Note how each deal started, who was involved, what the buyer asked and which content they used. The patterns you find are the first draft of your process and plays.
Agree the sales process and exit criteria first
Write the stages and what the buyer must have confirmed to leave each one. Align them with the CRM stages RevOps uses, so the playbook and the forecast describe the same process.
Write plays for situations reps actually meet
Ask managers and top reps which moments they coach most often: deals going quiet, a new executive, a late competitor. Give each play a trigger, steps, content and a "done when", and stop at the eight or ten that matter most.
Borrow words from customers and top reps
Take pains, questions and objection responses from call recordings and win/loss notes. Language buyers actually use is easier for reps to say and for buyers to recognize than product language written in a meeting room.
Validate, practice and launch in pieces
Review the draft with two or three reps and a manager, then rehearse the discovery questions and objection responses in role-play. Launch it section by section in team meetings rather than sending one long document.
Publish it where reps work and review it quarterly
Keep one live version where reps already look for answers, check which sections get used, and review it after product launches, pricing changes and each quarter's win/loss review.
Common sales playbook mistakes
Writing a product manual
Feature descriptions belong in product documentation. A playbook tells a rep what to do and say in a situation, through plays, questions and responses.
One playbook for every motion
New business, expansion and partner sales follow different processes. Give each motion its own playbook and share the persona and messaging sections between them.
Stages with no exit criteria
If "Qualify" has no definition, every rep moves deals on gut feel and the forecast suffers. Write down what the buyer must have confirmed.
Written without the people who sell
A playbook written by enablement alone often describes the process as it should be, not as it is. Involve top reps and managers from the first draft.
Launched once, never reinforced
A document sent in a kickoff email is soon forgotten. Practice the plays in role-plays and refer to them in deal reviews and coaching sessions.
No owner and no review date
Products, pricing and competitors change. Without a named owner the playbook quietly goes out of date and reps stop trusting it.
How Revspire turns playbooks into seller workflows
A document playbook is a good start, but it is hard to keep current and easy to ignore in the middle of a deal. Revspire's AI Playbook Engine creates playbooks with AI grounded in your approved revenue knowledge, including battlecards, objection plays, win/loss insights and role-specific messaging. Drafts are routed for approval, the governed version is published across seller workflows, and usage and performance analytics show which plays get used.
Revspire Content Hub keeps the content each stage links to in one governed repository, with versioning that keeps shared links current. With AI Sales Training & Coaching, reps can practice the playbook's discovery questions and objection responses in AI role-play, with instant AI scoring for clarity, confidence and objection handling.
Sales playbook template FAQs
What should be included in a sales playbook?
At minimum: your ideal customer profile, buyer personas, the sales process with exit criteria for each stage, discovery questions, plays for common situations, objection responses, links to competitor battlecards and approved content, and an owner with a review date. The template above has a section for each.
How long should a sales playbook be?
Long enough to cover each stage and your most common situations, short enough that a rep can find an answer in under a minute. We suggest keeping the core playbook to a few pages or screens and linking out to battlecards, demo scripts and the content library instead of pasting them in.
What is the difference between a sales playbook and a sales process?
The sales process is the sequence of stages a deal moves through and what must be true to leave each one. The sales playbook is broader: it contains the process plus who you sell to, what to say, which plays to run in specific situations and which content to use at each stage.
Who should own the sales playbook?
Usually sales enablement owns the document and keeps it current, sales leadership signs it off, product marketing supplies the messaging and competitive sections, and RevOps keeps stages and CRM fields aligned. Name one person as owner; shared ownership without a name tends to mean no one updates it.
Can AI write a sales playbook?
AI can draft sections quickly from material you supply, such as call recordings, win/loss notes and your messaging framework. Treat the output as a first draft: check every claim, have the people who sell review the plays, and publish only the approved version where reps already work.
Related templates and reading
- Free templateMessaging framework templateA B2B message house: positioning statement, value proposition, three pillars with proof, persona messages and answers to the questions buyers ask.
- Free templateSales battlecard templateA one-page card per competitor: why you win, where they are strong, landmine questions, objection responses and pricing guardrails.
- Free templateMutual action plan templateA shared, dated plan from discovery to go-live, with a buyer owner and a seller owner on every milestone.
- Free templateStakeholder map templateEvery person in the buying group on one page, with buying role, influence, stance, priorities and a next action.
- Blog: structuring an enterprise playbookEnterprise sales playbook guide
- Blog: getting sellers to use itPlaybook adoption guide
- Blog: practicing the playbookTurn playbooks into AI role-plays and coaching
- Glossary: sales playbookWhat is a sales playbook?
- Glossary: sales playWhat is a sales play?