B2B Sales Playbook Template: Free Google Sheet With First-Call Steps and Objection Categories

Sales playbook template cover: five tabs in one free Google Sheet, from ICP and personas to plays

Publish date: Nov 13, 2026

A B2B sales playbook template holds the four things a rep needs mid-call. Who you sell to, how the first call runs, what buyers object to, and which play fits which trigger. This one is a free Google Sheet with five tabs. Two of them come filled with Spona's own call records.

The Call flow tab holds four first-call steps from 187 recorded first calls. The Objections tab holds twelve objection categories from 317 recorded calls. Make a copy of the Sheet and replace the grey example rows with your own. The usage rates, shares and review flags update themselves.

The sheet is in English and recalculates in Google Sheets, Excel and LibreOffice. No scripts, no add-ons.

The Extractor
The Refiner
The Verifier
The Exporter

Get thousands of leads in 4 minutes.

Stop stitching tools together.
Start with verified sales data, delivered in minutes.

SCALE SALES NOW

No contracts · No setup · No onboarding

What should be in a sales playbook template?

A sales playbook template answers four questions in one fill-in document. Who do we sell to, and what do we say on the first call? Which objections will we hear, and which play runs when a trigger fires? Highspot calls a playbook the overarching system that tells sellers when and how to execute those activities.

The template is that system with the blanks marked. This sheet splits it into five tabs, and each answers a question a rep asks during the week.

TabWhat it answersWho fills itWhen to review
InstructionsWho owns the playbook, how often it is reviewed, which values the dropdowns holdPlaybook ownerWhen a list changes
ICP and personasWhich companies and buyer roles we sell to, and which we turn awaySales lead, with marketingEvery 90 days
Call flowWhat happens on a first call, step by step, and how often reps use each stepSales lead; reps count usage monthlyEvery 90 days, usage monthly
ObjectionsWhat buyers say, what we answer, how often each comes upSales lead; reps add new rowsAfter each call review
PlaysWhich outreach runs when a trigger fires, who owns it, when it stopsSDR or AE managerBefore each campaign

Shorter beats longer. Salesforce writes that a great playbook might be 50-80 pages long. Zendesk takes the other view: a concise playbook ensures that your reps will read the entire document.

Reps already spend 70% of their time on non-selling tasks, in a Salesforce survey of 5,500 sales professionals. Eighty pages nobody opens is not a playbook.

The reader who needs it most is the new rep. The Bridge Group puts SDR ramp at 3.0 months across 351 companies. Average tenure is 1.9 years, and median annual attrition is 40%. A quarter of ramp against two years of tenure: the playbook has to work on day one.

Diagram of the five sales playbook tabs and the dropdowns that link ICP rows, objections and plays
Add a segment, objection or play once and the dropdowns on the other tabs offer it.

The tabs feed each other. Plays reads its Segment or persona dropdown from the ICP and personas tab, and its Likely objection dropdown from Objections. Objections reads its Best play dropdown from Plays. Add a row in one place and the dropdowns on the other tabs offer it.

Make a copy of the Sheet and set the Playbook owner and Review every (days) on Instructions. Then work through the four tabs in order.

ICP and personas: who the sales playbook sells to

The ICP and personas tab has one row per target segment and one per buyer role. Row type says which: an ICP segment or a Persona. A segment row carries Industry, Size band and Country. A persona row carries Job titles and Role in decision, and both carry Pain points, Goal or success measure, Trigger events and Disqualifiers.

Why rows for roles, not one buyer? Gartner finds that the typical buying group for a complex B2B solution involves six to 10 decision makers. Gong's review of 10 million conversations found that won opportunities averaged 8.22 email participants. Lost ones averaged 3.38.

That is a correlation, not a cause. It still means a rep talking to one person is talking to a minority of the group.

The Role in decision dropdown holds six values: Decision maker, Economic buyer, Champion, User, Influencer and Gatekeeper. Pipedrive's persona fields include the role in the decision-making process, next to industry, company size, job title and pain points. The tab follows that list and adds two columns most templates skip.

The first is Disqualifiers: the signals that end the conversation. "No outbound team" sits on the example IT services row, "Government-only buyers" on the manufacturing row.

The second is Fit score (1 to 5), and Priority computes from it. A score of 4 or 5 is an A. A 3 is a B, anything lower a C, and an A turns its Priority cell green.

Our ideal customer profile template and buyer persona template go deeper on each field.

