HubSpot Admin Reference · Module 4

Lifecycle
Stages

The shared language between Marketing, Sales, and Customer Success — how to configure, automate, and govern the full contact funnel from Subscriber to Evangelist.

7 fixed stages 5 key workflows 3 case studies Interview Q&A
Naveed Abbas profile photo
Naveed Abbas
CRM Administrator
Foundation · 01
What Is a Lifecycle Stage?

A property that tracks how far along a contact is in their journey from stranger to customer — the funnel milestone property that drives everything else.

Core definition

A Lifecycle Stage is a dropdown property on Contact and Company records that tells you where that person sits in your overall relationship — from total stranger (Subscriber) all the way to loyal advocate (Evangelist). It answers the question: "How far along is this contact in becoming our customer?"

Why it's the backbone of your CRM

Business questionHow lifecycle stage answers it
How many potential buyers do we have?Count contacts where Lifecycle Stage = SQL or MQL
Where are leads getting stuck?Compare MQL count vs SQL count — gap = Marketing/Sales friction
What's our lead-to-customer rate?Customers this month ÷ Leads last quarter
How many MQLs did Marketing produce?Count contacts who entered MQL stage this month
Who should CS be onboarding right now?Active list: Lifecycle Stage = Customer AND Create date within 30 days
Which contacts should NOT get prospecting emails?Suppress contacts where Lifecycle Stage = Customer
Admin truth

If Lifecycle Stages are blank, stale, or inconsistently set — every funnel report is wrong, every automation that depends on stages breaks, and Marketing and Sales cannot align on performance. Stage governance is an ongoing admin responsibility, not a one-time setup task.

Foundation · 02
All 7 Stages Explained

Click each stage to see the full definition, ownership, triggers, how contacts leave, and admin notes.

Foundation · 03
System Logic & Rules

How HubSpot thinks about Lifecycle Stages — the four critical rules every admin must know.

RuleWhat it meansAdmin implication
Forward-only by default HubSpot ignores workflow actions that try to set Lifecycle Stage to an earlier value automatically To move a contact backward, you must manually update the record or use explicit workflow logic with a "Set property value" action that forces the change
Single-select — one stage at a time A contact can only be in one lifecycle stage simultaneously. Moving to MQL replaces Lead — they can't be both. Stage is a clean overwrite. You track history via HubSpot's property history log or custom date-stamp properties
Auto-set on form submit If a contact with a blank Lifecycle Stage submits any HubSpot form, HubSpot automatically sets their stage to Lead This is why form submissions are the primary Lead creation mechanism. Ensure your forms are HubSpot-hosted or connected via embedding
Auto-set on Deal events (if enabled) When a Deal is created → contact set to Opportunity. When a Deal closes won → contact set to Customer. Both require activation in Settings. Enable both in Settings → Objects → Deals. Always test in sandbox first. These save hundreds of manual rep updates per month.
The most misunderstood rule

The forward-only protection only applies to automated changes. Any user with edit permissions can manually set a contact to any stage — including backward. Workflows can also force backward movement with explicit Set Property actions. The protection prevents accidental workflow overwrites, not intentional admin actions.

What gets logged automatically

Every time a contact's Lifecycle Stage changes — regardless of how — HubSpot logs it in the property history. On any Contact record, click the Lifecycle Stage field → "View property history." You'll see every stage, when it changed, and what source changed it. This is your audit trail for debugging automation and data quality issues.

Foundation · 04
Lifecycle Stage vs Lead Status

The most common point of confusion in HubSpot — they look similar but serve completely different purposes.

Lifecycle stage
Big-picture funnel milestone
  • Answers: "How far have they come?"
  • Used by all teams: Marketing, Sales, CS
  • Changed by automation + all teams
  • 7 fixed options — cannot add more
  • Moves forward by default
  • Drives cross-functional reporting
  • Cannot be customised or renamed
  • Not for day-to-day sales tracking
Lead status
Sales-side working status
  • Answers: "What is the rep doing with them?"
  • Used by: Sales team only
  • Changed by: Sales reps
  • Fully customisable — add any options
  • Can move any direction at any time
  • Drives rep activity tracking
  • Not a funnel milestone
  • Not for cross-team reporting
