An outbound CRM model answers three separate questions: where a person is in the journey, what the team should do now, and what happened in the latest attempt. Keep those answers in separate fields so the record guides work and explains results. Lifecycle stages track how contacts or companies move forward through a process.1 Lead status values organize and prioritize leads and give the team a consistent way to discuss the funnel.2 A disposition records an outcome that the team can use for future work.
Start with the field boundary
Before naming values, decide which question each field answers. If two fields answer the same question, people will use the easier one and reports will split.
| Field | What you are trying to capture | Example question |
|---|---|---|
| Journey stage | Where the person is in the buyer journey3 | Where is this person in the journey? |
| Work status | The person's current relationship to the company4 | What should happen next? |
| Disposition | Whether the latest outcome is a not-now result or a structural campaign problem5 | What happened on this attempt? |
| Re-entry rule | Whether the person can enter, exit and re-enter the journey6 | What happens if this person returns? |
Keep the fields separate even when their labels feel related. A stage describes movement through the process. A status tells the team how the record stands now. A disposition records the result of a specific attempt.
Define the journey stages
Write the journey as a sequence of observable checkpoints. Give each stage an entry condition, an exit condition and a question that someone can answer from the record.
Lifecycle stages categorize contacts and companies according to their position in marketing and sales processes.7 Tracking can begin when Marketing acquires a name and continue as the person enters, exits and re-enters the buyer journey.6
Use this order as a starting structure for outbound work:
| Stage | What you are trying to learn | Example question |
|---|---|---|
| Acquired | Whether the record came through enrichment, prospecting or list purchase without enough interaction to become an MQL8 | How did this record enter the process? |
| Contact | Whether the path moved from a cold target to a contact and established the reason for reaching out9 | What prompted the outreach? |
| Qualified | Whether the person completed an activity that meets Marketing's definition of a qualified lead10 | What activity met the qualification rule? |
| Opportunity | Whether the process reached an opportunity with sales ownership11 | What evidence supports the handoff? |
| Outcome | Which journey applies to a Closed-Won or Closed-Lost result12 | What path follows this outcome? |
Email, call and list-import events belong to activities or acquisition events. Stages describe where the person has reached in the journey and what condition allows movement.
Define statuses as work states
A status should help someone decide what to do with the record today. Keep its values broad enough for quick use and precise enough to change the next action.
Lead Statuses quickly show how a Lead is represented within a sales process.13 Start with high-level statuses while the process is still being developed.14 Update the customizations as the team builds and refines the process.15
Have the sales department and marketing team define the values together.16 For each value, write the event that sets it, the evidence needed to leave it and the next action it creates. Remove any value that cannot change what someone does or what a report tells you.
Status values can prompt Sales to call a contact and help track funnel performance.17 Keep the field current as work changes so the record shows the current relationship and the next useful action.
Record dispositions as outcomes
A disposition belongs to an attempt or conversation. It preserves what happened so the next action does not depend on memory.
Track not-now outcomes over time, re-engage them on a cadence and distinguish them from dispositions that signal a structural problem with the campaign.5 Use the disposition to record the outcome, then use the status or next-action field to control what happens afterward. This keeps a temporary pause from looking like a failed market and keeps a recurring campaign problem from being buried among routine deferrals.
For a not-now result, require a reason and a point when the record should be reviewed again. When the result signals a structural problem, route it to a campaign review instead of ordinary follow-up. Give each outcome a clear owner and next action.
Make the model maintainable
A workable model needs rules for entry, movement, ownership and reporting. Put those rules in the field description and test them against real records before the team relies on them.
Configure the main areas of the system before selling begins.18 For each lifecycle stage, define the event that moves a record into it and the condition that permits movement out. For each status, define who changes it, when it changes and what work follows. For each disposition, define whether the record is re-engaged, reviewed for a campaign problem or removed from active work.
Lifecycle stages can be updated through settings, workflows or manually.19 Changes in lifecycle stage can also be tracked with corresponding calculated properties.20 Default automatic updates only move records forward.21 Test every automatic update against records that leave and later re-enter the journey.
Use the model to build routing and reporting around the same milestones. Sales teams benefit from clear qualification milestones and automated routing based on stage progression.22 Accurate tracking of lead flow, outreach and conversion helps Marketing filter work and helps Sales prioritize outreach.23
What not to do
- Do not leave records in vague labels such as "working" or "contacted" for weeks or months. Those labels hide work volume, bottlenecks and changes in conversion rates.24
- Do not create too many, too few or unclear status values. They make the process unclear, increase busywork and hinder growth.25
- Do not use a status to represent a campaign name. One example used a status called "New 2020" for high-value leads imported for a new campaign.26
- Keep journey stage and status in separate fields. The differences between them are nuanced but real.27
- Do not rely on a forward-only automatic update to handle re-entry, because default automatic updates only move records forward.21
Audit each field by asking which journey stage it represents, what the current status demands and what disposition explains the latest outcome. Build views and handoffs around those answers. Change a label only when the work or report it controls changes.