Two capable reps can hear the same prospect and leave with completely different deal records. That gap hurts follow-up long after the call ends.
HubSpot playbooks give every rep a shared path for discovery, while still leaving room to listen and respond. When prompts, CRM properties, and call settings match your sales process, the record becomes useful evidence instead of a loose collection of notes.
Decide what every discovery call must produce
A discovery playbook works best when it captures information your team will use after the meeting. Before opening the editor, decide which answers affect qualification, routing, follow-up, forecasting, or the next sales step.
For a solo founder, this may be a short set of fields. For a growing SaaS team, it may support handoffs between SDRs, account executives, and customer success. In both cases, the rule is the same: only ask for data that someone will act on.
Separate conversation notes from reporting fields
Free-form notes capture context, tone, and exact language from the prospect. CRM properties capture answers you need to filter, report on, or trigger in a workflow.
For example, “Their team is frustrated with missed handoffs after trade shows” belongs in the call notes. “Lead source,” “current CRM,” and “target launch date” should live in consistent properties. Otherwise, reporting becomes a pile of near-duplicates such as “Excel,” “spreadsheets,” and “manual tracking.”
Use the playbook to guide the conversation, but connect agreed qualification answers to the right contact, company, or deal properties.
Start with a small shared qualification model
A founder doesn’t need 14 mandatory fields to run a useful discovery call. Start with a set that tells you whether the problem is real, important, and actionable.
One practical set might include:
- A multi-line “Primary problem” property that captures the prospect’s own language.
- A dropdown for “Current solution” with options such as spreadsheet, HubSpot, Salesforce, or no formal system.
- A number field for team size when account scale affects fit or pricing.
- A dropdown for buying timeline, such as this month, this quarter, or later.
- A multi-line “Decision process” field for stakeholders, approval steps, and the agreed next action.
Keep property labels stable once reps adopt them. Changing labels or option values without a plan can split reports and make old data harder to trust.
Configure HubSpot playbooks and call settings
HubSpot positions playbooks as interactive content cards within contact, company, deal, and ticket records. Begin in CRM > Playbooks, then choose Create playbook. Some accounts place navigation under a “More” menu, so the path can look different depending on your subscription and account setup.
HubSpot’s current playbook instructions cover creating a playbook from scratch or starting with a Sales playbook template. A template can save time, but review every prompt before publishing. Generic sales language often creates vague call notes.
Choose a clear name and a usable home
Name the asset for the moment it supports, such as “Inbound Discovery Call” or “Partner Referral Discovery.” Reps should know which playbook to open without reading a description.
Then test it on the CRM record your team uses during calls. A founder may work from a contact record. A sales team managing several stakeholders often needs the associated company and deal nearby. The playbook itself can appear across several record types, but your operating process should tell reps where the primary call record belongs.
Set the interaction type to Call
In the playbook settings, choose Call as the interaction type for discovery conversations. If your portal offers default call types, select Discovery/Connect Call when that matches your team’s taxonomy.
This setting matters because HubSpot logs the completed playbook as a call interaction on the record timeline. It also makes call activity easier to separate from demos, presentations, emails, and internal notes.
HubSpot saves in-progress playbook input as a draft. The rep still needs to click Log call to save the interaction and write connected property answers back to the CRM. Teach that final step during rollout, because an excellent call record left in draft form helps nobody.
Write prompts that keep the conversation natural
A discovery call shouldn’t sound like a survey read aloud. Reps need a short prompt, a clear reason for asking it, and enough space to follow a useful answer.
A prompt earns its screen space when it changes a CRM property, the next question, or the next action.
Keep explanatory text short. Use it for a useful reminder, such as a positioning point or objection response. Put the actual questions in the order a prospect would naturally experience the conversation.
Open with the current situation
Start with the trigger that brought the prospect into the conversation. Prompts such as “What changed that made this worth looking at now?” work better than an early product pitch.
Next, ask how the work happens today. “Walk me through the current process” gives the prospect room to explain tools, people, workarounds, and friction. It also prevents a rep from assuming the problem based on a form submission alone.
Turn pain into business impact
Pain without impact rarely creates urgency. Follow an operational problem with a question about cost, risk, time, or missed revenue.
During a scheduling-software discovery call, a dental practice manager may explain that staff members phone every cancellation. The rep can ask, “How many appointments usually go unfilled each week?” Then capture the answer in notes and save the broader issue as the primary problem.
This is more useful than recording “interested in automation.” It tells the next person why the prospect is evaluating change and what a better process must improve.
Confirm the buying path before closing
End discovery with prompts about ownership, timing, and the next mutual commitment. Ask who will use the product, who approves the purchase, and what must happen before a decision.
Don’t force a budget question if it doesn’t fit the conversation. A small business owner may not have a formal budget yet, but they can often describe the cost of waiting. Record the real answer rather than pressuring the prospect into a number they don’t believe.
Connect questions to HubSpot properties carefully
HubSpot playbooks support written guidance, links, snippets, knowledge base articles, and question or prompt blocks. You can mark question blocks as Required, which helps prevent incomplete call records.
However, required fields need restraint. If every prompt is mandatory, reps may enter filler simply to log the call. That creates clean-looking data with little value.
Require only the fields that define next steps
Make the primary problem, buying timeline, and agreed next step required if your team needs those answers for every qualified conversation. Leave exploratory topics optional when they won’t apply to every prospect.
For example, “Current solution” may be required for a replacement sale but less useful for a brand-new business. A rep should be able to explain that distinction in notes without inventing a dropdown value.
A required playbook question prevents an incomplete log. A required CRM property can also block a record update, so both rules need careful testing.
Match answer formats to the data you need
Use open text for context that changes from call to call, such as a prospect’s stated goal or decision process. For repeatable categories, controlled answer options make reporting more reliable.
HubSpot documents open-text answers and, for Sales Hub Enterprise, list-of-answer-options questions that save as notes on the record. When a question is connected to a property, HubSpot updates that property after the rep logs the interaction.
Property conditional logic is separate from playbook writing. HubSpot’s conditional property logic can show or require dependent fields based on an earlier property value. Official playbook guidance does not confirm that the editor itself supports full if-then branching between prompts.
Therefore, don’t write a complex branching script and expect questions to disappear automatically. Keep the path visible, use concise guidance, and let the rep choose the relevant follow-up based on the conversation.
Test access, records, and real call behavior
A well-written playbook still fails if reps can’t open it, don’t know when to use it, or find that key fields don’t save. Test the published version with the same permissions and record layouts your team uses each day.
HubSpot ties playbook access and editing rights to assigned Sales or Service seats and playbook permissions. Navigation, availability, permissions, and plan requirements can vary by HubSpot subscription and account configuration.
Give editors and reps the right level of access
Keep edit access limited to the person who owns the sales process and a backup administrator. Too many editors can create competing versions of questions, property mappings, and call guidance.
At the same time, run a test with a standard rep profile. Confirm that the rep can find the published playbook on the intended record, complete required prompts, log the call, and see the saved interaction on the timeline.
Check contact-only calls and calls with associated companies or deals. Association gaps often appear when a rep opens a record from a notification or a meeting link.
Measure completion without rewarding filler
Review the first 10 to 20 discovery calls after launch. Look for missing fields, weak notes, and values that don’t match what you hear in call recordings or read in transcripts.
Track whether reps use the right HubSpot playbooks, but don’t treat usage as the only success metric. Compare property completion, discovery-to-demo conversion, and the rate of calls with a documented next step.
If every deal has the same timeline or problem value, the prompt may be too broad. If reps skip one field repeatedly, either the field isn’t needed or the question appears at the wrong point in the call. Remove friction before adding more questions.
Consistency comes from useful evidence
A strong discovery playbook gives reps a dependable conversation path and gives the business reliable CRM data. It captures the problem, the impact, and the buying path without turning the call into an interrogation.
Start small, make the call logging behavior explicit, and test the experience with real rep permissions. Over time, the best HubSpot playbooks become a record of what your strongest discovery conversations consistently uncover.
