Most independent restaurants run on three systems: a reservation book, a point of sale and a staff schedule. Each one holds something useful about the guest walking in tonight. In my experience they rarely talk to each other, so the team ends up forgetting what the systems already know: that this is a third visit, that the booking note said anniversary, that the server who looked after them last time is off tonight.
I'm Richard Yu. I have more than 15 years of startup and go-to-market experience, much of it in customer success and solutions engineering at software companies, where the job is getting customers to adopt, renew and expand. Today I'm a co-founder and the Managing Partner for marketing and operations at the restaurant I co-founded in San Francisco, and I built Regular inside it, one service at a time. This is what I think a hospitality operating system is, what it should do, and what it should not.
Three Systems That Never Talk to Each Other
The reservation system knows who is coming, how often they have booked and what they wrote in the notes. The point of sale knows what they ordered, how long the table sat and what they spent. The schedule knows who is working tonight and who clocked in late. Each one is good at its own job. The trouble is the space between them.
Picture a guest who books for two on a Thursday and mentions a birthday in the reservation note. The host sees it if she reads the notes before doors. The server hears about it if the host remembers to pass it on. The kitchen hears about it if the server catches them before the dessert ticket fires. Three handoffs, each one depending on memory during the busiest hour of the night.
When something gets dropped, it is rarely because the team does not care. It is because the information lives on three screens and the team has no time to read them together at 6:45pm. In my experience, many service misses trace back to a fact the restaurant already had in a system and did not bring to the floor.
What a Hospitality Operating System Is
A hospitality operating system is the layer that connects your reservations, point of sale and staff schedule, then turns that data into what each person needs at each moment of a guest's visit. It does not replace your reservation platform or your POS. It sits across them and does the reading, matching and remembering your team should not have to do by hand.
I think about it through five moments in the visit:
- Before they arrive: filling the book and knowing who is coming.
- When they arrive: the greeting, regulars, celebrations, allergies.
- At the table: pacing, service and who is working with whom.
- After they leave: the thank-you and the recovery after a bad night.
- Before they come back: repeat visits and what to change next week.
Restaurant management software often covers one of these moments well. An operating system covers the handoffs between them. That is what I built Regular to be: it works with the reservation, point-of-sale and scheduling systems a restaurant already uses and follows the guest from the day they book to the night they come back.
What It Should Do Before, During and After Service
Before service, it should put tonight's book in front of the host and manager with the context already attached. In Regular, that is Today's Guests: every reservation tonight with visit history, VIPs, allergies and seating notes. The host should not be cross-referencing last month's POS receipts to work out who is a regular. That work should be done before she arrives.
During service, it should answer the questions managers usually ask after the fact. How long are tables sitting at each stage? Which servers are pacing well? Who has not clocked in? The useful version of this is quiet: one alert to the manager when something needs a decision, not a dashboard someone has to watch.
After service, it should close the loop with the guest. Email Campaigns in Regular sends thank-you, cancellation and no-show emails from the restaurant's own mailbox, and holds regulars back so someone can write them a personal note instead. That last part matters to me. A regular deserves a sentence from a person, and the system's job is to tell you who they are, not to write it for you.
You can see how the pieces fit on the page listing every app in Regular.
What It Should Not Do
I spent years in software watching tools fail because they made the user's day harder. Restaurants are less forgiving than offices. If a tool slows the host down at 7pm, it gets abandoned by Friday. So here is where I think the line sits.
It should not put a screen between your staff and your guests. If a server is looking at a tablet instead of the table, the tool has taken the wrong thing. The information should arrive before the moment, in pre-shift or on a printed sheet, so the conversation at the table is human.
It should not ask your team to enter the same data twice. If the reservation already has the allergy, nobody on staff should be retyping it somewhere else.
It should not make judgement calls that belong to people. Software can surface that a guest might be a VIP or is celebrating something. A person should confirm it and decide what to do.
And it should not be priced in a way that discourages access. When a tool charges per seat, owners often limit logins to managers, and the line staff who need the information lose it. Regular is one plan with one login model and no per-seat pricing for exactly that reason.
How to Tell If Your Restaurant Needs One
Not every restaurant needs a hospitality operating system. A twelve-seat counter where the owner works every shift and knows most guests by name may be fine with a notebook. The need shows up when the knowledge of who your guests are lives in a few people's heads and the restaurant gets busy enough that those people cannot be everywhere.
A few signs I look for:
Your host prints the reservation list and handwrites notes on it before doors. Your manager exports reports from three systems on Monday and reconciles them in a spreadsheet. Regulars get recognised when their usual server is on and treated as strangers when that server is off. Thank-you emails go out when someone remembers. Allergy information lives in a free-text note that one person reads.
If two or three of those sound familiar, your restaurant tech stack has the data and is missing the connection. That is a systems problem, not a staff problem, and it is usually cheaper to fix than the cost of the guests who quietly stop coming back. The answer is rarely another standalone tool. It is getting the tools you already pay for to work together.
Where to Start This Week
You do not need new software to start thinking like an operating system. You need a routine that brings what your systems know onto the floor. Try this before your next service:
- Thirty minutes before doors, pull tonight's reservations and mark every guest who has visited before.
- Read every reservation note and flag birthdays, anniversaries and allergies on the list in a single colour.
- Check the schedule against the book: if a regular's usual server is off, tell whoever is covering that section.
- Run a five-minute pre-shift covering returning guests, celebrations and allergies by table number.
- After close, write down which regulars came in and send each one a short personal note within two days.
Do this for a week and count how long it takes. That time is what technology should take off your hands. What it should not take is step four, the conversation with your team, or step five's personal note. Those are the hospitality. The rest is reading and matching.
If the routine works and you want it done before you arrive, you can book a Regular demo. And if you try it, I would like to hear how it went. You can find me on Instagram.
Frequently Asked Questions
What is a hospitality operating system?
A hospitality operating system connects a restaurant's reservations, point of sale and staff schedule, then uses that combined data to support the team at each moment of a guest's visit, from booking to arrival, service, follow-up and the return visit. It works alongside the tools a restaurant already uses rather than replacing them, so the team stops forgetting what the systems already know.
How is a hospitality operating system different from restaurant management software?
Restaurant management software often handles one job well, such as reservations, payments or scheduling. A hospitality operating system focuses on the handoffs between those jobs: matching a reservation to past visits, telling the server about an allergy, flagging a missed clock-in, or sending a thank-you after the meal. The value sits in connecting data the restaurant already has.
Do I need to replace my POS or reservation system to use one?
No. A hospitality operating system should work with the reservation, point-of-sale and scheduling systems you already run. Replacing core systems is disruptive and usually unnecessary. The goal is to connect what you have so guest data reaches the host, servers and managers when they need it, without staff entering the same information twice.
What should restaurant technology not do during service?
In my view, it should not put a screen between staff and guests, ask the team to retype data that already exists, or make judgement calls that belong to people. Information should arrive before the moment it is needed, through pre-shift or a printed sheet, so the conversation at the table stays human and the team spends its attention on guests.