Skip to content
Book a build

Free tool

HubSpot lifecycle stage builder: design your stages and lead status

Choose how you sell and who qualifies leads. You get a recommended set of lifecycle stages with entry and exit rules and an owner, the lead status values that go with them, the HubSpot settings and workflows that set each one, and warnings about the setups that cause conflicts. Export it as a Markdown brief.

Free, no sign-up. Data checked .

How you sell
Custom lifecycle stages HubSpot lists custom lifecycle stages for all plans; only Super Admins can add or edit them.
Your team Picking a sales motion sets these to the usual team for it. Adjust them after.
Your portal today

Runs in your browser. Nothing you choose leaves this page. The design below updates as you change your answers; without JavaScript it shows the inbound B2B design.

The export is a brief you can hand to marketing, sales and whoever owns HubSpot. To build it with Jetstack AI, use Upload a build spec in a Projects chat: Markdown files work, and Jetty plans from your exact stage names and values. Workflows it builds are created switched off.

Inbound B2B: 7 stages, 6 lead status values, 6 workflows, 5 warnings.

Lifecycle stages for Inbound B2B

Default stages only. HubSpot lists custom lifecycle stages for all plans if you change your mind; only Super Admins can add them.

StageDefinitionEnters whenLeaves whenOwnerSet by
SubscriberOpted in to hear from you (newsletter or blog) and has done nothing else yet.Submits a newsletter or blog subscription form. That form's lifecycle stage setting is Subscriber.Converts on any other form, chat or event: Lead.MarketingThe subscription form's lifecycle stage setting
LeadRaised a hand beyond subscribing: downloaded content, attended an event, chatted or asked for a demo.Submits a conversion form (form setting: Lead), or is created by a rep or an import (default stage on create: Lead).Meets the MQL rule: Marketing Qualified Lead.MarketingForms and the default-stage-on-create setting
Marketing Qualified LeadMarketing judges the lead ready for sales: a score threshold or a high-intent action such as a demo request.Lead score at or above your threshold, or a demo or contact-sales request, while the contact is still Subscriber or Lead.The SDR accepts: Sales Qualified Lead. Rejected: stays MQL with lead status Unqualified.MarketingOne MQL workflow
Sales Qualified LeadSales has confirmed fit on a first conversation and is working toward a deal.The SDR ticks a "Sales accepted" checkbox; one workflow sets the stage.A deal is created: Opportunity.SDR teamOne "Sales accepted" workflow
OpportunityAssociated with a deal (HubSpot's definition). Its deal is open, or closed lost and not yet recycled.Its first deal is created (setting: Set lifecycle stage when a deal is created).Deal closed won: Customer. Closed lost: stays Opportunity; lead status says what's next.Account executivesHubSpot's deal-created setting
CustomerHas at least one closed-won deal.A deal is closed won (setting: Set lifecycle stage when a deal is won).Stays Customer. Track renewals, expansion and churn in deals or properties, not lifecycle.Sales / account managementHubSpot's deal-won setting
OtherNot a buyer: partners, vendors, job applicants, competitors, employees.An admin sets it, or one workflow on a "Contact type" property.Only by hand. Other is last in HubSpot's default order, so HubSpot tools can't move a record out of it without clearing the value first.RevOps / HubSpot adminOne Contact type workflow, or by hand

Default stages you won't use: Evangelist (no team runs a referral or advocacy program). HubSpot keeps them in the list; nothing in this design sets them.

Lead status values

These are HubSpot's default lead status values, minus Open and In Progress, which overlap with Attempted to Contact and Connected; leave them unused or remove them once no workflow or list uses them. HubSpot describes lead status as the sub-stages of Sales Qualified Lead; here it starts at Marketing Qualified Lead because that's where your reps start working. Write that down.

ValueMeansSet byLifecycle stage
NewIn the queue; nobody has reached out yet.Workflow, when the contact reaches Marketing Qualified LeadMarketing Qualified Lead
Attempted to ContactOutreach has started; no reply yet.Rep, after the first logged attemptMarketing Qualified Lead to Opportunity
ConnectedA two-way conversation happened.RepMarketing Qualified Lead to Opportunity
Bad TimingA fit, but not now. Require a follow-up date.RepMarketing Qualified Lead to Opportunity
UnqualifiedNot a fit. Require a disqualification reason.RepMarketing Qualified Lead to Opportunity
Open DealA deal is open (not closed won or closed lost); the deal stage takes over.Deal-based workflow, while an associated deal is open; a contact workflow clears it once none isOpportunity

HubSpot settings

In Settings > Data Management > Objects > Contacts > Lifecycle Stage, plus each form's options.

SettingSet it toWhat HubSpot does
Set lifecycle stage when a contact or company is createdOn: LeadForms with their own stage override it. If it's off, new records are left blank, except records created from the contacts or companies home page, from an associated record or by a form, which get the first stage in display order.
Each form's lifecycle stage settingSubscription forms: Subscriber. Every other conversion form, including demo requests: Lead. Let the MQL workflow own MQL.Applies to new and existing contacts and only moves forward: a contact already at a later stage keeps it.
Set lifecycle stage when a deal is createdOn: OpportunityRuns when a contact or company gets its first associated deal. A contact already at Customer stays Customer.
Set lifecycle stage when a deal is wonOn: CustomerRuns when an associated deal is closed won. While it's off, HubSpot also doesn't update Close date and Days to close on associated contacts and companies.
Set lifecycle stage when a lead is associatedOff (you don't use the Leads object)Leads created by automation, such as a workflow's create-lead action, don't update the stage.
Sync lifecycle stages (company to contacts)OnOne-way and forward only: a primary company's stage is copied to its contacts. A new contact at a Customer company becomes Customer straight away.

Workflows to build

One workflow owns each stage. Nothing else sets it.

  1. Lifecycle | Set MQL | Contact: Enroll when lead score is at or above your threshold, or a demo or contact-sales form is submitted, and lifecycle stage is Subscriber or Lead. Set lifecycle stage to Marketing Qualified Lead.
  2. Lifecycle | Set SQL | Contact: Use a "Property value changed" trigger: "Sales accepted" changes to Yes, and lifecycle stage is before Sales Qualified Lead. Set lifecycle stage to Sales Qualified Lead.
  3. Lead status | Set New | Contact: Enroll when lifecycle stage is Marketing Qualified Lead and lead status is unknown. Set lead status to New and rotate the contact to the SDR team.
  4. Lead status | Set Open Deal | Deal: Deal-based workflow. Enroll when a deal is created or its deal stage changes, and Is Closed Won is false and Is closed lost is false. Edit the associated contacts: set lead status to Open Deal. Don't use the contact's "Number of associated deals": HubSpot counts every associated deal there, closed ones included, so it isn't an open-deal test. Don't touch lifecycle stage here: the deal-created setting does that.
  5. Lead status | Clear Open Deal | Contact: Contact-based workflow. Enroll when lead status is Open Deal and the contact has no associated deal where Is Closed Won is false and Is closed lost is false, so a contact with another deal still open keeps Open Deal. Turn re-enrollment on for the lead status criterion, so a contact whose next deal sets Open Deal again is cleared again when that one closes. Clear lead status, then have the rep set what's next (Bad Timing or Unqualified) on a lost deal. Don't touch lifecycle stage here: the deal-won setting does that.
  6. Lifecycle | Set Other | Contact: Enroll when "Contact type" is Partner, Vendor, Applicant or Employee and lifecycle stage is not Customer. Set lifecycle stage to Other.

Conflict warnings

  • Watch Rejected MQLs stay MQL. When sales rejects an MQL, set lead status to Unqualified and leave lifecycle at MQL. A workflow that sets it back to Lead fails unless it clears the value first. If you want rejected leads back in nurture, tick "send lost or stale records back".
  • Watch Forms shouldn't set MQL. A demo form that sets MQL and a scoring workflow that sets MQL give the stage two owners, and property history stops telling you why a contact qualified. Have forms set Lead and let the MQL workflow treat a demo request as qualifying.
  • Watch Don't rebuild the deal settings as workflows. HubSpot's deal-created and deal-won settings already set Opportunity and Customer. A workflow that does the same is a second writer with a different timing.
  • Watch Company sync moves new contacts at customer accounts. With Sync lifecycle stages on, a new contact at a Customer company becomes Customer and never reaches your MQL or SQL rules. If new buyers at existing accounts need working, flag them with a property instead of relying on lifecycle.
  • Note Renaming stages and status values. Before renaming a stage or a lead status option, check the stage's Used In column and every workflow branch, list and report that compares against it. Only Super Admins can edit lifecycle stages.

What HubSpot does by itself

  • HubSpot tools only move the stage forward. Imports, form submissions, the API, the Salesforce integration and workflows can only move the default Lifecycle stage property forward. To set an earlier stage with them, the value has to be cleared first, by hand or in a workflow.
  • A backward set fails in a workflow. If a workflow's Edit record action would set an earlier stage, the action fails and the action log says the lifecycle stage would have been set backwards.
  • Competing writes aren't last-write-wins. Because automatic updates only move forward, a later workflow, import, form or integration write to an earlier stage doesn't replace a later stage: the record keeps the furthest-along stage any of them set. Only a manual edit, or a write after the value has been cleared, can move it back, and then the order of the writes decides the result.
  • People can move it backward by hand. A user editing the record can pick any stage. HubSpot then clears the legacy "Became a [stage] date" for the later stage.
  • The lifecycle settings never go backward. The deal-created, deal-won, lead-associated and company-sync settings won't set an earlier stage. A contact already at Customer stays Customer when a new deal is created.
  • Forms set a stage on new and existing contacts. A form's lifecycle stage setting overrides the account default. A contact already at a later stage keeps it. A new contact from a form with no stage set gets the account default, or the first stage in display order if that setting is off.
  • Every stage gets date properties. HubSpot records the date each record entered and exited each stage. Latest-time and cumulative-time properties per stage need a Professional or Enterprise subscription.
  • Custom stages: all plans, Super Admins only. HubSpot lists creating and customizing lifecycle stages for all products and plans. Only Super Admins can add, rename, reorder or delete stages. A stage that has records or is used in lists, reports or other tools must be emptied and removed from them before it can be deleted, and a stage used as a default for a connected app can't be deleted.

How to choose your lifecycle stages

Lifecycle stage answers one question: how far along is the relationship with this contact or company? HubSpot ships eight stages (Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, Evangelist, Other), and they’re defined in HubSpot lifecycle stages. Choose yours with three tests:

  1. Each stage marks a handoff or a commitment, not an activity. “Marketing says this lead is ready” is a stage. “Opened three emails” isn’t.
  2. Each stage has one written entry rule and one owner. One form setting, one HubSpot setting or one workflow sets it. Nothing else does.
  3. Skip the stages nobody sets. A team without marketing qualification doesn’t need MQL, and an ecommerce store rarely needs Sales Qualified Lead. Leave unused stages in place rather than giving them a new meaning.

Add a custom stage only when a real handoff has no default home, such as a product-qualified lead in a self-serve motion. Sales activity belongs in lead status, and the buying process belongs in deal stages. See lifecycle stage vs lead status vs deal stage.

Let HubSpot set what it already can

HubSpot’s lifecycle settings can set a stage when a record is created, when its first deal is created, when a deal is won and when a lead record is associated, and can copy a primary company’s stage to its contacts. Forms carry their own stage too. Use those before writing workflows, and build workflows only for the rest, usually MQL and SQL. How to set lifecycle stage with a workflow covers the pattern.

Common mistakes

  • Two writers for one stage. A form sets MQL and a scoring workflow also sets MQL, or a workflow duplicates the deal-won setting. This is why a lifecycle stage keeps changing.
  • Expecting a workflow to move a stage backward. HubSpot tools only move lifecycle stage forward. A backward set fails unless the value is cleared first, and a broad clear-and-set workflow can push customers back to Lead.
  • Lead status repeating lifecycle. Values like “MQL” in lead status give you two properties that have to agree.
  • Triggers that fire on every write. A workflow triggered when lifecycle stage changes runs on every form, import and setting that touches it. Read how property-change triggers work first.

How to roll out a change safely

  1. Write the brief first. Export it from the builder above and get marketing and sales to agree on the definitions.
  2. Find every current writer. Check the Lifecycle stage property’s usage, the lifecycle settings, forms, imports and integrations. See which workflows use a property.
  3. Turn off the extra writers before adding the new ones, so property history stays readable.
  4. Build new workflows switched off, test them on a few records, then decide whether to enroll existing contacts.
  5. Update lists, reports and branches that compare against any stage or lead status value you renamed.
  6. Watch property history for a week. The source column shows which tool made each change.

A Jetstack AI Workflow Audit shows every workflow that writes lifecycle stage and flags competing actions between them. Once the brief is agreed, Jetstack AI Projects can build it: upload the brief, review Jetty’s plan of stages, properties and workflows, approve it, then approve the deployment separately and check the receipt. Workflows are created switched off, and Projects is currently in limited release.

Want a hand with this project?

Get a partner recommendation.

We work with experienced HubSpot partners. Tell us about the portal and the work, and we'll recommend one that fits your scope, timeline and budget.

HubSpot lifecycle stage builder

Questions about this tool.

Can I add custom lifecycle stages on any HubSpot plan?

HubSpot's guide to creating and customizing lifecycle stages lists it for all products and plans. Only Super Admins can add, rename, reorder or delete stages. HubSpot doesn't document a limit on the number of stages.

Why can't a workflow move a contact back to Lead?

HubSpot tools, workflows included, only move the default lifecycle stage forward. A workflow that tries to set an earlier stage fails. To move a record back on purpose, clear the lifecycle stage in one action and set the earlier stage in the next, and keep that workflow's enrollment narrow.

Should lead status change when lifecycle stage changes?

Only at the handoffs: set lead status to New when a contact reaches the stage where sales starts working it, and to Open Deal when a deal is created. Everything in between is the rep's call. Lead status tracks sales work; it shouldn't repeat lifecycle stages.

Sources

HubSpot changes often. Spotted something out of date? Tell us at team@jetstack.ai.

Planning & implementation

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