Writing the First Sales Playbook a Non-Salesperson Founder Can Hand Off

Most founder-built sales playbooks fail for one of two reasons: they are too short (covering what to sell but not how to sell) or they are too long (covering everything the founder knows about the market but not the specific decisions a rep needs to make in each call). The version that works is neither comprehensive nor minimal — it is precise. It tells a rep, in the moment of a live discovery call, what question to ask next. It tells them, when a prospect says "we're already using a competitor," exactly how to respond and what to listen for in the answer. The knowledge a founder has internalized over dozens of calls does not transfer by proximity. It transfers by documentation — and documentation has to be specific enough to use without the founder in the room. Bessemer Venture Partners research on early-stage AE ramp time identifies documented sales playbooks as the single most correlated factor with sub-5-month ramp — more than experience, compensation, or training programs.

Section 1: ICP Definition With Behavioral Attributes

Most ICP sections in founder-built playbooks describe who your customers are. The useful version describes how they behave before they buy. The distinction determines whether a rep can use the ICP definition in real time or only retrospectively.

Firmographic baseline (required):

• Company size range (employees or ARR)
• Industry or verticals where you have the strongest use case
• Geography (if relevant)
• Tech stack indicators (if your product integrates with or replaces specific tools)

Behavioral attributes (critical):

• What problem does the champion say they are trying to solve in the first call? (List 3–4 problem statements that signal ICP fit)
• What do they say when they are NOT a fit? (List 3–4 problem statements that sound plausible but signal ICP miss)
• What do they ask for in the first demo that indicates real buying intent? (e.g., "Can you show me how the permissions work?" signals a team use case; "What does the pricing look like for 50 seats?" signals intent)
• What is the decision process at a typical ICP company? (Who is the champion? Who is the economic buyer? Who can block the deal?)

Negative ICP:

Include at least 3–5 profiles of accounts that look like a fit on paper but almost always churn or never close. For most SaaS companies these are: companies that are evaluating for a use case the product does not serve well, companies that want heavy customization, and companies that are too early (no operational infrastructure to benefit from the product). List the specific signals that identify each of these anti-patterns. See /blog/founder-led-sales-transition for how the ICP definition connects to the handoff process.

Section 2: Discovery Call Framework

The discovery call framework is the most-used section of the playbook. It should be written as a conversation guide, not a list of questions — with enough context that a rep knows why each question is asked, not just what to ask.

Pre-call preparation (5 minutes):

• What do I know about this company from their website and LinkedIn?
• Have they used competitors? (Check: do they mention a competitor in their job posts or tech stack tools?)
• What is the most likely use case given their industry?
• What are the 2 most likely objections based on their profile?

Opening (2 minutes):

Script: "Thanks for making the time. I looked at [company name] before the call — [1 sentence on what you found]. I'd like to spend the first 15 minutes understanding your current situation and what you're hoping to solve, and then we can figure out if there's a fit and whether it makes sense to go deeper. Does that agenda work?"

Note: The framing "whether it makes sense to go deeper" is deliberate — it signals that you are evaluating them as much as they are evaluating you, which sets a peer dynamic rather than a supplicant dynamic.

Situation questions (5 minutes):

Problem questions (5 minutes):

Discovery checkpoint (1 minute):

Before moving to the demo, confirm fit: "Based on what you've described, it sounds like [restate their problem in 1 sentence]. Is that right?" A "yes" confirms you understood. A correction gives you a better problem statement. A blank look signals a discovery failure — probe before proceeding.

Section 3: The Objection Map

The objection map is the highest-ROI section of the playbook for a first rep. Format each objection with: the exact language prospects use, the context (who says it, at what stage), the response, and the follow-up question that reveals whether the objection is real or a delay tactic.

"We already have a solution for this."

Context: Raised in discovery, usually in the first 5 minutes. Often a defense mechanism, not a factual statement.

Response: "That makes sense — most companies have something in place. What I'm usually curious about is: is what you have now good enough, or is there a gap between what it does and what you actually need?"

Follow-up: Listen for the gap. If they describe a gap, you are in the deal. If they say "it works well," ask: "What would have to be true for you to revisit this in the future?" Their answer tells you when (and whether) to follow up.

"We don't have budget right now."

Context: Raised after demo, or as a way to end the call politely. Most common at companies with a broken budget cycle or without a defined pain that has an owner.

Response: "Understood. Can I ask — is this more about timing (budget opens in Q3) or about priority (this isn't something the business is committing resources to right now)?"

The distinction is important: timing is a pipeline issue; priority is a qualification issue. If it is timing, set a specific follow-up date. If it is priority, ask what would have to change for this to become a priority — and determine if your product can be part of that conversation.

"We need to think about it."

Context: End of demo or proposal stage. Almost always means something specific was not resolved in the conversation.

