How to Build a Sales Playbook From Scratch (Step-by-Step)

Most B2B SaaS founders agree they need a sales playbook. Almost none of them have built one. The reason is simple: building it takes 6 to 8 weeks of focused work, and that work always gets crowded out by closing the next deal.

This post is the step-by-step. Order of operations, what to write, what level of detail, and how to know when each section is "done enough" to move on.

If you do this honestly, you'll end up with a 20 to 30 page working document. Reps will reference it daily. New hires will train on it in week one. Pipeline reviews will inspect against it. That's the test of whether you have a playbook or a slide deck.

Before you start: the rule

Don't build it in order of importance. Build it in order of dependency.

Some sections depend on others. You can't write your demo framework before you know your ICP. You can't write your hiring profile before you've documented the motion the hires will run. The order below reflects what can be built when.

Week 1: ICP definition and qualification rubric

Start here. Everything else depends on knowing exactly who you sell to.

What to write:

• Firmographic profile: company size, industry, geography, growth stage, team size, tech stack
• Persona profile: role/title, function, seniority, what they're responsible for, what they're measured on
• Trigger events: what's happening at the company that makes them ready to buy
• Anti-ICP: who you do NOT sell to (this section is as important as the ICP itself)
• Qualification rubric: 5 to 7 yes/no questions a rep can apply in under 60 seconds to qualify in or out

How to know it's done: Hand the document to someone who's never sold your product. Have them describe back to you who your customer is. If they can describe a specific person at a specific kind of company doing a specific job, your ICP is documented. If they describe a general category ("B2B SaaS companies"), you're not done.

Pull from your existing won deals. Look at the last 10 customers. What do they have in common? That's your ICP. Don't theorize.

Week 1-2: Messaging framework

Depends on: ICP.

What to write:

• The 15-second pitch (what your product does, who it's for, what problem it solves)
• Primary value proposition per persona (different roles care about different things)
• Three to five proof points (specific outcomes with numbers from real customers)
• Top three objections you hear, with documented responses
• "What we are not" statement (helps reps disqualify the wrong-fit accounts quickly)

How to know it's done: Three different reps deliver the 15-second pitch and they sound substantively the same. If they're improvising, the pitch isn't documented well enough.

Week 2-3: Pipeline stages with exit criteria

Depends on: nothing structural. Can be built in parallel with messaging.

What to write:

• 4 to 7 pipeline stages from first contact to closed-won
• Explicit exit criteria for each stage: what specifically has to be true to move forward
• Time-in-stage benchmarks (how long a healthy deal sits in each stage)
• Stalled-deal protocol (what happens when a deal exceeds the benchmark)
• Stage-by-stage rep activity expectations

How to know it's done: Pull a random deal from your CRM. Walk through the playbook stage criteria. Does the deal sit in the right stage based on the criteria? If you're guessing, the criteria aren't precise enough.

The single biggest source of forecast inaccuracy in B2B SaaS sales is loose stage definitions. Tighten this section and forecast quality lifts within a quarter.

Week 3-4: Discovery framework

Depends on: ICP, messaging, pipeline stages.

What to write:

• 5 to 7 discovery questions, in the order reps should ask them
• Branching logic: if the buyer says X, follow up with Y
• The "do not ask" list: questions that waste time in a velocity motion
• Pain confirmation script: how to validate the buyer's stated problem with their own words
• Next-step script: how to advance the deal to demo at the end of a discovery call

How to know it's done: Listen to three recorded discovery calls from three different reps. The structural moves should be the same (same questions, same sequencing) even if the wording varies. If each rep is running a different play, the framework isn't documented well enough.

Week 4-5: Demo framework

Depends on: discovery framework, messaging.

What to write:

• The opening (how to start the demo in the first 3 minutes)
• The standard demo flow (which features to show in what order)
• Customization rules (what to skip or add based on what came up in discovery)
• The pricing reveal moment (when and how to introduce the price)
• The closing ask (how to end the demo with a clear next step)
• Common objections during the demo and how to handle them in the moment

How to know it's done: Three reps deliver demos that hit the same beats within 5 minutes of each other on length. If demos are running 30+ minutes apart in length, the framework isn't enforced. (Read more: The 25-Minute Demo Framework.)

Week 5: Outbound sequence design

Depends on: ICP, messaging.

What to write:

• The cadence (how many touches over how many days)
• Channel mix (email, phone, LinkedIn percentages)
• Touch-by-touch message theme (cold opener, pattern interrupt, breakup, etc.)
• Copy framework for each touch (not word-for-word scripts; structural guidance)
• Personalization expectations (which touches require it, which don't)
• Stop conditions (when to remove a prospect from the sequence)

How to know it's done: A new BDR can take the doc and run a sequence in their first week without needing to invent anything.

Week 5-6: Meeting cadence framework

Depends on: pipeline stages, discovery and demo frameworks.

What to write:

• Daily standup structure (15 min, 3 questions)
• Weekly 1:1 structure with each rep (split between pipeline review and coaching)
• Weekly pipeline review structure (deal-by-deal, not forecast roll-up)
• Monthly skill development sessions (what to teach in each)
• Quarterly business review (QBR) structure

How to know it's done: Each meeting has a specific purpose, a specific agenda, and a specific outcome. If meetings keep collapsing into "what's happening with Acme," the cadence isn't structured well enough. (Read more: Sales Coaching vs Pipeline Inspection.)

Week 6: KPI framework

Depends on: pipeline stages.

What to write:

• 8 to 12 metrics that predict outcomes in your motion
• Targets and benchmarks for each metric
• How each metric is tracked (data source, frequency, owner)
• What to do when a metric falls below threshold

How to know it's done: You can answer "is the team on track this month?" using the metrics alone, without anyone needing to explain anecdotally. (Read more: The 5 Velocity Sales Metrics.)

Week 6-7: Hiring profile and org structure

Depends on: everything above. This goes last.

What to write:

• Ideal rep profile for each role (BDR, AE, AM, etc.)
• Compensation structure (base, OTE, quota, accelerators) per role
• Interview process and scorecard
• Hiring sequence for the next 12-18 months (who you hire when, what triggers each hire)
• 90-day ramp plan template (Read more: The First AE Hire)

How to know it's done: You could hand the doc to a recruiter and they could source candidates without needing additional guidance.

Week 7-8: Stitching it together

Final assembly. Three things to do:

• Consolidate. Put all the sections into one document. Add a table of contents and clear section headers.
• Test with a new hire (real or simulated). Hand the doc to someone unfamiliar with your motion. Ask them to describe back how to run a deal. Note every place they hesitate. Those are your gaps.
• Establish the update cadence. A playbook isn't done; it's living. Set a quarterly review date and an owner.

The trap most teams fall into

Building the playbook in spare time. You said "I'll get to it after we close this quarter." You won't. The quarter will end and another quarter will start. The playbook never gets built.

The teams that finish it either (a) block 6 weeks of dedicated time for a senior person to build it, or (b) bring in outside help to build it for them while the team keeps closing. Either is fine. Trying to fit it into the cracks isn't.

Where SAILS fits

The Build phase of the SAILS engagement runs through exactly this sequence in 4 weeks (compressed from the 6-8 above because we're full-time on it while you keep selling). Output: a documented 20-30 page Sales Playbook customized to your motion, your ICP, your product.