The Complete HubSpot SDR Playbook: From MQL to SQL

The best SDR in the world will miss quota if the lead pipeline is a mess, the scoring model inflates MQL counts, the Lead Object isn't set up, there's no playbook on the record, and every call starts with "let me pull up your info" while the prospect waits on the line.

Three parts:

1. The foundation — forms, scoring, lifecycle, and the Lead Object. What has to be true upstream before an SDR does anything.
2. The SDR system in HubSpot — lead pipeline, BANT properties, the HubSpot Playbooks tool, and the Sales Workspace where your team actually lives.
3. The daily motion — the call, the sequences, objection handling, and the handoff to the AE.

Built for B2B teams on Sales Hub Professional or Enterprise. Opinionated, HubSpot-native, no competing tools pushed.

Let's get into it.

Part 1 — The foundation

Before we talk about SDRs, we have to talk about the marketing plumbing that feeds them.

If the lead management architecture upstream is broken, even a perfect SDR motion won't hit quota. Garbage MQLs in, garbage pipeline out.

This part is tight — four sections — because the full marketing-side depth lives in [our attribution pillar]. What follows is the minimum an SDR team needs in place to function.

What lead management in HubSpot actually means

Lead management in HubSpot lives across three objects and two property stacks.

Most teams conflate them. That's the first mistake.

The three objects:

• Contact — a person. Every human you've ever captured an email from lives here.
• Lead — a separate CRM object (Sales Hub Pro and up), used as a working record for SDRs before a deal exists.
• Deal — a revenue opportunity. One contract, one company, one sales cycle.

The two property stacks:

• Lifecycle stage — sits on the contact. Strategic. Owned by the whole GTM team.
• Lead status — sits on the lead record. Operational. Owned by the SDR.

Lifecycle stage and lead status are not the same thing.

A contact can be an MQL (lifecycle) with a lead status of Attempting (operational). A contact can be an Opportunity (lifecycle) with no lead record at all, because the deal came in through a partner referral.

Teams that treat lead status as a substitute for lifecycle stage end up with ambiguous dashboards.

Teams that treat lifecycle stage as a substitute for lead status end up with SDRs who have no working queue.

You need both. On different objects. With clear owners.

The lifecycle model

The lifecycle model we recommend for B2B teams:

Lead → MQL → SQL → Opportunity → Customer → Advocate

No Subscriber. Remove it. Every new contact enters as 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, booked a meeting with an AE, prospect attended. Auto-flips one day after the meeting. AE can flag back if the meeting 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 HubSpot portals with 565 of them — most auto-collected from website form tags, or duplicated by well-meaning marketers who didn't know one already existed.

The principle is simple: as few forms as possible. One form per asset type, reused across every landing page that needs it.

One newsletter form — used on every page that captures newsletter signups. One content download form — used on every gated guide, ebook, and checklist. One demo request form — used on every "request a demo" CTA across the site.

Six to ten core forms covers most B2B teams:

• Newsletter (+5, sets Lead)
• Content download (+10, sets Lead)
• Webinar registration (+10 registration / +15 attendance, sets Lead)
• Contact / general inquiry (+15, sets Lead)
• Talk to sales (+25, auto-MQL if Sales selected)
• Demo request (+25, auto-MQL)

Hidden fields on every form — non-negotiable: lifecycle stage plus all five UTM parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term).

Without these, you can't report on campaign-level attribution or auto-set MQL status from high-intent submissions.

The full UTM treatment lives in our marketing attribution pillar. For the purposes of this playbook: 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 this wrong and they work junk all day.

Five design decisions.

1. Combined score — not just engagement.

Build a score from two dimensions: engagement (what they do) + fit (who they are). Engagement alone means journalists and students hit your MQL threshold. Fit alone ignores buying intent.

2. Score groups with limits.

Five groups, each capped:

• High-Intent Conversions (cap 25) — demo request, talk to sales, pricing + form.
• Content Engagement (cap 30) — downloads, webinars, email clicks.
• Website Activity (cap 15) — product page views, pricing page views, return visits.
• Job Title Fit (cap 15) — Decision Maker (+15), Champion (+10), Influencer (+5).
• Company Fit (cap 20) — business email, target industry, target account membership, company size.

Total: 105 points. MQL threshold: 26.

3. Score decay.

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, no decay on fit.

Most HubSpot portals have ~3,000 MQLs sitting stale. 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 form 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 — high-intent and low-intent.

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

