Lifecycle stages for a service business: lead, prospect, customer, lapsed
Four stages, and why adding a fifth makes the data worse. What must move a contact mechanically rather than by judgement, how to set the lapsed threshold for your own trade, and why lapsed does not mean marketable.
Sohail Safdar · · 6 min read
Four stages carry almost every service business: lead, prospect, customer, lapsed.
They matter because each one calls for a different message, a different urgency and often a different person on the team. And the main skill in using them is resisting the fifth.
The four
Lead. Somebody made contact: a text, a web chat, a form. You know little beyond what they asked. The goal is a fast, useful reply and one clear next step.
Prospect. They are actively considering you: they asked about a specific service, got a price, or started to book. The goal is removing whatever is stopping them, which is almost always a question or a time.
Customer. They have had a paid service. The goal is a good experience, reminders for whatever is next, and being easy to come back to.
Lapsed. A customer who has not returned within your normal interval. The goal is understanding why, and inviting them back only if you have a basis to.
Why four and not eight
More stages feel like more insight and produce less.
The value of a stage is that it means the same thing to everybody who looks at it. That requires each transition to be mechanical: a fact about what happened, not an assessment. Four stages have four unambiguous transitions. Eight have several that are judgement calls, and a judgement call made by three people produces three different answers and nobody is wrong.
So the test for a proposed new stage: can you write the rule that moves a contact into it, such that two people would always agree? If not, it is not a stage.
The usual casualty is "hot lead", and it is worth being specific about why. Urgency and interest are real and worth recording. They belong on a score or a tag, where being subjective is expected and nobody builds a report on it, rather than in the field you filter and segment on.
What moves a contact
- Lead to prospect: they engaged with a specific service, asked a price, or began booking.
- Prospect to customer: a completed, paid appointment or job.
- Customer to lapsed: time since the last visit passed your threshold.
- Lapsed to customer: they came back.
Three of those four are events and will happen on their own if the system is watching. The third is a clock, which means somebody has to decide the number.
Setting the lapsed threshold
This is the only judgement in the whole scheme, so it is worth getting right.
Roughly: six months for a salon, a year to eighteen months for a dental practice, two seasons for a lawn service, two or more years for a conveyancer. Those are starting points rather than answers.
The better method: take your own median gap between visits for returning customers, and set the threshold somewhere beyond it. Both errors cost you.
Too short and you are labelling people lapsed who are simply on their normal cycle, which means a win-back message to somebody who was going to book next week anyway. That reads as not knowing them.
Too long and nobody is ever reactivated, because by the time the flag appears the customer has found somebody else and the relationship is gone rather than dormant.
And set it per service if your services have genuinely different intervals. A dental practice's hygiene interval and its orthodontic interval are not the same number, and one threshold across both mislabels one group.
Lapsed does not mean marketable
The most common mistake in this area, and it is a compliance mistake rather than a strategic one.
Lapsing is a fact about behaviour and it grants nothing. Somebody who never agreed to marketing does not become marketable by staying away for eight months. So a win-back campaign goes to the segment "lapsed and consented", which is a smaller list than "lapsed" and the only one you may use.
Expect the gap to be larger than you hoped, particularly if you started recording consent recently. The right response is to treat it as evidence that consent collection needs fixing at the point of booking, rather than as a reason to send to the wider list once.
A reactivation message that is genuinely transactional, such as a clinical recall a practice is obliged to send, is a different category, and worth separating deliberately rather than leaving ambiguous.
A stage is not a pipeline
Worth one section, because conflating the two is common and produces a mess.
A stage describes a person. Where this customer stands with you, overall. One value.
A pipeline tracks a piece of work through steps: enquiry, quote sent, scheduled, done. A customer can have two jobs in two different pipeline stages at once and still be one customer.
The tell that you want a pipeline: you find yourself wanting a contact to be in two stages at the same time. Tags vs fields vs pipelines covers the three-way choice.
What changes at each stage
| Stage | Who owns it | What you send |
|---|---|---|
| Lead | Whoever works new enquiries | A fast reply and one next step |
| Prospect | The same person | The answer they need, and specific times |
| Customer | The team generally | Confirmations, reminders, and a review request if they opted in |
| Lapsed | Whoever owns marketing, if anybody | Nothing, unless there is a basis for it |
The last row is the one most businesses get wrong, in both directions: either sending to everybody, or sending to nobody because the whole area feels risky. The correct answer is a narrower list sent to properly.
In Frontiva
Lifecycle stage is a field on the contact alongside notes, tags and custom fields, with exactly these four values, so the stage stays the thing you filter and report on while the judgement calls live on tags.
Saved segments are where the stage earns its place: name a filter once, such as lapsed customers or anybody tagged implant, and reuse it on the contact list or as a campaign audience. "Lapsed and consented" is one of those filters rather than something somebody assembles by hand each time, which is what makes the compliance section above practical rather than aspirational.
Every outbound message then passes one send check for consent for that specific purpose, so a campaign aimed at a lapsed segment that includes somebody without a marketing basis is refused for that contact and says which rule refused it, rather than sending and being discovered later. Marketing by SMS is refused outright today, because no basis for promotional texting is recorded; email marketing runs on an opt-out basis and review requests on their own separate opt-in.
The contact's merged timeline is what tells you why somebody lapsed, which is the goal of that stage and the part no automation can do for you.