The eight example rows are invented: three segments and five personas, each marked "(example)". Last reviewed sits 30 days back on seven of them. The third segment sits 120 days back, so its Last reviewed cell turns red. That is what your rows will do when they go stale.

Call flow: Spona's four first-call steps

The Call flow tab holds one row per step per call type. The four rows marked First call are Spona's own script. It runs on our first calls to Heads of Sales at US companies with 10 to 49 staff. The Call type dropdown also holds Discovery, Demo, Follow-up and Renewal, so you can add flows for later calls.

StepPurposeSpona wordingFields to log
1Agree the call purpose"Would ten minutes to check fit, then decide whether a data sample makes sense, work for you?"Call purpose; time agreed; next-step rule
2Explore the problem"Which missing contacts or stale fields have prevented your team from reaching the right buyer?"Pain type; concrete example; current workaround
3Quantify impact and decision"How often does that happen, what does it cost in rep time, and who would approve changing the data source?"Hours lost; affected reps; decision owner; budget range
4Agree a test or disqualify"Which target segment and success measure should we test, and when will we review the result together?"Pilot scope; success metric; review date; proceed or close

Step 1 is a short up-front contract. Sandler's version outlines the purpose of the meeting, the process, the timeline and the expected outcomes. Ten minutes, a fit check, a decision about a sample: the buyer knows how the call ends before it starts. Our Sandler sales methodology post covers the full contract.

Step 2 asks one question about the problem and logs three fields. Gong reviewed more than 519,000 B2B calls. The best outcomes came when reps asked 11 to 14 targeted questions. Step 2 is the first of them, and our sales discovery questions post has the rest.

Step 4 is the one most playbook guides leave out. It ends the call with a test or a disqualification, never with a promise to send information.

Bar chart of four first-call steps on 187 recorded calls, with usage falling from 92.5% to 69.0%
The closing step that agrees a test or disqualifies is the one reps used least often.

The sheet tracks how often reps use each step. Spona's reps used the purpose line on 173 of 187 recorded first calls. That is a usage rate of 92.5%. The closing step, agree a test or disqualify, appeared on 129 calls, or 69.0%.

One call can hold all four steps, so the counts overlap and never add up to a total. The rates show recorded use, not whether a step works.

The drop from the first step to the last is the gap a sales lead can act on. Each month, count from your call recordings how many calls used each step. Type Calls using step (n) and Calls reviewed (n), and Usage rate computes. Set a Target rate per step, and Usage rate turns red where reps fall below it.

Objections: twelve categories from 317 sales calls

The Objections tab holds one row per category. Its columns are Category, Buyer wording, Response, Response type, Calls with objection (n), Share of calls, Best play, Owner and Last reviewed. Share of calls divides each count by Calls reviewed for Objections (n) on the Instructions tab.

One call can hold several objections, each counted once, so the counts never add up to that number.

The twelve example rows are Spona's own. They are objections to buying contact data, heard over the past three months from sales leaders at US companies with 10 to 49 staff. They show the method, not your list.

CategoryCalls with objection (n)Share of callsBuyer wordingResponse
Existing provider5718.0%"We already have a contact-data contract."Which target segment would justify testing a second source?
Budget4313.6%"This quarter's budget is committed."Would a narrow sample quantify the cost of the current gap?
Data accuracy3912.3%"Our last list had stale titles."Agree on titles, verification age and a blind sample before buying.
Timing3410.7%"We are focused on another rollout."Agree on a specific review date tied to that rollout.
Coverage uncertainty319.8%"I am unsure you cover our niche."Define the niche and inspect a representative sample.
Credit economics288.8%"I cannot estimate how quickly credits will run out."Price a defined field bundle using successful-result billing.
Privacy review268.2%"Our privacy team needs to review this."Offer documented provenance and route the specific questions to the privacy owner.
Approval authority237.3%"My manager owns this decision."Agree who should attend the sample review and what they need to see.
Workflow integration226.9%"We cannot add another manual export."Map the existing workflow and confirm supported delivery steps.
Phone quality196.0%"Direct numbers have not worked for us."Separate mobile, direct dial and switchboard, then compare per-dial outcomes.
Internal build175.4%"We collect our own data."Test only the fields or geographies your process leaves incomplete.
Team capacity144.4%"Our reps cannot work another list yet."Size the pilot to actual outreach capacity and revisit after the backlog.

Existing provider leads, on 57 of the 317 calls. That fits what buyers do before the first call. In 6sense's survey, 94% of buying groups had ranked their preferred vendors before first contact. The survey covered more than 4,000 buyers.

