Repeat Visits and Renewals: Retention Is the Real Hospitality Metric

A software company does not really know it has won a customer until the renewal. A restaurant does not really know it has won a guest until the second visit. This is the last of six stages in the guest journey and the customer lifecycle: the repeat visit for a diner, and renewal, expansion and advocacy for a software customer. My argument is simple. Customer retention is the real measure of hospitality, on both sides.

I'm Richard Yu. I spent more than a decade in customer success and solutions engineering at software companies, including as Director, Strategic Account Management (Customer Success) at Lob, where I drove 15% year-over-year growth with 0% churn across strategic accounts. I then co-founded Equal Parts, a restaurant and cocktail bar in North Beach, San Francisco, where I am Managing Partner for marketing and operations.

A Regular Is a Renewed Customer

In software, a renewal is a customer deciding, with full information, to pay again. They have used the product for a year. They know its flaws. They sign anyway. That is a stronger signal than the first contract, which was signed on a demo and a promise.

A second visit works the same way. The first booking was made on a Reel, a review or a friend's word. The second is made on what actually happened at the table. Picture a guest who came in for a birthday, liked the bartender, and books again three weeks later for a Tuesday with no occasion at all. That guest has renewed.

A regular is what renewal looks like once it becomes a habit, often with expansion folded in: more visits, bigger parties, a private event, a friend brought along. Software calls that second half expansion and advocacy. Restaurants usually just call it a good regular.

My view is that both industries spend too much attention on the first sale and too little on the second. The vocabulary differs. The economics are close.

Retention Is the Real Hospitality Metric

Software has a clean number for this: net revenue retention. Take the revenue from the customers you had a year ago, add what they expanded into, subtract what churned or shrank, and divide by where you started. Above 100% means your existing customers are growing on their own, before a single new deal.

Many restaurants track nothing equivalent, and I think that is a mistake. Covers, average check and review ratings tell you about tonight. They say little about whether tonight's guests come back.

A rough hospitality version is easy to sketch if your reservation system keeps guest profiles. Look at what share of a given month's guests return within 90 days, how many times a returning guest visits in a year, and whether returning guests bring more people or book events. None of this needs to be precise to be useful. The direction matters more than the decimal.

Picture two restaurants with the same busy Saturday. One fills it with new faces from a viral post. The other fills it with people who have been in four times. In my experience, the second business is far easier to staff, plan and improve, because it knows who it is serving.

Expansion Without Pressure: Events, Referrals and Upgrades

Expansion in software is a customer buying more seats, a higher tier or a second product. The good version happens because the customer found more value. The bad version is a quota-driven upsell that lands right before renewal and sours it.

Hospitality has the same split. Good expansion looks like a regular asking whether you host private dinners, a guest bringing their team for a farewell, or someone trying the full dinner menu after three visits at the bar. Bad expansion looks like a server pushing bottled water and a second round on a guest who came for a quiet drink.

In my view, expansion should follow value, not precede it. A few habits help on both sides. Make the next offering visible without pitching it: a line on the menu about private events, a short note inside the product about the higher tier. Let regulars hear about new things first. Ask for referrals after a good moment, not by default.

Advocacy is the quiet end of this stage. A customer who takes a reference call and a guest who brings a friend are doing the same thing: putting their own name behind yours.

Recognition Is the Cheapest Loyalty Program

Many restaurant loyalty programs are points, punch cards and discounts. They can work, but they tend to train guests to come back for the deal rather than for you. Software has its own version: renewal discounts that buy a year and teach the customer to ask again next time.

Recognition costs less and lasts longer. Picture a guest who walks in for the third time and the host says, 'Good to see you again, your usual corner is open.' Nothing was discounted. The guest feels known, which is the point of hospitality.

The software equivalent is a customer success manager who opens a quarterly review already knowing the customer's goals, last month's support ticket and the new VP who just joined. The customer does not have to repeat themselves. That is recognition in a B2B form.

The hard part on both sides is memory. A great server remembers a regular's drink; the trouble is the server's night off. I founded Regular, a hospitality operating system for recognising regulars, celebrating guests and running service, for hospitality teams on the web and on mobile. Whatever tool a team uses, my view is that guest knowledge belongs to the house, not to one person's memory.

Building a Regulars Practice in Five Steps

Here is how I would set this up, with both sides next to each other.

1. Define who counts. Restaurant: a guest with, say, three visits in six months. Software: a customer past their first renewal. Write the definition down so the team uses the same word for the same thing.
2. Capture what matters when it happens. Restaurant: a short note in the guest profile on the drink, the allergy, the occasion. Software: a note in the CRM on goals, champions and risks. Keep notes brief and factual.
3. Surface it before the next touch. Restaurant: review tonight's book at pre-shift and flag returning guests. Software: read the account notes before each call.
4. Mark the milestones. Restaurant: a tenth visit, an anniversary, a first event booked. Software: a contract anniversary or a usage milestone. A handwritten note or a small gesture does more than a coupon.
5. Watch for drift. Restaurant: a regular who has not been in for two months. Software: declining usage ahead of renewal. Reach out with a personal note, not a promotion.

If you want help putting a cadence like this in place, it is the kind of work the GTM & Operations Plan covers in a weekly 30-minute session.

Where Software Fits Into a Relationship Business

Technology should make a guest or customer feel known and looked after. It should not add steps between them and the people serving them.

What it should do: remember preferences so staff do not have to, put the right note in front of the right person at the right moment, and show the team who is drifting away while there is still time to act. For restaurants, that usually means a reservation system and point of sale that share guest data. For more on choosing tools a small team can actually run, see picking a restaurant operations stack.

What it should not do: replace the greeting with a tablet, send a generic 'we miss you' blast, or turn a regular into a segment that receives discounts. Automation tends to work best behind the scenes and worst in the guest's face.

Picture a software customer who gets an automated renewal reminder from an address they have never seen, compared with one whose account manager calls a month early to talk about next year's plans. Same tools, very different relationship.

Retention is earned by people and kept by systems. That is where hospitality and software meet. I'm on Instagram at @richhh90.