How to Write a Sales Playbook for a Small Team: Start With One Page

Somewhere in your company there is a person who sells better than everyone else, and very often that person is the founder. They know who to call, which questions open a conversation up, what to say when the price lands badly, and when to walk away. Almost none of it is written down. When the first salesperson arrives, they are handed a login, a list and a pat on the back, and they start from zero.

A sales playbook fixes that. It is simply the written version of how your best salesperson sells, so that the next person can begin from something proven instead of guessing. This guide explains why small teams resist writing one, why it pays anyway, and how to produce a useful first version in a week — on one page, not in a binder.

Key takeaways

Why founders resist writing one, and why it pays

The resistance is reasonable. A team of two or three does not feel like it needs documentation; everyone can just ask. The product is changing, the market is still being learned, and anything written today will be wrong in three months. Writing it down feels like bureaucracy arriving early.

Those objections are right about the binder and wrong about the page. A short playbook is not a bureaucratic exercise; it is a cheap way to find out what you actually believe. It pays back in three places.

• Hiring. A new rep with a playbook is productive in weeks instead of months, and you can judge their early calls against something specific rather than a feeling.
• Consistency. Without shared definitions, two people mean different things by “qualified” or “proposal sent”, and your pipeline numbers become unreliable.
• Coaching. You cannot coach against a standard that exists only in your head. A written standard turns “that call felt off” into “you skipped the budget question”.

Start with one page, not a binder

The first version should fit on a single page, or at most two. The limit is a feature. It forces you to keep only what changes behaviour on the next call and to drop what merely sounds thorough.

A useful test for every line: if a new rep did the opposite, would we notice, and would it cost us? If not, the line is decoration. Cut it.

What goes in it, in order

The order below follows the life of a deal, from who you chase to how you record the result. Under each heading is what to put there and how short to keep it.

1. Who we sell to

Describe your ideal customer in a few lines: industry, size, the role you usually talk to, the problem that makes them buy, and the situation that tells you it is the right moment. Then write the disqualifiers, which are more valuable than the description. These are the signs that a prospect will waste your time: no budget owner on the call, a need you cannot meet, a buying process longer than your runway, a request for heavy customisation.

If you want a method for turning this into a scoring approach, our guide to lead qualification covers it. For the playbook, a paragraph and a disqualifier list is enough.

2. What we sell, and the three-sentence pitch

Write what you sell in plain language, then compress the pitch into three sentences: the problem, what you do about it, and the proof it works. Everyone on the team should be able to say it without notes. If three people say it three ways, the playbook has found its first job.

3. Pipeline stages, with exit criteria and next-step rules

This is the section that most improves forecasting. For every stage, write what must be true for a deal to leave it, not just what happens while it is there. Then add a next-step rule: no deal sits in a stage without a dated next action.

These are illustrative; yours should use your own stages and your own evidence. Our guide to pipeline stages and exit criteria goes deeper on choosing them.

4. Discovery questions and call structure

Write the call as a short sequence: open and set the agenda, ask the questions, summarise back, agree the next step. Then list the six to ten questions that matter most, grouped by what they uncover — the problem, its cost, who decides, how they buy, what else they have tried. Keep it as a guide, not a script to read aloud. The discovery call guide in this series expands each question.

5. Objection handling: the five you hear most

Do not try to cover every objection. Write down the five you hear most often, and for each give a considered answer: what the buyer is really worried about, a response that is honest, and the evidence you can offer. A table works well because it can be scanned mid-call.

Replace these with the five you actually hear. Honest answers matter more than clever ones; buyers can tell the difference.

6. Pricing and discount rules

State the price list, what is negotiable and what is not, and who can approve what. A simple structure is enough: a rep can offer up to a small stated concession alone, anything larger needs the owner, and every concession must be traded for something — a longer term, an upfront payment, a case study. Write the rule down and discounting stops being a mood.

7. Proposal and follow-up rules

