The point at which somebody stops being a new customer
- 4 days ago
- 3 min read
Introduction
Businesses divide customers into new and existing, and almost none of them can say where the line falls. Is it after the first purchase, the second, the first year, the first problem handled well? The answer decides who receives the introductory attention, who gets counted in acquisition figures, and who is being treated like a stranger long after they stopped being one.
Getting it wrong is common in both directions. Some businesses keep sending introductory material to people who have bought four times, which reads as not paying attention. Others treat a first-time buyer as established and skip the reassurance that would have secured the relationship.
The transition is worth defining explicitly, even if the definition is somewhat arbitrary.
1. The point at which somebody stops being a new customer differs by business
The starting observation.
For a café it may be the third visit; for a builder it may be the second project, years later. The right answer depends on your purchase cycle. Copying somebody else's threshold produces nonsense. Derive it from your own repurchase interval.
2. The second purchase is the usual marker
The commonest definition.
Buying again is a deliberate choice made with knowledge of what you deliver, which the first purchase was not. It is also easy to count. For most businesses this is the sensible line. Where second purchases are rare, use a different marker.
3. Time alone is a weaker marker
The caution.
Somebody who bought eighteen months ago and never returned is not established, they are dormant. Elapsed time without repetition means very little. Use it only where repeat purchase is genuinely rare. In those cases a year is a reasonable line.
4. Watch for the moment they stop asking basics
The behavioural signal.
Established customers ask different questions and need less explanation. That shift is observable and frequently precedes the second purchase. It is a useful informal indicator. Whoever answers the phone will notice it first.
5. Define it so it can be counted
The practical requirement.
Whatever you choose, it must be derivable from records you keep, or it will not be applied consistently. Second invoice is countable; feels settled is not. Write it down beside your other definitions. One sentence is enough.
6. Change what you send them
The reason it matters.
Introductory material to an established customer is a small insult, repeated. Move them to different communication at the transition. This is the main practical consequence of defining the line.
7. Change who handles them
The service consequence.
Established customers usually want less explanation and faster access. Recognising them at first contact is worth a note on the record. Nothing irritates a loyal customer more than being treated as unknown.
8. Count the two groups separately
The measurement consequence.
Acquisition and retention are different problems with different costs, and mixing them hides both. The split depends entirely on where this line sits. That is the reason to define it precisely.
9. Mark the transition somehow
The relationship consequence.
A brief acknowledgement when somebody becomes a regular is inexpensive and unusual enough to be noticed. It does not need to be a scheme or a discount. Recognition is the point.
Be careful about a definition so generous that almost everybody counts as established. If two-thirds of your customers are classified as loyal, the category has stopped distinguishing anything and the measurements built on it will mislead.
Conclusion
Decide explicitly where a new customer becomes an established one, and count it.
Use the second purchase as the default marker, treat elapsed time alone as a weak signal, watch for the point at which someone stops asking basic questions, define the line so it can be derived from your records, change the material and the handling at that point, count acquisition and retention separately on either side of it, and mark the transition in some small way the customer notices.
.png)



Comments