Lead Lifecycle
The lead lifecycle is the full sequence of stages a contact moves through with your business, from the first interaction to becoming a customer (and beyond).
Key takeaways
- Each contact holds exactly one lifecycle state, which is what makes the model countable.
- Transition rules carry the value; the stage names are only a convention.
- Assign one owner per transition so a stage is a fact, not an opinion.
- Build the lifecycle backwards from closed customers, not forwards from traffic.
- Contacts and buying decisions diverge when several stakeholders share one purchase.
In depth
A lifecycle is a state machine drawn over your contact database. Each contact holds one state at a time, transitions are triggered by defined events, and no contact can be in two states at once. That single-state constraint is what makes the model countable: at any moment you can say how many contacts sit in each state and how many moved between them last week. The stages themselves are a naming convention; the value lives in the transition rules.
The number of stages is the main lever. A short lifecycle is easy to keep accurate but hides where deals actually stall; a long one exposes detail and decays quickly because nobody updates the middle. The other lever is who owns each transition. If both marketing and sales can promote a contact, the stage becomes an opinion. Assign exactly one owner per transition and the reporting stays trustworthy even when the definitions are imperfect at the edges.
In practice the lifecycle is built backwards from the customer stage: list what a closed customer did, name the last checkpoint before that, and keep working upstream until you reach anonymous traffic. A quiz funnel usually supplies the first named transition, since a Pivix scorecard turns a visitor into a contact with a score attached in one step. From there the CRM owns the record, and each subsequent transition fires from a booked meeting, a proposal sent, or a signature.
A lifecycle describes a person, not a purchase, and the two diverge in account-based selling where five contacts at one company sit in five different stages while the company has a single buying decision. Products with expansion revenue break it too, because the customer stage is an end state and there is nowhere to record a second purchase. And a lifecycle that is not enforced by automation drifts within a quarter into whatever each rep felt like recording.
Example in practice
How to measure it
Two families of numbers describe a lifecycle. Conversion between adjacent stages shows where contacts are lost, and time in stage shows where they are stuck; a stage can look healthy on conversion while holding contacts for months. Read them together, and always compare cohorts that entered in the same period rather than everything currently in the database, which mixes fast and slow arrivals.
Two hygiene checks matter as much as the headline rates. Count contacts that have not changed stage in longer than your median sales cycle; a large number means the model is recording history rather than status. And count backwards transitions. A lifecycle with none is not clean, it is unenforced, because in reality some contacts do move down.
Common mistakes
The first failure is a one-way model. The lifecycle is drawn as an arrow, and there is no state for a contact who was rejected by sales, went quiet for a year and then returned. Those contacts either sit forever in an advanced stage they no longer deserve or get reset to the beginning, and both distort conversion reporting. Add an explicit recycled state with its own entry rule and its own owner.
The second is copying a vendor's default stages without checking that each one changes somebody's behaviour. Teams end up with a stage nobody enters and another that half the database is stuck in, and reviews turn into arguments about definitions instead of about pipeline. Delete any stage that triggers no different action, and merge two stages whenever contacts pass through both within the same day.
Frequently asked questions
What are the typical lead lifecycle stages?
Common stages are visitor, lead, marketing-qualified lead, sales-qualified lead, opportunity, and customer. Some teams add subscriber at the top and evangelist after the sale.
Who owns the lead lifecycle?
Ownership is shared: marketing typically owns the early stages and sales owns the later ones, with RevOps defining the transition criteria. Clear handoff rules prevent leads from falling through the cracks.
How does a quiz funnel fit into the lifecycle?
A quiz funnel sits at the very top, converting anonymous visitors into named, scored leads. The score determines the starting lifecycle stage and can trigger the right nurture path automatically.
How many lifecycle stages should we define?
Enough that each one changes what somebody does, and no more. Most B2B teams land on five or six: visitor, lead, marketing-qualified, sales-qualified, opportunity, customer. If two adjacent stages always trigger the same follow-up, merge them. The right test is not completeness of the model but whether a rep behaves differently depending on which stage a contact is in.
Who owns the lifecycle, marketing or sales?
Ownership is per transition, not for the model as a whole. Marketing typically owns everything up to the handoff, sales owns everything after, and one person, usually in revenue operations, owns the definitions themselves. The important rule is that only one function can trigger any given transition; shared write access is the fastest way to make the reporting meaningless.
Can a contact move backwards through the lifecycle?
Yes, and a model that forbids it is lying. A sales-qualified lead who cancels three meetings is no longer sales-qualified. Allow demotion, but require a reason code so the movement is analysable, and keep the highest stage ever reached in a separate field. That way conversion reporting can still count the contact as having passed through the stage.
Where does a quiz or scorecard sit in the lifecycle?
At the first named transition, where an anonymous visitor becomes an identified contact. The submission supplies both the identity and the qualification data, so the contact can enter at a stage determined by its score rather than at the bottom by default. High scorers can skip the early stages entirely, provided the entry criteria for the stage they land in are genuinely met.
What happens to a contact after they become a customer?
That depends on whether you sell again. If renewals and expansion matter, the lifecycle needs states after customer, such as onboarding, active and at-risk, owned by customer success rather than sales. If you sell once, customer is a terminal state and the contact leaves the acquisition reporting. Either way, decide explicitly, because an undefined end state fills up with stale records.
How does the lifecycle relate to the sales pipeline?
The lifecycle tracks people, the pipeline tracks deals. One contact can generate several deals over time, and one deal can involve several contacts, so the two are separate objects in most CRMs. The link is a single transition: when an opportunity is created, the contact reaches the opportunity stage. Reporting on them as one thing produces double counting.