Customer Lifecycle
Define the customer states that every CRM process depends on.
Key takeaways
- The first CRM decision is a shared language for customer state, not fields or screens.
- The basic lifecycle spans nine stages from Unknown and Lead through Customer, Active, Expansion, Risk, and Dormant, each with a key question.
- Define stages with observable conditions, keep the first version to 7-9 states, and separate account status from user status.
- Strong definitions are measurable: for example, Active means 3+ core events in the last 30 days and 2+ active users.
- A clear lifecycle shifts leadership meetings from counting leads to asking where customers get stuck and why.
The first CRM decision is not fields or screens. It is the shared language for customer state. If marketing, sales, success, and leadership use different meanings for "lead", "active", or "at risk", the system will drift no matter which tool you choose.
Basic Lifecycle
| Stage | Meaning | Key question |
|---|---|---|
| Unknown | Unidentified visitor or demand | What behavior should convert them into a known contact? |
| Lead | Contactable potential customer | Does this customer fit our ICP? |
| Qualified | Prioritized opportunity | Is there a clear reason to intervene now? |
| Opportunity | Active buying or adoption discussion | Is the next step and buyer visible? |
| Customer | Contract or purchase completed | Has initial value been delivered? |
| Active | Repeated usage or purchase | Is the core usage pattern stable? |
| Expansion | Additional value is possible | Where can we create a larger outcome? |
| Risk | Churn or contraction is possible | Which signal explains the risk? |
| Dormant | Long-term inactive | Is this account worth reactivating? |
Definition Principles
- Define stages with observable conditions, not intuition.
- Make stage transitions consistent across teams.
- Keep the first version small; 7-9 states are usually enough.
- Separate account status from user status when multiple people use the product.
- Document who can change status manually and what should be automated.
Good Definitions
| State | Weak definition | Strong definition |
|---|---|---|
| Qualified | Looks interested | Meets at least 2 of 3 ICP criteria and has a problem confirmed within 30 days |
| Active | Uses the product well | Has 3+ core events in the last 30 days and 2+ active users |
| Risk | Feels unhealthy | Core events down 50%, 2+ unresolved tickets, or renewal within 60 days |
Health Score for State Decisions
To stop splitting Active and Risk by intuition, combine observable signals into a single score. The example below weights four signals into a 0-100 score.
Operating Checklist
- Entry and exit conditions are written for every stage.
- Each status has an owner or automated rule.
- Exceptions are visible and reviewed.
- The CRM stage matches what customers actually experience.
Leadership Signal
A clear lifecycle changes the leadership meeting from "How many leads do we have?" to "Where are customers getting stuck, and why?"