Response: "That makes sense. Can I ask — what's the main thing you'd be thinking through? I want to make sure I've given you everything you need to make a good decision."

The goal is to surface the unspoken objection. Common underlying issues: economic buyer not on the call, security concern not addressed, competitive option still being evaluated.

"Can you do a pilot/proof of concept first?"

Context: Mid-stage, usually from a technical champion who needs to reduce risk before presenting to leadership.

Response: Structured pilots (defined scope, defined success criteria, defined decision date) are acceptable. Open-ended pilots are not. Response: "Absolutely — can we talk through what success looks like in a pilot? I want to make sure we set it up so you have clear results to present to your team."

Follow-up: Send a written pilot scope document (scope, success criteria, timeline, next step after pilot) before the pilot starts. An unsigned pilot document is an unsigned deal.

Section 4: Demo Script

The demo script should not be a full product walkthrough. It should be a modular guide with a core flow and optional segments by ICP. The core flow covers the 3–4 features that address the universal pain point; optional segments cover use-case-specific features.

Core demo structure:

1. Context-setting (2 minutes): "Based on what you shared in discovery about [specific problem], I'm going to show you how [product] addresses [specific problem], starting with [feature]. I won't walk through everything — I want to focus on what matters for your situation."

2. Core value demonstration (8 minutes): Demo the 3 features that directly address the problem stated in discovery. For each feature: show it briefly → explain what it does in the prospect's language → pause and ask "does this match how you'd want to handle [their specific situation]?"

3. Customization segment (5 minutes): For ICP segments with distinct use cases, pivot to the segment-specific feature set. Trigger: if the prospect has mentioned a specific workflow or integration, go there.

4. Close for next step (5 minutes): "Based on what we've covered — does this address the core thing you're trying to solve?" If yes: "What would be the logical next step for your team?" If uncertain: "What would you need to see to feel confident that this is the right solution?"

Section 5: Deal Stage Definitions

Without deal stage definitions, pipeline is fiction. Each stage must have entry criteria (what must be true for a deal to enter this stage) and exit criteria (what next step must be completed before advancing).

See also /blog/first-sales-rep-ramp-plan-90-days for how stage definitions connect to the ramp plan.

Section 6: Mutual Action Plan Template

The mutual action plan (MAP) is the document that prevents deals from stalling in late stage. It is a co-created timeline that lists every step required to close the deal, with owner and due date for each step. The MAP is effective because it creates shared accountability — both the prospect and the seller have signed off on the sequence.

Minimum MAP content:

• Deal scope (what is being purchased, at what price, for what term)
• Key decision makers and their roles in the approval process
• Technical requirements (security review, IT approval, integration testing)
• Legal and procurement steps (contract review, redlining, signature authority)
• Timeline with specific dates and owners for each step
• Agreed decision date

Introduce the MAP after the proposal is received positively: "To make sure this moves forward on your timeline, I'd like to put together a mutual action plan that maps out each step between now and [target close date]. Can we spend 10 minutes on that now?"

For the full MAP framework including when to introduce it and how to handle resistance, see /blog/mutual-action-plan-mid-market-deals.

Conclusion

The playbook you write before your first rep starts is not the playbook you will have in six months. Every deal, every objection, every discovery call your rep completes in their first 90 days is an opportunity to refine the document — to add the objection you had not anticipated, to update the ICP definition based on what the market is actually responding to, to improve the demo script based on what questions prospects ask. The value of the playbook is not in the first version. It is in the organization it creates around knowledge that would otherwise stay in the founder's head, and in the feedback loop that improves it as the sales motion matures. Write the first version, hand it to the rep, and commit to reviewing and updating it monthly for the first quarter. The discipline of maintaining it is the actual investment; the writing is just the start. For the hiring decision that precedes the playbook, see /blog/first-saas-hire-playbook.

Frequently Asked Questions

What should a founder-built sales playbook include?

The minimum viable sales playbook includes six sections: ICP definition with behavioral attributes, discovery call framework, objection map, demo script, deal stage definitions, and a mutual action plan template.

How long should a sales playbook be?

The target length is 15–25 pages. Shorter than 15 pages is usually too thin; longer than 25 pages is typically not read past page 10. Prioritize scannability with section headers, bullet lists, and call scripts formatted as dialogue.

Should founders write the playbook themselves or hire someone to do it?

Founders should write the first draft themselves. The playbook captures the founder's implicit knowledge — questions that reveal ICP fit, objections that signal a dead deal — which a hired writer cannot extract without the founder doing the intellectual work anyway.

What is the most important section of the sales playbook?

The objection map. It is where most founders have never written down what they actually do, and where a first rep is most likely to default to generic sales training language rather than the context-specific response that works for your product and buyer.

When should the playbook be updated?

When a new objection is encountered in at least 3 deals, when a new ICP segment is validated, when pricing or positioning changes, and quarterly regardless to review whether stage definitions still match current data.