The founder led sales playbook, written while you still sell

Founder led sales works until the day it has to be handed to somebody else. The handover fails on things that were never written down, and almost all of them could have been.

You have closed the first customers yourself. You know which questions kill a deal, which type of prospect wastes six weeks, and what to say when somebody asks why you cost more than the alternative. None of that is written anywhere, because you have never needed to write it down for yourself.

Then you hire, and the new person runs the same conversations badly, and the obvious explanation is that they are not as good as you. Sometimes true. More often they are missing a set of judgements you make without noticing you are making them.

Write it while you are still selling, not after

The instinct is to write the playbook when the hire is imminent. By then you are compressing months of pattern recognition into a week under time pressure, and what you produce is a process diagram rather than a record of what you know.

The version worth having is written incrementally while you are still in the deals, because the details you need are the ones that feel too specific to matter. The exact phrase a buyer used when they were about to go quiet. The one question that reliably tells you whether a budget exists. Those are invisible in hindsight and obvious in the moment.

The five things that have to be in it

1. Who you have actually sold to, with evidence. Not a persona. The real list of closed customers with their size, sector, what triggered the purchase and how long it took. A new seller can pattern match against a list of twelve real accounts. They cannot pattern match against an aspirational description of an ideal customer.

2. The disqualifiers. This is the highest value page and the one most often missing. Which prospects look promising and are not. The ones with no budget cycle until next year, the ones who need a feature you will not build, the ones where your champion has no authority. You already refuse these instinctively. A new hire will pursue every one of them for six weeks each.

3. The questions, in order. Not a script. The sequence of things you need to know before you can price the deal, and the order you find them out in, because asking about budget too early costs you the meeting and asking too late costs you the quarter.

4. The objections, with your actual answers. Write the wording you use, including the parts that concede something. A new seller given a list of objections and no answers will invent answers, and the invented ones tend to be more defensive than yours.

5. What each stage means. A stage definition is worthless unless it names an observable event. Not "prospect is interested" but "prospect has named the person who signs". Vague stages are why forecasts are wrong, and the pipeline construction side of this is in how to build a B2B sales pipeline you can actually forecast.

Why this matters more than it used to

Deals now involve more people. The Optifai pipeline study of 939 B2B software companies, covering stage level CRM data from the second quarter of 2025 to the first quarter of 2026, puts the average buying group at 6.8 stakeholders against 5.4 previously, with a median cycle of 84 days.

A founder navigates a six or seven person buying group by reading the room, which is not a transferable skill on its own. What is transferable is the map: who these people usually are, which one blocks, which one you have to meet before the proposal goes in. That map is the thing worth writing, and we set out how those rooms are normally composed in the B2B buying committee.

Write it so it gets read

A playbook that nobody opens after week one has failed regardless of how complete it is. Nielsen Norman Group's research on how people read found that 79 percent of test users scanned rather than read, and that rewriting the same information concisely improved measured usability by 58 percent, with concise, scannable and objective wording together producing a 124 percent improvement.

That research is about web pages, and a playbook is not a web page. The mechanism carries over anyway, because the reader is doing the same thing: looking for the one paragraph that answers the question in front of them, between two meetings. Short sections, a real heading on each, the conclusion first. If your playbook needs to be read start to finish to be useful, it will be read once.

What to leave out

Anything that is really a description of your personality. Founders write down that they are direct, or curious, or that they build trust quickly. This is not instruction, and a new hire who tries to copy it produces an impression of you rather than a version of themselves that sells.

Also leave out the parts of the process that only worked because you were the founder. You could offer a discount in the room, promise a roadmap item, or get a reply from a chief executive because of who was asking. A seller who follows those steps without your authority is running a play that cannot work for them, and will conclude the playbook is wrong.

Write those down separately, as the list of things that need you. It is a short list and it is the real reason founder led sales does not disappear on the day of the first hire.

The test

The playbook is finished when somebody capable, who was not in any of your deals, can read it and tell you which of three inbound enquiries is worth a meeting and why. Not close a deal. Just sort three enquiries the way you would have sorted them.

If they cannot, the gap is usually in the disqualifiers, because that is the section founders write last and thinnest. Run that test before you hire and you learn what is missing at no cost. Run it after, and you learn it over the three to six months the new hire spends ramping, which is the expensive version.

Timing the hire itself is a separate decision with its own signals, set out in when to hire your first salesperson, and the first quarter after they start has its own shape in the first 90 days of business development.

Honest limits

If you have closed fewer than about ten deals, there is no playbook to write yet, and writing one anyway is how a founder converts a small sample into a rule. At that stage the honest document is a list of what you have observed and what you are still unsure about.

A playbook also goes stale, faster than most founders expect. If your pricing, your product or your target segment changes, the disqualifier list is wrong within a quarter and a wrong disqualifier list is worse than none, because it is followed confidently. Put a date on it and review it when something material changes rather than on a calendar.

And this does not make you replaceable in the deals that need you. It makes the other deals possible without you, which is a smaller claim than the word playbook usually implies and the only one that survives contact with a real handover.