How to Use HubSpot AI to Build a Better Sales Playbook
You don't have to start a sales Playbook...
September 25, 2026
Every rep should know what to ask on a discovery call. Turning that into an actual Playbook, one reps will open and follow, is the part that usually stalls before it starts.
Here’s how to use HubSpot AI to build the starting point, then turn it into something reps actually reach for mid-call.
From a blank Playbook, click the Breeze icon in the editor. It opens right there alongside the draft, no separate tab, nothing to lose track of. The prompt is where the real work happens: name the exact job, the audience, and the shape you need. Something like “create a discovery-call question framework for B2B sales reps, covering the prospect’s business problem, current process, impact, timing, and next step, keep the questions short” gives Breeze enough to work with, specific enough that it can’t default to something generic. A vague prompt produces a generic framework that could belong to any company selling anything, which defeats the entire point of building something specific to how your team actually runs a call.
What comes back is often more than one option in the same response, a full framework plus extra qualification or success-criteria questions nobody asked for, and sometimes a tighter, shorter version further down in the same reply. Reviewing the whole response before picking one matters here. The first thing Breeze returns isn’t always the version worth using, and stopping at the first block of text is how a Playbook ends up carrying questions nobody actually needed.
Once you’ve picked the questions that actually fit, add them one at a time using the plus icon rather than pasting the whole response in at once. Here’s the detail that’s easy to miss. HubSpot defaults every new question to a list of answer options, essentially multiple choice. For an open-ended discovery question, that’s wrong.
Click the answer type, switch it to Open text, and save. Repeat that for every single question, not just the first one or two. A list of preset options can’t capture what a prospect actually says in their own words, and that’s exactly the part of a discovery call worth capturing precisely, not forcing into a box that was never built for it. Before publishing, scroll through the finished Playbook one more time and confirm every question is actually set to Open text, not the default nobody remembered to change.
A published Playbook that never gets opened isn’t worth the time spent building it. The part that makes it useful happens on the contact record itself, and it only takes one setup step: add a Playbooks panel to the contact layout, so it’s sitting right there before the next call ever gets dialed.
From the record, a rep clicks the Playbook by name and it opens right there on screen while the conversation is happening. Each question has its own field, so answers get typed in as the prospect actually talks, not reconstructed from memory afterward. Logging the call, picking an outcome, and checking a box for a follow-up task all happen from the same window. What lands on the record’s timeline afterward isn’t just “call logged.” It’s the whole conversation, question by question, with the actual answers sitting right there for the next person who opens that record.
That’s the difference between a Playbook that exists and one that actually changes what a team’s call history looks like six months from now. It’s the same principle behind How We Use Claude to Prep for Every Client Call and How RevOps Solves the Discovery Call Data Problem Nobody Talks About: the value was never just having AI touch the call somewhere. It’s what ends up sitting on the record afterward, and whether the next person who opens it can actually use what’s there.
Use AI to create the starting point. Use your own judgment to turn it into something that actually fits how your team sells. Need help building HubSpot around your actual process? Book a meeting with us.
You don't have to start a sales Playbook...
A lot of founders have never actually calculated...
HubSpot already scores every contact in your portal...
Your CRM knows a deal has been sitting...
Your reps are still logging call data by...