Sales training solves the problem once. A HubSpot Playbook solves it every time the situation occurs. The distinction matters because the highest-impact sales behaviors — the questions asked in discovery, the way a rep handles a pricing objection, the criteria used to qualify or disqualify a deal — are not things that stick from a single training session. They require in-the-moment prompts that appear exactly when the rep needs them, inside the tool they are already using to run the call.
HubSpot Playbooks are structured guides that appear inside contact, company, and deal records. They can include prompts, talk tracks, answer fields, and checklists. When a rep fills out the fields in a playbook during or after a call, those answers can write directly to CRM properties, populating qualification data without requiring the rep to navigate away from the call view. That combination — in-context guidance plus structured data capture — is what separates Playbooks from a PDF in a shared drive.
The Three Playbooks Every B2B Sales Team Needs First
1. Discovery Call Playbook
The discovery call playbook is the highest-leverage starting point. It should contain: an opening framing statement, the 6-8 qualification questions the team has agreed are most predictive of deal quality, prompts for each question that help a less experienced rep understand what a good answer looks like, and answer fields that map to BANT or MEDDIC properties in the deal record. When the call ends, the rep fills in what they learned, the data lands in HubSpot, and the deal record reflects the qualification status without a separate data entry task.
2. Objection Handling Playbook
An objection handling playbook is a reference tool, not a script. It should list the 6-10 most common objections the team encounters (pricing, timing, incumbent vendor, internal champion availability, IT/security review) with a structured response framework for each. The framework is not a word-for-word script — it is: acknowledge the concern, ask a clarifying question to understand the specific form of the objection, then offer a framing that re-centers on value or addresses the real concern. Reps use this during a call when they hit an objection they are less practiced with.
3. Deal Qualification Playbook
A deal qualification playbook is used during pipeline reviews, not during calls. It is a structured set of questions a manager asks when reviewing a deal: Is the economic buyer identified? Has the rep spoken directly with them? Is there a defined timeline? Is there a business case established? Is there a next step with a specific date? This playbook formalizes the qualification conversation so pipeline reviews produce consistent data and consistent outcomes, rather than being dependent on a manager's memory of what to ask.
| Playbook | When to use | Primary output |
|---|---|---|
| Discovery Call | During or immediately after a discovery call | Qualification data populated in deal properties |
| Objection Handling | During a call when a specific objection arises | Consistent objection response, notes on the specific objection |
| Deal Qualification | During pipeline review or deal stage advancement | Qualification score, missing info flagged for follow-up |
Sales Playbooks
Want to build HubSpot Playbooks that your reps actually use?
We build discovery, objection handling, and qualification playbooks inside HubSpot, mapped to your deal properties and pipeline stages, with the analytics wired up to measure completion rates. Book a call.
Book a Free CallHow to Build a Playbook That Gets Used
Keep it short
A discovery playbook that takes 15 minutes to complete will not be completed. Reps are on calls, moving to the next task, writing follow-up emails. The target is 3-5 minutes to complete all required fields. That means 6-8 fields maximum. If the playbook needs more, split it into two playbooks used at different stages rather than building one long one that is always partially filled out.
Use prompts, not paragraphs
Each field in a Playbook can have a prompt below it. Use short, action-oriented prompts: "What specific pain did they describe?" rather than a three-sentence explanation of why understanding pain matters. Reps in the middle of a call do not read. They scan. Design the playbook for scanning.
Map fields to CRM properties
The only reason to use a Playbook over a note is that Playbooks can write data back to CRM properties. For every question in a discovery playbook, map the answer field to a deal or contact property: budget confirmation maps to Budget Confirmed (yes/no), decision timeline maps to Expected Close Date, key pain maps to Primary Pain Point. This turns the playbook from a guided note into a data capture tool that populates the qualification fields your pipeline reports depend on.
Surface it at the right deal stage
In HubSpot, you can configure which record types a Playbook appears on and add it to the right sidebar of a specific deal stage view. Configure the Discovery Call Playbook to appear on deals in the Discovery stage. The Qualification Playbook appears on deals in the Demo or Proposal stage. Reps should not need to search for a playbook — it should be visible the moment they open the relevant record.
Measuring Playbook Effectiveness
HubSpot's Playbook analytics show you how many times a playbook was opened versus completed, completion rate by rep, and which fields are consistently left blank. Use this data quarterly: playbooks with below 40% completion rates are either too long, surfaced at the wrong moment, or not perceived as useful by reps. Talk to the reps before rebuilding — the completion rate is the symptom; the conversation tells you the cause.