[object Object]

A weekly funnel review opens with marketing reporting 412 MQLs and sales claiming they only saw 188 worth a follow-up. Both numbers come from HubSpot. The disconnect traces to a lifecycle stage definition nobody agreed to in writing and a workflow that auto-promotes anyone who downloads two assets. Lifecycle stages only work when the definitions are crisp, the automation is transparent, and both sides accept the rules.

The default stages

Subscriber  -> opted into communication only
Lead         -> identifiable, no qualification
MQL          -> marketing-qualified per defined criteria
SQL          -> sales has accepted and is working
Opportunity  -> deal record exists in active stage
Customer     -> closed-won deal
Evangelist   -> active referrer or reference customer
Other        -> none of the above

These represent a buyer journey from awareness to advocacy. Most teams need exactly these eight; resist the urge to invent new stages until you can prove the existing ones cannot answer your question.

Customization on Enterprise

Enterprise unlocks custom lifecycle stages. Even there, think before changing — every existing report, integration, and workflow references the defaults. A new “Pre-MQL” stage looks innocent and breaks every conversion report that compares Lead to MQL.

Safe additions:
  - Stages added at the end of the funnel (e.g., "Renewal Risk")
  - Stages that don't break sequence ordering

Risky additions:
  - Stages between existing default stages
  - Renaming defaults (alias-only, never replace)

Automated transitions

Workflows advance lifecycle stage based on behavior or thresholds. Keep the rule set short and visible:

Lead -> MQL when:
  Engagement score >= 60 AND
  Fit score >= 50 AND
  Has provided email + company

MQL -> SQL when:
  Sales accepts (button click on rep view) OR
  Demo meeting booked AND held

SQL -> Opportunity when:
  Deal created with stage past Qualified

Opportunity -> Customer when:
  Any deal closed-won

Backwards transitions (SQL back to MQL when sales rejects) belong in the workflow too. Sales rejection without a backstop creates contacts permanently stuck at SQL.

The MQL definition that ends the argument

Document the MQL criteria in one paragraph that both marketing and sales sign:

An MQL is a contact who:
  - Has provided business email and company
  - Has lifecycle fit score >= 50 (matches ICP)
  - Has engagement score >= 60 (3+ qualifying touches in 30 days)
  - Is not a current customer
  - Is not on the do-not-contact list
The MQL definition is reviewed quarterly by marketing and sales leadership.

Pin the document inside HubSpot in the lifecycle stage description so anyone investigating finds it.

Reporting that surfaces leaks

Funnel report:
  Lead         100%
  MQL          42%   (lead -> MQL conversion)
  SQL          28%   (MQL -> SQL conversion)
  Opportunity  62%   (SQL -> Opportunity)
  Customer     22%   (Opportunity -> Customer)

A 28 percent MQL-to-SQL conversion rate that drops to 12 percent month over month is the single most useful early signal of a misaligned definition. Investigate before chasing top-of-funnel volume to compensate.

Reverse handoff and SQL rejection

When sales rejects an SQL, the contact should not silently revert to a state that re-promotes them next week. Capture rejection reason and route to a nurture path:

SQL rejected workflow:
  Capture: rejection reason (dropdown, required)
  Set:     lifecycle = MQL (back to nurture)
  Suppress: do not re-promote for 90 days
  Enroll:  educational nurture per rejection reason

Governance cadence

Quarterly review with both teams: actual conversion rates, MQL definition tuning, rejection-reason patterns, and any process change since last review. Without this cadence, the definition drifts and the argument resumes.

What to do this week

Document your MQL definition in one paragraph, paste it into the lifecycle stage description, audit your auto-promotion workflow for transparency, and schedule the quarterly review on the calendar before the next funnel argument.

[object Object]
Share