Foundation done. Now let's build the SDR system on top of it.

Part 2 — The SDR system in HubSpot

This is where HubSpot's sales-side tools — the Lead Object, pipelines, custom properties, Playbooks, and Sales Workspace — turn the foundation into a daily working system for your team.

The lead pipeline — 5 stages

HubSpot's Lead Object (Sales Hub Pro and up) is the most underused piece of the CRM.

Before it existed, SDRs worked out of the contact record or — worse — straight out of the deal pipeline. Unqualified prospects inflated the deal count. Close rates looked worse than they were. SDR activity was invisible in deal reports.

The Lead Object fixes all of that.

A lead record is auto-created when a contact's lifecycle flips to MQL. A workflow assigns it to an SDR and notifies them.

The five stages:

New → Attempting and Attempting → Connected are automated on activity. The move to Qualified stays manual — it requires SDR judgment, and BANT properties must be populated first.

Lead tags

Each lead record should be tagged at creation. 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."

Pipeline 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 when email reply received, call outcome = Connected, or meeting outcome = Completed.
• Create a lead for follow-up 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, Sales Manager, and leadership. Create a 24-hour task for the AE. Set contact lifecycle = SQL one day post-meeting (with the AE flag-back option).
• On Disqualified: set contact lifecycle back to Lead — unless reason = Wrong industry or Too small (those stay disqualified permanently). If reason = Bad timing, enroll in a 90-day nurture sequence.

BANT as custom properties

Qualification lives on the Lead Object as custom properties. Create these under Settings → Objects → Leads → Properties.

B — Budget:

A — Authority:

N — Need:

T — Timeline:

Scoring & qualification:

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, vendor 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 qualification framework into an interactive card SDRs see directly on the lead record. They open it during the call, fill in BANT answers, and properties update automatically — no separate admin step.

Requirements: Sales Hub Professional or Enterprise, assigned Sales seat, Publish/Write playbooks permissions.

The 6-step build:

1. Create the playbook. CRM → Playbooks → Create playbook → Sales playbook template. Name it SDR BANT Qualification Playbook.

2. Build the content. In the Write tab, add the opening talk track as formatted text. For each BANT question, click the Question icon, set Answer type = "Update a property," and link to the corresponding lead property (e.g., the "biggest headache" question links to primary_pain_point). The SDR's answer writes straight to the property.

3. Configure settings. Settings tab → check Log playbook submissions. Engagement type = Call. Default call type = Qualification (so logged calls are tagged correctly in reporting).

4. Set recommendation rules. Settings tab → Recommendation Settings → Create rule with filters like "Lead Status is New or Attempting or Connected." The playbook now auto-surfaces on matching records.

5. Add the Recommended Playbook card to record views. Settings → Data Management → Objects → Leads → Default view → Add card → search Recommended Enablement → drag to the top of the middle column.

6. Publish and train. SDRs now see the playbook at the top of every matching lead record. All notes and property updates save automatically as they work through it.

Track adoption under CRM → Playbooks → Analyze. Views, active users, per-SDR usage. A playbook that isn't used doesn't exist.

Sales Workspace — where SDRs actually work

Everything above lives somewhere. That somewhere is the Sales Workspace.

Sales Workspace (Sales Hub Pro and up, assigned Sales seat required) is HubSpot's dedicated interface for SDRs and AEs. Not the general CRM view. Not the contact index. A purpose-built workspace that brings tasks, leads, deals, sequences, meetings, and AI-prioritized guided actions into one home.

This is where your SDRs should live from 9am to 5pm. Every tab they don't work out of is friction your process is paying.

The tabs that matter for SDRs:

• Summary tab — daily hub. Tasks due today, sequence tasks, guided actions, upcoming meetings, a feed of prospect activity. Open this first every morning.
• Prospects → Leads — the active working queue. Every lead assigned to the SDR, filterable by stage, source, activity, and custom properties.
• Schedule tab — meetings with full context. Attendee details, past interactions, AI-generated summaries, one-click join. Prep time compresses from 10 minutes to 2.
• Feed tab — real-time engagement alerts. Email opens, link clicks, website visits, document views. Time your outreach to when interest is hot.

Saved views every SDR team should create:

• My New Leads — Stage = New, Owner = Me. Work this first every morning.
• Needs Follow-Up — Stage = Connected, last activity > 3 days. Re-engage or move on.
• Inbound Hot — Tag = Inbound, created < 24h. Speed-to-lead queue, worked in real time.
• Stale Attempting — Stage = Attempting, last activity > 7 days. Re-engage or disqualify.
• Recycled for Follow-Up — Tag = Recycled, last engagement > 90 days. Time to re-engage.

