RevOps Playbook: Lead Assignment, MQL/SQL Handoff, and Pipeline Hygiene Across HubSpot and Salesforce

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.

The fastest way to lose revenue is a fuzzy handoff. This playbook defines a precise contract for MQL creation in HubSpot, assignment and acceptance in Salesforce, and the hygiene rules that keep pipeline trustworthy. You will learn how to design assignment rules, instrument SLAs, and enforce quality signals without slowing reps down.

Make handoffs boring (and fast)

Handoffs succeed when they are simple, observable, and owned. Marketing knows exactly when a record becomes an MQL; Sales knows exactly when and how to accept or reject it; and RevOps sees the metrics that prove the loop is healthy.

Defining MQL and SQL

Start with a crisp definition:

MQL: a contact meeting ICP fit and intent thresholds with consent; created in Salesforce as a Lead or Contact with clear source fields and campaign association.
SQL: an accepted, sales‑validated MQL with documented pain, timeframe, and authority; either an accepted Lead (Lead Status = Accepted) or a Contact with an associated Opportunity.

Record MQL/SQL timestamps and the actor (automation vs. user). These timestamps fuel SLA tracking and funnel analytics.

Assignment design

Route based on territory, segment, product, and channel. Keep rules declarative and config‑driven so RevOps can evolve them without code.

Practical patterns

Territory mapping tables keyed on country/state + segment.
Round‑robin pools per segment/product with vacation logic.
Named accounts and ABM lists with explicit owner overrides.

Acceptance and recycling

Require reps to accept or reject within an SLA (e.g., 24 hours). Rejections must include a reason code; rejected MQLs recycle to nurture or enrichment tracks in HubSpot.

SLA instrumentation

Measure time‑to‑first‑touch and time‑to‑acceptance from the MQL timestamp. Alert on SLA breaches by team and geography. Publish weekly scorecards showing acceptance rates, speed, and conversion to SQL and Opportunity.

Pipeline hygiene rules

Healthy pipeline is a product of clear expectations:

Stage definitions with entry/exit criteria.
Mandatory next step and close date accuracy for forecastable stages.
Opportunity contact roles for each buying committee member; minimum data quality thresholds for stage advancement.

Campaign association and attribution

Ensure every MQL and Opportunity is tied to a primary campaign and relevant touches. HubSpot manages engagement depth; Salesforce Campaign Influence models the revenue view. Keep a shared taxonomy for offers, channels, and quarters so dashboards line up.

Runbooks

MQLs are created but not routed

Check assignment rules and pool capacity. Validate that the integration is writing the correct routing keys (segment, country/state). If routing is paused, queue MQLs and backfill once rules are live.

Reps aren’t accepting within SLA

Expose SLA timers on list views, coach on workflow shortcuts, and use manager dashboards. Automate reminders and escalate on chronic breaches.

Pipeline stages are stale

Require a next step for forecastable stages and alert on inactivity windows. Partner with sales leadership to align accountability with compensation.

Governance and continuous improvement

Hold a weekly RevOps + Sales sync reviewing acceptance rates, recycling reasons, and stage leakage. Monthly, audit assignment rules against headcount and territory changes. Quarterly, re‑validate MQL and SQL definitions against current segments and products.

FAQ

Should MQLs create Salesforce Leads or Contacts?

Either can work. If your org uses Leads, create MQLs as Leads and convert on acceptance. Contact‑only orgs should directly create Contacts under Accounts with clear lead status equivalents and timestamps.

Who owns the assignment rules?

RevOps owns the rules, with Sales leadership approving segment and territory policies. Publish the rules and change logs to reduce confusion.

How do we handle named accounts?

Override territory pools for named accounts and ABM lists; route directly to the account owner and ensure campaign influence is attributed.

What’s a good SLA for acceptance?

Common targets are 4 business hours for inbound and 24 hours for all MQLs. Tune by segment and region, then coach to the metrics.

How do we stop junk MQLs?

Tighten ICP filters and bot/role suppression, add required fields to forms, and require disqualification reason codes with a feedback loop to marketing.