The rep is usually talking to someone who has already ranked the vendors. A sales battlecard for the incumbent belongs next to that row.

Sort the tab by Calls with objection (n). Reps rehearse the top three. The sales lead reviews the bottom three for rows to merge or retire. For answers by objection type beyond contact data, see our post on common sales objections.

Writing a response that ends in a test

Read the Response column again. Most of the twelve end in something the buyer can check: a sample, a pilot or a date. None argues. The Budget response does not defend the price; it asks whether a narrow sample would quantify the cost of the current gap.

The Response type dropdown holds six endings. They are Test or sample, Pilot, Review date, Route to owner, Price or quote and Map workflow.

When you write a response for your own product, pick the ending first. Then write one sentence, as a question or an offer, that names the next thing the buyer will see. A response with no ending is a rebuttal, and rebuttals do not get logged.

Add a row when a new objection comes up twice in a month. Vouris names a recurring buyer objection as one of three reasons to check a playbook section early. The other two are a pricing change and a pattern across call reviews. Type the buyer's words as said, not your paraphrase; the wording is what a new rep recognizes on a live call.

Plays: one sales play per trigger

A play is the smallest unit of the playbook: a trigger, a segment, a channel, an owner, the steps, and the rule that ends it. The Plays tab holds one row per trigger, with fifteen columns. Six of them are dropdowns: Segment or persona, Channel, Owner, Likely objection, Exit rule and Rules checked.

Revenue.io's play examples carry the three fields most templates leave out: entry criteria, owner and handoff, and exit rules. Exit there means reply, meeting, disqualification, opt-out or completion. The Exit rule dropdown here holds Meeting booked, Disqualified, Opted out, No reply after last step and Handed to AE. A play without an exit rule runs until someone forgets it.

The seven example plays are invented. Competitor contract renewal fires when an account's data contract ends in 90 to 120 days. Champion changed jobs fires when a past buyer starts at a company that fits the ICP. The stalled-deal play fires after 14 days without an agreed next step and re-runs step 4 of the call flow.

Every play also carries Rules checked and Rule or list checked, because plays send emails and make calls. The rules differ by country and channel, and the US and UK differ most on email.

Side-by-side US and UK rules for B2B sales emails and calls that a play must check before it goes live
US rules are stricter on B2B email than on calls; UK live B2B calls need TPS and CTPS screening.

In the US, CAN-SPAM makes no exception for business-to-business email. Each violating email risks a penalty of up to $53,088. You honor opt-outs within 10 business days and print a postal address in every message.

Calls are looser. Most calls between a telemarketer and a business fall outside the Telemarketing Sales Rule. The exception is calls selling nondurable office or cleaning supplies.

In the UK, the ICO says to screen against both the CTPS and TPS registers before you make live B2B calls. The PECR email rule does not apply to corporate subscribers, but you must still identify yourself and give a valid opt-out address. A named contact's details are personal data under UK GDPR. Sole traders and some partnerships count as individuals, so you email them only with consent or, for existing customers, the soft opt-in.

Rules checked turns red on Not done. Our cold call scripts and B2B cold email templates give the Steps and talk track column something to point at.

A filled sales playbook example: one account

Here is one invented account through all four tabs, with the real step wording. A US IT services firm with 30 staff holds a contact-data contract that ends in 100 days. It matches the segment row US IT services, 10 to 49 staff (example), Priority A. The persona row is Head of Sales (example), a Decision maker.

The trigger sits on the Plays tab. Competitor contract renewal (example) fires 90 to 120 days before renewal, with Channel Call, Owner AE and Exit rule Meeting booked. Likely objection is Existing provider. Rules checked reads Not needed, because this B2B call, like most, falls outside the Telemarketing Sales Rule.

The AE opens with step 1 as written: ten minutes to check fit, then a decision about a data sample. Step 2 asks which missing contacts or stale fields have stopped the team reaching the right buyer. The Head of Sales answers with the Existing provider line: "We already have a contact-data contract."

The Objections row supplies the response: which target segment would justify testing a second source? The buyer names one. Step 3 asks how often the gap costs rep time and who approves a change of data source. The AE logs hours lost, affected reps and the decision owner.

Step 4 closes with the segment to test, the success measure and a review date. The example ends with a review date, not a signature. Whether the sample lands is a separate row, on a separate day.

Three cells update afterward: Calls using step (n) for each step the AE used, Accounts entered (n) on the play, and the Existing provider count on Objections. Meetings booked (n) rises once the review date is in the calendar. Add one to Calls reviewed (n) and Calls reviewed for Objections (n) as well, and Usage rate, Meeting rate and Share of calls recompute.

