Startup Sales Playbook: Writing Your First One

In the early days, the founder is the sales process. Everything lives in one head: who to call, what to ask, how to handle the price question. A sales playbook gets that knowledge onto paper so a first sales hire, a co-founder or a future you can sell the same way, learn faster and improve the process together.

Man standing in front of a large screen presenting charts and data to a group of seated colleagues — A playbook turns what the founder knows about selling into something the whole team can use.

Key takeaways

A first sales playbook is a short, living document, not a corporate manual. Ten to fifteen pages is plenty.
Build it from real deals you have already won and lost, not from theory.
The core sections are your ideal customer, sales stages with exit criteria, discovery questions, objection answers and handover steps.
Write it before you hire your first salesperson, then let them help improve it.
Review it every quarter and update it whenever a pattern changes.

Founder-led sales works because the founder knows the product deeply and believes in it completely. The problem comes when you try to hand it off. A new salesperson joins, and suddenly you are answering the same questions every day: which leads are worth chasing, what do we say when they ask about security, when is it time to send a proposal? Every answer you give in a chat message is a page of the playbook you have not written yet.

This guide shows you how to write your first one in a few focused sessions. It covers what to include, how to gather the material from your own deals and a template you can copy straight into a shared document.

What a sales playbook is (and is not)

A sales playbook is a shared document that describes how your company finds, qualifies and closes customers. It answers practical questions: who we sell to, what problem we solve for them, what happens at each stage of a deal and what to say in the moments that matter.

It is not a rigid script that everyone must read word for word. Good salespeople adapt to each conversation. The playbook gives them a reliable starting point and a common language, so you can compare deals, spot problems and coach people.

It is also not your CRM. The CRM records what happened in each deal. The playbook explains how deals are supposed to work. You need both, and the stage names in your playbook should match the stage names in your CRM.

When to write your first playbook

The best time is just before you hire your first dedicated salesperson. By then you have closed enough deals to see patterns, but you have not yet spent months training someone by memory.

Signs that you are ready:

You have closed a meaningful number of customers through a repeatable route, not just friends and early adopters.
You can describe your best customers in a sentence or two.
You hear the same five or six questions and objections in most calls.
You are spending more time explaining how to sell than actually selling.

If you have only closed a handful of deals, start smaller. Write a two-page version with your ideal customer and your discovery questions, then grow it as you learn.

Pro tip

Late June is a good moment to write a first draft. Many buyers slow down for summer holidays, so pipeline activity often dips, and you can use the quieter weeks to document what worked in the first half of the year before a new hire starts in the autumn.

Gather material from your real deals

The strongest playbooks are built from evidence. Before you write a word, collect what you already have.

List your last 10 to 20 deals. Include both wins and losses. Note the company type, the buyer's role, the deal size and how long it took.
Review call notes and recordings. If you record calls with permission, tools such as Gong, Fathom or Otter.ai can make transcripts easier to search. Check current features, pricing and privacy policies, and follow local consent rules for recording.
Pull your best emails. Find the first-touch emails, follow-ups and proposals that got replies. These become your templates.
Ask customers why they bought. A short call with three or four recent customers often reveals the real reason, which may not be the one you pitch.
Ask lost prospects why they did not. Even a few honest answers will improve your objection handling.

As you go, write down the exact phrases customers use to describe their problem. Their words will work better in your outreach than yours.

The core sections of a first playbook

Keep the structure simple. These six sections cover what a new seller needs in their first month.

1. Ideal customer profile and buyer roles

Describe the companies that get the most value from your product and buy most easily: industry, size, location, the tools they already use and the trigger events that make them look for a solution. Then list the people involved in a typical deal, such as the user, the budget holder and anyone who can block it, like IT or legal. Add a short "who we do not sell to" list. It saves hours of wasted calls.

2. The problem and your value story

In plain language, explain the problem you solve, what it costs the customer to leave it unsolved and how your product changes that. Include two or three short customer stories, with permission or anonymized, that a seller can tell in under a minute.

3. Sales stages with exit criteria

Define each stage of your process and, most importantly, what must be true before a deal moves to the next one. Exit criteria stop deals from looking healthier than they are.

4. Discovery questions

List the questions that help you understand the buyer's situation, pain, timeline, decision process and budget. Group them by topic so sellers can pick the ones that fit the conversation.

5. Objections and answers

Write down the objections you hear most and the answers that have worked. Be honest: if an objection is valid for some customers, say so and explain how to spot those cases.

6. Handover and onboarding

Describe what happens after a deal closes: who gets told, what information is passed on and what the customer can expect in the first weeks. A smooth handover protects the trust the seller built.

Common mistake

Writing the playbook about your product instead of your customer. Pages of feature descriptions do not help a seller run a good call. Spend most of your words on the buyer: their situation, their questions, their worries and how they decide.

Man presenting to colleagues seated around a table during a meeting in a bright office — Walk the team through the playbook together so everyone agrees on the stages and the language.

