The Meal Is the Product: Adoption and Experience in Both Worlds
Richard Yu argues that customer experience is judged in use, comparing restaurant service with software adoption and value realization.
A guest rarely remembers the confirmation text. They remember whether the drinks arrived before the conversation stalled, whether the server knew the menu, and whether the check came when they wanted it. A software customer is similar: the sales deck fades, and what is left is whether the product does the job on an ordinary Tuesday. This is the fourth stage of the guest journey and the customer lifecycle: the experience at the restaurant for a diner, adoption and value realization for a software customer. My argument is simple. Customer experience is judged in use, not in the promise.
I'm Richard Yu. I have more than 15 years of startup and go-to-market experience, including a role as Director, Strategic Account Management (Customer Success) at Lob, where I led the enterprise customer success organisation for a $90M+ ARR portfolio of Fortune 100 clients. I'm also a co-founder and the Managing Partner for marketing and operations at Equal Parts, a restaurant and cocktail bar in North Beach, San Francisco, where I led the operating stack (OpenTable and Toast).
Judged by the Experience, Not the Promise
By the time someone sits down or logs in, a promise has already been made. A Reel showed a dish, a menu described a cocktail, a demo showed a dashboard. The experience either confirms that promise or quietly breaks it.
Picture a guest who books because of a video of one pasta dish. They arrive, settle in, and only learn at ordering that the dish is off tonight. Nothing dramatic happened, but the night now starts with a small letdown. Now picture a buyer who signed because of a reporting feature, then finds it needs weeks of configuration before it shows anything useful. Same shape, different vocabulary.
My view is that trust erodes in the gap between what was shown and what is delivered, and that gap is usually small and fixable. One practical step: write down the three things your marketing promises most clearly, then check each one against a normal weeknight service or a normal customer's first month. If a promise only holds on a good day, either change the operation or change the promise.
Service Is Adoption
In software, adoption means a customer actually uses the product, keeps using it, and gets the result they paid for. In a restaurant, good service does the same job across a couple of hours. I think it helps to walk it from both sides:
- First use. The guest places a first order and gets a drink quickly. The customer completes one meaningful task in the product, not just a login.
- Rhythm. The guest settles into a pace that suits the table. The customer builds the product into a weekly routine.
- Depth. The guest tries the special or a second cocktail on a well-timed suggestion. The customer picks up a second feature because someone showed it at the right moment.
- Value realized. The guest leaves feeling the night was worth it. The customer can point to the outcome they bought the product for.
In my experience, a good server and a good customer success manager share one habit: they read where the person is and suggest the next step only when it helps. Pushing depth before rhythm is established tends to feel like upselling, on either side.
The Invisible Systems Behind a Good Night
Most of what makes a night feel easy is never seen by the guest. A reservation note, a ticket printing in the kitchen at the right time, a check that splits cleanly. In software the equivalents are uptime, sensible permissions and integrations that pass data without anyone retyping it.
Picture a table of four where one guest mentions a shellfish allergy when booking. In a well-connected setup, that note travels from the reservation system to the host, to the server, and onto the kitchen ticket in a point of sale like Toast POS, without the guest repeating it three times. In a poorly connected one, the guest becomes the integration.
A step worth taking: pick one piece of information and trace it from the moment it enters your system to the moment it matters. Where does a person have to copy it by hand? That is where errors and repeated questions come from. For more on choosing tools a team can actually run, see picking a restaurant operations stack. The same test applies to a software company's support and success tooling.
Support When Something Goes Wrong
Something will go wrong eventually. A steak comes out overcooked, a cocktail is unbalanced, a report breaks the night before a board meeting. My view is that the recovery often shapes the memory more than the mistake does.
Picture a guest who sends back a drink. One version: the server looks unsure, the drink returns ten minutes later, and nobody mentions it again. Another version: the server takes ownership on the spot, says what will happen and how long it will take, and checks back once the new drink lands. The cost is nearly identical. The experience is not.
Software support follows the same pattern. A customer with a broken workflow usually wants three things:
- One named person who owns the problem.
- A clear statement of what happens next and when.
- A follow-up that closes the loop, even when the fix was small.
I think teams often overinvest in the size of the remedy, the comped dessert or the service credit, and underinvest in speed and ownership. Train for the second and the first matters less.
Measuring the Experience Without Annoying People
Asking a guest to rate their meal while they are still eating it is a poor trade. The same goes for a pop-up survey inside a product while a customer is mid-task. Measurement should not become part of the friction it is meant to find.
Many of the useful signals already exist. In a restaurant: plates that come back half eaten, long gaps between courses, items voided or remade in the point of sale, tables that skip dessert at a much higher rate than usual. In software: which features a customer uses weekly, which ones they tried once and abandoned, and what their support tickets keep circling.
A practical step: choose three signals you already capture and review them on a fixed cadence, weekly for most small teams. Save direct questions for one well-timed moment, which belongs to the next stage of the journey, the follow-up. If you want to compare notes on what you track, you can find me on Instagram.
In my experience, a short list of signals reviewed consistently beats a large dashboard nobody opens.
What Technology Should Stay Out Of
Restaurant technology and customer success software are at their best when they carry information and remove repetition. Reservation notes that reach the table, a point of sale that keeps tickets accurate, usage data that warns a team before a customer quietly drifts. That is the work technology should do.
Where I think it should step back is the moments that carry warmth or judgment. The greeting. The recommendation that reads the table. The apology when something goes wrong. Picture a guest asking a server what to order and being pointed to a QR code, or an enterprise customer with an urgent issue routed through three automated replies before reaching a person. Both are efficient on paper and cold in practice.
A simple test: for each tool you use during the experience, ask whether it makes the guest or customer feel more known and looked after, or whether it mainly saves the team a step at their expense. Keep the first kind and rethink the second. If you want a regular outside view on questions like this, the GTM & Operations Plan is one 30-minute session each week.
Frequently Asked Questions
What is customer experience in a restaurant?
Customer experience in a restaurant is the sum of what a guest feels from arrival to departure: the greeting, pacing, food and drink, how problems are handled, and how easy the check is. In my view it is judged in use, not in the marketing, so the useful question is whether a normal weeknight service delivers what your menu and social posts promised.
What is value realization in customer success?
Value realization is the point where a software customer can show the outcome they bought the product for, not just that they log in. It usually follows first use, a regular rhythm of usage and adoption of deeper features. The restaurant equivalent is a guest leaving with the sense that the night was worth the time and money spent.
How does a POS like Toast affect restaurant service?
A point of sale such as Toast sits behind most of the service a guest experiences: orders reaching the kitchen, modifications and allergy notes on tickets, timing, and payment. When it is set up well, guests rarely notice it. When information has to be retyped or relayed by hand, errors and repeated questions tend to show up at the table.
How can a restaurant measure guest experience without surveys?
Many signals already exist in daily operations: food that comes back unfinished, items voided or remade, long gaps between courses and unusual drops in dessert or second-drink orders. Reviewing a short list of these on a fixed weekly cadence often reveals more than mid-meal surveys, and it adds no friction for guests. Direct questions work best in a single, well-timed follow-up.
Richard Yu
Richard Yu is the Managing Partner of Rich Ventures, a San Francisco startup consulting and early-stage investment firm, and co-founder and Managing Partner of Equal Parts, a restaurant and cocktail bar in North Beach. He was Director of Strategic Account Management at Lob, founding Head of Solutions Engineering at ChartHop and at Naehas, and in customer success at LeadIQ. He has experience scaling startup post-sales organizations from $1M to $20M+ ARR and advises pre-seed and seed stage founders on go-to-market strategy.