The Complete HubSpot SDR Playbook

The lifecycle model

The lifecycle model we recommend for B2B teams is: Lead → MQL → SQL → Opportunity → Customer → Advocate. No Subscriber stage — remove it. Every new contact enters as a Lead.

• Lead. Net-new contact, filled out a non-demo form, no qualification yet. Owner: marketing.
• MQL. Crossed the scoring threshold or submitted a high-intent form. A Lead record is auto-created on the Lead object. Owner: SDR.
• SQL. SDR qualified the lead and booked a meeting the prospect attended. Auto-flips one day after the meeting; the AE can flag it back if it didn't qualify. Owner: AE.
• Opportunity. Deal created in the sales pipeline.
• Customer. Closed-won deal.
• Advocate. High-health-score customer.

The MQL → SQL conversion is where your whole system gets audited. Low conversion means one of two things: marketing is generating junk MQLs, or SDRs are over-qualifying to the AE. The stage funnel tells you which.

Forms and UTM hygiene

Too many forms is the most common issue we see — we've audited portals with 565 of them, most auto-collected from website form tags or duplicated by well-meaning marketers. The principle is simple: as few forms as possible, one per asset type, reused across every landing page that needs it.

Six to ten core forms cover most B2B teams:

Hidden fields on every form are non-negotiable: lifecycle stage plus all five UTM parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term). Without them you can't report on campaign-level attribution or auto-set MQL status from high-intent submissions. One form per asset type, lock the hidden fields, archive everything else.

Scoring — the MQL trigger

HubSpot lead scoring (Marketing Hub Pro and up) decides who becomes an MQL and lands in your SDRs' queue. Get it wrong and they work junk all day. Five design decisions:

1. Combined score, not just engagement. Build the score from two dimensions — engagement (what they do) and fit (who they are). Engagement alone means journalists and students hit your threshold; fit alone ignores buying intent.

2. Score groups with limits. Five groups, each capped:

Total: 105 points. MQL threshold: 26.

3. Score decay is the single biggest lever for cleaning up an inflated MQL count. Recommend 50% every 3 months on engagement, 50% every 6 months on high-intent conversions, and no decay on fit. Most portals have around 3,000 stale MQLs; decay deflates them to what's actually live.

4. Auto-MQL bypasses. Demo requests and "talk to sales" submissions should flip lifecycle to MQL on submission, regardless of score — waiting for a score to accumulate on a demo request is how you lose deals to faster competitors.

5. Two MQL queues. A hidden "MQL intent" property set to High or Low at creation drives the SDR's queue view. High-intent SLA: 5 minutes. Low-intent SLA: 24 hours.

Lead tags

Each lead record should be tagged at creation, with three dropdowns on the Lead object:

• Lead Source Type — Inbound, Outbound, Partner Referral, Event, Recycled.
• Lead Source Detail — Demo Request, Content Download, Webinar, Event, Cold Outreach, Partner Referral.
• Lead Status Type — New, Recycled.

Tagging at creation is the difference between "inbound drove 200 leads this quarter" and "inbound demo requests drove 47 qualified meetings and €380k in pipeline."

Lead automation

Configure under Settings → Objects → Leads → Pipelines → Automate.

Templated automation (native, toggle on):

• Create a lead when contact lifecycle = MQL.
• Move to Attempting when any outreach activity is logged.
• Move to Connected on email reply, call outcome = Connected, or meeting outcome = Completed.
• Create a follow-up lead when disqualification reason = Bad timing or Unresponsive (sets Lead Status Type = Recycled).

Custom workflows (build these yourself):

• On Qualified: auto-create a deal in the sales pipeline; notify SDR, manager and leadership; create a 24-hour AE task; set lifecycle = SQL one day post-meeting (with the AE flag-back option).
• On Disqualified: set lifecycle back to Lead — unless reason = Wrong industry or Too small (those stay disqualified permanently). If reason = Bad timing, enrol in a 90-day nurture.

BANT as custom properties

Qualification lives on the Lead object as custom properties (Settings → Objects → Leads → Properties), grouped by BANT.

B — Budget

A — Authority

N — Need

T — Timeline

The threshold: 3/4. A lead needs three of four BANT dimensions confirmed to move to Qualified. Exception: a 2/4 qualifies if the two confirmed are Need + Timeline.

The single highest-signal field on the whole record isn't Budget — it's Trigger Event. A prospect with a clear trigger (failed project, new executive, contract expiring, compliance deadline) is dramatically more likely to close than one who's "just exploring."

Deploying this as a HubSpot Playbook

HubSpot's Playbooks tool turns this BANT framework into an interactive card SDRs see directly on the lead record — they open it during the call, fill in answers, and properties update automatically. Requires Sales Hub Professional or Enterprise, an assigned Sales seat and Publish/Write playbooks permissions.

The build, in six steps:

1. Create the playbook. CRM → Playbooks → Create → Sales playbook template. Name it "SDR BANT Qualification Playbook."
2. Build the content. In the Write tab add the opening talk track, then for each BANT question set Answer type = "Update a property" and link it to the matching lead property — the SDR's answer writes straight to the property.
3. Configure settings. Log playbook submissions; engagement type = Call; default call type = Qualification, so logged calls are tagged correctly in reporting.
4. Set recommendation rules. Filter on "Lead Status is New, Attempting or Connected" so the playbook auto-surfaces on matching records.
5. Add the card to record views. Settings → Data Management → Objects → Leads → Default view → add the Recommended Enablement card to the top of the middle column.
6. Publish and train. SDRs now see the playbook on every matching record; notes and property updates save automatically.

Track adoption under CRM → Playbooks → Analyze. A playbook that isn't used doesn't exist.

Sales Workspace — where SDRs work

Everything above lives somewhere — and that somewhere is the Sales Workspace (Sales Hub Pro and up, Sales seat required). Not the general CRM view, not the contact index: a purpose-built workspace bringing tasks, leads, deals, sequences, meetings and AI-prioritised guided actions into one home. Your SDRs should live here from 9 to 5.

The tabs that matter:

• Summary — daily hub: tasks due, sequence tasks, guided actions, upcoming meetings, prospect activity feed. Open it first every morning.
• Prospects → Leads — the active working queue, filterable by stage, source, activity and properties.
• Schedule — meetings with full context and AI summaries; prep time drops from 10 minutes to 2.
• Feed — real-time engagement alerts (opens, clicks, visits) so you time outreach to when interest is hot.

Saved views every SDR team should create: My New Leads (Stage = New, Owner = Me); Inbound Hot (Tag = Inbound, created < 24h); Needs Follow-Up (Connected, last activity > 3 days); Stale Attempting (Attempting, last activity > 7 days); Recycled for Follow-Up (Tag = Recycled, last engagement > 90 days).

HubSpot also auto-generates AI-prioritised guided actions — newly assigned leads, leads awaiting your reply, sequence tasks due, upcoming meeting prep, post-meeting follow-up — which end the "what do I work on next?" decision fatigue that kills SDR productivity after lunch.

Pre-call checklist

Tools & environment — confirm before the call:

• HubSpot open on the contact/company record — name, title, company, prior activity, form submissions.
• Calendar integration active — you'll offer meeting slots live.
• HubSpot Sales Notetaker active in the room (tell the prospect the call may be recorded).
• This playbook open in the sidebar — talk track and property updates in one place.
• Headset tested, notifications muted, background clean.

Prospect research — 2 minutes, not 20: website + LinkedIn (industry, size, recent news, tech-stack clues from job posts); lead source and conversion context (what they downloaded, attended or requested); existing HubSpot activity (page views, email opens, prior calls); AE calendar availability. If they came from a specific campaign, weave it into the opener: "I saw you read our guide on [topic] — what caught your eye?"

The qualification call — opening

The goal of the opening is not rapport — rapport comes from understanding someone's problem faster than anyone else, not from small talk. Skip the weather. Three steps, about 90 seconds.

Step 1 — set context immediately.

"Hey [First Name] — glad we could connect. I want to understand your situation and see if we can help. What made you take this call?"

That one question replaces five minutes of small talk.

Step 2 — go straight into the problem. Based on your research, show you already understand their world:

"From what I can see, it looks like you're scaling your sales team without a repeatable process. Can you walk me through what's happening today?"

Step 3 — mirror and frame. Reflect their pain back better than they said it, then set the structure and wait for a verbal "yes":

"So it sounds like your team is spending half its time on manual work instead of selling. Is that right? … I'd like to ask a few more questions to understand the full picture, then if it makes sense I'll share how we've helped similar teams. If it doesn't, no problem."

That micro-commitment makes the rest of the conversation collaborative.

BANT discovery — the order matters

Fill in the BANT properties in this order: N → T → B → A. Need is the most natural opener; Authority is the most intrusive. Order them accordingly.

N — Need (start here): What tools and processes are you using today? How much is manual versus automated? What's the biggest headache right now? If you could fix one thing, what would it be?

T — Timeline: Is this something you're actively looking to change? What triggered you to start thinking about it now? Are you evaluating other solutions alongside this?

B — Budget (gently): Has the team allocated budget, or is that still being determined? Any sense of current spend in this area? If they're uncomfortable, don't push — mark Budget as Unknown and move on.

A — Authority (last): Who else would need to be involved in the decision? Is there an executive sponsor? Any standard procurement process — IT security review, RFP, board approval?

The ask

If BANT looks promising (3/4 or better), ask for the AE meeting — framed as exploring options, not a demo:

"This sounds like it might be worth exploring further. Would it make sense to invest 60 minutes with one of our solution engineers who works specifically with [their industry] companies? Maybe [Day] or [Day]?"

Two follow-ups that lift show rates: "Is there anyone else who cares about this you'd want to invite?" and "If your schedule changes and you can't make it, will you let me know?" — the second is a commitment device that measurably reduces no-shows.

