HubSpot Lifecycle Stages

HubSpot lifecycle stages are a built-in contact property that tracks where a person is in the journey from first touch to customer. HubSpot ships with 8 default stages. Most B2B SaaS teams need to customize them. The defaults are a starting point, not a destination.

The HubSpot-specific challenge: lifecycle stage is a single property shared across contacts and companies, but it behaves differently than most properties. It has special automation rules, a built-in hierarchy, and quirks around backward movement. Understanding these mechanics matters more than the stage names themselves.

HubSpot Default Stages vs Recommended B2B SaaS Setup

HubSpot defaults

Recommended B2B SaaS configuration

Adding custom lifecycle stages (Enterprise only)

HubSpot Enterprise allows custom lifecycle stages. Use sparingly.

Worth adding:

Not worth adding:

• "Prospect" (between Lead and MQL) — use lead status instead
• "Nurture" — use a list or lead status, not a lifecycle stage
• "Demo Scheduled" — use deal stages, not lifecycle
• "Evaluation" — use deal stages

Rule of thumb: If the stage describes a sales process step (demo, proposal, negotiation), it belongs in deal stages. If it describes where the contact is in the overall journey, it's a lifecycle stage. Max 8-10 lifecycle stages total.

How Lifecycle Stage Works in HubSpot

The hierarchy and automation rules

HubSpot lifecycle stages have a built-in hierarchy. The platform treats them as ordered:

Subscriber < Lead < MQL < SQL < Opportunity < Customer < Evangelist

Key mechanics:

Lifecycle stage vs lead status

HubSpot has two related but separate fields. Using them correctly prevents the most common lifecycle architecture mistakes.

Lead status values to configure:

Lead status rules:

• Lead status is operational. Reps update it daily. Lifecycle stage is strategic. It moves only at key transitions
• Never use lifecycle stage for operational tracking ("Attempting Contact", "Demo Scheduled"). Use lead status or deal stages
• Lead status resets when lifecycle stage changes. When a contact moves from MQL to SQL, reset lead status to "New" (or your equivalent) so the AE starts fresh

Configuring Lifecycle Stage Transitions

Transition 1: Unknown → Subscriber / Lead

Trigger: Contact is created in HubSpot.

Configuration:

• In HubSpot Settings → Objects → Contacts → Lifecycle stage: set default lifecycle stage for new contacts
• Set to "Lead" by default. Only set to "Subscriber" if the creation source is explicitly a newsletter/blog subscription
• If using forms: set lifecycle stage per form. Newsletter form → Subscriber. Content download form → Lead. Demo request form → MQL (skip Lead)

HubSpot setup:

Settings → Objects → Contacts → Lifecycle Stage
  Default lifecycle stage: Lead

Per form override:
  Newsletter form → Subscriber
  Demo request form → MQL
  Contact us form → MQL
  Content download form → Lead

Transition 2: Lead → MQL

Trigger: Lead score reaches threshold OR high-intent action.

Configuration (workflow):

Workflow: Lead → MQL Promotion
Trigger: Contact-based
Enrollment:
  - Lifecycle stage IS Lead
  - AND (HubSpot Score IS >= 50 OR
         Contact has submitted form: Demo Request OR
         Page views includes Pricing Page >= 2 times)
Action:
  1. Set lifecycle stage to MQL
  2. Set lead status to "New"
  3. Set MQL date to today (custom property)
  4. Trigger notification to assigned SDR (or routing workflow)

MQL scoring model (basic):

Firmographic score (added to behavioral):

MQL threshold: Set at a point where ~30-50% of MQLs are accepted by sales. If acceptance rate is below 30%, the threshold is too low. If above 60%, the threshold is too high and you're leaving pipeline on the table.

Transition 3: MQL → SQL

Trigger: SDR qualifies the contact manually.

Configuration:

• SDR manually updates lifecycle stage to SQL after a qualifying conversation
• Or: SDR updates lead status to "Qualified" and a workflow promotes to SQL

Workflow: MQL → SQL Promotion
Trigger: Contact-based
Enrollment:
  - Lifecycle stage IS MQL
  - AND Lead status IS Qualified
Action:
  1. Set lifecycle stage to SQL
  2. Set lead status to "New" (reset for AE)
  3. Set SQL date to today (custom property)
  4. Notify assigned AE

