Let’s talk about the difference between a place that knows your name and a place that made room for you.
Those two things get sold as the same thing now. They are not the same thing. One of them costs almost nothing and works on a billion people at once. The other costs something real, and it is the only reason anybody has ever trusted anybody.
Picture a small office on a Monday morning. A client arrives forty minutes early because the traffic was better than he expected. Nobody planned for him. There’s no waiting area with a screen and a coffee machine that remembers his order. There’s a woman at the front desk who says sit down, I’ll put the kettle on — and then she doesn’t disappear. She sits with him for ten minutes and asks about his daughter’s school, because she remembers the daughter’s school.
He will not remember your deck. He’ll remember the ten minutes.
Now here’s the part most people never look up. Hospitality and hostility come from the same root. The Latin hospes means guest and host in the same word — the stranger you took in, and the person who took him in. Hostis meant stranger, and later it meant enemy. Guest and enemy were the same word until somebody decided which one you were going to be.
That’s the whole thing. The oldest trust protocol humans have is a meal you didn’t have to serve. It was never about being nice. It was a ritual that turned a potential threat into a person with a name, in front of witnesses, at cost to the host.
So ask yourself what we’ve actually built in the last three years.
We built recognition. Industrial-scale recognition. The machine knows your name, your order, the way you take your coffee, the thing you complained about in March, the tone you prefer when someone tells you no. It can greet ten million people by name before lunch and mean none of it. It is genuinely useful, and it is now nearly free, which is exactly why every company is buying it and calling it care.
But recognition is a lookup. Hospitality is a cost you absorb for someone whose preferences you did not model.
The chair you fetch for a person whose name you don’t know yet. The forty minutes on a call that was never going to close. The fifteen minutes at the door with someone who came to complain. None of that is in a database, because the whole point is that it’s for someone the database hasn’t got.
Notice which one of those two things shows up on a dashboard.
Personalisation has beautiful metrics. Open rates, repeat purchase, satisfaction score at the greeting. Hospitality has nothing. You cannot attribute it, you cannot A/B it, and the person who received it usually can’t explain why they came back. Which means the moment a business gets serious about efficiency, hospitality is the first thing on the list. It looks like waste. It looks like the receptionist who could be a kiosk, the account manager who could be a portal, the founder who insists on doing the handover himself when there’s a perfectly good automated flow.
And it’s being cut in the name of something that feels like the same thing but is cheaper. A system that greets you by name and remembers your last ticket feels like being known. It is not being known. It’s being indexed.
Here’s where it goes past customer experience and becomes something bigger.
Personalisation has no category for the stranger. To a system, a person with no history is a cold-start problem — thin data, low confidence, probably not worth the spend. That is a completely rational read of the data. It is also the exact opposite of what hospitality does, because hospitality is the one human practice that treats an unknown person as owed something before they’ve proved anything at all.
Every door we automate gets a default. And the default for the person the system can’t recognise is going to be suspicion, a longer queue, a deposit, a rejection that arrives with no reference number. Not because anyone decided to be cruel. Because the model was trained on who showed up before.
Watch that logic compound and you get a world where the person with no footprint is the person with no access. And that’s a strange place for a species that spent its whole history building rituals specifically so the unknown could be let in.
Now the uncomfortable part, because this piece is not an argument for being soft.
Hospitality costs, and it can be taken advantage of. Some people will eat your lunch and never call again. Some will sit in the chair for two hours and buy nothing. If you turn it into a funnel it stops working, because people can smell a script — the warmth that has a next step attached to it isn’t warmth, it’s a sales tactic with better manners. And you can’t hand it to your agent. The machine can send the invitation. The machine cannot give up the afternoon. The giving up is the message.
So what do you do with that, as a person running something.
Three things, and they’re practical.
Keep the unbilled hour, but count it. If hospitality stays invisible it gets cut in the next cost review, every time, by someone doing their job properly. Put a number on it — hours given, clients who came back, referrals that started with a coffee. It’s the only marketing line you own that nobody can bid against you for.
Second: personalise the logistics, never the welcome. Let the machine do the speed, the memory, the reminders, the boring accuracy that makes a business feel competent. Keep the human on the part where somebody has to absorb a cost. The moment the machine handles the greeting, the greeting becomes inventory.
Third, and this is the one that compounds: hire and keep people who will fetch a chair for a stranger. Not the ones with the best scripts. The ones who’ll stay late for a person who isn’t a customer yet. That is the single asset in your business that doesn’t get copied in a quarter, because it can’t be bought, only grown.
And one piece of homework, if you sell anything. Go and count where your last ten clients actually came from. Not the attribution report — the actual story. My bet is a decent number of them came out of a moment where somebody made room for them before there was a reason to.
Which brings it down to the principle, and it’s a small one.
The right to be received. Not the right to be known — that’s a lookup, and the machine will give it to anyone with a cookie. The right to be made room for by a person who didn’t have to, who doesn’t have your data, who may not get anything out of it.
And on the other side of that right, a duty that doesn’t sound like a duty: keep making room for the ones your system can’t see. The new client, the kid with no history, the person starting over in a city where nobody has their number.
The machine will remember everyone.
It will not make room for anyone.
Somebody still has to put the kettle on.