What you’re working toward.
A transition contract that separates relationship milestones from day-to-day follow-up.
- Bring these people
- Sales and marketing process owners, with the CRM administrator
Have these inputs ready
- Your current lifecycle and lead-status values.
- A list of workflows, forms, integrations, and users that write either field.
- Examples of recycled leads, existing customers, and expansion opportunities.
Write down the questions
Lifecycle should describe the relationship to your business. A follow-up status should describe what is happening in the working queue. Agree the difference with sales and marketing before changing automation.
- Write one sentence for each field: lifecycle describes the relationship; follow-up status describes the work in progress. Add a concrete example of what each field must not represent.
- Review a sample record with sales and marketing independently. If their answers differ, fix the definition before changing the field.
A shared dictionary with examples and a business owner for each definition.
Define transitions
For every stage, document entry criteria, responsible team, evidence, and exceptions. Specify how recycled leads, returning customers, and multiple buying cycles are represented.
- For each transition, record from-state, to-state, evidence, authorized writer, timestamp, and exception. Decide which changes are milestones and which are reversible working states.
- Represent a returning customer or expansion as a new buying motion without erasing the established customer relationship. Choose the appropriate deal or lead process for the current motion.
A state-transition table that covers new business, recycle, and expansion.
Audit every writer
List the forms, imports, workflows, integrations, and users that change these fields. Remove conflicting rules. Preserve milestone dates when teams need historical conversion reporting.
- Trace every update path and note its trigger and precedence. Look for a form default or integration that overwrites a later qualification decision.
- Choose the authoritative writer for each automated transition. Disable or narrow overlapping rules in a controlled test, and preserve needed historical dates before changing logic.
A writer register with conflicts resolved and changes documented.
Validate the handoff
Test a new inbound lead, a disqualified lead, a recycled prospect, and a customer expansion. Check owner assignment and reports after each transition. Publish the definitions where the team can find them.
- Walk a record through new inquiry, attempted contact, qualification, disqualification, and recycle. Verify the task, owner, and reporting result after each move.
- Test a customer expansion separately. Confirm that the new opportunity does not restart acquisition reporting as if the customer were brand new.
A signed scenario test and a short field-usage guide for the team.
Two fields, two different questions
Illustrative semantics. Use the actual working-status field and values supported by your chosen process.
Know when the work is ready.
Use these checks in the handover. Keep evidence of the result and assign an owner to anything that still fails.
- Every automated transition has one accountable owner.
- Repeated form submissions do not reset a later milestone.
- Recycle and expansion tests preserve the intended historical reporting.
- The team can explain when to change each field.
Catch the problems early.
Using lifecycle as a task list
Attempted contact and follow-up due describe work, not necessarily a new relationship milestone. Mixing them makes conversion reports difficult to interpret.
Changing values without auditing writers
A forgotten integration can restore the old behavior immediately. Trace all update paths before switching the process.