Say when a proposal is sent (never before discovery is complete), what it contains, and who reviews it. Then set the follow-up cadence: how many touches, over how long, through which channels, and when to stop. The stopping rule is as important as the cadence; a clear break-up message keeps your pipeline honest and your reputation intact. Our guides to follow-up cadence and proposals cover the detail.

8. Handoff to delivery

A deal is not finished when it is signed. List what the person delivering the work needs to know: what was promised, the buyer’s stated goals, key contacts, any commitments made in negotiation. A short handoff note prevents the most common early churn cause, which is a customer receiving something different from what they were sold.

9. How we record things in the CRM

Name the required fields on a deal, the naming convention, and the lost reasons to choose from. Keep the list short enough that people will actually fill it in. A lost reason chosen from a fixed list is worth ten free-text notes, because you can count it later.

• Required on every deal: owner, value, expected close date, next step and its date.
• Naming: one convention, such as company name followed by what is being bought.
• Lost reasons: a fixed list of five to eight, plus “other” that requires a note.

10. Weekly rhythm

Finally, write down the meetings. A weekly pipeline review focused on next steps, not storytelling. A regular one-to-one with each rep. A monthly win-loss review where you look at why you won and lost. The rhythm is what keeps the playbook alive, so it belongs in the playbook itself. Our win-loss analysis guide explains how to run that monthly session.

How to write it from reality

The biggest risk is a playbook written from imagination. A document that describes how you wish people sold will be ignored by the people who sell. Use three sources instead.

Record two good calls

Take two recent calls that went well, with the participants’ consent and in line with local recording laws, and listen to them with a pen. Note how the call opened, which questions produced the most useful answers, how objections were handled and how the next step was agreed. Patterns appear quickly.

List the questions that unlocked deals

Ask each person who sells to name the three questions that most often move a conversation forward. The overlaps become your discovery section; the differences are worth a discussion, because they show where people disagree about what matters.

Interview the last five customers

Talk to five recent customers and ask why they bought, what nearly stopped them, who else they considered, and what they would tell a colleague. This gives you real language for the pitch and honest material for the objection table, and it often reveals that the ideal customer is slightly different from the one you assumed.

Rules versus guidance

Not everything in a playbook should carry the same weight. If every line is a rule, people either follow all of it mechanically or ignore all of it. Decide which items are which, and say so on the page.

Version and ownership

Documents die when they belong to everyone. Name one owner — usually the head of sales, or the founder until there is one. Their job is not to write everything but to decide what goes in and to keep it current.

• A named owner at the top of the page.
• A review every quarter, booked in the calendar, ideally after a win-loss review so changes reflect evidence.
• A short changelog at the bottom: date, what changed, why. It takes two minutes and shows the team the document is alive.
• One place to find it. If there are three copies, there are three versions.

Onboarding a new rep: 30, 60, 90 days

The playbook earns its keep when someone new joins. Use it as the spine of the first three months rather than a document handed over on day one.

First 30 days: learn

Read the playbook, listen to recorded calls, shadow live ones, learn the product and the CRM conventions. By the end of the month the new person should be able to give the pitch, explain each stage and describe the ideal customer unprompted. Check this by asking, not assuming.

Days 31 to 60: practise with support

Start running calls, with the owner listening in or reviewing recordings afterwards. Feedback should refer to the playbook specifically: which question was skipped, which exit criterion was missed. Add a weekly roleplay of a real objection and review one recorded call. Begin owning a small slice of the pipeline.

Days 61 to 90: own and contribute

Carry a full pipeline, run follow-ups to the cadence, and bring one improvement to the playbook, whether a new objection or a better question. A new person sees the document with fresh eyes, and their first-quarter confusion is the most reliable guide to what is unclear.

Keeping it alive

Most playbooks die the same way: written with enthusiasm, shared once, and never mentioned again. The test of a living playbook is simple. Is it referred to in the weekly pipeline review? In one-to-ones? In the conversation after a lost deal?

Common mistakes

