RevOps Playbook: Lead Lifecycle, Routing, and Handoff from HubSpot to Salesforce

Marketing creates readiness. Sales creates revenue. The seam between the two—the moment a person becomes truly sales‑ready and gets routed—is where most funnel leakage occurs. This playbook defines an end‑to‑end operating model for MQL thresholds, sales acceptance (SAL/SQL), routing, SLAs, and the operational telemetry that keeps teams accountable across HubSpot and Salesforce.

We’ll standardize the lifecycle semantics, codify routing rules, and specify the observable signals that prove the handoff worked. The outcome is predictable conversion rates, shorter time‑to‑first‑touch, and a shared understanding of quality.

Lifecycle Semantics That Don’t Drift

Lifecycle must reflect business intent, not just tool defaults.

Lead (HubSpot): a known person with minimally viable data (email, name) and consent to process; not necessarily sales‑ready.
MQL (HubSpot): exceeds a quantitative score threshold and satisfies qualitative rules (ICP fit, intent, eligible region). Stamp MQL_Date.
SAL/SQL (Salesforce): sales accepts responsibility and confirms qualification criteria; stamp Sales_Accepted_Date and/or mark status as Working/Qualified per your model.
Opportunity (Salesforce): a real commercial engagement exists; mirror to HubSpot for reporting.
Customer (Salesforce): closed won; mirror to HubSpot for lifecycle.

Avoid collapsing SAL and SQL; they measure different things (acceptance vs. qualification). Use separate stamps to analyze latency and fallout.

Scoring Meets Rules: How MQLs Are Decided

Build MQL on two pillars: behavior (intent) and profile (fit). Behavior is clicks, visits, content consumption, and product usage; profile is title, seniority, industry, company size, region.

Recommended pattern:

Points‑based behavioral score in HubSpot (decay older activity).
Discrete fit grade (A–D) or numeric fit score based on firmographics and title.
MQL when behavior ≥ threshold AND fit ≥ threshold AND no blocking rule (e.g., student email) applies.

Keep the scoring model small; it’s a prioritization mechanism, not a crystal ball. Review quarterly against outcomes (MQL→SAL→Opp).

Routing Policy

Routing turns an MQL into a sales task. Encode rules that reps can understand:

Ownership: route by named territory or round‑robin pool. Respect account ownership: if an Account/Contact already exists, route to the owning team automatically.
Fairness: use round‑robin with hold‑out windows; if a rep does not touch the lead within SLA, re‑route.
Special handling: partner leads, strategic accounts, and product‑qualified leads (PQLs) may bypass normal pools to specialized teams.

In HubSpot, routing can occur via workflows that set interim owner fields. Confirm in Salesforce via an Apex or Flow step that writes final OwnerId. This prevents tools from silently fighting over ownership.

Handoff Contract and SLAs

Define SLAs as a contract across teams:

Marketing guarantees MQLs meet the definition and include key context (source, campaign, last activity, fit grade).
Sales guarantees touch within X business hours and a disposition within Y days (Working, Nurture, Disqualified, or Converted).
Operations guarantees the sync and routing pipeline remains under Z minutes and monitors exceptions.

SLAs must be visible in dashboards that leadership reviews weekly. Misses trigger retrospectives and adjustments.

Disposition Model

Keep dispositions simple and meaningful:

Working: active attempt to engage; not yet qualified.
Qualified: meets your BANT/MEDDICC or equivalent threshold and is moving to Opportunity.
Nurture: not ready; specify a reason (timing, budget, wrong role), then hand back to HubSpot nurture tracks.
Disqualified: never a fit; include a standardized reason.

Dispositions are Salesforce‑owned. HubSpot consumes a summarized view for segmentation and reporting but does not overwrite them.

Opportunity Creation Triggers

Choose one of two consistent triggers:

Sales‑driven: on disposition Qualified, create Opportunity with a minimal top‑of‑funnel stage.
Event‑driven: certain product or sales events (signed NDA, accepted proposal) create the Opportunity automatically.

Always link the Contact Role and Account; stamp the shared external key so HubSpot Deals mirror the Opportunity.

Nurture Return Loop

Most MQLs won’t become SQLs on first pass. Treat “Nurture” as a safe harbor, not a graveyard:

When a record is dispositioned to Nurture, HubSpot enrolls it into the appropriate program (based on role, industry, last content).
If engagement resumes, re‑raise to sales with a new SLA clock and a Re‑MQL stamp for cohort analysis.

Observability: Proving the Handoff Works

Instrument a handful of timestamps and counters:

MQL_Date (HubSpot), Sales_Accepted_Date (Salesforce), First_Touch_Timestamp (Sales rep’s first task/call), Opportunity_Created_Date.
Time deltas: MQL→First Touch, MQL→SAL, SAL→Opp medians and 90th percentiles.
SLA misses by rep and by segment.

Pair these with funnel counts (MQLs, SALs, SQLs, Opps) by channel and program. Use the same definitions in both systems so the numbers reconcile.

Governance and Change Cadence

Evolve your lifecycle in small, well‑documented steps:

Monthly operational run‑through: sample 50 dispositions for accuracy; review SLA misses and routing exceptions.
Quarterly scoring tune‑up: adjust weights, thresholds, and fit drivers based on conversion outcomes.
Semiannual policy review: confirm definitions with sales leadership; update documentation and training.

Anti‑Patterns

Avoid these drift‑inducing behaviors:

Constantly changing MQL rules without communicating to sales; it ruins trust and makes trends meaningless.
Using dozens of dispositions that reps can’t remember; they become meaningless.
Letting HubSpot overwrite Salesforce ownership and statuses; creates silent conflicts and audit gaps.

FAQ

Should we route at the Contact, Lead, or Account level?

Route where your sales team works. If you use Leads for inbound and convert later, route Leads. If you run a contact‑only model, route Contacts. Always check for an existing Account and route to its owner if present to avoid collisions.

How fast should our SLA be for first touch?

Within one business hour for high‑intent channels (demo requests, pricing page form fills) and same day for standard MQLs. Track median and 90th percentile to ensure speed is consistent, not just for the easy cases.

How do we prevent turf wars between SDR and AE?

Define ownership stages: SDR owns from MQL to SAL; AE owns from SAL/SQL to Opportunity. For named accounts, allow AE first right of refusal but enforce SLAs—if not accepted in time, SDR can work it.

Where should lead scoring live if product signals matter?

Keep the score in HubSpot for operational simplicity, but source product events into HubSpot via a sane, summarized schema (e.g., “Activated,” “Key Feature Used”). For advanced modeling, compute a supporting score in the warehouse and mirror a normalized value to HubSpot.

When should Opportunities be auto‑created?

Only for clear buying signals (contract requested, trial usage threshold met). Otherwise require rep confirmation to avoid inflating pipeline with fake opportunities.