Keeping the sales playbook current

Three settings on the Instructions tab run the maintenance: Playbook owner, Review every (days) and Calls reviewed for Objections (n). Review every (days) starts at 90. Every tab reads it: a Last reviewed date older than that turns red, so one change moves every due date.

Vendors disagree on the cycle. Salesforce says to revisit the playbook with its owner each quarter, at a minimum. Pipedrive settles for at least bi-annually, or whenever there are significant updates. The 90-day default follows Salesforce; type 180 if your cycle is slower.

Three events bring a review forward, whatever the date. Vouris lists them: a recurring buyer objection, a pricing change, or a pattern across call reviews. The first adds an Objections row, the second rewrites the Budget response, and the third shows up in the Call flow usage rates.

Usage is the leading signal. Zendesk advises you to look at the usage data to see which parts reps use most and which they rarely touch. Then track that usage against sales numbers. Highspot splits the two: leading signals such as how often a play is used at a given stage, and trailing indicators on deal health.

The sheet holds the leading side, Usage rate on Call flow and Meeting rate on Plays. Your CRM holds the trailing side. When a step's usage rate falls and the meeting rate falls with it, the step wording is the first suspect. When usage holds and results fall, the ICP row is.

Where Spona fits, and where it does not

Spona has no playbook feature. It does not record calls, count how often reps use a step, or hold scripts. A call recording tool fills the Calls using step (n) column faster than a human with a notepad.

If your team runs HubSpot, its Playbooks tool provides a Discovery Call playbook and a Qualification playbook by default. A rep opens one from a record, and the answers save to that record's timeline. That takes a Sales Hub or Service Hub seat at the Professional or Enterprise tier.

Where Spona fits is the ICP and personas tab, and the plays that read from it. Describe a segment row in a chat, in the words the row already holds: industry, size band, country, job titles. Spona returns a verified, scored list of the accounts and contacts behind it.

Deep Search costs 60 to 200 credits a lead, scored, verified and enriched in real time. That is $0.48 to $2.00 a lead, and the price per lead shows at checkout before you buy.

The blacklist matters for one play in particular. Competitor contract renewal should never reach a current customer or an open deal. Add both to the blacklist, and they stay out of every new list.

Two limits stay. Spona delivers the rows for the ICP tab and the accounts a play enters. The call, the objection and the exit rule are still the rep's. And a vague ICP row buys a vague list.

A dialer and AI cold calling are coming soon. Until then, the Call flow counts come from your own recordings.

The Extractor
The Refiner
The Verifier
The Exporter

Get thousands of leads in 4 minutes.

Stop stitching tools together.
Start with verified sales data, delivered in minutes.

SCALE SALES NOW

No contracts · No setup · No onboarding

Sales playbook template FAQ

What four elements should your sales playbook include?

The four working tabs of this template. ICP and personas says who you sell to, and Call flow says what you say on the first call. Objections holds what buyers push back with and how you answer, and Plays holds what you run when a trigger fires.

What format should your sales playbook be in?

A shared digital file that reps can search mid-call. Vouris strongly recommends a digital playbook, such as a shared document or an internal wiki. This sales playbook template is a Google Sheet because objections and plays are rows with counts, and rows with counts belong in a spreadsheet. If your team needs another file type, Google Sheets downloads a copy through File, Download in different formats, such as PDF or Excel.

Does HubSpot provide sales playbook templates?

Yes, two. HubSpot automatically provides a Discovery Call playbook and a Qualification playbook, which reps open from a record. The feature needs Sales Hub or Service Hub at the Professional or Enterprise tier. HubSpot playbooks hold text, links and questions whose answers log to the record; they have no ICP rows, objection counts or plays with triggers.

How often should you update a sales playbook?

Set a cycle and keep three exceptions. Salesforce suggests each quarter at a minimum, and Pipedrive accepts at least bi-annually. The sheet's Review every (days) setting starts at 90 and flags every row past its date. The exceptions are a new recurring objection, a price change and a pattern in call reviews.

What is a sales play?

A sales play is a repeatable set of steps a rep runs when a defined trigger fires. Salesforce defines plays as specific strategies or steps the team can follow during each stage of the selling process. In this sheet, a play is one row on the Plays tab, from Trigger and Segment or persona to Exit rule and Success measure.

Share this article

GET FREE LEADSSparkle

Similar Topics For You

see all texts