Most sales playbooks are documentation projects that masquerade as enablement tools. Someone spent three weeks writing a Notion doc that covered every objection, every competitor, every stage of the sales process, and then uploaded it to a folder that nobody goes back to.
That’s not a playbook. That’s a box-ticking exercise.
A real sales playbook is a working tool — something a new hire can follow to close their first deal, something a manager can use to coach, something that gets pulled up during call prep and deal reviews. If it isn’t being used, it isn’t a playbook. It’s a document.
Here’s how to build one that actually works.
What a sales playbook actually is
A sales playbook is not a slide deck. It’s not a brand guide. It’s not a collection of product specs or pricing sheets.
A playbook codifies how to sell. Specifically: who to sell to, how to find them, what to say to get their attention, how to run a discovery conversation, how to qualify whether there’s a real deal, how to build a proposal, how to handle the objections that will come, and how to close. It covers the entire sales motion from first contact to signed contract, in enough detail that someone who’s never done it before can follow it.
The test of a good playbook is simple: can a new hire close a deal following it, without having to shadow the founder for three months? If the answer is no, you haven’t finished.
The sections your playbook needs
1. ICP and target profile
Who you’re selling to, and — equally important — who you’re not. Include firmographic criteria (company size, industry, geography), behavioural criteria (what problem triggers make them likely to buy), and disqualifying criteria (what makes a company a bad fit, regardless of how interested they seem).
If your ICP isn’t well-defined, stop here and do that work first. There’s no point writing a playbook for an audience you can’t describe.
2. Discovery framework
The questions to ask in a discovery conversation, and why. This isn’t a script — it’s a framework that experienced reps can adapt while junior reps can follow more closely.
Cover: what you’re trying to understand (the problem, the impact of the problem, what’s been tried, what success looks like, who else is involved in the decision, what the timeline and budget situation is). Include example questions for each area, and guidance on what different answers mean for qualification.
3. Qualification criteria
What makes a deal worth pursuing, and what moves it out of the pipeline. I’d recommend building this around a qualification framework rather than just a checklist — MEDDIC, MEDDPICC, SPICED, or a custom version that fits your sales motion. The framework should be explicit enough that a rep and their manager can agree, looking at the same deal, on whether it’s qualified.
This section should also define what each pipeline stage requires for a deal to move forward. Stage progression should be earned, not assumed.
4. Objection handling
The eight to twelve objections you hear most often, and how to handle each one. Not scripts, but the underlying logic: why does the prospect raise this objection, what is it usually a proxy for, and what response addresses the real concern rather than the surface-level pushback.
The most common objections in most B2B sales cycles: “we don’t have budget right now”, “we’re happy with our current solution”, “can you send some information and I’ll pass it on”, “we need to involve someone else before we can move forward”, “you’re more expensive than the alternative.”
Every one of these has a response. Write them down.
5. Competitive positioning
For each of your main competitors (or the “do nothing” option, which is often your most common competitor), explain honestly where you win, where you lose, and what the key differentiators are. This section should be updated at least twice a year as the competitive landscape shifts.
Be honest about where competitors are stronger. A rep who knows your weaknesses can manage them; a rep who’s never been told they exist will be blindsided mid-deal.
6. Proposal and commercial process
How proposals get built, who reviews them, what approval process governs non-standard pricing, what the standard contract terms look like, and what to do when a prospect wants to negotiate. This sounds operational but it’s where a lot of deals either accelerate or stall based on how well the rep understands the process.
7. Handoff to customer success
What information gets passed to CS at close, what the customer should expect in the first 30 days, and who owns the handoff meeting. A bad handoff is one of the most common causes of early churn — the customer feels like they’ve been sold something that doesn’t match what they signed up for. The playbook should make the transition seamless.
Build it from call recordings and existing deals, not from scratch
The biggest mistake in playbook construction is starting with a blank page. Everything in the sections above already exists, implicitly, in how your best salespeople (often just you, the founder) actually sell. You just haven’t written it down.
Start with your last ten closed-won deals. Go back through the emails, the call recordings if you have them, the proposal documents. Ask yourself: what did I say in the first call that resonated? How did I handle the budget question? What was the moment in each deal where momentum built — and what did I do to create that moment?
Then do the same for five or six closed-lost deals. What objections came up that you didn’t handle well? Where did deals stall? What information did you not have at the point when it would have helped?
The playbook should be a distillation of these patterns — what worked, why it worked, and how to replicate it intentionally. It should also include what you’ve learned doesn’t work, and why.
If you use a tool like Gong, Chorus, or even just Fireflies for call recording, this exercise becomes easier. But even without call recordings, a careful review of email threads and deal notes will surface the patterns you need.
The founder trap: a playbook that only works for you
The most common failure mode in founder-built playbooks is that they describe how the founder sells — which often relies on the founder’s credibility, network, ability to improvise under pressure, and deep product knowledge accumulated over years — rather than a process that can be followed by someone who has none of those things.
A playbook that only works for you isn’t a playbook. It’s a job description for a clone.
The test for this is asking whether a competent but new hire could follow the process and get similar results. If the answer requires them to have your specific energy, your specific instincts, or your specific relationship with a particular customer type — that’s knowledge that hasn’t been externalised yet.
This is uncomfortable for founders, because it means being explicit about the intuition and instinct you’ve never had to articulate. But that externalisation is exactly the point. The goal is to build a commercial function that doesn’t depend on you being present in every deal. The playbook is the first step in that transition.
I’ve written more about this specifically in the context of founder extraction — the process of systematically removing founder dependency from the sales function. The playbook is usually the right place to start.
Maintenance: how to keep it alive
A playbook that gets written once and never updated becomes outdated within six months and harmful within twelve. The competitive landscape changes. Your ICP shifts. New objections emerge. Old ones become less common. Your product evolves.
Build in a quarterly review process. Assign someone to own it — in a small team, this might be the sales manager or the RevOps function. Make updating the playbook part of the workflow when new objection patterns emerge, when a competitor makes a significant move, or when you adjust your go-to-market.
The most reliable way to keep a playbook current is to use it in coaching. If managers are running deal reviews against the playbook — “what qualification criteria did you confirm here?”, “how did you handle the pricing objection?” — the gaps and outdated sections will surface quickly and get fixed.
A playbook that’s woven into daily sales practice will self-improve over time. One that lives in a Notion folder won’t.
For the underlying process architecture that should inform your playbook, my post on how to build a sales process covers the structural foundations in detail. And if you’re working through the broader challenge of building a sales function that operates without the founder in every deal, the Founder Extraction Playbook explains how that work typically unfolds.