When assessing a tour operator, a database of several thousand customers and prospects can quickly be presented as a major asset.

The number is reassuring. It creates the impression that part of the business development potential is already there, ready to be reactivated. Yet that number ultimately tells us very little. In a recent analysis, we began by looking at the size of the database, then examined who had actually purchased, when, how often, and what share of the business still came from those customers. The picture changed.

Behind several thousand contacts, the economic value was actually concentrated in a few hundred long-standing customers who continued to travel with the company. They were far fewer than the size of the database suggested, but far more important in understanding what the company could still generate in the future.

A contact list measures volume. A customer database should measure the capacity to keep generating revenue.

To assess it, the first instinct should therefore be to move beyond the total number of contacts and reconstruct the history of the customer relationship. A customer who travelled a few months ago clearly does not have the same value as a contact recorded several years ago with no interaction since. A customer who has travelled four or five times with the same tour operator also tells a different story from a one-time buyer. And tracking cohorts over time can sometimes reveal that a significant share of current business still rests on customers acquired several years earlier.

At that point, the customer database is no longer read as a list of names. It becomes a fairly accurate picture of the loyalty the company commands. A large database can conceal a weak ability to retain new customers; conversely, a company that acquires few customers may have an exceptionally strong long-standing core. In the first case, the size of the database creates an impression of value that exceeds reality. In the second, the accounts may understate the value of customer relationships built over years.

The next step is to examine whether that value can actually be realised. A database of several thousand prospects becomes much less attractive if contact sources, consent, preferences or opt-outs are poorly documented. Similarly, a customer database without travel history, segmentation or an understanding of purchasing behaviour severely limits the buyer’s ability to identify whom to reactivate and with which offer. This is therefore not simply a compliance issue: it is also a commercial one, because the more we know about a customer’s history, the better we can understand what prompted them to buy, what might bring them back and which offers are likely to interest them.

This is why a customer database should be analysed as a living asset. The real question is not “how many contacts do we have?” but “how many of them still have an economic relationship with the company, and what do we know well enough to sustain it?” That question requires us to consider recency, purchase frequency, value generated, loyalty over time and the actual ability to resume the relationship together. It also helps avoid a fairly common acquisition pitfall: assigning value to thousands of prospects simply because they exist in a system.

A long-standing prospect who has never purchased does not have the same value as a customer who has travelled regularly for several years. That seems obvious once stated. Yet those two people may count in exactly the same way in the figure displayed at the top of a CRM. This is precisely why database size is a poor shortcut: what matters is not how many people the company knows, but how many commercial relationships are still active, what value they have already demonstrated and to what extent they can continue to generate revenue.

The value of a customer database is not measured by its volume. It is measured by the quality and continuity of the relationships it contains.

And in an acquisition, that distinction can substantially change the perception of what is actually being bought.

About BloomingPilot