The analogy that makes it click

Lifecycle Stage is the chapter of the book. Lead Status is what's happening on the current page. A contact can be in the SQL chapter (Lifecycle Stage) while their Lead Status is "In Progress" — the rep is calling them. Or "Bad Timing" — the rep spoke to them, they're qualified, but not ready. The lifecycle stage doesn't change. The working status does.

Default Lead Status options

Default optionWhat it meansWhen to use
NewLead just entered — nobody has touched it yetAuto-set when MQL is created or handed to Sales
OpenSDR is aware but hasn't started outreachInitial review stage
In ProgressSDR is actively reaching outWhile calling or emailing sequence is active
Open DealA Deal has been created for this contactContact has moved to Opportunity stage
UnqualifiedNot a good fit — wrong company, wrong personAfter disqualification conversation
Bad TimingQualified but not ready to buy yetAfter conversation — revisit in future
ConnectedSDR has made first contactAfter first meaningful conversation
Custom options to add

Consider adding: "Contacted — no response" (attempted outreach, awaiting reply) · "Nurture — revisit Q3" (timing issue, flag for future) · "Wrong person — find DM" (right company, need to find decision maker). Customise in Settings → Properties → Contacts → Lead status.

Admin Setup · 05
Step-by-Step Setup

Every configuration decision an admin makes when setting up Lifecycle Stages — with the exact path in HubSpot.

  1. Enable Deal auto-set for Opportunity — Settings → Objects → Deals → scroll to "Lifecycle stage" → enable "Automatically set associated contact and company lifecycle stage to 'Opportunity' when a deal is created." This removes a major manual burden from AEs.
  2. Enable Deal auto-set for Customer — Same settings page → enable "Automatically set associated contact and company lifecycle stage to 'Customer' when a deal is closed won." Test this in your sandbox with a test deal before enabling in production.
  3. Define MQL criteria jointly with Marketing and Sales — This is a business conversation, not a technical task. Facilitate a joint session (see MQL section below). Document the agreed criteria in writing before building anything.
  4. Build the MQL promotion workflow — Automation → Workflows → Create workflow → Contact-based. Set the enrolment trigger to your agreed MQL criteria. Actions: set Lifecycle Stage = MQL, set Lead Status = New, notify assigned SDR, create follow-up task.
  5. Build the Customer post-close workflow — Enrolment: associated Deal stage = Closed Won. Actions: set Lead Status = Open Deal, enrol in onboarding sequence, notify CS team, create onboarding task.
  6. Customise Lead Status options — Settings → Properties → Contacts → Lead status → edit the dropdown options. Add options relevant to your sales motion. Remove options nobody uses.
  7. Create date-stamp custom properties — For each key stage (MQL, SQL, Customer), create a custom Date property on Contact: "MQL Date," "SQL Date," "Customer Date." Build workflows that stamp these when stages are entered. (See Date-stamp section.)
  8. Build the "blank Lifecycle Stage" monitor list — Active list: Lifecycle Stage is unknown. Review weekly. Any contact without a stage is invisible to your funnel reports. Fix by importing with a default or building a catch-all workflow.
  9. Sync Lifecycle Stage to Companies — Build a workflow: when Contact Lifecycle Stage = Customer AND associated Company Lifecycle Stage ≠ Customer → set Company Lifecycle Stage = Customer. Keeps your account-level data accurate.
Admin Setup · 06
Defining MQL Criteria

The most important admin configuration — and the one that requires Marketing and Sales to agree before you build anything.

Admin interview gold

When an interviewer asks "how do you configure Lifecycle Stages?" — the answer that separates senior admins from juniors is: "Before I build any workflow, I facilitate a joint MQL definition session with Marketing and Sales. I document the agreed criteria and get sign-off from both sides before writing a single workflow action." This signals RevOps thinking, not just technical execution.

The MQL SLA document — what you produce as admin