Guided actions worth paying attention to:

HubSpot auto-generates AI-prioritized next actions based on pipeline state:

• Newly assigned leads — new leads in the queue.
• Leads awaiting your reply — the prospect replied, you haven't.
• Sequence activity — sequence tasks are due today.
• Recently engaged leads — a lead showed activity in the last 7 days.
• Upcoming meeting preparation — meeting starts in 1 hour.
• Follow-up on your meeting — a meeting ended, no follow-up task yet.

These aren't gimmicks. Used correctly, they end the "what should I work on next?" decision fatigue that kills SDR productivity in the second half of the afternoon.

If your team is on Sales Hub Pro and isn't living in Sales Workspace, the problem isn't the tool. It's the setup. Book a Sales Workspace audit with Superwork — we'll configure the saved views, guided actions, recommended playbook cards, and daily workflow your team should run.

Part 3 — The daily motion

The foundation is built. The Lead Object is wired. Sales Workspace is configured. The playbook is live on every matching record.

Now the SDR actually works.

Pre-call checklist

Tools & environment — confirm before the call:

• HubSpot open on the contact/company record. Name, title, company, prior activity, form submissions.
• Outlook or Google Calendar integration active — you'll need to offer meeting slots live.
• HubSpot Sales Notetaker active and in the meeting room. Tell the prospect the call may be recorded.
• This playbook open in the HubSpot sidebar — talk track and property updates from 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 postings.
• Lead source and conversion context — what did they download, attend, or request? Reference it in your opener.
• Existing HubSpot activity — page views, email opens, prior calls. Know what they've already seen.
• AE calendar availability — so you can offer concrete slots if they qualify.

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. Skip the weekend. Three steps, about 90 seconds total.

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. Let them tell you what matters.

Step 2: Go straight into the problem.

Based on 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 / managing reporting across disconnected tools / trying to reduce churn]. Can you walk me through what's happening today?"

You're not asking to learn. You're showing you already know. Trust compounds from there.

Step 3: Mirror and frame.

Reflect their pain back better than they said it. Then set the structure:

"So it sounds like [your team is spending half its time on manual processes instead of selling / you're stitching together five tools and nothing talks to each other]. Is that right?"

After they confirm:

"OK — 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."

Wait for a verbal "yes." 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 to handle [their core challenge]?"
• "How much of that is manual vs. automated?"
• "What's the biggest headache for you or your team right now?"
• "How big is the team that manages this, and where do they spend most of their time?"
• "If you could fix one thing about how this works today, what would it be?"

T — Timeline (next):

• "Is this something you're actively looking to change, or more of a long-term consideration?"
• "What triggered you to start thinking about this now?"
• "Are you evaluating other solutions alongside this?"

B — Budget (third, gently):

• "Has the team allocated budget for a project like this, or is that still being determined?"
• "Do you have a sense of what you're currently spending in this area — tools, people, maintenance?"

If they're uncomfortable, don't push. Mark Budget as Unknown and move on.

A — Authority (last):

• "If you decided this was worth pursuing, who else would need to be involved in that decision?"
• "Is there an executive sponsor who would champion a project like this?"
• "Does your company have a standard procurement process — IT security review, RFP, board approval?"

The ask

If BANT looks promising (3/4 or better), ask for the AE meeting. Frame it 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, so you can review your options? Maybe [Day] or [Day]?"

Two follow-ups that dramatically improve show rates:

"Is there anyone else who cares about this that you'd want to invite?"

"If your schedule changes and you can't make it, will you please let me know?"

The second is a psychological commitment device. It reduces no-shows measurably.

If qualified → book the AE meeting

1. Move the lead stage to Qualified. Populate any missing BANT properties.
2. BANT Score auto-sets via workflow.
3. AE review task auto-creates (24-hour SLA).
4. Send the calendar invite titled "Exploring [solution area] options for [Company]."
5. Include an agenda + one relevant resource in the invite.
6. Create a handoff note on the contact or company record — BANT findings summary, Notetaker recording link.
7. Notify the AE on Teams or Slack with an @-mention.

If disqualified → polite off-ramp

"I appreciate you taking the time to walk me through this. Based on what you've shared, it sounds like [the timing isn't right / your current stack is handling things well / this isn't a priority]. I completely understand. Would it be OK if I checked back in [timeframe] in case anything changes?"

