On this page
What HubSpot supports natively
These are HubSpot’s default stages, in order, with HubSpot’s own definitions.
| Stage | HubSpot’s definition |
|---|---|
| Subscriber | A contact that has opted in to hear more from you, for example by subscribing to the blog or newsletter |
| Lead | A contact or company that has converted on your website or through some other interaction beyond a subscription |
| Marketing Qualified Lead | A contact or company your marketing team has qualified as ready for sales |
| Sales Qualified Lead | A contact or company your sales team has qualified as a potential customer |
| Opportunity | A contact or company associated with a deal |
| Customer | A contact or company with at least one closed deal |
| Evangelist | A customer that has advocated for your organization |
| Other | A contact or company that doesn’t fit any of the above |
How stages move:
- Forward only by default. Imports, forms, the API, integrations and workflows can only move the default lifecycle stage forward. To set an earlier stage, the value has to be cleared first.
- Automation settings (Settings > Objects > Contacts > Lifecycle Stage) can set a stage when a deal is created, when a deal is won and when a lead is associated, and can sync a primary company’s stage to its contacts.
- Each stage has date properties. Date entered and date exited are recorded per stage, which is what lifecycle reports are built on.
How to define your HubSpot lifecycle stages
HubSpot’s definitions say what a stage is. Your team also needs to know when a record enters it and who decides.
| Stage | Entry rule to write down | Usually set by |
|---|---|---|
| Lead | Which conversions count (form, chat, event) | Form or workflow |
| MQL | The score or behavior threshold | One scoring workflow |
| SQL | What sales confirms on the first conversation | Sales rep or a lead-status workflow |
| Opportunity | A deal exists | Deal-created setting |
| Customer | A deal is closed won | Deal-won setting |
Then:
- Give each stage one owner. One workflow or one setting, not several. Overlapping owners are why lifecycle stage keeps changing.
- Decide what happens on disqualification. Usually lead status changes and lifecycle stays, or it’s set to Other. Write down which.
- Keep sub-stages out of lifecycle. Sales-working states belong in lead status. See lifecycle stage vs lead status vs deal stage.
- Build the automation last, once the rules are agreed. See how to set lifecycle stage with a workflow.
Where Jetstack AI fits
Once your stage definitions and entry rules are written, Jetstack AI Projects turns that brief into a plan you review: custom lifecycle stages, properties, lists and the workflows that apply your entry rules. Approving the plan generates the assets, deployment is a separate approval, and the receipt shows what was created, read back from HubSpot. Projects adds new lifecycle stages and can rename or reorder the custom stages you’ve added, and it creates workflows switched off. It’s currently in limited release; see what Projects can build.
Sources
- Use contact and company lifecycle stages (HubSpot Knowledge Base)
- Manage how lifecycle stages sync between objects (HubSpot Knowledge Base)
- Projects capabilities (Jetstack AI documentation)
Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
Workflows & automation
Turn the brief into approved HubSpot assets.
Projects plans the build against the client portal, generates the assets and deploys them only after you approve.
Explore Projects