MQL Definition — Marketing/Sales Agreement
Lead score threshold≥ 50 points
Required industrySaaS, FinTech, or B2B Services
Required job titleContains: Manager, Director, VP, Head of, C-level, Founder
Company size≥ 20 employees
Behavioural triggerVisited pricing page OR submitted demo request OR attended webinar
SDR response SLAReview within 4 business hours. Accept or reject with reason.
Rejection feedback loopRep fills "MQL Rejection Reason" property. Marketing reviews monthly.
Review cadenceMonthly review of MQL-to-SQL conversion rate. Adjust criteria if conversion < 25%.
RevOps perspective

The MQL definition is where Marketing and Sales alignment is tested. If Sales constantly rejects MQLs, the criteria are too loose. If MQLs pile up ignored, Sales doesn't trust them. As admin, you don't just build the workflow — you facilitate the negotiation, document the agreement, and build the feedback loop. This is the operational governance work that separates a CRM admin from a RevOps practitioner.

Admin Setup · 07
Key Workflows to Build

Every admin building a Lifecycle Stage system needs these five workflows — in this order.

Workflow 1 — MQL promotion
Enrolment trigger: Lead Score ≥ 50 AND Industry is any of [SaaS, FinTech] AND Job Title contains [Director, VP, Manager]
  • Set Lifecycle Stage = Marketing Qualified Lead
  • Set Lead Status = New
  • Notify deal owner via email: "New MQL — {{contact.firstname}} at {{contact.company}}"
  • Create task for owner: "Review and accept/reject MQL — due in 4 hours"
  • Set MQL Date = Today (custom date property)
Workflow 2 — MQL to SQL transition
Enrolment trigger: Lead Status = Connected OR Lead Status = In Progress (rep has made contact)
  • Set Lifecycle Stage = Sales Qualified Lead
  • Set SQL Date = Today
  • Notify SDR manager: "SQL created — {{contact.firstname}}"
Workflow 3 — Customer promotion on deal close
Enrolment trigger: Associated Deal Stage = Closed Won
  • Set Lifecycle Stage = Customer
  • Set Customer Date = Today
  • Set Lead Status = Open Deal
  • Enrol in onboarding email sequence
  • Create task for CS owner: "Begin onboarding — {{contact.firstname}}"
  • Notify CS Slack channel with deal value and contact details
Workflow 4 — MQL SLA escalation
Enrolment trigger: Lifecycle Stage = MQL AND MQL Date is more than 1 business day ago AND Lead Status = New (nobody has touched it)
  • Notify SDR manager: "MQL unreviewed for 24h — {{contact.firstname}}"
  • Create urgent task for SDR manager: "Review stale MQL immediately"
Workflow 5 — Blank stage catchall
Enrolment trigger: Lifecycle Stage is unknown AND Contact created date is known
  • Set Lifecycle Stage = Lead (default — no stage = treat as Lead)
  • Set Lead Status = New
Admin Setup · 08
Date-Stamp Properties

The RevOps superpower that turns Lifecycle Stage into a full funnel velocity reporting system.

Why you need these

Lifecycle Stage shows you the current stage. It doesn't show you when a contact entered each stage. Without date-stamp properties, you cannot calculate average MQL-to-SQL time, average SQL-to-Customer time, or sales cycle length — the core RevOps metrics every CEO asks for.

Property nameField typeWhat it capturesSet by
Lead DateDate pickerWhen the contact first became a LeadWorkflow: on Lifecycle Stage → Lead
MQL DateDate pickerWhen the contact was promoted to MQLWorkflow: on Lifecycle Stage → MQL
SQL DateDate pickerWhen Sales accepted the lead as SQLWorkflow: on Lifecycle Stage → SQL
Opportunity DateDate pickerWhen a Deal was created (Opportunity stage)Workflow: on Deal creation
Customer DateDate pickerWhen the contact became a CustomerWorkflow: on Deal Closed Won

With these properties, you can build reports: "Average days from MQL Date to SQL Date" → your Marketing-to-Sales handoff speed. "Average days from SQL Date to Customer Date" → your sales cycle. These are executive-level metrics that prove the RevOps function's value.

Applied Learning · 09
Full Contact Journey

