What's the actual difference between a sales playbook and a sales process, and do I need to build both separately?
The short answer
A sales process is the sequence of stages a deal moves through — say 6 stages from lead to closed-won. A playbook is everything that makes each stage executable: scripts, qualification criteria, objection handling, email templates, pricing rules. You need the process first; the playbook operationalizes it. Building one without the other produces either a flowchart nobody follows or scripts with no structure to hang them on.
The confusion is understandable — most companies conflate them
Ask ten founders what their "sales process" is and half will describe a pipeline stage list, the other half will describe how their best rep handles a discovery call. Neither is wrong, but they're answering different questions. A process answers "what stage is this deal in and what has to be true to move it forward." A playbook answers "what does a rep actually say, send, or do at each stage." One is structural, the other is tactical. You genuinely need both, but they're not the same document and they don't get built the same way.
What a sales process actually is
The process is the skeleton: a defined, ordered set of stages a deal passes through, each with entry and exit criteria. A typical founder-led B2B process might look like: lead identified → qualified → discovery call held → proposal sent → verbal commit → contract signed. Each stage has a gate — a deal can't move to "proposal sent" until specific qualification questions are answered, for instance. The process is what your CRM pipeline should mirror. It's short — often a single page or a stage diagram — and it rarely changes once set, because changing it means re-training everyone and re-configuring the CRM.
The process also defines who owns what: does the founder still run discovery calls personally, or has that moved to a hired rep? Does marketing hand off qualified leads, or does the rep source their own? These are structural decisions, not scripting decisions.
What a playbook actually is
The playbook is the operating manual for executing the process. It includes the actual discovery call script or question set, the ICP criteria a rep uses to qualify (not just "qualified" as a stage name but the specific firmographic and behavioral filters), objection-handling language for the five most common pushbacks, email and follow-up cadences, proposal templates, and pricing/discounting guardrails. A good playbook runs 15-40 pages depending on complexity, gets revised quarterly as objections and win/loss patterns shift, and is the thing a new hire actually reads to get productive in week one rather than shadowing the founder for six weeks.
The playbook without a process is just a pile of scripts with no map for when to use them. The process without a playbook is a pipeline that looks organized in the CRM but falls apart the moment someone other than the founder tries to run it, because nobody wrote down what "qualified" means or what to say when a prospect asks for a 20% discount.
Where they overlap and where they diverge
| Sales Process | Sales Playbook | |
|---|---|---|
| Answers | What stage, what gates it | What to say/do/send at each stage |
| Length | 1 page, a stage diagram | 15–40+ pages |
| Changes | Rarely — structural | Quarterly — tactical, based on win/loss data |
| Lives in | CRM pipeline configuration | Onboarding doc, wiki, or enablement tool |
| Built by | Founder or sales leader, once | Sales leader, ongoing, informed by rep feedback |
| Fails without | Reps don't know what stage a deal is in | Reps freelance messaging, inconsistent results |
Most founder-led companies get partway to a process — a rough pipeline in a spreadsheet or CRM with stage names — and stop there because building the playbook is the harder, more time-consuming work. It requires interviewing whoever's been closing deals (often the founder), extracting the actual language and judgment calls they make intuitively, and writing it down in a way someone else can execute without three years of pattern-matching experience.
Do you need both, and in what order?
Build the process first — it's fast, it's a diagram, and it forces you to make explicit decisions about stage ownership and criteria that you're probably making implicitly already. Then build the playbook against that process, stage by stage, prioritizing the stages where deals currently die (usually discovery-to-proposal or proposal-to-close). Trying to write playbook content before the process exists means writing scripts for a structure that doesn't exist yet, and you'll rewrite half of it once the process forces different stage boundaries.
A reasonable budget for the documented version of both, done properly, runs from roughly $999 for a single ideal customer up to $4,999 for an uncapped version covering multiple product lines, teams and brands — the range depends on how many distinct buyers and motions (inbound vs. outbound, SMB vs. enterprise) you need covered.
Where SalesARC fits
SalesARC's Playbook offering builds both pieces together rather than treating them as separate engagements — the process gets mapped first, then the tactical content gets written against it, so you're not left with a diagram and no scripts or a script library with no structure. Pricing is $999 (Basic, one ideal customer), $2,499 (Standard, up to three) or $4,999 (Enterprise, uncapped and scoped with our strategists), all one-time. Details at /product/playbook.