HubSpot–Salesforce Lead Lifecycle and MQL→SQL Handoff Playbook

Published by Bles Software, a custom software and AI company based in Yehud-Monoson, Israel, building web apps, AI agents and API integrations for clients in Israel, the US, the UK and the EU.

High‑velocity go‑to‑market teams win or lose on the seams: the moments when a visitor becomes a lead, a lead becomes an MQL, and Marketing passes the baton to Sales. This playbook gives you a durable, audit‑friendly lifecycle architecture across HubSpot and Salesforce so you can hit SLA, reduce response times, and keep funnel reporting consistent.

Outcomes to Target

Define success as measurable outcomes:

Median speed‑to‑lead under 5 minutes for MQLs during business hours.
SAL acceptance rate ≥70% with documented reasons for rejections.
SQL conversion rate benchmarked by segment; outliers trigger experiments rather than blame.
Funnel parity across HubSpot and Salesforce within 3% for MQL, SAL, SQL, Opp Created.

Canonical Lifecycle Definitions

Publish short, testable definitions:

• Lead: known person with consent tied to a Company or domain. • MQL: meets fit score threshold and intent threshold (behavioral score), or hits a fast‑track trigger (e.g., demo request). • SAL: accepted by Sales; routed and owned with a next step planned. • SQL: verified opportunity potential; typically after discovery call and qualification. • Opp Created: Opportunity opened in Salesforce with stage ≠ Prospecting only when a real chance exists.

These definitions should map to stored fields: HubSpot Lifecycle Stage, MQL Date, and Salesforce Lead Status/Contact Status plus Opportunity Stage.

Scoring and Triggers

Use a two‑dimensional scoring model: Fit × Intent.

• Fit Score combines firmographic and technographic attributes: industry, employee band, region, ICP tier, installed tech. • Intent Score tracks engagement signals: high‑intent pages, pricing views, repeat visits, email clicks, product usage trials. • Fast‑track MQL when a lead submits a demo request, pricing request, or equivalent high‑intent form.

Thresholds must be published, versioned, and reviewed quarterly with Sales.

Routing and Ownership

After MQL, route to the right owner within seconds. Recommended pattern:

• Round‑robin for in‑segment SMB; named account rules for mid‑market/enterprise. • Use Salesforce lead assignment rules or a routing app; write the owner to HubSpot for visibility. • Create a task automatically with SLA timer fields; if no action within SLA, escalate to a queue and notify a manager.

SAL Acceptance and Feedback Loop

Sales acceptance is not a black hole. Create an explicit feedback loop:

• SAL = Accepted when a rep schedules a meeting or logs a next step; set a SAL Accepted Date field in Salesforce and mirror it to HubSpot. • SAL = Rejected requires a reason picklist (e.g., No fit, No intent, Wrong geography, Student/test). Reasons inform scoring and campaign tuning. • Weekly RevOps reviews rejection patterns and proposes playbook tweaks.

SQL and Opportunity Creation

SQL should correspond to a real opportunity. Require a minimal set of fields at creation: Account, primary Contact, problem statement, next step, and expected value (or stage probability). Guard against “empty opps” by blocking creation without a meeting set or a discovery note.

Preventing Stage Ping‑Pong

Stage regression causes reporting chaos. To avoid:

• Lock Lifecycle Stage from moving backward automatically; allow a manual admin correction only. • Allow Salesforce to own Lead/Contact status once SAL; HubSpot can still promote to MQL earlier but cannot demote. • Build a “Stage Change Reason” field for any retrograde moves required by Sales and audit weekly.

Reporting That Sales Will Trust

Show the same story in both systems:

• HubSpot: MQL volume and velocity (speed‑to‑lead), campaign impact, and assisted touches. • Salesforce: SAL/SQL rates, opportunity creation, and pipeline from accepted leads. • Reconcile weekly; if drift exceeds 3%, raise an alert and investigate mapping or process changes.

Enablement and Change Management

Document lifecycle definitions in a 2‑page playbook. Train Sales on SAL/SQL criteria with short Loom walkthroughs. Any change to scoring thresholds or fast‑track triggers goes through the weekly change board with test results and a rollback plan.

Minimal Data Model

• HubSpot: Lifecycle Stage, Fit Score, Intent Score, MQL Date, Fast‑Track Reason, Owner, Original Source, UTMs. • Salesforce: Lead Status, Contact Status, SAL Accepted (date, user), SQL date, Opportunity fields, Owner. • Shared: Account Tier, Industry, Region, Product Interest, Inferred Intent topics.

FAQ

What SLA should we target for MQL response?

Five minutes during business hours. Outside hours, set expectations and route to a follow‑the‑sun team or an on‑call rotation if the motion demands it.

Should we still use Salesforce Leads or go Contact‑only?

Either works if it’s documented. Contact‑only simplifies conversion but requires routing rules that assign Contacts directly. Leads are fine when you need the classic qualification workflow.

How often should we revisit scoring thresholds?

Quarterly by default, earlier if conversion rates drift. Use SAL reasons and SQL hit rates to tune.

Can Marketing move a record from SAL back to MQL?

No. After SAL, only Sales can change status, and only forward. If a lead wasn’t ready, reject with a reason so Marketing can nurture with the right track.

How do we keep HubSpot and Salesforce counts in sync?

Publish a weekly parity report that compares MQL, SAL, SQL, and Opp Created between systems. Investigate any metric with >3% drift; it’s usually mapping or workflow timing.