Why the hotel restaurant does not compete with the one across the street

A guest checks in at six in the evening, drops the suitcase, sits on the bed and opens the phone. In the next three minutes they decide where to have dinner. If your restaurant does not show up in those three minutes, you did not lose to the restaurant on the corner: you lost to the screen in front of them.

The wrong comparison

It is common to hear in the hotel's weekly meeting something like "the restaurant across the street is taking our guests". It is a convenient way to explain a drop in consumption, because it puts the cause outside the hotel. The problem is that it is rarely true, and when it is, it is almost never the main cause.

The restaurant on the corner competes for the same dining budget as any other restaurant in the city, but it does not compete for the same guest at the same moment. The guest who goes for a walk and decides to step into another place already made the decision to leave the hotel. The question that actually matters is not how to beat that restaurant out on the street: it is why the guest decided to leave in the first place, when they could have stayed.

Real competitor number one: not coming down

The hotel restaurant's strongest competitor has no storefront, no menu and no servers. It is the option of staying in the room watching a show with room service closed or with a menu so short it is not worth ordering from. Every guest who decides not to come down and does not order upstairs either is a lost sale with no outside competitor ever getting involved.

This happens more often than the restaurant team notices, because it leaves no trace. A guest who walks into the restaurant and leaves without ordering generates a complaint or a comment. A guest who never comes down generates no signal at all: they simply do not show up in any report, and that is why this is the most dangerous competitor, the one nobody sees.

Real competitor number two: the delivery app

The second competitor is not across the street either: it is on the guest's own phone, right next to the hotel's own app, if one exists. When room service (Room service) is slow to answer, when nobody picks up the phone at ten at night, or when the in-room menu is much shorter than the full restaurant menu, the guest opens an outside delivery app and orders from a place they never saw, that pays the hotel nothing, and that also forces someone from security to go down and meet the delivery at the door.

That order could have been yours. The food existed in your kitchen, the guest was inside your property, and the money went, whole, somewhere else. It was not the restaurant across the street that won that sale: it was the friction in your own process that pushed it outside.

Real competitor number three: the hotel's own poor first impression

There is a third competitor, more uncomfortable to accept, and it is the hotel competing against itself. If nobody mentioned the restaurant at check-in, if the signage inside the property does not clearly show where it is or when it opens, or if the guest tried to book a table and nobody answered, the hotel itself created the reason to leave. The guest did not choose the one across the street over yours: they never found out yours was a real option.

Check-in is the first sale

Check-in at the front desk is the moment of highest guest attention in the entire stay: they just arrived, they are listening carefully, and they have not yet decided anything about dinner. If the front desk does not mention the restaurant, the bar (Bar and lobby bar) or a promotion for the day, that silence is not neutral, it is an opportunity closing on its own.

When the restaurant across the street really is the problem

There are cases where the outside competitor really does matter, and it is worth naming them honestly. If the hotel's menu has not changed in years, if prices are clearly above similar places nearby with no reason the guest can perceive, or if service is noticeably slower than any nearby alternative, then yes, there is a real reason for the guest to prefer leaving. In those cases, the fix is not competing on price: it is reviewing the menu, service times and the actual in-restaurant experience.

The distinction matters because the two causes call for different actions. Blaming the restaurant across the street when the real problem is internal friction leads to spending on promotions that do not address the cause. Blaming internal friction when the real problem is a stale menu leads to fixing processes that already worked fine.

How to know who you are actually competing against

An illustrative example with numbers

The figures below are made up to show the reasoning. They are not market data and they are not from any particular hotel.

A 50-room hotel at 70 % occupancy has, in a 30-day month, 50 × 30 × 0.70 = 1,050 occupied room nights. If the restaurant serves 420 dinners to guests that same month, dinner capture is 420 ÷ 1,050 = 40 %. In other words, out of every ten guests who slept at the hotel, four had dinner there. If the manager believes the problem is the restaurant across the street, they will try cutting prices. But if they check how many room service calls after nine went unanswered, and find there were 180 that month, the real problem may be much closer: in the restaurant's own phone.

What to do about each real competitor

1. Against "not coming down": give a concrete reason to come down at check-in, like a promotion for the day or a table already booked for that night.
2. Against the delivery app: cut room service response time and offer ordering by message instead of only by phone.
3. Against poor signage: check whether the guest can find the restaurant's hours, location and menu without asking anyone.
4. Against silence at the front desk: give everyone doing check-in a short script that mentions the restaurant and the bar.
5. Against the restaurant across the street for real: review the menu every season and compare your service times against your own history, not against an opinion.

What the right report reveals

The metric that separates these causes is the same food and beverage revenue per occupied room (How food and beverage revenue per occupied room is calculated, and what a good number looks like), cross-checked against the number of occupied rooms that generated no hotel consumption at all that night. If that number is high and steady, the hotel is competing against itself, and no price adjustment against the restaurant across the street will fix it.

It is also worth checking the report by revenue center (Reports): if the bar rises while the restaurant falls, you probably did not lose guests, you moved them from one place to another inside your own property, which is a completely different problem from losing sales to the street.

• Revenue per occupied room, by week, to see the real trend.
• Unanswered room service calls or messages, by shift.
• Table requests versus confirmed bookings.
• Mention of the restaurant in the check-in script, spot-checked by the manager.

What to do this week

1. Calculate your dinner capture rate for the last four weeks, not just total revenue.
2. Count how many room service calls after nine at night went unanswered.
3. Check whether the front desk mentions the restaurant and bar during check-in, by listening to two random check-ins.
4. Check whether signage and the menu are visible and clear from the lobby and from the room.
5. Compare this week's revenue per occupied room against the same week last month before blaming the competition.

Inn Restaurant shows how many occupied rooms generated no consumption at any point in the hotel, so you know whether the problem is outside or inside before spending money fixing the wrong one. If you want to see that report with your own hotel, book the fifteen-minute demo (contact).