A sales stage template you can copy

This is the heart of the playbook. Copy the table into your document and adjust the stages to fit how your customers actually buy. The examples below are illustrative, not a standard you must follow.

Stage	Goal	Key activities	Exit criteria	Useful assets
1. Qualified lead	Confirm the company fits	Research the account, send first outreach, book a call	Matches ideal customer profile and a discovery call is booked	Outreach email templates
2. Discovery	Understand pain, timeline and decision process	Run discovery call, take notes, agree next step	Clear problem, a named budget holder and a target date	Discovery question list
3. Demo or trial	Show the product solving their problem	Tailored demo or guided trial with success goals	Buyer confirms the product meets their needs	Demo outline, trial checklist
4. Proposal	Agree scope and price	Send proposal, handle questions, involve legal or IT	Verbal yes from the budget holder	Proposal template, security answers
5. Closed	Sign and hand over	Contract signed, handover call booked	Signed contract and onboarding started	Handover form

If you send proposals and contracts through a tool such as PandaDoc or DocuSign, link the templates directly from the "Useful assets" column so sellers always use the latest version.

Writing discovery questions and objection answers

These two sections are where new sellers look most often, so make them easy to scan.

Discovery questions that work

Good discovery questions are open, specific and about the buyer. Here is a starter set you can adapt:

Situation: "Walk me through how you handle this today."
Pain: "What happens when that process breaks down? How often does it happen?"
Impact: "Who else feels the effect of this problem?"
Timeline: "Is there an event or date that makes solving this more urgent?"
Decision: "Besides you, who usually gets involved when you choose a new tool?"
Budget: "How do purchases like this normally get approved?"

Objection answers

For each common objection, write the objection, what usually sits behind it and a suggested response. For example:

"It is too expensive." Often means the value is not yet clear. Go back to the cost of the problem and ask what a good outcome would be worth to them.
"We are too busy to switch right now." Often about effort, not interest. Explain the setup steps and offer a realistic start date after their busy period.
"We already use another tool." Ask what they like about it and where it falls short. If it genuinely fits them better, say so and part on good terms.

Hypothetical example

Imagine Omar, founder of a small scheduling software startup. He wrote a 12-page playbook before his first sales hire, Grace, started. Grace used the discovery questions on her first calls and noticed that one question, about who else feels the problem, often uncovered a second buyer in the operations team. She suggested moving it earlier in the call and adding a short story about an operations manager. Omar updated the playbook, and within a few weeks both of them were running calls the same way and comparing notes using the same stage names.

Roll it out and keep it current

A playbook that sits in a folder untouched does nothing. Make it part of how the team works.

Store it in one place. Use a shared document or knowledge base such as Notion or Confluence, and link it from your CRM.
Walk through it together. Spend an hour going section by section with anyone who sells.
Use it in coaching. When you review deals, refer to the stage exit criteria and discovery questions.
Invite edits. Ask sellers to suggest changes whenever they find a better question, email or answer.
Review every quarter. Check win and loss reasons, update the ideal customer profile and retire anything that no longer works.

Pro tip

Add a short "changelog" at the top of the playbook with the date and a one-line summary of each update. It helps everyone notice what changed and shows the team that the document is alive.

A quick note on compliance: if your playbook includes outbound email, make sure your templates follow the rules where your prospects are. In the US, CAN-SPAM requires a clear unsubscribe option and a valid physical postal address in commercial emails, and in the UK and EU, PECR and GDPR consent rules apply. This is general information, not legal advice, so check with a qualified professional if you are unsure.

Your sales playbook checklist

List your last 10 to 20 deals, won and lost
Collect call notes, best emails and proposals
Talk to a few recent customers and lost prospects
Write your ideal customer profile and buyer roles
Describe the problem and two or three customer stories
Define sales stages with clear exit criteria
Write discovery questions and objection answers
Document the handover after a deal closes
Store the playbook in one shared place and walk the team through it
Book a quarterly review

Frequently asked questions

How long should a first sales playbook be?

Short enough that a new seller will actually read it. For most early-stage startups, 10 to 15 pages covers the essentials. You can always add detail later as patterns become clear.

Should the founder or the first salesperson write it?

The founder should write the first draft, because they hold most of the knowledge. The first salesperson should then help refine it in their first few months. A playbook that both of them own tends to get used.

Is a sales playbook the same as a sales script?

No. A script tells you exactly what to say. A playbook explains who you sell to, how deals progress and what to ask or answer at key moments, while leaving room for sellers to have natural conversations.

The bottom line

Your first sales playbook does not need to be long or polished. It needs to capture what you have learned from real deals: who your best customers are, how they buy, what to ask them and how to answer their doubts. Write it before your first sales hire, build it around clear stages and exit criteria, and keep it in one shared place.

Set aside a few hours this week to list your recent deals and draft the stage table. Every improvement your team adds from there makes the next deal a little easier to win.