The Follow-Up: Feedback Loops Restaurants and Software Both Skip

For many restaurants and many software companies, attention drops the moment the transaction ends. The check is paid or the contract is signed, and the customer goes quiet until a review appears or a renewal date arrives. My view is that this is when customer feedback is most useful, and it is the stage both industries skip most often. This is the fifth stage of the guest journey: the follow-up for a diner, and check-ins, health scores and feedback loops for a software customer.

I'm Richard Yu, Managing Partner of Rich Ventures and a co-founder of Equal Parts, a restaurant and cocktail bar in North Beach, San Francisco. I have more than 15 years of startup and go-to-market experience, and more than a decade of my roles were in customer success and solutions engineering at software companies, including Customer Success & Partnerships at LeadIQ, where I built customer journey frameworks with the sales and product teams. I compare the two worlds here because the follow-up problem looks the same from either side.

The Moment After the Transaction

Picture a guest who leaves a dinner happy at ten at night. The next morning, nothing arrives. No thank-you, no question about the dish they hesitated over, no note that they mentioned an anniversary next month. A week later they have mostly forgotten the details, and so has the restaurant.

Now picture a software customer who signs a contract after a long evaluation. The sales team celebrates, the account is handed over, and the next real conversation happens two months before renewal. By then the customer has formed a view, and it is hard to change.

In both cases the business went silent at the point where the customer had the most to say. In my experience, feedback is freshest in the first day or two after a visit or a signature. The guest still remembers which cocktail was too sweet. The buyer still remembers which promise from the sales cycle matters most to their boss.

The fix is not complicated. Decide who owns the moment after the transaction, decide what they say, and decide how quickly. Restaurants and software teams that do this tend to hear about problems while they are still small.

Reviews, Surveys and the Quiet Signals

Most businesses lean on two loud channels. Restaurants watch restaurant reviews on Google and Yelp. Software companies send surveys after a support ticket or once a quarter. Both are useful, and both have the same weakness: they arrive late and they skew toward the extremes. The guest who writes a review is often either delighted or annoyed. The customer who answers a survey is often the one with time to spare.

I think the more useful customer feedback is quiet. In a dining room, it is the plate that comes back half full, the guest who asks for the check before dessert, the regular who orders something different for the first time. In software, it is logins that slowly drop, a champion who stops joining calls, or a run of support tickets on the same feature.

None of these signals require the customer to fill anything in. They require someone to notice and write it down. A server who adds one line to a guest profile after a table leaves is collecting better data than many survey programs. The same is true of a customer success manager who logs a two-sentence note after each call instead of waiting for a formal review.

Health Scores for Guests

Software teams use a customer health score to decide where to spend attention. It usually combines a few inputs: how often the product is used, how support conversations feel, whether the main contact is engaged, and how close the renewal is. Green accounts get a light touch. Red accounts get a call this week.

Restaurants rarely do this, and I think they should, in a simpler form. A guest health score can rest on three things that most reservation and point of sale systems already hold as guest data:

Recency: when did they last visit? Frequency: how often did they come over the past few months? Last note: was there a complaint, a celebration or a request on their last visit?

Picture a regular who came twice a month through the spring and has not booked in eight weeks, and whose last visit included a note about a long wait for the entrée. In software terms, that account is red. A short, personal message from a manager is worth more here than a discount code.

Technology should do the flagging. A person should do the reaching out. And the score should stay internal: guests want to feel remembered, not measured.

Closing the Loop, Visit After Visit

Collecting customer feedback is half the job. The other half is showing the customer that it went somewhere. In my experience, this is where many feedback programs stall: the notes pile up, nothing visibly changes, and customers stop bothering to share. Here is the loop I would run, from both sides:

1. Capture. The server adds a note to the guest profile before the end of the shift. The customer success manager logs the call the same day.
2. Acknowledge. Within a day or two, the guest gets a short thank-you that references something specific. The software customer gets a recap email with the next steps you agreed.
3. Route. A comment about a dish goes to the kitchen. A comment about a feature goes to the product team, with the account name attached.
4. Act and tell them. When the dish is adjusted or the feature ships, tell the person who asked. This is the step most often skipped.
5. Record. Update the guest profile or account record so the next person who serves them knows the history.

The quarterly business review is the software version of step four done at scale: here is what you told us, here is what changed. A restaurant can do the same for its regulars in a sentence at the table.

A Follow-Up Rhythm That Fits a Busy Team

The usual objection is time. A restaurant team is on its feet all night, and a small software team is shipping and selling at once. My view is that follow-up fails less from lack of effort than from lack of a fixed slot in the week.

A rhythm I like is a 30-minute review, once a week, on the same day. In that half hour, someone looks at three things: new restaurant reviews or survey responses from the past seven days, any guests or accounts that moved to red, and the open loops from the list above that still need a reply. Each item gets an owner and a date before the meeting ends.

Picture a restaurant that holds this review on a quiet Monday afternoon. A manager reads the week's reviews aloud, the chef hears the two comments about a dish, and the host takes the three regulars who have not booked in a while. On the software side, the same half hour covers usage dips and the next quarterly business review on the calendar.

For a full version of this kind of meeting, see A Weekly Operating Cadence for a Five-Person Company. If you would rather build the rhythm with someone each week, that is what the GTM & Operations Plan is for.

Remembering a Guest Is a Technology Problem and a Human One

Good follow-up depends on memory. A guest who mentions a shellfish allergy, a favorite table or a birthday expects the restaurant to remember. A software customer who explains their reporting needs on a kickoff call expects not to explain them again at renewal. When that memory lives in one person's head, it leaves when that person changes shifts or changes jobs.

This is where technology earns its place. It should hold preferences, occasions and past feedback in a guest profile or account record that anyone on the team can see at the right moment. It should flag who needs attention. It should not add friction: no long surveys after a nice dinner, no automated messages that read like they came from a machine, no request for information the business already has.

The human part is deciding what to do with what the system remembers. A note that a guest celebrated an anniversary is only useful if someone says something warm next year. Regular, which I founded, is a hospitality operating system for recognising regulars, celebrating guests and running service, for hospitality teams on the web and on mobile.

I'm on Instagram as @richhh90.