How to Build a Lifecycle Stage Model Your Whole Team Agrees On

Ask marketing, sales and customer success what "Marketing Qualified Lead" means and you will often get three answers. Nobody is lying. Each team wrote its own definition in its own head, and the Lifecycle stage property quietly absorbed all three. That is why the MQL number in the board pack never matches the number sales says it received.

A lifecycle stage model only works when every stage has one written definition, one way of being set and one owner. This is the order we build it in, with the HubSpot settings behind each step.

Why Lifecycle Models Break Before Anyone Notices

The failure is rarely the stage names. It is everything around them:

• Definitions live in a slide, not the CRM. The deck from the kick-off meeting says what an SQL is. The portal does not, so new hires guess.
• Too many things set the stage. Forms, imports, a workflow, the Salesforce sync and a rep editing by hand all write to the same property. Nobody can say why a contact is where it is.
• The stage is used as a status. "Bad timing" and "No response" are lead statuses, not lifecycle stages. Adding them as stages breaks the funnel order.
• Nobody owns the handoff. Marketing owns MQL, sales owns Opportunity, and the gap between them belongs to nobody.

If your portal already shows these symptoms, our junk drawer post explains how they compound. The fix starts on paper.

Step 1: Write One Definition, One Trigger and One Owner per Stage

HubSpot ships eight default stages: Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, Evangelist and Other. HubSpot's lifecycle stage documentation defines each one and notes that Opportunity means the record is associated with a deal and Customer means at least one closed deal. Start from those before inventing new ones.

For each stage, write three lines. The example below is illustrative; your criteria will differ.

• Entry criteria. MQL: a contact at a target company has requested a demo, or meets an agreed lead score threshold your teams have set together.
• Exit criteria. MQL ends when sales accepts it (SQL) or rejects it with a reason.
• Owner. The person who answers for records stuck in this stage. One name per stage, not a team.

Keep custom stages to a minimum. If you need one, a Super Admin adds it in Settings > Data Management > Objects > Contacts > Lifecycle Stage, as HubSpot's guide to customising lifecycle stages describes. Each new stage automatically gets its own calculated properties, so do it before you build reports, not after.

Put each definition in the property's description field too. Then anyone who hovers over the stage in a record sees the agreed meaning, not a guess. Who owns the underlying data quality is a separate argument, and our post on who owns data quality covers it.

Step 2: Choose One Mechanism for Each Transition

Most lifecycle chaos comes from overlapping automation. Map every transition to exactly one mechanism:

• Subscriber and Lead. Set by form submissions or by the default stage for newly created records.
• MQL. A workflow using the Set a property value action, which needs a Professional or Enterprise subscription. On a Starter portal, keep this a manual, documented step rather than a mix of both.
• SQL. Set by sales when they accept the lead. Track the work inside SQL with the Lead Status property (New, Attempted to Contact, Connected, Bad Timing and so on), not with extra stages.
• Opportunity and Customer. Let deals drive them. In the Lifecycle Stage tab's Automate settings, turn on Set lifecycle stage when a deal is created and when a deal is won, as set out in HubSpot's lifecycle automation settings.

Decide on company sync deliberately. With Sync lifecycle stages on, the primary company's stage is applied to its associated contacts. That suits account-based selling, but it can push a junior contact to Customer the day the account signs.

Plan recycling too. HubSpot tools such as imports, forms, the API and workflows only move the default lifecycle stage forward. To send an unresponsive SQL back to Lead, a workflow must clear the property first and then set the earlier value. Add a recycle_reason property so the move is explained, not silent.

Step 3: Get Sign-Off With Real Records, Not Opinions

Agreement in a meeting room does not survive the first busy week. Agreement tested on your own data usually does.

1. Export a recent sample of contacts from each stage.
2. Put marketing, sales and customer success leads in one session. For each record, ask: under the written definitions, which stage should this be in?
3. Every disagreement is a definition gap. Rewrite the criteria until the room classifies the same record the same way.
4. Agree the handoff service level in writing: how quickly sales responds to an MQL and what happens if they do not. Set the time from your own sales capacity, not a borrowed benchmark.
5. Have each stage owner sign off the final one-page document, then restrict who can edit Lifecycle stage by hand, using property edit permissions if your subscription includes them.

A note on consent: a Subscriber stage is not a marketing permission. Lawful basis and subscription types are tracked separately, and our HubSpot GDPR checklist covers those settings for teams under UK GDPR and PECR.

Step 4: Measure the Model So It Stays Agreed

For every default and custom stage, HubSpot creates Date entered [stage] and Date exited [stage] properties. Professional and Enterprise portals also get Latest time in [stage] and Cumulative time in [stage]. These are the evidence for whether the model works.

• Stuck records. HubSpot's own example is a workflow that creates a follow-up task when Date entered Sales Qualified Lead is more than five days ago. Use your agreed service level instead of five days.
• Skipped stages. Filter Customers with no Date entered Marketing Qualified Lead. A high count means the model is being bypassed.
• Property history. Each record's lifecycle stage history shows which tool made the change. If one source dominates unexpectedly, your mechanism map from Step 2 has a leak.

Review these monthly with the stage owners. Our HubSpot audit checklist includes a full lifecycle integrity check, and the RevOps KPIs post shows which conversion metrics to report from these properties.

Frequently Asked Questions

What is a lifecycle stage model?

It is the agreed set of stages a contact or company moves through, from first interest to customer, with written entry and exit criteria and an owner for each stage. In HubSpot it lives in the Lifecycle stage property on contacts and companies.

What is the difference between lifecycle stage and lead status in HubSpot?

Lifecycle stage tracks where a record sits in the overall funnel. Lead Status describes the sales activity within the Sales Qualified Lead stage, such as Attempted to Contact or Bad Timing. Use lead status for sales follow-up, not extra lifecycle stages.

Can a lifecycle stage go backwards in HubSpot?

Not automatically. Imports, forms, the API and workflows only move the default lifecycle stage forward. To recycle a record you clear the value, manually or with a workflow, and then set the earlier stage.

Should we create custom lifecycle stages?

Only when a default stage cannot describe a real step in your process. Each custom stage needs Super Admin permissions, adds its own calculated properties and has to be reflected in reports, so start from the eight defaults.

Who should own the lifecycle stage model?

One person should own the model as a whole, usually in RevOps or marketing operations, with a named owner for each stage. The model owner chairs the monthly review and approves any change to definitions.