WHAT THIS COVERS
- What HubSpot's default lifecycle stages are and where they fall short for B2B
- How to define criteria for each stage transition — not just names
- The MQL definition framework that ends the marketing-sales argument
- Lifecycle stage vs. lead status — and why both matter
- Automation triggers for each lifecycle transition
HubSpot's default lifecycle stages are Subscriber, Lead, MQL, SQL, Opportunity, Customer, and Evangelist. For B2B companies, the most critical work is not choosing stage names — it is writing the specific criteria that trigger each transition, especially the MQL-to-SQL handoff. Without written definitions agreed on by both marketing and sales, lifecycle stages are just labels that mean different things to different people.
What HubSpot Gives You Out of the Box
HubSpot ships with seven default lifecycle stages: Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, and Evangelist. These cover the full arc of the buyer journey from first touch to post-sale advocacy.
The problem is that HubSpot's documentation defines these stages in general terms that do not map to any specific business. "An MQL is a contact that your marketing team has qualified as ready for the sales team" is technically correct and practically useless. What does "qualified" mean? What makes a contact ready? HubSpot cannot answer that — your team has to.
Most HubSpot implementations go live with the default stages populated by whatever CRM migration script ran first, with no discussion about what each stage means. This creates a database where lifecycle stages are noise rather than signal.
How Lifecycle Stages Break Without Definitions
When stages are not defined, contacts pile up in whichever stage they were assigned when they entered the system and stay there forever. Pull a lifecycle stage distribution report in most untended HubSpot portals and you will find 60 to 70% of contacts sitting in "Lead" — because no workflow ever moves them anywhere else.
Sales teams learn to ignore HubSpot's lifecycle data because it has never been accurate. Marketing reports on MQL volume that sales disputes because their definitions do not match. The pipeline review becomes a debate about data quality rather than a discussion about revenue.
All of this is preventable. The fix is not technical — it is definitional. You need written stage criteria before you build any automation around lifecycle stages. Read our HubSpot implementation mistakes guide for why this is consistently the first problem we find in a portal audit.
Defining Each Stage: A Framework
For each lifecycle stage, define three things: the entry criteria (what must be true for a contact to enter this stage), the exit criteria (what must be true for a contact to advance to the next stage), and the owner (which team is responsible for contacts in this stage).
Subscriber
Entry: Contact has opted into marketing communications — newsletter sign-up, content download, webinar registration — but has not yet been qualified for fit or intent.
Owner: Marketing. No active sales engagement.
Exit to Lead: Contact meets minimum fit criteria (company size, industry, job title match your ICP definition).
Lead
Entry: Contact meets ICP fit criteria. Profile enrichment confirms they work at a company in your target market in a relevant role.
Owner: Marketing. Active nurture sequences based on persona.
Exit to MQL: Contact meets both fit criteria AND crosses an intent threshold — see MQL definition below.
Marketing Qualified Lead (MQL)
This is the most argued-about stage in B2B. See the dedicated section below for a full definition framework.
Owner: Marketing passes; sales must accept within your SLA window.
Exit to SQL: Sales rep reviews and accepts the lead, confirming they will actively work it.
Sales Qualified Lead (SQL)
Entry: Sales has accepted the lead. Rep is assigned and a follow-up task is created within your SLA.
Owner: Sales. Marketing continues suppressed nurture (they remain on the list but receive lower-frequency touchpoints).
Exit to Opportunity: Discovery call completed, BANT or MEDDIC criteria met, deal created in the pipeline.
Opportunity
Entry: Deal created in HubSpot pipeline. Contact is actively being worked through the sales process.
Owner: Sales — AE or closing rep, depending on your team structure.
Exit to Customer: Deal moved to Closed Won in HubSpot pipeline.
Customer
Entry: Triggered automatically when the associated deal is Closed Won. This must be an automated workflow, not a manual update.
Owner: Customer Success.
Exit: Either to Evangelist (expansion criteria met) or to a churned state (you will need a custom property for this — HubSpot has no default "Churned" stage).
Defining the MQL: The Framework That Ends the Argument
The MQL definition is where marketing and sales conflict most frequently. Marketing says a contact is an MQL. Sales says the contact is not ready. Both are right with different criteria. The solution is to make the criteria explicit, written, and agreed on by both teams.
An effective MQL definition has two required components: fit and intent. Both must be true. Fit alone (this person works at the right kind of company) is not enough. Intent alone (this person visited the pricing page) is not enough if the company is too small to buy.
Fit criteria (what makes a contact ICP-matched):
- Company employee count: define the range (e.g., 50 to 2,000 employees)
- Industry: define which SIC codes or industry categories qualify
- Geography: if relevant to your sales motion
- Job title seniority and function: does this person have budget authority or influence over the buying decision?
- Company revenue or funding stage: if relevant
Intent criteria (what actions indicate buying interest):
- Lead score threshold: define the minimum score and what behaviors contribute to it
- High-intent page visits: pricing page, comparison pages, ROI calculator
- Demo or meeting request: the clearest possible intent signal
- Content engagement: multiple downloads of bottom-funnel content (case studies, implementation guides)
Write these criteria in a shared document. Present them in a marketing-sales alignment meeting. Get explicit sign-off from both the VP of Marketing and the VP of Sales. When a lead is disputed later, refer to the document — not the argument.
Lifecycle Stage vs. Lead Status: Why You Need Both
Lifecycle stage and lead status are separate properties in HubSpot that serve different purposes. Confusing them is a common source of data model errors.
Lifecycle stage tracks where a contact is in the overall buyer journey. It moves forward (usually) and provides a high-level view of the database composition. Lead status tracks the sales activity status within a stage — specifically, what is happening with this contact right now in the sales process.
A contact at the SQL lifecycle stage might have a lead status of "Attempting Contact," "Connected," "Open Opportunity," or "Unqualified." Lead status is what a sales rep updates after each interaction. Lifecycle stage is what the system updates based on rules.
Build workflows that keep these two properties in sync. When a deal closes, the lifecycle stage should automatically update to Customer. When a rep marks a lead as Unqualified in lead status, a workflow should either move the lifecycle stage back to Lead or enroll them in a recycle nurture sequence.
Automating Lifecycle Stage Transitions
Once the definitions are written and agreed on, the automation is the straightforward part. In HubSpot, lifecycle stage transitions are managed through workflows with enrollment triggers based on your defined criteria.
- Lead → MQL: Workflow enrolls contacts who meet both fit criteria AND have crossed the intent threshold. Sets lifecycle stage to MQL, notifies the assigned SDR, creates a follow-up task.
- MQL → SQL: Triggered by a manual action (sales rep accepts the lead via a HubSpot property update or a deal creation). Or triggered automatically when a meeting is booked via HubSpot Meetings or Calendly.
- SQL → Opportunity: Triggered by deal creation in HubSpot. The workflow sets the lifecycle stage to Opportunity on the associated contacts automatically.
- Opportunity → Customer: Triggered by deal stage moving to Closed Won. Sets all associated contacts to Customer lifecycle stage immediately.
For a comprehensive look at the automation that runs these transitions, see our guide to lifecycle marketing automation in HubSpot.
Work With Revo-Sys
We run lifecycle stage definition workshops and implement the automation that keeps them accurate — including the MQL alignment session that marketing and sales teams often need a third party to facilitate. Book a call to get started.