1. Set Disqualification Reason.
2. Add notes to Qualification Notes.
3. Move the lead to Disqualified.
4. If reason = Bad timing or Unresponsive, automation creates a recycled lead for 90-day follow-up.

Objection handling

Six objections you'll hear most. 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. Out of curiosity, what are you using today? A lot of teams we work with started with [common tool] and found they 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 at least understand what's possible?"

"I'm not interested."

"Understood. You don't owe me an explanation. Is it the timing, or is this not relevant for your team?"

"Send me some information."

"Sure — what's the best email? Just so I don't send anything irrelevant, is it OK if 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 the business grows, does the team spend more time keeping things running than building new things?"

"I'm not the right person."

"No problem at all. Could you point me toward the person who 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. Move fast.

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

Outbound sequence — 21 days

Prospects the SDR sourced. They didn't ask to hear from you. The motion is research-driven, low-pressure, curiosity-based.

Handoff checklist — SDR → AE

Before marking a lead as Qualified and creating a deal, the SDR confirms:

• All BANT properties populated
• BANT Score = 3/4 or 4/4 (or 2/4 with Need + Timeline)
• Qualification Notes summarize key findings
• Contact record current (title, phone, email confirmed)
• Company record associated and populated (industry, size, website)
• Meeting booked on both calendars
• Lead tags updated (source, use case, competitive context)
• Deal created with tags at birth (source, use case, competitive context, company size)
• AE notified, with access to the full lead 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.

If you want to pressure-test your SDR handoff before your next pipeline review, book a working session with Superwork — we'll audit 10 recent SDR-to-AE handoffs against this checklist and show you where the leaks are.

Part 4 — Daily SDR workflow

Daily workflow + reporting

SDR daily structure — six hours of focused work in 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 7 reports that matter:

1. Lead velocity — New leads per week by source (inbound vs. outbound). 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 — Avg time from 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 — Pie chart. Feeds ICP refinement and marketing targeting.
6. Meetings booked — Per SDR per week. Primary activity KPI.
7. Sequence performance — Open rate, reply rate, meeting rate per sequence. Tells you which messaging is working.

Common mistakes

Skipping the Lead Object. Creating deals directly from MQLs. Pipeline inflates. Close rates tank. SDR activity becomes invisible.

Lifecycle-as-status confusion. Overloading lifecycle stage with operational meaning. "Open" and "In Progress" start appearing as lifecycle values. Dashboards become unreadable.

Scoring without decay. Stale MQLs pile up. SDRs waste hours working dead records. The MQL count brag is a vanity metric.

Treating BANT as a survey. Reading questions off a script like a form. The conversation collapses. BANT is a conversation guide, not an interrogation.

No recycle loop. Bad-timing disqualifications stay disqualified forever. You lose the 30% who would have bought six months later.

Playbook without adoption. Shipping a beautiful HubSpot playbook that no SDR opens. Monitor adoption weekly under Playbooks → Analyze. A playbook that isn't used is a PDF with extra steps.

Where this approach doesn't fit

Pure product-led motions. If self-serve signup + product usage is your qualification mechanism, this SDR playbook is overkill. PQL scoring + a lightweight sales-assist layer is the model.

Very low ACV, high volume. Under $5k ACV and hundreds of deals a month, the overhead of manual BANT doesn't pay for itself. You want inbound → demo → close, heavily automated.

No Sales Hub Pro. The Lead Object, Playbooks, and Sales Workspace all require Sales Hub Professional or higher. Without it, you lose the object separation, the interactive playbook card, and the workspace itself. On Starter, much of Part 2 doesn't apply.

No dedicated SDR function. If AEs prospect and qualify themselves, collapse to MQL → SQL in a single motion. The Lead Object is less valuable when one person owns the whole flow from MQL to close.

Conclusion

The complete HubSpot SDR playbook is three layers, built in order:

1. The foundation — forms, scoring, lifecycle, Lead Object.
2. The system in HubSpot — pipeline, properties, Playbooks tool, Sales Workspace.
3. The daily motion — the call, the sequences, the handoff.

Don't try to build it all at once. Build the layers in order. Each layer makes the next one 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.

Get a free audit of your HubSpot SDR setup with Superwork. We'll walk through your Lead Object configuration, BANT properties, Sales Workspace setup, and SDR sequences — and give you a prioritized list of what to build first.