Lifecycle Stage Definitions template.

What's inside — the exact file

This is the complete template, not a sample. The rows are worked examples — replace them with your data (and delete them before any platform import).

What this template is for

Every HubSpot portal has lifecycle stages; almost none has written definitions for them. The result is predictable — marketing calls something an MQL that sales won't touch, 'opportunity' means three different things, and funnel reporting is fiction. This worksheet is the document that fixes it: every default stage with a written definition, entry and exit criteria, and a named owner for each transition.

It's pre-filled with workable definitions for all eight default stages (subscriber through evangelist) as a starting position. The value isn't our words — it's making your team argue to agreement in a spreadsheet instead of in a pipeline review.

How to use it, step by step

1. Get marketing and sales in one room. Lifecycle definitions are a treaty, not documentation. Both sides edit the definitions until they'd both defend them — that argument is the actual deliverable.
2. Make entry criteria mechanically checkable. 'Shows buying intent' can't drive automation. 'Submitted a demo request or hit a lead score of 50' can. Every entry criterion should be something a workflow could evaluate.
3. Name the mover for every transition. Each stage change is done by someone or something — a form, a workflow, a rep, an integration. The automation_that_moves_it column exposes the gaps where records get stuck.
4. Reconcile the definitions with your portal's reality. Audit a sample of current records against the new definitions. The mismatch count tells you how big the cleanup is — usually bigger than expected, and worth doing before automation trusts the stages.
5. Build the workflows to match. Implement the agreed transitions as HubSpot workflows, using exactly the criteria written here. The sheet is the spec; the portal should be its implementation.
6. Revisit quarterly with funnel data. Conversion rates between stages tell you whether definitions hold — a 2% MQL→SQL rate usually means the MQL definition is too loose, and this sheet is where you tighten it.

What each column means

Common mistakes to avoid

• Letting each team keep a private mental definition of MQL — the sheet exists to kill exactly this.
• Writing aspirational criteria your data can't evaluate (intent, budget) instead of signals your portal actually captures.
• Moving stages backward casually — HubSpot allows it, but backward moves corrupt funnel conversion reporting; disqualification usually belongs in a lead status, not a stage regression.
• Defining stages and never wiring the workflows, leaving the movement manual, inconsistent, and eventually abandoned.

Questions, answered

What's the difference between lifecycle stage and lead status?

Lifecycle stage is the macro funnel position (lead → MQL → SQL → opportunity → customer). Lead status is the working-state detail inside the sales handoff (attempting contact, connected, unqualified). Conflating them is the most common lifecycle mess we untangle.

Can we rename or add lifecycle stages?

HubSpot allows customizing lifecycle stages, but the defaults carry built-in reporting benefits and integrations expect them — as of July 2026, our advice is to customize only with a written reason, and to exhaust lead status and custom properties first.

Which stage should imported contacts get?

The stage their evidence supports, decided per list — event scans are leads, current clients are customers, newsletter signups are subscribers. Defaulting everything to one stage is how funnels lie; this sheet's definitions are the sorting rule.

This is a Market Disrupt worksheet, not a vendor file. Import-format templates follow each platform's documented layout as of July 2026 — platforms evolve, so validate against current documentation before a large import.