Buyers don't value your guests. They value whether you can prove that those guests come back. If knowledge about returning customers lives in your receptionists' heads rather than in documents, it is not an asset in due diligence. It is an unknown, and buyers always price unknowns at a discount.
This article uses a hotel to show what preparing data for a company sale looks like, and why it pays to start several months before talks with an investor rather than after the first difficult questions. The case is a composite of several projects in hospitality. We have anonymized the details, and the mechanism is repeatable.
A Hotel That "Knew Its Guests" but Couldn't Show It
Picture a hotel run for years by its founders. Good location, steady occupancy, a long-tenured team. A receptionist sees a group walk into the lobby and says, "Oh, they're back. They stayed last year, and the year before." The sales manager knows a certain company returns every season for training. Everyone knows the hotel has loyal customers.
But nobody could prove it. There was no place where a given guest or company had a single history. Reservations came through different channels, under different names, with different email addresses. The same company appeared once under its full name, once as an abbreviation, and once under the name of whoever happened to make the booking.
The founder heard from the transaction advisor: "The buyer will ask about the structure of your customer base. They'll want to know how many return and how much they're worth." An answer like "we think quite a lot" won't survive any due diligence.
Why "We Know It from Experience" Is Not an Asset
Knowledge that exists only in people has three weaknesses that a buyer spots immediately.
It is unverifiable. An investor doesn't buy a story about loyalty. They buy a predictable revenue stream, and predictability has to be shown in data, not in narrative.
It is a fragile dependency on individuals. If the key receptionist or sales manager leaves after the transaction, the "knowledge about guests" leaves with them. For the buyer, that is an operational risk built into the model.
It cannot be valued. You can't calculate the value of a customer over the whole relationship if you don't know who is the same customer.
What is LTV? LTV (Lifetime Value) is the total value a customer brings to a business over the entire relationship. In a hotel, it is not one booking but the sum of all stays, extra services, and referrals attributable to one guest or one company.
Without a credible LTV, the buyer can't tell whether the guest base is an asset or just a list of random check-ins. When they don't know, they assume the cautious case.
What a Buyer Does with an Unknown
Does the lack of organized customer data lower a company's valuation? Yes. Not because the buyer punishes mess, but because they can't verify the assumptions in the financial model, so they adjust them in their own favor.
In practice, the unknown turns into one of several forms:
- a price reduction justified by "risk to revenue repeatability,"
- contract provisions, such as part of the price deferred or tied to post-transaction results (escrow, earn-out),
- extended due diligence, which eats the founder's time and weakens their negotiating position,
- an avalanche of follow-up questions, which the team answers on the fly, often inconsistently.
Note that none of these consequences requires the buyer to look at code, databases, or systems. It is enough that they ask a simple question and the answer is uncertain.
Data Debt is accumulated debt in your data: inconsistent definitions, duplicates, no coherent history, and manually patched reports. Like any debt, it carries interest. In a company sale, you pay it off directly in the price.
What Data Cleanup Looked Like Several Months Before the Transaction
We started with a question that makes sense to a management board, not to the IT department: "Which buyer questions can we not answer today in one sentence?" The list was short and painful. Who returns? How often? Are they individual guests or companies? How much is such a customer worth over the whole relationship?
Step One: A Single Customer Identity Instead of Many Records
First, we had to establish that a guest and a company are the same person and the same entity, regardless of how and when the booking was made. We merged scattered records into one coherent history for each customer.
This is what we call a Single Source of Truth: one reliable place where a given piece of information exists in one agreed version. Not "several reports that differ," but one answer that the board can show a buyer without caveats.
Along the way, something came up that often surprises founders. Some "new" guests turned out to be returning ones, and some "regulars" from the team's stories came back less often than everyone assumed. The team's intuition was good, but it wasn't precise. The data didn't contradict what people felt. It gave it shape.
Step Two: Segmentation Instead of One Bucket Called "Guests"
Once each customer's history was coherent, we could classify them. A simple split emerged: one-time guests, occasional returners, and regular returners. Corporate clients were treated separately, because their behavior and value follow different rules than private stays.
Segmentation is not decoration for a presentation. It is a tool that shows the buyer where revenue comes from and how repeatable it is. A hotel whose revenue largely comes from customers who return of their own accord is a completely different asset in an investor's eyes than a hotel living off one-time bookings from portals.
Step Three: LTV You Can Defend
Only on top of an organized history could we calculate customer value over time. The key word here is "defend." A number you can't derive step by step is worse in due diligence than no number, because the buyer will start questioning everything else.
That's why every metric had a clear definition written in plain language: what counts toward customer value, how we define "returning," and how we treat companies with multiple people making bookings. These definitions were part of the documentation ready to show in the data room.
Step Four: The End of Memory Instead of a System
The last element is the least spectacular and the most important to the buyer: knowledge stopped depending on specific people. What the receptionist used to know was now recorded automatically, in the same place and in the same way. An employee leaving stopped being a risk to customer information.
What Changed Before the Buyer Showed Up
We describe qualitative effects here, because every project has a different scale, and reliable figures would require a specific case.
The founder saw a true picture of the guest base for the first time. Instead of the belief that "quite a lot probably return," they had a structure: who the customers are, how they behave, and which groups build revenue stability.
The question about returning customers stopped being a weak point. It used to be what the founder feared most, because they had no answer. After the project, it became one of the arguments for the price: revenue predictability that could be shown, not just declared.
The board stopped improvising in conversations with the investor. Every answer was backed by the same set of data. For a buyer, the absence of contradictions between what the founder, the sales manager, and the finance director say is a signal of organizational maturity.
The team got its time back. Fewer hours spent manually stitching together lists and answering ad hoc questions about guests, and more spent running the hotel at a time when it has to look its best.
And one more thing, the least measurable but the most felt: peace of mind. The founder entered negotiations knowing that no one could surprise them with a question they couldn't answer.
Buyers don't punish you for what you don't have. They punish you for what you can't show.
What This Case Teaches, Even If You Don't Run a Hotel
The mechanism is universal and applies to any company with a recurring customer relationship: agencies, service firms, e-commerce, PropTech.
Do you need to organize data before selling a company? Yes, if you want the data to work for the price rather than against it. The buyer will ask about what can't be verified, and they assume the worst about anything unverified. The earlier you organize your data, the more time you have for corrections and the less for firefighting during the process.
Where to start? With a list of the questions the buyer will certainly ask and to which you currently answer "more or less." Every such "more or less" is a potential discount. Start with those concerning revenue repeatability, customer structure, and the reliability of management reports.
When is it too late? When the buyer has already asked the question and the team is answering in crisis mode. Data organized under time pressure is more expensive, less credible, and shows signs of haste. Order established in advance looks like a mature organization, not makeup before an inspection.
It is also worth remembering a simple principle: code is a cost, a solution is an asset. The buyer won't pay because you have a system. They'll pay because that system yields an unambiguous, credible answer to the question about the value of the business.
Three Questions to Ask Yourself Today
- Can I say in one sentence, based on documents, what share of my customers return?
- Would two people on the board give the same answer if the buyer asked each of them separately?
- What happens to the knowledge about customers if two key team members leave in a few months?
If the answer to any of these is "I don't know" or "it depends who you ask," you have exactly the kind of debt that a buyer will turn into a discount.
Conclusion
The hotel in this example didn't change its offer, location, or team. It changed one thing: it moved from "everyone knows guests come back" to "here is proof of how often and how valuably." For a buyer, that is the difference between a story and an asset.
A founder preparing a company for sale has an advantage if they start early. Several months is enough time to organize data so that it works in your favor in due diligence. Once the buyer is already at the table, time works against you.
If you're preparing your company for a transaction and want to check which buyer questions you can't answer unambiguously today, book a 15-minute call. No obligation. We'll start with the list of those questions.