Blog · How-to guides · Sales teams
The sales life cycle connects qualification, selling, close and customer handoff. Map the evidence required at each stage, then measure conversion, aging and acceptance delays from CRM histories.
The sales life cycle maps the stages from a qualified prospect to a sale and the handoff into an ongoing customer relationship. It becomes measurable when each stage has an entry event, an owner and evidence that the next team has accepted responsibility. Stage counts alone cannot tell you whether that transition worked.
A stage should describe something that changed in the commercial relationship. Sending a proposal is observable; feeling confident about a deal is not a reliable stage definition.
OpenStax's description of the personal selling process includes qualification, presentation, handling objections, closing and follow-up. Your operating stages can combine those activities, provided their boundaries remain clear. The following is an illustrative map for a US business services company, not a required industry standard.
| Stage | Evidence to enter | Accountable owner | Evidence to leave |
|---|---|---|---|
| Qualification | Identified need and a contact able to discuss it | Sales development | Sales accepts the opportunity or records a rejection reason |
| Discovery | Accepted opportunity and scheduled buyer conversation | Account executive | Requirements and buying process documented |
| Proposal | Buyer receives a defined commercial offer | Account executive | Accepted terms, explicit loss or continued negotiation |
| Closed won | Accepted order under the company's bookings policy | Account executive | Customer handoff sent with the required information |
| Onboarding | Receiving team accepts the handoff | Implementation lead | Agreed completion evidence recorded |
| Retention or expansion | Customer is active and assigned an account owner | Account management | Renewal outcome or a separately tracked expansion opportunity |
Put the required fields and rejection reasons in the stage definition. The pipeline stage definitions guide explains how inconsistent meanings distort analysis. Keep that mapping stable during a reporting period, and identify a definition change when comparing periods.
Export opportunity ID, sales motion, owner, segment, stage-entry timestamp, close status and close date. Add the handoff-sent and handoff-accepted timestamps from the receiving team's records. Keep the original identifiers when combining those files.
For progression, count distinct opportunities that entered a stage, rather than the number of history rows. An opportunity that returns to proposal should count once in the cohort's proposal-entry total. Its repeated visits still matter when measuring time spent there.
For a handoff, decide what acceptance means. It might require a signed scope, billing contact and agreed start date. A blank accepted date means the handoff remains unaccepted; it does not mean a delay of zero.
This illustrative company qualified the following opportunities during September 2026. The observation date is September 30, 2026. Every date below is in September; a dash means the event has not occurred. To keep the example readable, discovery is combined with qualification in this export.
| Opportunity | Qualified | Proposal entered | Status at September 30 | Closed | Handoff sent | Handoff accepted |
|---|---|---|---|---|---|---|
| A | September 1 | September 3 | Won | September 8 | September 8 | September 9 |
| B | September 2 | September 5 | Won | September 12 | September 12 | September 15 |
| C | September 3 | September 7 | Lost | September 14 | — | — |
| D | September 4 | September 8 | Open | — | — | — |
| E | September 5 | — | Lost | September 9 | — | — |
| F | September 6 | September 10 | Won | September 19 | September 19 | September 20 |
| G | September 7 | — | Open | — | — | — |
| H | September 8 | September 12 | Won | September 22 | September 22 | September 24 |
Observed stage advancement = Distinct cohort opportunities entering the next stage / Distinct cohort opportunities entering the starting stage
| Measure | Calculation from the rows | Result |
|---|---|---|
| Qualification to proposal | A, B, C, D, F, H / all eight | 6 / 8 = 75.0% |
| Proposal to won | A, B, F, H / A, B, C, D, F, H | 4 / 6 = 66.7% |
| Qualification to won | A, B, F, H / all eight | 4 / 8 = 50.0% |
| Won to accepted handoff | A, B, F, H / the same won opportunities | 4 / 4 = 100.0% |
Percentages are rounded to one decimal place. These are observed rates at the cutoff, not final conversion rates: D and G remain open. A later report can show how the same cohort matured without replacing its original membership.
The population check is eight qualified opportunities = four won + two lost + two open. At qualification, six progressed, E was lost and G remains. At proposal, four won, C was lost and D remains. Each stage accounts for every entrant.
Winning a deal does not prove that delivery has what it needs. Measure elapsed calendar days between sending and acceptance, and list unaccepted handoffs separately.
| Opportunity | Sent day | Accepted day | Acceptance delay, days |
|---|---|---|---|
| A | 8 | 9 | 1 |
| B | 12 | 15 | 3 |
| F | 19 | 20 | 1 |
| H | 22 | 24 | 2 |
| Total | 7 |
Mean acceptance delay is 7 / 4 = 1.75 days. The sorted delays are 1, 1, 2 and 3, so the median is (1 + 2) / 2 = 1.5 days. Both figures are exact here.
In Excel, with sent and accepted dates in B2 and C2, calculate =DAYS(C2,B2) only for accepted records. Microsoft documents that DAYS subtracts the starting date from the ending date. Covirage is not affiliated with Microsoft.
For open-stage aging, D has spent September 30 minus September 8 = 22 days in proposal. G has spent September 30 minus September 7 = 23 days in qualification. Those are current-stage ages, not completed sales durations; sales cycle length owns that separate timing measure.
The sales manager reviews whether G has a valid next step and whether D is awaiting the buyer or an internal approval. The implementation lead reviews B's acceptance delay and checks which required information arrived late. Neither finding by itself proves that a person performed poorly.
Revenue operations owns the stage definitions and population reconciliation. Sales owns commercial progression. The receiving team owns acceptance, while account management owns the ongoing relationship. Use customer life cycle analysis for the broader acquisition, retention and expansion view.
Bring your CRM stage history and customer handoff file to Covirage. Covirage maps the columns, and its tools compute and check stage counts, conversion and acceptance delays; 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 export.
See Covirage for sales teams for the supporting team context.
There is no required stage count. Use enough stages to identify real changes in buyer commitment and responsibility. A qualification stage and a customer handoff usually need different evidence, while minor internal tasks can remain checklist items within a stage.
Assign a named sending owner in sales and a receiving owner in implementation, service or account management. The handoff is complete when the receiving owner accepts the required information, rather than when sales first sends an email.
A current snapshot shows where opportunities are now, but usually cannot establish which stages they previously entered or skipped. Use stage histories or dated snapshots to measure progression, and retain opportunity identifiers so repeated stage visits do not inflate counts.
Only where the buying process and entry evidence match. Keep the original customer relationship connected, but give a renewal its own opportunity identifier and motion label. Otherwise repeat business can make new-customer conversion appear better than it is.