Most SaaS founders make the same mistake before their first sales hire: they try to shortcut the learning. They read about sales, they listen to podcasts about outbound, they buy a CRM. What they don't do is close 20 deals themselves and write down exactly how they did it.
That document — the one that explains how a deal moves from first touch to closed-won in your specific product, for your specific buyer — is the SaaS sales playbook. You can't outsource writing it. You can only discover it.
What a Sales Playbook Actually Is
Not a slide deck. Not a CRM configuration. Not a library of templates.
A sales playbook is the operating manual for how your company sells. It covers who you're selling to (ICP definition — role, company size, industry, trigger events), how you find them, what you say to open the conversation, how the deal moves from stage to stage, what objections come up and how you respond, and what closes deals.
This isn't written at a whiteboard. It's discovered through deals — typically 20 to 50 of them — and written down so someone else can repeat the pattern without you in the room.
The Founder's Unfair Advantage in Sales Discovery
Founders who come from the industry they're selling into — operator founders who spent years in the domain before building for it — have a sales discovery advantage that generalist founders don't.
When an operator founder sells to their former peers, the conversation is different from the first minute. You're not asking a buyer to explain their world to you — you already know it. The subtext of every exchange is peer to peer, not vendor to buyer. That changes the entire sales motion.
What this means for the playbook: the ICP definition is more precise, the trigger events are more specific (because you lived them), and the objection responses are more accurate — because you know what's behind the objection, not just what people say on a sales call.
Write this down. A sales hire who doesn't have your domain context needs it to replicate what you did.
The Four Core Playbook Sections
Outreach. Your first message, your follow-up sequence, the LinkedIn message that gets a response versus the one that gets ignored. For vertical SaaS, this means hyper-targeted personalization — referencing the specific role, company size, or pain point — rather than high-volume spray approaches.
Discovery call. The questions you ask to diagnose the problem, confirm budget authority, and understand the buying process. The goal isn't to pitch — it's to understand if there's a real problem, whether it's urgent, and whether the person you're talking to can make a decision.
Demo. Not a feature tour. A demonstration of how the product solves the specific problem the buyer described on the discovery call. Vertical SaaS demos work best when they show the exact workflow the buyer already knows, not a generic overview.
Close. What you say to advance a deal that's stalled. How you handle price negotiation. When you ask for the business. Most founders don't ask — they wait for the buyer to self-select, then wonder why the deal took six months.
When the Playbook Is Ready to Hand Off
You'll know the playbook is good enough to hand off when you can predict a deal's outcome at each stage. If you know by the end of a discovery call whether the deal will close, and approximately when, the pattern has been discovered.
That's when the first sales hire becomes a good idea — not before.
The go-to-market motion for vertical SaaS especially requires the playbook before scaling, because the ICP is narrow enough that a wrong message in the market quickly exhausts the available prospects. You have 500 potential customers in the country, not 50,000.
If you're building the sales motion for a vertical SaaS product and want a second set of eyes on it, Alder is worth a conversation. We've watched these playbooks get built and know what separates the ones that scale from the ones that stall.