Marketing hits its MQL target. Sales says the leads are rubbish. Both point at the other team, and the pipeline leaks in the gap between them. The marketing to sales handoff is where most B2B pipeline is lost.
This is the most common failure in a HubSpot portal, and it shows up the same way almost every time. The handoff exists on paper. It does not work in practice.
A broken handoff is rarely the only thing leaking. It is usually a symptom of RevOps being deferred rather than designed. Click here to read what delaying RevOps costs a startup.
The MQL to SQL handoff is the moment a lead marketing has qualified becomes a lead sales has accepted and owns. In HubSpot it is carried by two properties working together: Lifecycle stage moves the contact from MQL to SQL, and Lead status tracks what the rep does with it. A working handoff has an agreed definition, automated routing, a response SLA, and a feedback loop back to marketing.
A working MQL to SQL handoff has four parts: a definition both teams agreed, a routing rule, an SLA on speed, and a feedback loop. Most portals have one or two. Here is what each looks like when it is built properly.
An MQL that only marketing believes in is a scoring threshold and nothing more. Sales never agreed to it, so sales never treats it as qualified.
The fix is a shared definition. Sales and marketing agree what an MQL means in your business: the firmographic fit, the behaviour, the intent signals that make a lead worth a rep's time. You write it down. Both leaders sign it.
In HubSpot, the Lifecycle stage property carries this. The Lead, MQL, SQL and Opportunity stages should each have a one-line written definition, not a shared assumption. If three people describe an MQL three different ways, the handoff was broken before a single lead moved.
A definition holds when it sits inside an operating model both teams already run to, rather than a document one team wrote. Click here to read the RevOps framework we use with B2B SaaS teams.
The second failure is a handoff that depends on someone remembering. Lead routing in HubSpot exists to remove that step. A lead hits MQL, and a person is supposed to notice and assign it. Leads slip, and the ones that slip are the ones nobody chases.
Automate the assignment. In HubSpot, a workflow triggered on Lifecycle stage becoming MQL uses the Rotate record to owner action to distribute leads round-robin across a team, or route by territory, company size or product line. The lead lands with a named owner the moment it qualifies, with no human step in between.
Routing by real logic matters. A lead sent to the wrong rep, or to a general queue nobody owns, is a lead nobody works.
Most portals automate the move to MQL and leave SQL to a rep updating a dropdown when they remember. That is why MQL to SQL conversion reporting rarely holds up.
SQL means one thing: a rep has worked the lead and accepted it as worth pursuing. So the trigger should be an action the rep takes anyway, rather than a separate admin step. Two options that work:
Pick one and enforce it. Two paths to SQL means two definitions, and your conversion rate becomes an average of two different things.
If your portal has the Leads object and the prospecting workspace, the handoff has a second home. Leads sit between contact and deal, with their own stages, and give SDR work a place to live that Lifecycle stage was never designed for.
The trap is running both. Lifecycle stage says MQL, the Lead record says Attempting, and your reporting has two competing versions of the same funnel. Decide which object owns the pre-deal working state and make the other one follow it. For most teams under fifty people, Lifecycle stage plus Lead status is enough, and the Leads object earns its place once you have a dedicated SDR function.
A speed to lead SLA is the rule most portals never write down.
A qualified lead has a shelf life. In the portals we audit, the gap between a contact being created and a first meaningful sales touch often runs into weeks, and those leads convert at a fraction of the rate of the ones worked the same day. Most portals have no rule on this, so speed drifts.
Set an SLA and enforce it in the system. When the routing workflow assigns the lead, it should also create a task with a due date reflecting your SLA, whether that is one hour or one business day. Then add an escalation: if the task is not actioned in time, a delay branch fires a notification to the rep, then to their manager. The SLA stops being a guideline and becomes something the portal tracks.
Without enforcement, speed to lead is a target in a deck nobody is measured against.
Here is the part almost every portal misses. Sales works an MQL, decides it is not qualified, and marks it dead. Nothing flows back to marketing. So marketing keeps sending the same profile, sales keeps rejecting it, and neither team learns.
The Lead status property is where you close this loop. As a rep works a lead, they move Lead status through New, Attempting, Connected, and then either Open Deal or Unqualified. When a lead is marked Unqualified, capture the reason in a property, then use a workflow to route it: back into nurture if the timing was wrong, or flagged to marketing if the fit was wrong.
Make it a dropdown select rather than free text, or the data will be unreportable inside a month. Click here to read why the right CRM fields beat more fields.
The reason data is the asset here. It tells marketing which MQLs convert and which waste everyone's time, so the definition in part one gets sharper each quarter. A handoff without a feedback loop repeats itself every quarter. The reason data is what breaks that cycle.
Here is what breaks a well-built handoff six months after launch. Lifecycle stage in HubSpot moves forward. A contact rejected as Unqualified at MQL stays at MQL, so when they come back nine months later and fill in a demo form, the workflow triggered on Lifecycle stage becoming MQL never fires. They are already MQL. Nothing routes. Nobody calls.
Two things fix it:
Skip both and your best re-engagement signals land nowhere. The lead that came back on their own is usually the strongest one you get that month.
Lifecycle stage and Lead status are different properties doing different jobs, and conflating them breaks reporting.
Lifecycle stage tracks how far a contact has moved toward becoming a customer: Lead, MQL, SQL, Opportunity, Customer. It moves forward, rarely back.
Lead status tracks what the rep is doing right now with an MQL or SQL: New, Attempting, Connected, Unqualified. It cycles.
Use Lifecycle stage for the funnel and the handoff trigger. Use Lead status for the working state and the feedback loop. Mix them into one property, which many portals do, and neither your funnel reporting nor your rep activity reporting will hold up.
The full handoff, in the order to build it:
This runs on the properties you already have, configured to talk to each other. No new tool required.
The symptom tells you where to look.
Most portals fail two or three of these at once, and the order above is the order to fix them in. Routing on top of a definition sales never agreed only moves bad leads faster.
Pull your MQL to SQL conversion rate, then pull the average time between a lead hitting MQL and a rep's first action. If conversion is low and time to action is high, your handoff is leaking, and the routing and SLA steps above will recover most of it fast.
Recovering the leads you already generate is usually cheaper than adding capacity on top of a leaking funnel. Click here to read how to hit targets without adding full-time RevOps.
The handoff is a set of workflows that either fire or do not. A document in a shared drive proves nothing about what happens to a lead at 4pm on a Friday.
A RevOps Audit maps your full lead-to-opportunity flow: lifecycle definitions, routing logic, SLA enforcement and the feedback loop most portals are missing. You get a scored view and a prioritised roadmap in two weeks. Book a RevOps Audit at revopsconsulting.io.
Prefer senior hands on the build? Fractional RevOps embeds an operator to design and ship the handoff in your portal, right-sized to your stage.
Click here to read what to expect in your first 90 days with a fractional RevOps partner.