The Guest Who Only Comes for One Person
A venue's most loyal guests are frequently loyal to a person, not the room. That is worth money until the person leaves. How to measure the dependency and what can be done about it without pretending it away.
A guest has come in every fortnight for two years. Excellent spender, no trouble, knows the staff.
They have never once come in when a particular person was not working.
Nobody noticed, because from the venue's side they look like a regular. They are not. They are somebody else's regular, using your room.
Why this is worth measuring rather than worrying about
The instinct is to treat this as a risk to be reduced. That is only half right.
Personal loyalty is why they come at all. A room with no personal relationships is a room people visit rather than return to. Trying to reduce the dependency by discouraging it destroys the thing producing the revenue.
The useful question is not "how do we stop this" but "how much of our revenue is in this shape, and do we know which people carry it."
The measurement
For each of your top guests by spend, one number:
What share of their visits coincided with a specific member of staff working?
You are looking for the extremes. A guest whose visits are spread across everyone is loyal to the venue. A guest at ninety-plus percent with one person is loyal to that person.
⚠️ The middle of the distribution is not interesting. The tail is.
Then flip it: for each member of staff, how much revenue is attached to guests in their tail. That number is what walks out if they leave, and it is frequently concentrated in two or three people.
What to do with the answer
Three things, in the order they actually work.
Know it. Most of the value is here. A departure that is a surprise costs far more than one you saw coming, and the number tells you which departures to see coming.
Build a second relationship, deliberately and early. Not a handover — a second familiar face while the first is still there. This is the only intervention that reliably works, and it has to happen years before it is needed.
Capture what the person knows. Preferences, history, the things that make the guest feel recognised. ⚠️ The relationship does not transfer, but the knowledge can — and the knowledge is what makes the second relationship possible instead of starting from nothing.
What does not work
Rotating staff to break the dependency. The guest stops coming. This is tried surprisingly often and it fails almost every time.
A handover at the point of departure. Two weeks' notice is not enough time to transfer two years of relationship. By then the useful move is a graceful introduction, not a transfer.
Pretending the guest is the venue's. They will follow the person if the person goes somewhere else, and treating that as disloyalty gets you neither the guest nor a good reference.
The part people avoid saying
Some of these guests will leave when the person leaves. That is not a failure of retention; it is the nature of the business, and a plan that assumes otherwise will be wrong.
What is a failure is finding out afterwards — losing the guest and only then discovering they were a fifth of one person's book.
The related number worth having
Requests as a share of visits, per member of staff.
A person with a high request rate is carrying relationships, which is valuable and also concentrated. A person with a low one is serving whoever is in front of them. Both are needed; a room made entirely of the first is fragile and a room made entirely of the second does not retain anyone.
Knowing the mix tells you what your room is, which is more useful than either number alone.
Three to hold
Guests above eighty percent overlap with one person. Your concentration list.
Revenue attached to each person's tail. What a departure actually costs.
Requests as a share of visits, per person. Whether your room runs on relationships or on service, and in what proportion.
Where the record has to sit
If visits are not linked to who was working, none of this is computable — and in most venues that link exists in the rota and in the booking, but never in the same place.
tasteck keeps requests, visits, and shifts on one record, so which guests only come when this person works is a query rather than something a manager half-suspects.
They were never your regular. That is worth knowing before the notice period, not after.
Related articles
Your Pour Cost Is a Schedule Problem
Most venues chase pour cost with tighter counts and better jiggers. The variance usually tracks who was behind the bar, not what they were pouring. How to read pour cost by shift, and why the fix is often on the roster.
Your Coat Check Is a Queue Problem
In cold markets the coat check decides how your night starts and how it ends. What the queue costs in unbought first drinks and in clearance time at close, and the three changes that move it without new staff.
Your Best Night Was Not Your Best Night
The night with the highest take is rarely the night that earned the most. What has to be subtracted before a night can be ranked, and why the answer usually reorders the whole week.
Map out your operations in 5 minutes
Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.
Your answers are not stored. The assessment runs entirely in your browser.
Try tasteck free for 30 days
No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.
- No card required
- Free data migration support
- All features unlocked for 30 days