A sales playbook. The structure that turns one good rep's habits into everyone's.

What the template covers. Six sections, one page each.

A Harvard Business Review analysis, "Companies with a Formal Sales Process Generate More Revenue" (2015), found an 18 per cent gap in revenue growth between businesses with a defined, formal sales process and those without one. A sales playbook is what makes that process real and repeatable, rather than something that lives in one person's head and leaves with them.

Founder-led teams tend to skip the playbook precisely because the founder already sells well without one. The gap only becomes visible once someone else has to sell, a first sales hire, a second, a team, and the results are inconsistent in a way nobody can quite explain. The playbook is what closes that gap, by writing down the judgement calls a good rep makes instinctively so a newer one can make them too.

A playbook that earns its place, rather than sitting unread in a shared drive, covers six things:

• Ideal customer profile. Who you sell to, and the specific signals that tell a rep a prospect is actually worth chasing.
• Messaging by audience. How the value proposition changes depending on who is in the room, a founder versus an operations lead versus a finance sign-off.
• Objection handling. The three or four objections that come up in almost every deal, with a real answer for each, not a deflection.
• Deal stages and exit criteria. What has to be true for a deal to genuinely move from one stage to the next.
• Proof points by stage. The case study, reference customer or data point that lands best at each point in the conversation.
• A review cadence. Who owns keeping it current, and how often it gets checked against what is actually working.

How to use it. Build it from your best rep's habits, not a template off the internet.

Start with the ideal customer profile. Look at your last ten closed-won deals and your last ten closed-lost deals. The pattern in what separates them, company size, urgency, existing tooling, is your real ICP, not the one on your website's homepage. Write down the two or three buying signals that showed up repeatedly in the won deals, since those are what a rep should actually be listening for on a first call.

Write messaging for the audience, not the product. The same feature matters for different reasons to different buyers. A founder cares about speed to value; a finance lead cares about total cost and risk. One generic pitch deck asked to do both jobs usually does neither well. Give each audience its own half-page rather than trying to fit every angle into a single script that satisfies no one fully.

Draft objection handling from real calls, not guesswork. Pull the objections that actually came up in your last quarter of calls, not the ones you assume prospects will raise. The gap between the two is often larger than founders expect. If a call recording tool exists, this is the fastest way to build the section: listen to the last twenty calls and note every objection, then keep only the ones that recur.

Set exit criteria that are genuinely testable. "Prospect is interested" is not exit criteria. "Prospect has confirmed budget and a decision date" is. Clear, criteria-based stages are worth getting right once, and our guide to defining pipeline stages covers how to write criteria a whole team will actually use consistently rather than interpret differently deal by deal.

Attach proof to the stage where it lands, not a single case studies page. A reference customer similar in size and sector matters most just before a decision, not on a first call. Map two or three proof points to the stages where they actually change a buyer's mind, and retire proof points that have stopped landing rather than leaving a slide deck bloated with logos nobody references any more.

Assign an owner and a cadence. Someone needs to be responsible for updating the playbook every quarter, or whenever pricing, product or a competitor's pitch changes. A playbook nobody owns goes stale within two quarters and nobody notices until a rep loses a deal on an argument that stopped working months ago.

A worked example. A six-person team launching a new product line.

A six-person B2B sales team is about to launch a second product line alongside its core offer. Before the launch, the founder pulls the last ten closed-won deals for the core product and finds the pattern: mid-market operations leads who had already tried and abandoned a spreadsheet-based workaround. That becomes the ICP for the new line too, tested rather than assumed.

The founder and the two most experienced reps then draft messaging split by audience: one page for the operations lead who will use the product daily, one for the finance sign-off who needs the cost case. Objection handling gets built from the four questions that came up in every core-product demo over the past quarter, since the new line will face nearly identical scrutiny.

Two weeks after launch, the newest rep on the team, six months into the role, closes a deal using the same messaging and objection answers the top performer uses, at a comparable pace. That is what the playbook is actually for: not a document to file away, but the reason a newer rep's results start looking like a proven rep's, faster than they would by working it out alone. Where a business is scaling a whole go-to-market motion around a launch like this, it sits inside the wider go-to-market strategy work we do with founder-led teams, and it connects directly to how a product actually reaches the buyer once the playbook is proven on a small scale.

By the end of the quarter, the founder reviews the playbook against what actually happened: one objection answer needed rewriting after a competitor changed its pricing, and a proof point that worked well on paper never came up naturally in a real call, so it moved further down the document. That quarterly discipline, checking the playbook against reality rather than leaving it untouched since launch day, is the difference between a document that keeps earning its place and one that quietly stops being used.

Common mistakes. Where playbooks go stale.

Copying a template instead of building from real deals. A generic playbook downloaded from the internet reads well and matches nothing about how your specific buyers actually behave. Every section should trace back to a real deal, won or lost, not a best-practice guess.

Writing it once and never testing it on anyone else. A playbook drafted entirely from the founder's own instinct can fail the moment a different personality tries to use it. Hand a draft to whoever is newest on the team and watch where they get stuck before calling it finished.

Treating it as a one-off project rather than a living document. Without an owner and a quarterly review built in from the start, a playbook is finished the day it is written and irrelevant within a year.

Making it too long to actually use on a call. A forty-page playbook gets read once and then ignored. A rep needs to find the answer to an objection in seconds while a prospect is still on the line, which means short, scannable sections beat exhaustive ones every time.