Use this when: You've personally closed 10-20 deals and the sales process works, but it lives in your head. You're about to hire your first salesperson and have nothing to hand them. Or you already hired someone and they're floundering because they're guessing at what you do instinctively.
You're done when: A new hire could read your playbook on Monday and run a credible sales call by Wednesday without shadowing you first.
Why this matters
Most founders skip this step entirely. They hire a salesperson, sit them next to the founder for a week, and hope osmosis does the job. It doesn't. What actually happens: the new hire picks up 40% of what the founder does, invents the other 60%, and closes at half the rate. The founder blames the hire. The hire blames the lack of training. Both are right.
The sales playbook is the bridge between "I know how to sell this" and "anyone can sell this." Without it, every new hire starts from scratch. With it, they start from your best version.
This isn't about documentation for documentation's sake. It's about making your sales motion transferable. The playbook captures the decisions you've already made through trial and error so the next person doesn't repeat your mistakes.
The Sequence
1. Start with what you actually do, not what you think you should do
Sit down after your next five sales calls and write down exactly what happened. Not the idealized version. The real version. What did you say to open? What questions did you ask? What objections came up? How did you handle them? What did you send after the call?
Most founders discover a gap between their mental model of how they sell and what they actually do. The playbook captures reality, not aspiration. If you write down what you wish you did, the new hire will try it, fail, and lose confidence.
Record your next 5-10 calls if you aren't already. Watch them back. Transcribe the key moments. Your playbook should sound like you on a good call, not like a sales textbook.
- Deliverable: Raw notes from 5 real sales calls, including exact questions asked, objections encountered, and follow-up actions taken.
- Common mistake: Writing the playbook from memory in a conference room instead of from real call recordings.
2. Define who you sell to
Your playbook starts with the buyer, not the product. Write a one-page ICP definition that answers:
- Who buys: Job title, company size, industry, and the specific trigger that makes them look for a solution right now.
- What they care about: The 2-3 problems they're trying to solve, in their language, not yours.
- What they've tried: The alternatives they've already considered or used, and why those fell short.
- Who else is involved: The other people in the buying decision, what they care about, and what power they have.
- Red flags: The signals that tell you this prospect will waste your time. Write these down explicitly so new hires don't learn them the hard way.
Be specific. "Mid-market SaaS companies" is not an ICP. "Head of Engineering at 50-200 person B2B SaaS companies who just raised Series A and are scaling their team faster than their tooling can support" is an ICP.
- Deliverable: A one-page ICP document with all five sections filled in.
- Common mistake: Describing your ICP so broadly that it doesn't help a new hire prioritize who to call first.
3. Write your call scripts
You need two scripts: discovery and close. Not word-for-word scripts that sound robotic, but structured outlines that ensure every call covers the right ground in the right order.
Discovery script:
- Opening question (why they took the call, what they're hoping to solve)
- 5-7 discovery questions that go deeper than surface-level pain
- Transition phrases for moving between sections
- The specific moment when you know enough to move to a close
Close script:
- How you bridge from discovery to pitch (the transition sentence)
- Your pitch structure (3 bullets, under 3 minutes)
- The ask (how you actually request the sale)
- Objection responses for your top 5 objections, with exact language
Write these in your voice. If you naturally say "that's interesting, tell me more about that," put that in the script. If you never say "I'd love to unpack that further," don't put it in the script. Authenticity matters more than polish.
- Deliverable: Two written call outlines with specific questions, transitions, and objection responses.
- Common mistake: Writing scripts so detailed that reps read them verbatim and sound like robots, or so vague that reps have no structure at all. The right level is a skeleton with key phrases, not a screenplay.
4. Document your process, not just your pitch
The pitch is maybe 20% of what makes your sales motion work. The other 80% is everything that happens between calls: how you follow up, how fast you respond, how you prepare, what you send, when you escalate, when you walk away.
Your playbook needs sections for:
-
Lead qualification: How to decide in under 5 minutes whether a lead is worth a call. What data to check, what signals matter, what's an automatic disqualify.
-
Pre-call prep: What to research before every call. Where to look. How long to spend (hint: 5-10 minutes, not an hour).
-
Follow-up sequences: Exactly what to send after each type of interaction, with templates and timing. Day 0, Day 2, Day 5, Day 10.
-
CRM hygiene: What to log, when to log it, how to update deal stages, what "qualified" actually means in your pipeline.
-
Handoffs: If anyone else touches the deal (technical resource, founder for strategic calls, customer success for onboarding), when and how that handoff happens.
-
Kill criteria: When to stop pursuing a deal. This is the section most playbooks lack and most reps need. Without it, reps hold onto dead deals for months because giving up feels like failure.
-
Deliverable: Written SOPs for each section above with specific actions, timing, and templates.
-
Common mistake: Only documenting the "happy path." Your playbook needs to cover what to do when things go wrong: the prospect ghosts, the champion leaves, the budget gets cut, the competitor shows up.
5. Add your war stories
The most useful parts of any sales playbook aren't the scripts. They're the examples. Real scenarios that teach judgment, not just procedure.
For each section, include 1-2 examples:
- "Here's a call where discovery went well, and here's why"
- "Here's an objection that seemed like a dealbreaker but wasn't"
- "Here's a deal we should have killed earlier, and the signs we missed"
- "Here's exactly how we won the deal against [competitor]"
These stories do something scripts can't: they transfer intuition. A new hire who reads "qualify on budget early" will nod and forget. A new hire who reads about the time you spent six weeks on a deal only to learn the prospect had no budget will remember.
If you recorded your calls, link to specific recordings with timestamps. "Listen to minutes 4-7 of the Acme call to hear how I handle the 'we already have a vendor' objection."
- Deliverable: 2-3 annotated examples per major section, drawn from real deals.
- Common mistake: Only including success stories. The losses teach more.
6. Keep it alive
A playbook that's accurate on day one and wrong by month three is worse than no playbook at all. It builds false confidence.
Set a monthly review cadence:
- What's changed in the market, the product, or the buyer?
- Which scripts are converting and which aren't?
- What new objections are showing up?
- What questions are new hires asking that the playbook doesn't answer?
Version your playbook. Date every update. When you change an objection response, note what it replaced and why. This creates a learning record, not just a reference document.
The best playbooks have a feedback loop built in. Every new hire who uses the playbook should flag what was unclear, what was missing, and what was wrong. After three hires, the playbook is three times better.
- Deliverable: A recurring monthly calendar block to review and update the playbook, plus a simple changelog.
- Common mistake: Treating the first version as the final version. A playbook is a living system, not a one-time document.
Template
Example
A B2B SaaS founder selling workflow automation to operations teams had closed 15 deals herself over 4 months. Her sales process worked, she closed at 35%, but it was entirely in her head:
- She hired a rep who shadowed her for a week, then went solo. His close rate: 12%
- She spent a weekend writing the playbook using recordings from her last 10 calls
- The ICP section specified that their best buyers were ops managers at 100-300 person companies who had tried Zapier and hit its limits, and that "we're happy with our current tools" was almost always false and could be reframed by asking about manual workarounds
- The objection section included her exact response to "we don't have budget this quarter": "totally fair, when does your next budget cycle start? Let's get the evaluation done now so you're ready to move when the budget opens."
- She added three war stories, including a deal she'd spent two months on before realizing the "champion" had no actual authority to buy
- The new rep re-read the playbook, re-listened to the tagged call recordings, and within three weeks was closing at 28%. Not her 35%, but more than double his starting rate
- By version 3 of the playbook, which incorporated the rep's own learnings, both were closing at 33%
Written with ❤️ by a human (still)