Lifecycle design
Define the stages, signals and ownership behind a reliable customer journey.
On this page
Separate lifecycle from pipeline
A lifecycle describes the relationship between an organization and a person or account. An opportunity pipeline describes a specific commercial process. Conflating them makes returning customers, multiple opportunities and account expansion difficult to represent.
Define entry and exit criteria
For each stage, write the business definition, permitted entry conditions, accountable team and expected next action. A score can support qualification, but the meaning of qualification should be understood outside the scoring tool.
Agree handoff expectations
A handoff needs an owner, a response expectation and a return path. Define what happens when a lead is uncontactable, rejected, routed to the wrong territory or held for later. Make the reason available to marketing and reporting.
Treat identity as an operational concern
People can change employers, use multiple addresses and appear in several tools. Decide how records are associated and what evidence is required before merging them. Account ownership rules should distinguish an individual contact from an organization relationship.
Review the exceptions together
Use representative scenarios with marketing, sales and customer success. Include reactivation, duplicate qualification, overlapping campaigns and existing customers. Review stalled handoffs and inconsistent stage movement after rollout.
Keep a transition ledger when history matters
A current stage is a snapshot. A transition record explains when the state changed, what triggered it and which rule was applied. Preserve the entity type because account, contact and opportunity transitions have different meanings. A business event can carry that context consistently across different CRM data models. Use the business change time for duration analysis and retain receipt time separately for operational monitoring.
{
"entity_type": "contact",
"entity_reference": "contact_1042",
"from_stage": "qualified",
"to_stage": "sales_accepted",
"reason": "owner_accepted",
"owner_reference": "team_enterprise",
"occurred_at": "2026-09-14T10:15:00Z",
"rule_version": "lifecycle_v3"
}Specify the ordinary exceptions
Reactivation, existing customers and rejected handoffs should be modeled before rollout. Otherwise teams often force records backward through a funnel to make an automation run. Keep the commercial relationship intact and represent the new activity or opportunity explicitly. Agree the appropriate CRM behavior for the chosen platform because native lifecycle rules may differ from a custom state model.
| Scenario | Modeling decision | History to retain |
|---|---|---|
| Existing customer enquires | Create or associate the new interest or opportunity. | Original customer relationship and new enquiry source |
| Sales rejects a lead | Record the rejection reason and return route. | Original qualification and receiving owner |
| Contact changes employer | Review the account association and active opportunities. | Previous relationship and evidence for reassociation |
| Opportunity reopens | Apply the agreed commercial stage rule. | Earlier close event and reopening reason |
Define the denominator before publishing conversion
Choose whether a conversion measure describes records created during a period, transitions occurring during a period or a fixed cohort followed over time. These are different populations. Define repeat qualification, merged records and stage reentry explicitly. A useful review can show the total eligible population, exclusions and unresolved identities alongside the resulting rate so teams understand why it changed.
Standards and documentation
Explore the protocol specifications and platform guidance for this topic.
Bring the contract into your operating environment.
Discuss an implementation