Blog · Territory, capacity and quota planning
The customer lifecycle describes how an account moves from acquisition through repeat purchases, inactivity, and return. Define each stage, compare customer counts, revenue, retention, and service costs, and reconcile the results to your exports.
The customer lifetime cycle, usually called the customer lifecycle, describes how an account moves from acquisition to first purchase, repeat business, inactivity, and return. A useful report assigns a dated stage to each account and compares the outcomes within those stages. The labels matter less than having rules people can reproduce from the same files.
A lifecycle is a relationship framework. HubSpot describes the lifecycle from initial awareness through purchasing and the ongoing customer relationship. It is not expected customer lifespan, a profit forecast, or a map of every conversation. Accounts can move backward, skip a stage, or return after a gap.
Use a stage dictionary with an owner and a triggering event. The following is a policy for an illustrative US business supplier, rather than a universal standard.
| Stage | Rule at the monthly cutoff | Useful measure | Action owner |
|---|---|---|---|
| Prospect | Qualified account with no completed purchase | Qualified accounts becoming customers | Sales |
| New | First completed purchase occurred this month | First purchasers and follow-up readiness | Sales operations |
| Active | Established buying relationship with no higher-priority flag | Revenue per account and purchase retention | Account management |
| At risk | Open relationship with a documented renewal or service concern | Revenue exposed and unresolved issues | Account management |
| Dormant | No current purchase and beyond the approved buying-gap threshold | Dormant accounts and carrying costs | Sales operations |
| Reactivated | Purchased after previously meeting the dormant rule | Returning purchasers and revenue | Account management |
Apply precedence when conditions overlap. For this policy, reactivated and new take priority over at risk; at risk takes priority over active. Dormant requires the buying-gap test, so a customer does not become dormant simply because it has an open issue.
Record the reason and effective date behind an at-risk flag. A manager's concern can be useful, but it should remain visibly different from a purchase event. Review the policy when buying patterns change; do not rewrite old stages silently.
Start with an account export containing a stable account ID, owner, stage, stage effective date, and snapshot date. Add a transaction export with account ID, order or invoice ID, posting date, and net revenue in USD. Add service records with account ID, service date, and a consistently assigned cost.
The account file supplies the reporting population. Transactions explain what each account bought. Service records explain what supporting that relationship cost. Aggregate the last two by account before combining them with the stage snapshot; joining every invoice directly to every service record can multiply both amounts.
Decide whether the report uses the stage at transaction date or the stage at the reporting cutoff. This example uses the September 30, 2026 stage and September activity. It answers what accounts in each current stage contributed during the month, including activity before their latest stage change.
Keep costs on the same basis across stages. Use the cost-to-serve method for allocation details, and keep customer lifetime cost separate from this month's service spending.
These are all the account rows for the example. Revenue is September net sales; service cost is September support effort valued under the supplier's stated allocation policy. The prior-purchase flag records whether the account purchased in August.
| Account | September 30 stage | Purchased in August? | Revenue (USD) | Service cost (USD) |
|---|---|---|---|---|
| A | Prospect | No | 0 | 120 |
| B | New | No | 2,400 | 600 |
| C | Active | Yes | 5,000 | 700 |
| D | Active | Yes | 3,000 | 450 |
| E | At risk | Yes | 2,000 | 500 |
| F | Dormant | Yes | 0 | 180 |
| G | Reactivated | No | 1,800 | 420 |
| H | Dormant | Yes | 0 | 90 |
| Total | 14,200 | 3,060 |
F and H crossed this supplier's approved inactivity threshold during September. G had purchased before August and returned after a dormant interval; its August flag alone would not prove reactivation. Keep that historical evidence in the account file.
Group the rows by their declared stage:
| Stage | Accounts | Revenue (USD) | Service cost (USD) |
|---|---|---|---|
| Prospect | 1 | 0 | 120 |
| New | 1 | 2,400 | 600 |
| Active | 2 | 8,000 | 1,150 |
| At risk | 1 | 2,000 | 500 |
| Dormant | 2 | 0 | 270 |
| Reactivated | 1 | 1,800 | 420 |
| Total | 8 | 14,200 | 3,060 |
The counts must equal the account export. Revenue and service costs must separately equal their source totals. Prospects belong in the account population but not the customer count: the report contains seven accounts with purchase history and one prospect.
Revenue per stage account = Stage revenue / Accounts in that stage
Prior-period purchase retention = Prior-period purchasers who also purchased this period / Prior-period purchasers
Active-stage revenue per account is 8,000 / 2 = $4,000. Its service-cost share is 1,150 / 8,000 = 14.4%, rounded to one decimal place. The whole population's service-cost share is 3,060 / 14,200 = 21.5% on the same basis.
Those ratios are service-cost comparisons, not profit margins. Product cost, selling expense, and other expenses have not been deducted. A zero-revenue stage has no meaningful service-cost-to-revenue percentage; show the dollar cost instead of dividing by zero.
The August purchasers were C, D, E, F, and H. C, D, and E purchased again in September, so prior-period purchase retention is 3 / 5 = 60.0%. B and G increase September purchasing activity, but neither belongs in that retention numerator. Contract retention and net revenue retention answer different questions.
In Excel, with the account table in A2:E9 and a stage name in G2, count accounts with =COUNTIFS(B2:B9,G2). Microsoft documents that COUNTIFS counts rows meeting all specified criteria. Sum stage revenue with =SUMIFS(D2:D9,B2:B9,G2); SUMIFS adds values that meet the criteria. Use column E for service costs. Covirage is not affiliated with HubSpot or Microsoft.
The example gives different owners specific questions. Account management can review E's documented risk alongside its $2,000 of revenue. Service leadership can investigate the $270 spent on dormant accounts F and H. Sales can check whether B received the support needed for a second purchase.
None of those figures proves that a particular intervention will work. They identify the accounts, costs, and events to investigate. Record the action owner and due date, then review the next dated snapshot. The decision-latency guide explains how to measure the time between a finding and an assigned decision.
Bring your dated account snapshot, net-sales export, and service-cost file; Covirage maps the columns, and its tools compute and check stage counts, revenue, retention, and service-cost comparisons. The external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.
See Covirage for sales insights for the supporting business context.
A practical set is prospect, new customer, active customer, at risk, dormant, and reactivated. The labels are management choices. Define the events, dates, and precedence behind each label so an account receives one stage at each reporting cutoff.
No. Lifecycle describes the current relationship stage and movement between stages. Lifetime value estimates the economic value of a relationship over time. A lifecycle report can supply inputs to that estimate, but a stage label alone does not establish future value.
Review them on a schedule that matches the buying pattern and available records. A monthly review can work for frequent purchases. Businesses with long renewals should use contract or renewal events rather than calling a customer dormant after a quiet month.
Sales operations usually maintains account identities and stage rules, while finance reconciles revenue and service costs. Marketing and customer service own actions within their stages. Assign one report owner to resolve overlapping labels and keep the cutoff policy consistent.