Sales playbook examples: 7 plays with sample excerpts

Quick answer

A sales playbook is a set of written plays, one for each situation your team meets again and again. The most useful examples for a B2B startup are an outbound prospecting play, a discovery play, a demo play, an objection handling play, a competitive play, an expansion play and, if you are hiring your first rep, a founder-to-first-hire handoff play. Each play has a trigger, a goal, steps, one concrete example and an exit rule. Below are all seven with sample excerpts, and a sales playbook template to put them in.

What does a good sales play look like?

Before the examples, the shape. Every play in a working playbook answers the same five questions, which keeps them short and easy to scan.

If you are building the playbook from scratch, read how to build a sales playbook for the sections to include. This article focuses on what the plays inside it look like.

The excerpts below are illustrative examples written for a fictional B2B software company, not copied from any real company's playbook. Swap in your own ICP, language and numbers.

1. Outbound prospecting play

Trigger: a target account shows a buying signal, such as hiring for a role your product supports, a funding round or a new leader in the buying team.

Goal: a booked first meeting with the person who owns the problem.

Sample excerpt:

Who: Heads of Revenue Operations at Series A to C SaaS companies, 50 to 300 employees, using HubSpot.

Signal: a RevOps or sales ops job posting in the last 30 days.

Sequence: connection request on day 1, email on day 2, LinkedIn message on day 5 if connected, follow-up email on day 7, final email on day 12.

First email: "Saw you are hiring a RevOps analyst. Teams at that stage often find the CRM was set up for five reps, not twenty. Worth comparing notes on what to fix before the new hire starts?"

Exit rule: reply with interest moves to a meeting. No reply after the final touch moves to a 90-day nurture list.

For more sequence shapes, see outbound sequence examples.

2. Discovery play

Trigger: a first meeting is booked.

Goal: confirm there is a real problem, an owner and a reason to act now, or disqualify quickly.

Sample excerpt:

Open (2 minutes): confirm time, agree on the agenda, ask what made them take the call.

Current state: "Walk me through how a new lead gets from your website to a rep today."

Pain: "Where does that break? What does it cost you when it does?"

Priority: "Why look at this now rather than next quarter?"

Process: "Who else would be involved in a decision like this?"

Exit rule: if there is no named pain and no reason to act this quarter, mark the deal closed-lost with the reason logged. Otherwise book the demo with the right people before the call ends.

The discovery call question bank has a fuller set of questions grouped by stage.

3. Demo play

Trigger: discovery confirmed a qualified problem.

Goal: show only what solves the problems you heard, and agree on a next step.

Sample excerpt:

Prep: list the top three pains from discovery in the buyer's words. Build the demo around those three, in that order. Nothing else.

Open: "Last time you said routing takes two days and leads go cold. I will start there, then show reporting, then onboarding. Anything changed since we spoke?"

During: after each section, ask "How would this work for your team?" rather than "Any questions?"

Close: "Based on what you saw, what would need to be true for this to move forward?" Book the next meeting on the call.

Exit rule: a dated next step with a named attendee, or the deal does not advance a stage.

4. Objection handling play

Trigger: a prospect raises a concern at any stage.

Goal: understand the real concern and either resolve it or learn the deal is not a fit.

Sample excerpt:

Method: acknowledge, ask a question, answer briefly, check.

"We do not have budget right now." Acknowledge: "That makes sense, most teams we talk to did not plan for this." Ask: "Is it that there is no budget at all this year, or that this is not yet a priority?" Answer: if priority, go back to the cost of the problem they described. If no budget, agree on a date to revisit and log it. Check: "Does that seem fair?"

"We are already using a spreadsheet for this." Ask: "How much time does maintaining it take each week, and who owns it?"

Keep objections in one shared place and add new ones as they come up. The objection handling cheat sheet gives you a ready structure.

5. Competitive play

Trigger: a prospect names a competitor or is clearly evaluating alternatives.

Goal: make the decision about fit, not features, and set criteria where you are strong.

Sample excerpt:

Competitor: a large all-in-one CRM suite.

Where they win: breadth of features, brand familiarity, existing contracts.

Where we win: setup time, price for small teams, support from people who know the product.

Landmine question: "How long did your last tool take to roll out, and who on your team owned it?"

Do not say: anything negative about the competitor you cannot back up.

Proof: a short reference from a customer who switched for the same reason.

Build one card per competitor with the competitive battlecard template, and review it each quarter.

6. Expansion play

Trigger: a customer hits a usage milestone, adds a new team or reaches a set point after go-live, such as 90 days.

Goal: a conversation about a second team, use case or tier, based on results the customer has already seen.

Sample excerpt:

Prep: pull the customer's usage and the outcome they told you mattered at the start.

Open: "When we started, your goal was to cut lead response time. Here is where that is now. How does that compare to what you expected?"

Bridge: "You mentioned the partnerships team handles leads the same way. Is it worth showing them what your team set up?"

Exit rule: an introduction to the new team's owner, or a note in the CRM to revisit at the next review.

7. Founder-to-first-hire handoff play

Trigger: the first salesperson starts.

Goal: the new hire runs deals on their own, with the founder stepping back on a clear schedule.

Sample excerpt:

Week 1 to 2: new hire reads the playbook, listens to recorded founder calls and shadows live calls.

Week 3 to 4: new hire runs discovery with the founder on the call, silent unless asked.

Week 5 onward: new hire owns new deals end to end. Founder joins only for late-stage deals above an agreed size.

Deals in flight: founder keeps any deal past the demo stage on the start date. Everything earlier moves to the new hire with a written handoff note: pain, people, next step.

Exit rule: the new hire has run a set number of discovery calls alone and the founder has reviewed them.

This play is where many startups stumble. The founder-led sales playbook covers how to capture what works before the hire, and transitioning off founder-led sales covers the handoff itself.

Are there real, public sales playbooks to learn from?

Most companies keep their playbooks private, but a few publish parts of how they sell. The best-known example is GitLab, which runs much of the company from a public handbook. Its sales section includes a page on MEDDPPICC, the qualification framework it uses, and a Command Plan page that describes how opportunities are documented.

Public examples like these are useful for structure and vocabulary. They are less useful as something to copy: an enterprise qualification process built for a large sales organization is usually too heavy for a startup with one or two reps. Take the idea, such as clear qualification criteria or a written deal plan, and keep your version short.

How do you turn these examples into your own playbook?

1. Pick the plays you actually run. Most early teams need outbound, discovery, demo and objection handling first. Add competitive, expansion and handoff plays as they become real.
2. Write from real deals. Replace every illustrative excerpt above with an email that got a reply, a question that opened up a call or an objection you actually hear.
3. Use one structure. Trigger, goal, steps, example, exit rule. The sales playbook template gives you this layout for every section.
4. Match the CRM. Every exit rule should map to a deal stage. See CRM pipeline stages.
5. Test it on a new person. If a new rep cannot run a play from the page, it is missing something. Pair the playbook with a ramp plan from how to onboard a sales rep.
6. Give it an owner. One person reviews it monthly in the first year, adds new objections and retires messages that stopped working.

Where Enablemnt fits

A playbook is only as useful as the system it describes. Plays need a clear ICP to target, a CRM whose stages match the exit rules and live outbound that produces the meetings the later plays depend on.

Enablemnt's 14-day sprint delivers your ICP, CRM and live outbound in 14 days, documented and yours to own, so your first sales hire starts from a working motion rather than a blank page.

If you would rather have that foundation built than write it from scratch, tell us about your startup.

Filed under Building a sales team. Written by Enablemnt AI.