Use three questions to build the model: Where is this person in the journey? What is their current relationship with the company? What happened in the latest motion? Lifecycle stage covers journey position, status covers the current relationship,1 and disposition captures the outcome. Vague labels such as 'working' or 'contacted' become a problem when they sit unchanged for weeks or months. The team can no longer see how many records are active or where work is stuck.2 Give each field one job so the CRM is easier to act on.
Separate the fields
Decide which question each field answers. Keep campaign details, journey position, current action and outreach outcomes from competing inside one dropdown.
- Lifecycle stage: Use it for the person's position in the buyer journey. Stage tracking can follow a person as they enter, exit and re-enter that journey.3
- Status: Use it for the person's current relationship with the company. Statuses give a quick view of how a lead is represented in the sales process.4
- Disposition: Use it for the result of the outreach or decision point. Keep an outcome that means 'not now' separate from one that signals a structural campaign problem.5
Do not ask a status to explain where someone came from, whether they qualify, what happened on the last attempt and what should happen next. Put each question in the field that owns it. When a value answers more than one question, people update it inconsistently and reporting loses its meaning.
Define the lifecycle stage
Use lifecycle stage to describe movement through the journey. Write the entry condition, exit condition and, when needed, the event that allows a record to move back into the journey.
Start with high level stages while the sales process is still being developed.6 Change preloaded or generic stages to reflect the process your team actually runs.7 Each stage should tell someone reading the record what kind of relationship exists and what threshold the person has crossed.
If the model uses acquisition and qualification stages, define them in plain language. MAL means a name acquired through enrichment, prospecting or list purchase that has not interacted with the brand enough to become an MQL.8 MQL means a person has completed an activity that meets marketing's definition of a qualified lead.9 Keep these definitions in the stage documentation so the same label means the same thing across the team.
The journey can include exits and re-entry, while default automatic lifecycle updates move records forward through the stages.10 Decide how to handle a returning person before switching on automation. A manual correction may be needed when the journey moves backward in reality but the default automation does not.
Define the status
The person working the record should be able to see the current relationship and the action it is ready for without opening the activity history.
Lead status values organize and prioritize leads while giving the team a consistent way to communicate about the funnel.11 They can also prompt Sales to call a contact and support funnel measurement.12 Base each status on an observable condition, then define the action that follows it, the event that ends it and the person responsible for changing it.
Keep status values broad enough for consistent use. A developing process benefits from a short set of high level values, which can change as the process becomes clearer.13 If the team needs a new value, ask what decision the current set cannot support. Add it only when it creates a distinct action or report.
Use status to show the current relationship. Keep campaign, source and qualification details in their own fields. A campaign label can describe where a record came from, while status tells the team what to do with it now.
Record the disposition
Disposition closes the loop on an outreach result. It preserves what happened without taking over the lifecycle stage or current status.
When an outcome means 'not now', keep it visible over time and give it a re-engagement cadence. Keep that outcome separate from dispositions that expose a structural campaign problem.5 This lets the team recover timing issues while still seeing problems with targeting, messaging or process.
Define what happens after a win and after a loss before records reach those points. The sales and marketing team should map the journey for both Closed Won and Closed Lost scenarios.14 Write the next destination, ownership and follow-up rule for each outcome, then use the same definitions in the CRM and reporting.
Read a record without its activity history as a test. The lifecycle stage should explain its place in the journey, the status the present relationship and the disposition the latest outcome. If one field has to borrow meaning from another, revise the definitions.
Run the workflow
Use the fields in a fixed order when a new record enters the outbound process. This keeps classification separate from the result of the work.
- Classify the lifecycle stage from the person's current journey position.
- Set the status from the current relationship and the action the team can take now.
- Run the outreach using the status as the operating signal.
- Add the disposition when the outreach produces a clear outcome.
- Review outcome labels over time, sending 'not now' records into their agreed cadence and isolating structural campaign problems.
Track flow, outreach and conversion together so the team can prioritize records and plan work from the same view.15 Review whether a stalled record reflects a real pause, a missing disposition or a status nobody understands. Finish the design when each record can be classified without an explanation from the person who entered it.
Lifecycle stages can be updated automatically through settings or workflows, and they can also be updated manually.16 Track stage changes with the corresponding calculated properties when the CRM supports that approach.17 Automate only transitions with clear entry conditions. Leave exceptions visible for review instead of forcing every record through a rule that cannot represent its journey.
Govern the model
Treat field definitions as part of the operating process. Revise the model as the team learns which values create decisions and which create confusion.
Have the sales department and marketing team define the statuses together.18 Before selling begins, customize the main CRM areas that control the process.19 For every value, record its meaning, entry rule, exit rule, owner and permitted next action. Keep this definition beside the field configuration so a new user can apply it without relying on tribal knowledge.
Review the values after the team has used them in real work. Teams can update their customizations as they build and refine the sales process.13 A change is ready when it makes an existing decision clearer, removes duplicate meanings or improves an important report.
What not to do
- Do not create more lead statuses than the process needs.20
- Do not let the status field become the default contact property for every situation.21
- Do not use a status to represent a campaign. One example used the status 'New 2020' for high value leads imported for a campaign.22
- Do not accept too many, too few or unclear values that increase Sales busywork and obscure the process.23
- Do not treat status as an occasional afterthought that gets updated only when someone remembers or when a manager asks.24
Before the next outbound block, map every existing value to lifecycle stage, status or disposition and remove values that answer multiple questions. Test the model on records with different journey positions and outcomes, and check whether the next action is clear from the fields alone.