It’s exciting because you’re finally getting traction. It’s also messy because you are the entire sales department. You are the SDR, AE, sales engineer, and sometimes customer success, all while trying to ship product and keep the company alive.
And then one day you realize something kind of uncomfortable.
You do have a process. It’s just trapped in your head. In your inbox. In a hundred little calls you don’t record. In a few Notion pages you never finished.
A sales playbook is basically the act of pulling that process out of you. Then turning it into something other people can actually use. Quickly.
This guide is about speed. Not a perfect playbook. Not a corporate enablement binder.
Just a real, usable playbook. Built fast. Good enough that a first rep can follow it and not embarrass you. Good enough that pipeline becomes visible. Good enough that deals stop being magical.
Let’s do it.
What a sales playbook actually is (and what it is not)
A sales playbook is not a PDF that lives in Google Drive and nobody reads.
It’s also not a 70 page manifesto on “our unique approach to revenue excellence.”
A useful playbook is simple. It answers:
- Who we sell to (and who we do not)
- What problems we solve (in the customer’s words)
- How we run a deal from first touch to close
- How we qualify (and disqualify) fast
- What we say and show at each stage
- How we price and negotiate without panic
- How we forecast without lying to ourselves
That’s it. Everything else is optional.
If you’re trying to get out of founder led sales and into a team driven engine, the playbook is the bridge.
The fastest way to build a playbook is to stop “writing” and start extracting
Most founders approach a playbook like a school assignment.
They open a blank doc. They try to outline “Sales Process.” They stall. They rewrite the same paragraph three times. Then a customer issue hits and the doc dies.
The faster approach is extraction.
You already have the raw material:
- Your last 10 closed won deals
- Your last 10 closed lost deals
- Your best demo recording
- Your best follow up email thread
- The discovery questions you always ask (even if you do it casually)
- The objections you handle on repeat
- The pricing conversation you dread but have gotten decent at
Your job is to grab those artifacts, label them, and organize them into a simple structure.
Writing comes after. Lightly.
The “fast playbook” structure (steal this)
Here’s the structure I recommend when speed matters and you’re building for your first 1 to 3 reps.
- ICP and Targeting
- Positioning and Messaging
- Sales Stages and Exit Criteria
- Discovery and Qualification
- Demo and Narrative
- Objections and Competitive
- Pricing, Packaging, and Negotiation
- Multi thread and Procurement
- CRM Rules and Pipeline Hygiene
- Sequences, Templates, and Talk Tracks
- Metrics and Reporting
- Onboarding and Coaching Plan
If you create even a “v1” for each section, you’re ahead of most startups.
Step 1: Define your Ideal Customer Profile (ICP) in one page, not ten
This is where founders often overcomplicate things. They create an ICP document as if they're writing a PhD thesis.
Don't do that.
Instead, create a one-page document that includes:
ICP Snapshot
- Industry:
- Company size (employees or revenue):
- Geography:
- Tech environment (if relevant):
- Trigger events (what causes them to start looking):
“Must have” pains
Identify three key pains. Max. Write them in the voice of the customer.
Example:
- “We lose deals because handoffs are chaos.”
- “We can’t see what’s in pipeline, it’s all vibes.”
- “We need enterprise reporting but we’re running on spreadsheets.”
Disqualifiers
This is crucial. It saves time.
- Too small to feel the pain
- No budget owner
- Buying committee is missing
- Problem is “nice to have”
- They want custom dev work disguised as procurement
If you can’t define disqualifiers, your reps will waste months being polite.
Step 2: Turn your best deals into a repeatable “why we win” story
Look at your last 5 closed-won deals and answer these questions in bullet points:
- What did they believe before they talked to you?
- What changed in their thinking?
- What internal pressure made the project real?
- Why did they pick you (not the feature list, the real reason)?
- What almost killed the deal?
Now do the same for 5 closed-lost deals:
- Where did the deal stall?
- What objection did you not handle well?
- What competitor angle landed?
- What stakeholder did you fail to win?
This process becomes your deal narrative, which also serves as a foundation for your messaging, discovery, demo, and objection handling.
For a more comprehensive understanding of defining an Ideal Customer Profile, consider these insights.
Step 3: Map your sales stages with exit criteria, not vibes
Founders often have stages like:
- Discovery
- Demo
- Proposal
- Negotiation
- Closed
That’s not a process. That’s a calendar.
Stages should have clear exit criteria. Meaning, you don’t move the deal forward until specific things are true.
A simple version might look like this:
Stage 1: Qualified Discovery
Exit criteria:
- Confirmed pain with impact
- Identified economic buyer (or likely owner)
- Confirmed timeline driver
- Agreed next meeting with required stakeholders
Stage 2: Solution Fit (Demo)
Exit criteria:
- Demo tied to their workflow, not your UI tour
- Success criteria documented
- Buying process discussed (yes, already)
Stage 3: Evaluation
Exit criteria:
- Mutual plan created (dates + people)
- Security/procurement started (if enterprise)
- Champion identified and enabled
Stage 4: Commit
Exit criteria:
- Commercial terms agreed
- Legal route understood
- Close date tied to real event
If you use a methodology like MEDDPICC, Challenger, SPIN, or Sandler, this is where it plugs in naturally. Not as theory. As fields and checkboxes and habits.
David Consulting Services’ work is basically built around this kind of operationalizing. Taking the founder’s natural motion and turning it into stages, criteria, CRM rules, and coaching. The boring stuff that makes deals repeatable.
Step 4: Write your discovery like a script, then loosen it later
Discovery is where early reps struggle the most. They either interrogate the prospect or they chat for 30 minutes and learn nothing. This phase is crucial, as it's essentially a discovery call that sets the foundation for the sales process.
So in a fast playbook, you give them a script. Not to sound robotic. Just to keep the call on rails.
Here’s a founder friendly discovery flow:
Opening (2 minutes)
- “What prompted you to take this meeting now?”
- “If this goes well, what do you want to walk away with?”
Problem exploration (10 to 15 minutes)
- “Walk me through how you do this today.”
- “Where does it break?”
- “How are you measuring it right now?”
- “What happens if nothing changes this quarter?”
Impact and urgency (5 minutes)
- “What’s the cost of this staying the same?”
- “Who feels the pain the most?”
- “What internal deadline is driving this?”
Stakeholders and process (5 minutes)
- “Who else will weigh in?”
- “Have you bought something similar before?”
- “What does procurement or security usually look like?”
Close (2 minutes)
- Recap pains and desired outcomes
- Confirm next step with date and attendees
You can make this better later. Today you just need something usable.
Step 5: Build a demo framework that forces relevance
A demo should not be a product tour.
A demo is a story where the prospect recognizes themselves and thinks, okay. They get it.
Your playbook should include:
- A demo agenda (always)
- A “demo setup” checklist
- A narrative arc
- A few demo paths by segment (light, medium, enterprise)
The simplest narrative arc
- The world today (their messy reality)
- The cost of staying there
- The new way (your approach)
- Proof (case study, numbers, references)
- Next steps (mutual plan)
Also, include a section called “things we do not demo.”
If you don’t, reps will show every feature to look smart. Then the buyer gets confused. Then you lose.
Step 6: Create an objection bank from your actual calls
You don’t need to brainstorm objections. You already know them.
Make a table with:
- Objection
- What it really means
- The response
- A follow up question
- Proof or asset to send
Example:
Objection: “We’re already using X”
Meaning: Switching cost fear, status quo
Response: “Makes sense. Usually teams using X come to us when they hit [specific limit]. Are you seeing that?”
Follow up: “What happens if X stays your system for the next 12 months?”
Proof: Competitive one pager, case study
Keep it tight. Real language. No sales poetry.
Step 7: Pricing and negotiation rules (so reps stop improvising)
If you want speed, write down the rules.
- Standard pricing and packaging
- Discount bands allowed (by who)
- Give gets (if discount, what do we ask for)
- Red lines (terms we do not accept)
- When to bring the founder in
This is where founders often keep control because it feels risky.
But if you do not document it, every deal becomes a fire drill. And hiring reps will not fix that. It will multiply it.
Step 8: CRM rules that make forecasting possible
Your playbook should include “how we use the CRM.”
This is not optional. It’s the difference between pipeline you can manage and pipeline that lies to you.
Minimum viable CRM rules:
- What fields are required before moving stages
- What counts as a real next step
- How to log stakeholders
- Where MEDDPICC or qualification notes live
- Naming conventions for opportunities
- Activity expectations (calls, emails, meetings) by role
If you are moving from founder chaos into a repeatable engine, this is exactly the kind of stuff David Consulting Services builds into their 90 Day Method. Not just advice, but actual implementation. Pipeline stages, sequences, reporting. Then training reps against it.
Step 9: Sequences and templates, but keep them founder simple
You do not need 47 templates.
You need the ones that happen every day:
- First outbound email
- Follow up after no response
- Post discovery recap email
- Post demo recap email
- Mutual plan email
- Procurement nudge
- Closed lost breakup email
And you need call talk tracks for:
- Discovery
- Demo
- Pricing
- Renewal or expansion (if relevant)
Write these in your voice. Slightly imperfect. Human.
If your emails are too polished, they will feel like marketing and get ignored.
The 10 hour playbook sprint (a real schedule)
If you want to build this fast, here’s a sprint you can do in a week. Or even two days if you clear the calendar.
Hour 1: Gather artifacts
- 5 closed won calls, 5 closed lost notes
- Best demo recording
- Top email threads
- Current deck, proposal, pricing doc
Hour 2: ICP and disqualifiers
One page. Done.
Hours 3 to 4: Stages and exit criteria
Define stages. Add required fields. Map to your CRM. For a more comprehensive understanding of how to define deal stages and align them with your sales methodology, check out this ultimate guide.
Hours 5 to 6: Discovery script + qualification
Write the call flow. Add a MEDDPICC checklist if you use it.
Hours 7 to 8: Demo narrative + agenda + demo paths
Document the story. What to show, what not to show.
Hour 9: Objection bank + competitive notes
Start with top 10 objections. Add proof assets.
Hour 10: Templates and sequences
Just the essentials.
That’s your v1.
And v1 is enough to hire and onboard your first reps without everyone drowning.
Common mistakes that slow everything down
Trying to make it “perfect” before anyone uses it
Your reps will improve it through reality. The playbook is a living thing. Don’t treat it like a product launch.
Writing theory instead of instructions
“Be consultative” is not helpful.
“Ask these questions, listen for these signals, don’t advance the stage until these boxes are checked.” That helps.
Not documenting disqualification
Founders like to keep hope alive. Reps will do the same. Then your pipeline becomes fantasy.
Separating the playbook from the CRM
If the playbook lives in a doc and the CRM lives somewhere else, behavior won’t change.
What “done” looks like
A fast playbook is done when:
- A new rep can run discovery without you
- Demo is consistent and tied to customer pain
- Stages have exit criteria and the CRM reflects it
- You can look at pipeline and actually trust it
- Objections are handled consistently
- Pricing rules prevent chaos
- You can coach from artifacts, not from memory
That’s the goal. Not a big document. A working system.
If you want help, here’s the shortcut
If you’re in that awkward middle stage where deals are coming in, but it’s still all founder powered. You can keep grinding, sure.
Or you can extract what’s working and turn it into something the team can run.
That’s basically what David Consulting Services does inside their structured 90 Day Method. Pulling the founder’s approach into a documented playbook, cleaning up CRM and pipeline, supporting the first hires, and coaching reps through early deals so it sticks. If you want to move fast without reinventing everything, you can check them out here: https://www.davidconsulting.services and book a consultation.
Quick recap (so you can start today)
- Build v1 fast. Extract, don’t author from scratch.
- Start with ICP, stages, discovery, demo, objections, pricing, CRM rules.
- Tie the playbook to daily behavior. Especially in the CRM.
- Improve it weekly based on real calls and real deals.
You don’t need more motivation. You need a playbook that makes the next hire safer.
And you can have that in a week.
FAQs (Frequently Asked Questions)
What is founder led sales and why is it considered a weird season?
Founder led sales is the early stage of a startup where the founder handles all sales roles, including SDR, AE, sales engineer, and sometimes customer success, while also managing product development and company survival. It's considered a weird season because it's exciting due to gaining traction but messy as the founder juggles multiple responsibilities without a formal sales process.
What exactly is a sales playbook and what should it include?
A sales playbook is a simple, actionable document that captures your sales process in a way others can follow quickly. It should include who you sell to (and who you don’t), the problems you solve in the customer's words, how to run deals from first touch to close, qualification criteria, messaging for each stage, pricing and negotiation strategies, and honest forecasting methods. Everything beyond this core is optional.
How can founders quickly build an effective sales playbook?
Instead of starting from scratch by writing out processes, founders should extract existing materials like recent closed won and lost deals, best demo recordings, follow-up email threads, discovery questions, common objections handled, and pricing conversations. Organizing and labeling these artifacts into a simple structure allows for faster creation of a usable playbook with minimal writing afterward.
What structure should I follow to create a fast and functional sales playbook?
A recommended fast playbook structure includes: 1) ICP and Targeting; 2) Positioning and Messaging; 3) Sales Stages and Exit Criteria; 4) Discovery and Qualification; 5) Demo and Narrative; 6) Objections and Competitive; 7) Pricing, Packaging, and Negotiation; 8) Multi-threading and Procurement; 9) CRM Rules and Pipeline Hygiene; 10) Sequences, Templates, and Talk Tracks; 11) Metrics and Reporting; 12) Onboarding and Coaching Plan. Creating even a version one for each section puts you ahead of most startups.
How do I define my Ideal Customer Profile (ICP) effectively without overcomplicating it?
Keep your ICP definition to one concise page including: Industry, Company size (employees or revenue), Geography, Tech environment if relevant, Trigger events that cause prospects to look for solutions. Also identify three 'must have' pains in the customer's voice, plus clear disqualifiers such as too small companies or lacking budget owners. This approach saves time by focusing reps on qualified prospects.
How can analyzing past deals improve my sales messaging and process?
Review your last five closed-won deals by answering questions about customer beliefs before engaging you, shifts in their thinking, internal pressures driving decisions, reasons they chose you beyond features, and deal risks overcome. Similarly analyze five closed-lost deals to identify stalling points, unhandled objections, competitor advantages gained, or stakeholders missed. This 'deal narrative' forms the foundation for refining messaging, discovery questions, demos, objection handling, and overall sales strategy.
