Lead Lifecycle, MQL/SQL, and Attribution Across HubSpot + Salesforce: A RevOps 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.

Lifecycle, qualification, and attribution tie together how demand is captured, how sales acts, and how revenue is reported. If these concepts diverge between HubSpot and Salesforce, you get frustrated teams and unreliable dashboards. This playbook aligns lifecycle definitions, MQL/SQL criteria, and attribution so marketing and sales can operate as one system.

Lifecycle Definitions That Hold Up in Both Systems

Write lifecycle states as operational definitions, not just labels. Define the event that moves a record forward, who is responsible, what fields must be set, and which automations fire. Keep the sequence simple and universal across business units to prevent cross‑system drift.

MQL and SQL Criteria

MQL should represent sales‑worthy interest; SQL should represent real sales engagement with a defined next step. Calibrate with data and feedback: if acceptance rates are low, tighten sources; if speed‑to‑lead is slow, simplify routing and notifications. Publish the rules and examples so everyone can audit outcomes.

Handoff, SLAs, and Feedback Loops

Handoff fails without explicit SLAs. Define time‑to‑first‑touch, acceptance windows, and what happens when time is exceeded. Close the loop with disqualification reasons that map back to campaign and content improvements, not just pipeline hygiene.

Attribution That People Believe

Pick a model that matches your motion—position‑based or time‑decay for multi‑touch is common. Standardize UTM governance and campaign association so the same touches appear in both HubSpot and Salesforce. Reconcile differences in object ownership by deciding where campaign membership lives and who updates it.

Reporting Alignment

Decide on system‑of‑record per metric and document it in the dashboard description. Compare key funnel counts and conversion rates across systems monthly. Investigate deltas like scientists: assume a contract break or a timing issue until proven otherwise.

Enablement and Change Management

Teach sellers how lifecycle and qualification interact with their daily actions. Short videos that show “what happens when I change this status” build trust fast. Hold monthly office hours for questions and suggestions.

FAQ

Where should lifecycle live—HubSpot or Salesforce?

Keep lifecycle in HubSpot for marketing control with a mirrored field in Salesforce for reporting and automations. Keep opportunity stages in Salesforce and mirror to HubSpot as read‑only.

How strict should MQL criteria be?

Strict enough to earn sales attention but flexible enough to adapt. Track acceptance rate and speed‑to‑lead; adjust criteria when those leading indicators degrade.

How do we resolve reporting differences?

Standardize definitions and timing windows, then audit key reports monthly. Most differences come from timing, object ownership, or picklist drift rather than true logic gaps.

Which attribution model is best?

Use the simplest model that helps you decide budget allocation with confidence. Position‑based often works well for mixed inbound/outbound motions; time‑decay helps long cycles.

How do SLAs actually stick?

Instrument them. Surface SLA compliance on team dashboards and hold short weekly reviews. Make exceptions rare and explicit.