A real contact's complete lifecycle — every stage, every trigger, every owner, from first touch to signed contract.

  • S
    Subscriber
    Sarah Khan subscribes to the SaaS Insights blog. HubSpot creates a Contact record and auto-sets Lifecycle Stage = Subscriber. Marketing owns her — she's in long-form nurture content drip.
    Day 1 · Auto-set on blog subscribe form
  • L
    Lead
    Sarah downloads the "2024 B2B SaaS Buyer's Guide" — a gated asset requiring a form fill. HubSpot auto-sets Lifecycle Stage = Lead. She's now in a lead nurture workflow: 3 emails over 14 days.
    Day 8 · Auto-set on form submission
  • M
    Marketing Qualified Lead (MQL)
    Sarah opens 4 emails, visits the pricing page twice, and her lead score reaches 55. The MQL workflow fires: Lifecycle = MQL, Lead Status = New, SDR Naveed is notified with a task to review within 4 hours. MQL Date is stamped: Day 14.
    Day 14 · Workflow-set on lead score threshold
  • SQL
    Sales Qualified Lead (SQL)
    Naveed calls Sarah. She confirms: budget ($12k approved), she's the VP of Operations (decision maker), they need a solution by Q1, and her current process is a clear pain. Naveed accepts the MQL. Lifecycle = SQL, SQL Date stamped. Lead Status → In Progress.
    Day 17 · Rep-set after qualification call
  • Opp
    Opportunity
    AE James creates a Deal: "TechCorp — Pro Plan | $12,000 | Close: 45 days." HubSpot auto-sets Lifecycle Stage = Opportunity because the Deal is associated to Sarah's Contact. Opportunity Date stamped. The Deal enters the pipeline at Prospecting stage.
    Day 19 · Auto-set when Deal is created
  • Cust
    Customer
    Sarah signs the Quote via HubSpot. James marks the Deal as Closed Won. HubSpot auto-sets Lifecycle Stage = Customer. Customer Date stamped. The Customer workflow fires: CS team notified, onboarding sequence starts, Sarah is added to [SUPPRESS] Customers list — no more prospecting emails ever. Total sales cycle: 17 days from MQL.
    Day 34 · Auto-set on Deal Closed Won
Applied Learning · 10
Three Case Studies
📊
Case 1 — The MQL rejection problem
When Sales rejects 70% of Marketing's MQLs
MQL criteriaB2B SaaS
Problem
Solution
Outcome
The problem

A B2B software company's marketing team was generating 120 MQLs per month and feeling great about it. But the Sales Director complained that "these leads are useless." SDRs were rejecting 85 of the 120 MQLs every month — 71% rejection rate. Marketing said Sales was being picky. Sales said Marketing had no idea what a good lead looked like. The HubSpot admin had built the MQL workflow based on a single criteria: lead score ≥ 30. That was it.

  • 1.
    Admin facilitated a joint workshop with CMO and VP of Sales. Reviewed the last 6 months of closed-won contacts — what did they have in common? Industry (SaaS/FinTech), job title (VP+), company size (50+ employees), and they had either visited pricing or requested a demo.
  • 2.
    Rebuilt MQL criteria: Lead Score ≥ 45 AND (Industry = SaaS OR FinTech) AND Job Title contains (VP OR Director OR C-level) AND (visited pricing page OR requested demo). Also required Company Employees ≥ 50.
  • 3.
    Added a "MQL Rejection Reason" custom dropdown property on Contact. When an SDR rejects an MQL, they must select a reason: Wrong Industry, Wrong Seniority, No Budget, Bad Timing, Already a Customer. Made it a required field on rejection.
  • 4.
    Built a monthly report: MQL rejection reasons by count. Shared with Marketing every first Monday. Both teams review together and adjust criteria quarterly.
RevOps outcome

MQL volume dropped from 120 to 38 per month. MQL acceptance rate jumped from 29% to 84%. Sales stopped complaining. Marketing stopped producing vanity metrics. The CMO initially pushed back on "fewer MQLs" — until the data showed MQL-to-Customer conversion went from 4% to 22%. Fewer, better leads outperformed more, worse ones by every measure.

