Lead Lifecycle Stage
A lead lifecycle stage is a single, named position within the lead lifecycle (such as MQL or SQL) that describes how far a contact has progressed toward becoming a customer.
Key takeaways
- A complete stage names entry criteria, an owner, a next action and an exit condition.
- Entry strictness controls volume; exit clarity controls how long contacts sit.
- Pairing a hard attribute with a behavioural event makes a stage hard to game.
- Timers move contacts out of a stage without them meeting anyone's criteria.
- Stage names are company-specific, so external conversion benchmarks compare different tests.
In depth
A stage is a definition, not a label. A complete one names four things: the condition a contact must satisfy to enter, the person or team accountable while it sits there, the action expected next, and the condition that moves it out. Written that way, a stage becomes testable, because you can take any contact and check whether it belongs where it is. Written as a name only, it becomes whatever the person updating the record believes it means.
Two settings decide how a stage behaves. The strictness of the entry criteria controls volume: raise the bar and fewer contacts qualify but each is worth more attention. The clarity of the exit condition controls ageing: if leaving is defined only as 'sales decides', contacts pile up. Adding a time limit is the usual fix, but it trades accuracy for movement, since a contact pushed out by a timer has not actually met the criteria for anywhere else.
Most stage definitions combine one hard attribute with one behavioural event, because either alone is easy to game. A marketing-qualified stage might require a business email address plus a completed assessment above a threshold. In a Pivix funnel both halves come from the same submission, so the stage can be set at the moment the quiz result is written rather than by a nightly job, and the result page itself can present the action the stage expects next.
A stage compresses a situation into one token, and some situations do not compress. A contact who is perfect but on parental leave, or who is evaluating for a subsidiary rather than the parent company, fits no stage well and will be filed somewhere misleading. Stage names also travel badly between companies: your sales-qualified is not the same test as anyone else's, so benchmarking stage conversion against outside figures compares two different definitions rather than two different funnels.
Example in practice
How to measure it
Three numbers describe a single stage: how many contacts entered it in a period, what share left for the next stage, and how long the median contact stayed. Read the third first, because a long median with a healthy conversion rate means the stage works but slowly, which is a capacity problem rather than a quality one. Break the median by source to find which channel is clogging it.
Add one audit that is not a metric: sample twenty contacts sitting in the stage and check each against the written entry criteria. The share that would not qualify today is your definition drift, and it is usually higher than anyone expects. Repeat it quarterly. A stage that passes this audit can be trusted in forecasts; one that fails it makes every downstream number optimistic.
Common mistakes
The recurring failure is defining a stage by who owns it instead of what is true. 'Sales-qualified means sales accepted it' describes a handoff, not a condition, so acceptance rates swing with how busy the team is rather than with lead quality. Write the criteria as facts about the contact, such as role, problem stated and meeting booked, and let acceptance be the check that those facts hold, not the definition itself.
The second is changing a definition without versioning it. Somebody raises the qualifying score in March, and the year-on-year stage conversion chart now compares two different populations while looking continuous. Record the date every definition changes and annotate reports at that point. If a change is large, run the old and new rules in parallel for one cycle so the size of the shift is known rather than inferred.
Frequently asked questions
How is a lifecycle stage different from a lead status?
A lifecycle stage describes overall progress toward becoming a customer, while a lead status (like 'attempting contact') tracks a sales rep's micro-activity within a stage. Both coexist and serve different reports.
Should every stage have exit criteria?
Yes. Each stage needs both entry and exit criteria so contacts advance only when they meet a clear bar. Without them, stages become subjective and conversion metrics lose meaning.
How do quiz scores map to lifecycle stages?
You define a score threshold per stage, for example a score above 60 makes a contact an MQL. The scorecard assigns the stage automatically and can trigger the matching result page and follow-up.
What makes a good stage definition?
One a third party could apply without asking anyone. It states an observable entry condition, names one owner, gives the expected next action and says what ends the stage. Avoid adjectives: 'engaged' and 'qualified' mean nothing on their own, whereas 'answered the assessment and selected a timeline within six months' can be checked against the record.
Can a contact be in two stages at once?
No, and systems that allow it produce numbers that do not add up. A contact holds one current stage; anything else you want to know goes in a separate field, such as the highest stage ever reached or the date each stage was entered. If two teams need different views of the same contact, give them different fields, not a second stage value.
Should a quiz score alone move a contact to MQL?
Usually not on its own. A score measures fit and interest but says nothing about whether the contact is reachable or real, so most definitions pair the threshold with a verifiable attribute such as a business email domain. The score decides priority within the stage; the attribute decides whether the stage applies at all.
How long should a contact stay in one stage?
Long enough for the expected next action to happen, and no longer. Compare the median time in stage against how long that action realistically takes: a stage whose next action is a phone call should clear in days, one whose next action is a procurement review may take weeks. Anything sitting past three times the median needs a review, not a reminder email.
Who should be allowed to change a contact's stage?
Automation for the rules that can be evaluated, and one named role for the exceptions. Most transitions should fire from an event: a form submitted, a meeting booked, a deal created. Manual changes should require a reason, because they are the only way to tell a genuine judgement call from someone tidying their queue before a review.
Do we need a stage for disqualified contacts?
Yes, otherwise they stay in whatever stage they were in when the decision was made and inflate it. A disqualified stage should record why, because 'wrong industry' and 'no budget this year' need different treatment: the first is permanent, the second is a date to revisit. Without the reason code, the stage becomes a place records go to disappear.