Owners ask for sales playbooks all the time. It sounds like the right fix. Write down what good looks like, hand it to the team, and consistency follows.
I recently spent five months as a fractional sales leader with a company rebuilding its sales organization. We turned two positions into three new roles, and I built a playbook for each one before handing everything off to their new director of sales.
That work reinforced something I've seen for years: A playbook is documentation of a sales process. If the process doesn't exist, there's nothing to document.
What a Sales Playbook Includes
A real playbook goes from strategy all the way through execution. For each role, it should cover:
- The purpose of the role and how it fits the overall sales strategy
- The sales process, stage by stage
- Messaging for outbound prospecting
- The questions to use in a first discovery conversation
- The cookbook: the types and number of activities the role needs to be successful
- A section for the manager on how to coach and support the person in that role
Look at that list closely. Almost every item depends on decisions that have to be made before anyone writes a page.
The Symptoms Show Up First
Nobody calls and says, "We don't have a sales process." They call because of what the missing process causes:
- They miss the number and can't explain why
- The forecast swings from month to month
- The team is busy but not productive
- Every rep sells a little differently, and results depend on who got the lead
- The founder is still closing the big deals
These are all process problems. A playbook sounds like the answer because it's tangible. But writing it before the process is defined just gives the problem a nicer cover page.
Why Writing It Down First Doesn't Work
When there's no defined process, playbooks usually get built one of two ways.
- Documenting what the top performer does. That captures habits, instincts, and personality. It rarely transfers, because the top performer often can't explain what they're doing differently.
- Starting from a template. The result looks professional, is stored on a shared drive, and nobody opens it after onboarding.
Neither approach answers the questions that make a playbook useful.
- What does a qualified opportunity look like?
- What has to be true for a deal to move to the next stage?
- How does your buyer make decisions?
- Which activities predict results and which just fill a calendar?
Build the Process, Then the Playbook
The order matters. Before documenting anything, leadership needs to settle a few things.
- Define the purpose of each role. In the engagement I mentioned, the biggest decisions weren't about scripts. They were about what each of the three new roles was for and where one ended and the next began.
- Map the buyer's decision process. Your stages should reflect what the buyer does, not what the seller does. If a stage can be completed without the buyer confirming anything, it's a seller activity, not a stage.
- Set clear criteria for every stage. When reps and managers use the same definitions, pipeline reviews become decisions instead of discussions.
- Set a starting cookbook, then adjust it. With brand-new roles, no one knows the right activity numbers on day one. A good playbook sets a reasonable starting point and makes it clear who owns adjusting it once real data comes in.
- Build coaching in from the start. If the manager's section is an afterthought, the playbook becomes a reference document instead of a management tool.
- A playbook is a management tool, not a binder. When the process is right, the playbook earns its keep. New hires ramp faster because expectations are written down. Managers coach against a shared standard instead of their own preferences. And when your best salesperson leaves, the process stays with the company instead of walking out the door with them.
That's the real value. Not the document itself, but the clarity it forces.
If you've been thinking about a sales playbook, start with a harder question: Could you explain your sales process, stage by stage, and would your team describe it the same way? If the answers don't match, that's where the work starts. Let's connect.