If qualified, move the lead to Qualified, populate missing BANT, let the workflow auto-set BANT Score and create the AE review task, send a calendar invite titled "Exploring [solution area] options for [Company]" with an agenda and one resource, and write a handoff note (BANT summary + Notetaker link). Notify the AE with an @-mention.

If disqualified, set the Disqualification Reason, add Qualification Notes, and offer a polite off-ramp: "Based on what you've shared, it sounds like the timing isn't right — would it be OK if I checked back in [timeframe]?" Bad-timing and unresponsive leads auto-recycle into a 90-day follow-up.

Objection handling

Six objections you'll hear most. The principle behind every response: acknowledge, reframe, ask. Never argue; always redirect toward a question that reopens the door.

"We already have a solution." — "That makes sense — what are you using today? A lot of teams we work with started with [common tool] and hit a ceiling at scale. Has that been your experience?"

"We don't have budget." — "I appreciate the transparency. Some companies use this time to evaluate options so they're ready when budget opens up. Would it be useful to understand what's possible?"

"I'm not interested." — "Understood — you don't owe me an explanation. Is it the timing, or is this just not relevant for your team?"

"Send me some information." — "Sure — what's the best email? So I don't send anything irrelevant, can I ask a couple of quick questions about what you're working on?"

"We handle everything in-house." — "That's impressive. The question we usually hear from strong teams is around maintenance at scale — as you grow, does the team spend more time keeping things running than building?"

"I'm not the right person." — "No problem — could you point me toward whoever owns this area? Would it be OK if I mentioned you referred me?"

Inbound sequence — 14 days

For leads who filled out a form — they expect to hear from you, so move fast.

Breakup emails consistently get the highest reply rates of any email in a sequence — loss aversion works.

Outbound sequence — 21 days

For prospects the SDR sourced — they didn't ask to hear from you, so the motion is research-driven, low-pressure and curiosity-based.

Handoff checklist — SDR → AE

Before marking a lead Qualified and creating a deal, confirm: all BANT properties populated; BANT Score 3/4 or 4/4 (or 2/4 with Need + Timeline); Qualification Notes summarise the findings; contact record current; company record associated and populated; meeting booked on both calendars; lead tags updated; deal created with tags at birth (source, use case, competitive context, company size); AE notified with access to the full timeline.

The deal carries tags at birth — otherwise you'll spend the next quarter bulk-updating tags on closed-won deals to make the attribution report work.

Daily workflow + reporting

SDR daily structure — six hours of focused work in the Sales Workspace:

• 30 min — confirm booked meetings, send prep materials.
• 30 min — new prospects into sequences, account research.
• 60 min — morning call block (highest connect rates).
• 60 min — email follow-ups and sequence tasks.
• 30 min — more prospecting into sequences.
• 60 min — afternoon call block.

The seven reports that matter:

1. Lead velocity — new leads per week by source. A leading indicator: if it drops, pipeline dries up in 30–60 days.
2. Stage conversion funnel — New → Attempting → Connected → Qualified. Bottlenecks show up here first.
3. Speed to lead — MQL creation to first outreach. Target <5 min high-intent, <24h low-intent.
4. Qualification rate — % of connected leads that become Qualified. Benchmark 25–40%.
5. Disqualification reasons — feeds ICP refinement and marketing targeting.
6. Meetings booked — per SDR per week. The primary activity KPI.
7. Sequence performance — open, reply and meeting rate per sequence.

Common mistakes

• Skipping the Lead object. Creating deals directly from MQLs inflates the pipeline, tanks close rates and makes SDR activity invisible.
• Lifecycle-as-status confusion. Overloading lifecycle stage with operational values makes dashboards unreadable.
• Scoring without decay. Stale MQLs pile up and SDRs waste hours working dead records.
• Treating BANT as a survey. Reading questions off a script collapses the conversation — BANT is a guide, not an interrogation.
• No recycle loop. Bad-timing disqualifications stay dead forever, and you lose the ~30% who'd buy six months later.
• Playbook without adoption. A beautiful playbook no SDR opens is a PDF with extra steps — monitor adoption weekly.

Where this approach doesn't fit

Pure product-led motions (self-serve signup is the qualification mechanism) — PQL scoring plus a light sales-assist layer is the model. Very low ACV, high volume (under ~$5k ACV, hundreds of deals a month) — manual BANT doesn't pay for itself; go inbound → demo → close, heavily automated. No Sales Hub Pro — the Lead object, Playbooks and Sales Workspace all require Professional or higher. No dedicated SDR function — if AEs prospect and qualify themselves, collapse to MQL → SQL in a single motion.

Conclusion

The complete HubSpot SDR playbook is three layers, built in order: the foundation (forms, scoring, lifecycle, Lead object), the system in HubSpot (pipeline, properties, Playbooks, Sales Workspace), and the daily motion (the call, the sequences, the handoff). Don't build it all at once — build the layers in order, because each one makes the next work.

If your SDR team is running HubSpot and the system feels like it's held together with Slack reminders and individual heroics, the fix is architectural, not more effort.