⚙️
Case 2 — The customer who got a prospecting email
When Lifecycle Stage = Customer doesn't stop marketing outreach
SuppressionE-commerce SaaS
Problem
Solution
Outcome
The problem

An e-commerce SaaS company ran a "Free trial — last chance" campaign targeted at leads who hadn't converted. The email copy: "You're missing out — start your free trial today." A customer who had been paying $800/month for 8 months received it. They replied to the account manager: "Are we not considered a customer? Should we be looking at your competitor?" The deal auto-renewal was at risk. Investigation found: the campaign used a list filtered only on Lead Score < 60. Lifecycle Stage was never checked. The customer's lifecycle stage had never been set to Customer — the Deal close workflow wasn't enabled.

  • 1.
    Enabled Deal auto-set in Settings → Objects → Deals. All future closed-won deals now automatically set contact to Customer. Ran a one-time import to retroactively set Customer stage for all 200+ contacts with associated Closed Won deals.
  • 2.
    Created [SUPPRESS] Current customers — active list filtering Lifecycle Stage = Customer. Applied to every existing and future campaign as a mandatory exclusion.
  • 3.
    Added a campaign pre-send checklist to the team's process: every email send over 100 contacts must have a Suppression List review by admin before scheduling.
  • 4.
    Built a data quality monitor — active list: "Has associated Closed Won deal AND Lifecycle ≠ Customer." Found 47 more contacts in the same situation. Fixed all of them within 24 hours.
RevOps outcome

Zero suppression errors in the following 10 months. The pre-send review process caught three more errors before they went out. The at-risk renewal was saved — the customer received a personal apology from the CSM and renewed. The admin's data quality monitor list is now reviewed every Monday morning.

Applied Learning · 11
Common Admin Mistakes
  • 01 — Building MQL workflow before defining criteria
    Building a workflow based on a guess at what MQL means leads to Sales rejecting most leads and losing trust in marketing data. Fix: document the agreed criteria with both teams before writing a single workflow action. Get written sign-off.
  • 02 — Confusing Lifecycle Stage with Lead Status
    Trying to track "Contacted — no response" as a Lifecycle Stage (impossible), or reporting on Lead Status as if it were a funnel milestone (wrong). Fix: Lifecycle Stage = funnel milestone. Lead Status = rep working status. Never use one for the other's purpose.
  • 03 — Not enabling auto-set on Deal close
    Reps close deals and forget to update lifecycle stage. 40 contacts sit as SQL when they should be Customer. Suppression lists don't fire. Fix: enable Settings → Objects → Deals → auto-set lifecycle stage. Test in sandbox first.
  • 04 — Leaving Lifecycle Stage blank on new contacts
    60% of contacts have no stage. Every funnel report is wildly inaccurate. Fix: build a catchall workflow (Lifecycle Stage is unknown → set to Lead) AND set defaults in import templates.
  • 05 — Never building date-stamp properties
    You can report current stage count, but not velocity — how long contacts spend at each stage. CEO asks "what's our MQL-to-Customer time?" and you have no answer. Fix: build date-stamp properties from day one. Retroactive repair is painful.
  • 06 — Not moving contacts backward after lost deals
    A lost deal leaves the contact at Opportunity or SQL — excluded from all lead nurture workflows. They're never re-engaged. Fix: when a deal closes lost, build a workflow that evaluates re-nurture eligibility and moves the contact back to Lead or MQL with appropriate reason logged.
  • 07 — Not syncing lifecycle stage to Company records
    Contact = Customer, Company = Lead. Account-level reporting is wrong. ABM targeting is broken. Fix: build a workflow that syncs Contact lifecycle stage to the associated Company record when it changes to Customer.