SDR qualification must include (minimum):

• Confirmed need (the contact articulated a problem)
• Budget range discussed (even directionally)
• Timeline indicated (this quarter, next quarter, exploring)
• Next step agreed (meeting with AE)

Transition 4: SQL → Opportunity

Trigger: AE creates a deal and associates the contact.

Configuration:

Settings → Objects → Deals
  ✓ "Set lifecycle stage to Opportunity when a deal is associated"

This is a native HubSpot setting. Enable it. No workflow needed.

Transition 5: Opportunity → Customer

Trigger: Associated deal moves to Closed Won.

Configuration:

Settings → Objects → Deals
  ✓ "Set lifecycle stage to Customer when a deal is won"

Also native. Enable it.

Transition 6: Recycling (MQL/SQL → Recycled)

Trigger: SDR marks contact as unqualified but potentially re-engageable.

Configuration:

Workflow: Recycle Contact
Trigger: Contact-based
Enrollment:
  - Lead status IS "Unqualified" OR "Bad Timing"
  - AND Lifecycle stage IS MQL or SQL
Action:
  1. Set lifecycle stage to Lead (or custom "Recycled" stage if on Enterprise)
  2. Set lead status to "Recycled"
  3. Enroll in re-nurture email sequence
  4. Set "Recycle Date" to today (custom property)
  5. Set "Recycle Reason" (custom property, from a dropdown)

Recycling rules:

• Recycled contacts must re-qualify through the scoring model to become MQL again. Don't manually re-MQL recycled contacts
• Set a cooling-off period. Recycled contacts should not be re-eligible for MQL for at least 30 days
• Track recycle reasons. The top 3 recycle reasons tell you what's wrong with MQL criteria or targeting

Transition 7: Customer → Churned

Trigger: Subscription cancelled or contract not renewed.

Configuration depends on your billing system integration:

• If using HubSpot Payments or Commerce Hub: automate on subscription status change
• If external billing (Stripe, Chargebee): sync via integration or API
• If manual: CS team updates lifecycle stage when churn is confirmed

Workflow: Customer → Churned
Trigger: Contact-based
Enrollment:
  - Lifecycle stage IS Customer
  - AND (Custom property "Subscription Status" IS "Cancelled"
         OR Deal property "Renewal Status" IS "Not Renewed")
Action:
  1. Set lifecycle stage to "Other" (or custom "Churned" stage)
  2. Remove from customer-only campaigns
  3. Enroll in churn-recovery email sequence
  4. Notify CS manager

Reporting on Lifecycle Stages

Essential reports

Building in HubSpot

Reports → Create Report → Contact reports

Funnel report:
  X-axis: Lifecycle stage
  Filter: Created date in last 90 days
  Breakdown by: Lead source (optional)

Stage velocity:
  Create calculated property "Days as MQL":
    = SQL Date - MQL Date
  Report on average "Days as MQL" over time

Common HubSpot Lifecycle Mistakes

Anti-Pattern Check

• 15 lifecycle stages. HubSpot functions best with 8-10. More than that creates reporting confusion and automation complexity. Use lead status and deal stages for granularity within stages
• MQL threshold produces 80% rejection rate. The threshold is too low. SDRs lose trust in MQLs and stop following up. Calibrate until acceptance rate is 30-50%
• No recycling mechanism. Contacts that fail SQL go to "Disqualified" and are never re-engaged. Many are right-company-wrong-timing. Build a recycling flow that re-enters nurture and allows re-qualification
• Lifecycle stage changes are all manual. Forward transitions (Lead → MQL, Opportunity → Customer) should be automated. Manual-only lifecycle management means stages are always outdated
• No velocity tracking. "How long do contacts spend as MQLs?" is unanswerable without MQL Date and SQL Date properties. Add these custom date fields and set them via workflow on each transition
• Same lifecycle stage setup as HubSpot defaults with no customization. The defaults don't include scoring triggers, lead status, transition workflows, or recycling. They're a skeleton, not a finished system
• Lifecycle stage never audited. Run a monthly report: contacts per stage, contacts with blank lifecycle, contacts in "Other." If any number looks wrong, investigate
• No SLA on MQL follow-up. An MQL that sits for 5 days is a dead MQL. Configure a workflow that alerts the SDR manager if an MQL is untouched after 4 hours