Every sales team eventually writes down what a good discovery call sounds like. The hard part is getting that document in front of a rep at the exact moment they are on the call, instead of buried in a shared drive nobody opens twice.
HubSpot playbooks are the native answer to that problem. They put a guided script directly on the CRM record, with fields the rep fills in while they talk. This guide covers what playbooks actually are, which plans include them, how to build one that reps use, and the specific point where they run out of room.
In this article
1.
2.
3.
4.
5.
6.
7.
8.
9.
What are HubSpot playbooks?
A playbook is an interactive content card that renders on a CRM record. It is part script and part form: the rep reads the guidance, asks the questions, and types the answers into the playbook itself rather than into a separate note.
Static guidance
The talking points, positioning statements, objection responses, and framework definitions a rep should have in front of them. This is the part that behaves like a document.
Question blocks
Structured fields (open text, single choice, multiple choice) that capture what the rep learns. This is the part that behaves like a form, and it is what makes a playbook more than a saved snippet.
Property mapping
Each question can be pointed at a CRM property, so an answer typed during the call writes straight to the contact, company, or deal record. No second pass of data entry.
Which HubSpot plans include playbooks
This is the first thing to check, because a lot of playbook planning dies here. Playbooks are a paid-tier feature and are not part of the free CRM.
| Plan | Playbooks included |
|---|---|
| Free HubSpot CRM | No |
| Sales Hub Starter | No |
| Sales Hub Professional | Yes |
| Sales Hub Enterprise | Yes, with usage reporting |
| Service Hub Professional and Enterprise | Yes |
Each rep who needs to open a playbook has to sit on a paid seat for that hub, which is worth pricing before you design a process around them. If your team is on Starter, the practical substitutes are note templates, a linked document, or an app-provided card on the record. Our guide to HubSpot custom cards covers what a record can display when the native feature is out of reach.
What teams actually use playbooks for
The feature is generic, but the use cases that stick are narrow. These are the ones that survive past the first month.
Discovery calls
The most common by far. The playbook holds the question set and captures the answers as properties, which is how discovery data stops living only in someone's memory. If you are still building that question set, start with our sales discovery questions.
Qualification frameworks
BANT, MEDDIC, and MEDDPICC map almost perfectly onto question blocks, because each letter is a field. The playbook enforces the framework instead of hoping reps remember it.
Competitor battlecards
Mostly static content, no property mapping needed. The value is having the counter-positioning on the record when the objection actually lands.
Support and onboarding triage
On Service Hub, a playbook walks an agent through the diagnostic questions and writes the outcome to ticket properties.
How to create a HubSpot playbook
Building one takes about fifteen minutes. Getting reps to use it takes longer, and most of that comes down to how tightly the questions map to properties.
- 1
Open the playbooks library
Find Playbooks under the Library section of your HubSpot navigation. This is a shared library, so everything you build here is a team asset rather than a personal doc.
- 2
Start from a template or blank
HubSpot ships starting points for discovery, qualification, and battlecards. Even if you plan to rewrite everything, opening a template first shows you how question blocks are meant to sit inside the guidance.
- 3
Write the guidance, then add the questions
Put the talking points and framing in headings and lists, then drop question blocks where the rep needs to capture something. Keep the reading short. Anything a rep has to scroll past mid-call gets ignored.
- 4
Map every question you can to a property
This is the step that makes the playbook worth building. An unmapped question produces text on a timeline. A mapped question produces a filled property you can filter, report, and automate on.
- 5
Scope it and publish
Choose which object types the playbook appears on and which teams see it, then publish. A deal-stage playbook that shows up on every contact record is a playbook reps learn to ignore.
Playbooks best practices
The difference between a playbook that gets used and one that gets abandoned is almost always length and mapping, not content quality.
Keep playbooks usable mid-call
- Cap it at what a rep can actually work through while talking. Eight to twelve questions is a realistic ceiling; twenty is a form nobody finishes.
- Map every question you can to a CRM property. An answer that only exists as timeline text cannot be reported on, so it quietly stops mattering.
- Use choice questions over open text wherever the answer is genuinely a set. Free text is unfilterable and drifts in wording across reps.
- Scope playbooks to the right object and team so reps see one obvious option instead of a list they have to choose from.
- Review them quarterly against closed-won deals. A discovery playbook written for last year's ICP is worse than none, because reps follow it.
Where playbooks stop working
Playbooks are good at one shape of content: short, structured, answerable. The moment your team's context does not fit that shape, the feature works against you.
A playbook is a form with a script attached. It was never meant to hold the document your team actually thinks in.
The gap shows up fastest on account plans, renewal context, technical scoping notes, and anything a team writes collaboratively before or after the call. That material is long, formatted, linked to other pages, and edited by more than one person. It lives in a real document tool, and for a lot of teams that tool is Notion.
A playbook cannot pull that document in. Playbook content is authored in HubSpot's library and stays there, so a team that writes in Notion ends up either rewriting the content as playbook blocks or copy-pasting a summary onto the record after the fact. Both create a second copy that goes stale, which is the same trap described in the hidden cost of copy-pasting notes.
What playbooks do well
- Guided script sits on the record at call time
- Answers write straight into CRM properties
- Enforces a qualification framework consistently
- Completed playbook logs to the timeline
Where they run out
- Professional and Enterprise tiers only
- Built for short Q and A, not long-form documents
- Content must be authored inside HubSpot
- Cannot render a doc your team wrote elsewhere
- No collaborative editing or rich page structure
Playbooks vs notes vs a live Notion card
All three put context on a record, and they are not competitors so much as different jobs. This is the decision in one place.
Playbooks are the right tool for discovery and qualification, where the output is fields. Requires Sales Hub or Service Hub Professional or above.
Notes are free, fast, and unstructured. Good for a quick summary, poor for anything you need to report on later. See our guide to HubSpot notes.
NoteLinker renders your Notion database rows directly on the matching contact and deal, so account plans and meeting notes show up on the record without being rewritten as playbook content.
Most teams that run playbooks well end up doing both. The playbook captures the fields, because fields belong in the CRM and need to be reportable. The document stays in Notion, because that is where it gets written and edited, and a card brings it onto the record so the rep never has to go find it.
Getting your Notion docs onto the record
If the reason you were looking at playbooks is "our sales context is not visible in HubSpot," and that context is written in Notion, a playbook is solving a different problem than the one you have.
- 1
Install NoteLinker from the HubSpot Marketplace
Find NoteLinker in the HubSpot App Marketplace and install it. Standard OAuth, no code and no developer build.
- 2
Connect Notion and pick your databases
Authenticate with Notion and grant access only to the databases holding your sales notes and account plans. Everything else in your workspace stays private.
- 3
Name the match properties
Tell NoteLinker which Notion property holds the contact email and which holds the deal name. That is how the card knows which rows belong on which record.
- 4
Open any contact or deal
The card renders the matching Notion rows inline. Rows are visible by default, so there is no sync step and nothing to press.
The full walkthrough lives on the setup page, and if you want to see the result before installing, here is Notion inside a HubSpot record.
Put your Notion docs on every HubSpot record
NoteLinker adds a card that renders your live Notion database rows on the contact and deal record. No rewriting, no copy-paste, and no Professional-tier requirement.
Playbooks are one of the better things HubSpot ships, and if you are on a tier that includes them, a tight discovery playbook mapped to real properties will pay for itself. Just be clear about what you are buying: a form with a script attached, sitting on the record. For the documents your team actually writes, you need something that shows the document itself. See how the two surfaces fit together in our guide to the Notion HubSpot integration.