Applied Learning · 12
Admin Best Practices
  • 📋
    Document your MQL definition in writing — create a living document both Marketing and Sales reference. Paste the criteria into every related workflow's description field. Revisit quarterly.
  • 🕒
    Always date-stamp stage entries — MQL Date, SQL Date, Customer Date properties + workflows. These unlock velocity reporting and sales cycle analysis — the metrics executives actually care about.
  • 🔗
    Sync lifecycle stage to Companies — don't leave Company lifecycle stages out of sync with their Contacts. Build the sync workflow from day one.
  • 🚫
    Build suppression before your first send — [SUPPRESS] Customers active list should exist before any campaign goes out. Make it a non-negotiable part of every campaign setup checklist.
  • 📊
    Build the funnel dashboard immediately — Leads, MQLs, SQLs, Opportunities, Customers — all with month-over-month tracking. This gives stakeholders immediate visibility and justifies the admin function's value.
  • 🔄
    Build the lost deal re-nurture workflow — when a deal closes lost, evaluate whether the contact should return to Lead for nurture. A lost deal isn't a lost contact forever — many buy 6–18 months later.
  • 📅
    Run monthly lifecycle audits — check: blank stage count, Customer count vs Closed Won deal count (should match), MQL-to-SQL conversion rate. These three numbers tell you if your system is healthy.
Applied Learning · 13
Practice Exercise

Do this in your free HubSpot sandbox — approximately 45 minutes.

  1. Enable Deal auto-set — Settings → Objects → Deals → enable auto-set for both Opportunity and Customer. This is your first step in any real implementation.
  2. Create 5 test contacts — give each a different lifecycle stage manually: Subscriber, Lead, MQL, SQL, Customer. Note how each looks in the record view.
  3. Create date-stamp custom properties — Settings → Properties → Contacts → Create property. Create "MQL Date" (Date picker type). Repeat for "SQL Date" and "Customer Date." Put them all in a new group called "Funnel Dates."
  4. Build the MQL promotion workflow — Automation → Workflows. Enrolment: Lead Score ≥ 5 (low for testing). Actions: (1) Set Lifecycle Stage = MQL, (2) Set Lead Status = New, (3) Set MQL Date = Today, (4) Create task for owner. Save and activate.
  5. Trigger the workflow — Go to one of your Lead contacts. Manually set their Lead Score to 10. Wait 5 minutes. Watch: their stage should change to MQL, a task should be created, and MQL Date should be stamped.
  6. Test the Deal auto-set — Create a Deal for your MQL contact. Does Lifecycle Stage automatically change to Opportunity? If yes, the setting is working. Move the Deal to Closed Won — does the contact become Customer?
  7. Build the Customer suppression list — Active list: Lifecycle Stage = Customer. Name it [SUPPRESS] Current customers. Verify your Customer test contact appears in it.
  8. Build the blank stage monitor — Active list: Lifecycle Stage is unknown. Any contact in this list needs fixing. In a real portal, this list should trend toward zero.