• Copying a big company’s playbook. Their process suits their price, team size and market. Borrow headings if you like, but fill them with your own evidence.
• Forty pages nobody reads. Length is not rigour. If it cannot be skimmed before a call, it will not be used during one.
• Written by someone who does not sell. A marketing or operations draft can look tidy and be useless on the phone. The people who sell must write or approve it.
• Never updated. An out-of-date playbook is worse than none, because it teaches the old way with authority.

How Scalry handles this

A playbook is a document, but most of it only works if it is reflected in the tools your team uses every day. Scalry’s CRM has places for much of what the page describes.

• Who we sell to. The CRM stores an ideal customer profile record, and lead-scoring rules with a score log show why a lead scored as it did.
• Stages and exit criteria. Pipelines have ordered stages with win probabilities, and deals carry an owner, a value, an expected close date and a lost reason. Tasks hold the dated next step, and a timeline records activities against each deal.
• Call guides. The calling module stores call scripts by type — discovery, qualification, cold outreach, follow-up, demo, objection handling and closing — each with an objective, opening, questions, talking points, objection responses and a closing.
• Email templates. Reusable email templates can be shared with the team, and proposals can start from templates.
• Recording what is required. Custom fields let you add the fields your playbook says are mandatory.
• Call review. Calls can be recorded where permitted and summarised by AI, which makes the review habit quicker to keep.

To be clear about scope: Scalry stores the structures and keeps the records. It does not write your playbook, and it will not decide your discount rules or exit criteria for you. Those come from your own evidence. The tool makes them easier to apply consistently once they exist.

Questions to ask before you commit

Whichever way you are leaning, these are the questions that change the answer. Work through them against your own numbers rather than anyone's feature matrix — including this one.

• Could a new rep describe our ideal customer and disqualifiers after a day? If not, that section needs writing first.
• Does every pipeline stage have an exit criterion? If two people disagree on what a stage means, your forecast is guesswork.
• Do we know the five objections we hear most? And do we all answer them the same honest way?
• Who can approve a discount, and by how much?
• Who owns the playbook, and when is it next reviewed?
• Where is it referred to in our weekly meetings? If nowhere, it is not yet part of how you work.

If you cannot answer the first three, you are not ready to choose between Scalry and a written sales process yet — you are still deciding what you need, which is a cheaper problem to solve first.

A plan to get started

This week: draft the page

Write the ten headings on one page, fill in what you already know, and mark the gaps. Review two recorded calls and interview a couple of recent customers to fill them.

By the end of the month: revise and set the rhythm

Make the corrections, name the owner, add a changelog and put the quarterly review in the calendar. Then decide which one section is worth expanding into its own document first — usually discovery or objections.

Frequently asked questions

What is a sales playbook?

A sales playbook is a written guide to how your team sells: who you sell to, what you say, how deals move through the pipeline, how you handle objections and pricing, and how you record results. It captures what your best people already do so new hires can start from something proven.

Is a sales playbook worth it for a team of two or three?

Yes, if you keep it short. A one-page version forces you to agree on definitions, exposes gaps such as improvised discounts, and makes your first hire much faster to onboard. A forty-page binder is not worth it at that size.

How long should a sales playbook be?

Start with one page, or two at most. Expand a section into its own document only when the short version stops being enough. If it cannot be skimmed before a call, it is too long.

What should a sales playbook include?

In order: who you sell to and who you do not, what you sell and a three-sentence pitch, pipeline stages with exit criteria, discovery questions, your top five objections with answers, pricing and discount rules, proposal and follow-up rules, handoff to delivery, CRM recording rules and the weekly rhythm.

How do I write a playbook if I have never written one?

Write it from reality rather than imagination. Record and review two good calls, list the questions that unlocked deals, and interview your last five customers. Draft the page in a week, share it with everyone who sells, and revise it from their corrections.

How often should a sales playbook be updated?

Review it at least once a quarter, ideally after a win-loss review, and make small edits whenever something changes, such as a new objection. Name one owner and keep a short changelog so the team can see it is current.

How do I get my team to actually use the playbook?

Build it into routines. Refer to it in the weekly pipeline review, in one-to-ones and when reviewing lost deals. Let the people who sell write and edit it, keep the rules few, and explain the reason behind each one.