Applied Learning · 14
Interview Questions
"What is the difference between Lifecycle Stage and Lead Status in HubSpot?"
Lifecycle Stage tracks the big-picture funnel milestone — where a contact sits in their overall journey from Subscriber to Customer. It's used by all teams and drives cross-functional reporting. Lead Status is a sales-specific working status — it tells a rep what action they're currently taking: New, In Progress, Bad Timing. The key differences: Lifecycle Stage has 7 fixed options that cannot be customised; Lead Status is a customisable dropdown. Lifecycle Stage is moved forward by default in automation; Lead Status can move any direction at any time. The analogy I use: Lifecycle Stage is the chapter of the book, Lead Status is what's happening on the current page.
"How would you define and configure MQL criteria for a new client?"
First, I'd facilitate a joint session with Marketing and Sales leadership before building anything. I'd review the last 12 months of closed-won contacts to identify their common attributes — industry, job title, company size, behavioural signals. I'd ask Sales what makes a lead worth picking up the phone for. Then I'd translate the agreed criteria into a documented SLA — score threshold, required properties, behavioural triggers, and an SDR response time commitment. I'd build a workflow that promotes contacts meeting those criteria and a rejection feedback loop — a required dropdown property that reps fill when rejecting an MQL, so the data feeds back into refining criteria over time. The system is never set-and-forget — I'd review MQL-to-SQL conversion monthly and adjust criteria if conversion drops below the target rate.
"A contact is at Customer stage but is still receiving prospecting emails. How do you diagnose and fix it?"
Three layers to check. First: are suppression lists applied to the campaigns sending those emails? I'd open each active campaign and verify that a [SUPPRESS] Customers list is in the exclusion field. If not, I add it immediately. Second: is the contact's Lifecycle Stage actually Customer? I'd check their property history to see when and how it was set. If it was never set to Customer despite a closed-won deal, the Deal auto-set isn't enabled — I'd turn that on and retroactively fix the contact. Third: are there workflow-based emails sending based on criteria that bypass the lifecycle stage check? I'd audit all active workflows for any email actions without an explicit "Lifecycle Stage is not equal to Customer" branch. The fix addresses all three simultaneously rather than patching one at a time.
"How do you report on sales cycle length using HubSpot?"
Out of the box, HubSpot doesn't make this easy — Lifecycle Stage shows current state, not history. My solution is date-stamp custom properties: I create "MQL Date," "SQL Date," and "Customer Date" as Date properties on Contact, then build workflows that stamp each one when the corresponding stage is entered. With those three dates, I can build a calculated report in HubSpot: average days between MQL Date and Customer Date gives total sales cycle length. Average MQL Date to SQL Date gives Marketing-to-Sales handoff speed. Average SQL Date to Customer Date gives the Sales team's close speed. These are the metrics executives ask for, and having them available in a live dashboard is usually what separates a RevOps-capable admin from a basic HubSpot user.
"Can you add new Lifecycle Stage options in HubSpot? What do you do if the standard 7 stages don't fit your client's process?"
No — HubSpot's 7 lifecycle stages are fixed. You cannot add, rename, or remove them. If a client's process doesn't map cleanly to the standard stages, I have three options. First, I check whether the standard stages can be stretched to fit — "Warm Lead" often maps to either Lead or MQL depending on qualification level. Second, I use Lead Status to capture the additional granularity — it's fully customisable and can represent sub-states within a lifecycle stage. Third, for truly unique business models, I create a custom property called "Custom Stage" with whatever options the business needs, and use that alongside the standard Lifecycle Stage. What I never do is try to rename or misuse the standard stages — that breaks reporting, automation, and everyone else's understanding of what the stages mean.
Applied Learning · 15
Summary Cheatsheet
ConceptKey point
What is itA funnel milestone property — tracks a contact's big-picture position from Subscriber to Customer
The 7 stagesSubscriber → Lead → MQL → SQL → Opportunity → Customer → Evangelist
Fixed optionsCannot add, remove, or rename — all 7 are permanent HubSpot options
Forward-only defaultAuto-moves forward only — backward moves require manual action or explicit workflow logic
Auto-set: form submitBlank contact submits any HubSpot form → auto-set to Lead
Auto-set: Deal createdDeal associated to contact → auto-set to Opportunity (must enable in Settings)
Auto-set: Deal closed wonDeal closes won → auto-set to Customer (must enable in Settings)
vs Lead StatusLifecycle Stage = funnel chapter. Lead Status = rep's daily working state. Never confuse them.
MQL definitionAgreed criteria between Marketing and Sales — documented, signed off, reviewed quarterly
Date-stamp propertiesMQL Date, SQL Date, Customer Date — enables velocity reporting and sales cycle analysis
Most critical workflowCustomer promotion on Deal close — with suppression list update as first action
Suppression ruleCustomer = immediate suppression from all prospecting. Build [SUPPRESS] Customers before first send.
Company syncBuild workflow to sync Contact lifecycle stage changes to associated Company records
RevOps metricMQL→SQL conversion rate = the primary marketing-sales alignment health indicator
Admin interview gold"Before building, I facilitate a joint MQL definition session and document the agreed criteria with sign-off from both teams."
RevOps mindset on lifecycle stages

Lifecycle Stages are the revenue reporting backbone. Every funnel metric — lead volume, MQL rate, MQL-to-SQL conversion, SQL-to-close rate, average sales cycle — depends on stages being accurate. Bad stage data means wrong decisions at the executive level. As a RevOps admin, you treat stage governance as a weekly operational responsibility: monitor blank stages, verify auto-set workflows are firing, review conversion rates, and facilitate the Marketing-Sales SLA conversation every quarter. This is the work that makes the CRM a reliable business intelligence tool rather than just a digital rolodex.