You are pricing yesterday’s hotel

It is Tuesday, 3pm. The F&B outlet just cleared its last cover — quieter than any Tuesday this quarter. The corporate group in Ballroom B cancelled their Thursday working lunch two hours ago; the S&C team knows, catering knows, the GM knows. On Thursday, OTA pace just softened by six points on the compression date the strategy meeting was built around. Someone in operations noticed the housekeeping ratio slipping since the wash the day before.

Your revenue management system knows none of it.

It will make tonight’s pricing recommendation on the picture the world had yesterday morning, filtered through the room-revenue silo it was born inside. Tomorrow at nine, the revenue meeting will discuss those recommendations as if the last twenty-nine hours never happened.

The discipline earned its name in an era it no longer lives in. What we still call revenue management now prices yesterday’s hotel.

The silo that made the discipline

I want to be fair to the past. Revenue management as we practise it today was built for a world where the only reliable, timely signal was room-nights pickup. POS was locked in another vendor’s basement. Group displacement lived in a paper contract file. Labour was HR’s problem. Even the CFO did not want to hear about it until the month-end pack.

Given those inputs, the room-revenue silo was a rational specialisation. You could build models, hire analysts, run BAR strategies, learn what a pickup curve looks like. The discipline earned its seat at the commercial table by getting very good at one thing.

That world is gone. The signals the discipline was originally starved of are now sitting in your PMS, your POS, your S&C system, your labour tool, and your channel manager — updated by the hour. They are sitting there separately. Ask any hotel commercial team how much of the past week they spent reconciling numbers across those systems; the industry average, lands around eleven hours per person, per week.

Five signals that now belong in one view

If pricing a hotel means predicting the value of every unsold room-night, the modern definition of “value” has grown five dimensions the RMS was never designed to see. Any pricing recommendation that misses two or more of them is a guess dressed in a confidence interval.

Room pickup and pace. The classic — and still the foundation. Nothing here has changed except that it is no longer enough.

F&B and outlet activity. A room booked into a night when the outlet is running at 40% covers is a different product from the same room on a night when the outlet is turning tables twice. TRevPAR is the metric everyone quotes; almost nobody uses it inside the pricing decision itself. If F&B pace does not influence what you charge, you are yielding half the hotel and hoping the other half follows.

Group and event displacement. M&E is the last hotel commercial blind spot. A hundred-room block at a strong ADR that historically washes 15–20% is a different animal from a hundred-room block that holds firm; a peak-Tuesday association conference at rate card can quietly displace three smaller corporate groups at higher revenue per m². A pricing engine that cannot see the group pipeline is optimising against a moving inventory it does not know is moving.

Channel mix and cost of acquisition. Two €200 reservations are not the same €200. Net revenue after distribution cost — the number the owner cares about — depends on channel, on segment, on loyalty status, on which acquisition dollar bought the booking. Pricing to gross RevPAR while the owner is asking about GOP is a communication failure with a P&L cost attached.

Labour and capacity constraints. Pricing a room the hotel cannot service is a satisfaction bomb with a delayed fuse. When housekeeping is running short, when the outlet is understaffed, when front-office is at the ratio where check-in queues bleed into complaints. a smart RMS would hold rate rather than fill. Today’s RMS holds rate against a labour reality it cannot see.

Why the category has under-shipped this

I will not pretend I am neutral here. My company sells the layer this argument implies you need, and we win our share of these processes. What I am about to say is what I would say if I were still sitting on the operator side of the table, watching the vendor category drag its feet.

The RMS category has under-shipped cross-domain pricing for a reason that sits squarely with the vendors. RMS incumbents monetise per-property, per-module. Adding domains explodes integration surface, increases support cost, and dilutes the pricing engine’s central story. The commercial incentive is to double down on the room-revenue island, add a “total revenue” pill to the marketing deck, and let hoteliers stitch the rest together.

Procurement will object that cross-domain pricing is unproven, that no vendor has shipped it at scale, so the risk sits with the first mover. Fair. That is exactly why the first move belongs to the hotelier. The move is smaller than it looks: one view that shows the five signals in the same room, in front of the same people, on the same morning. Vendor pressure follows buyer pressure. It has never worked the other way around.

What changes on Monday

Three moves are available inside the tech you already own.

First, pull the five signals into one view. Even a stitched dashboard beats five browser tabs. The stitching itself is trivial; the value comes when the revenue manager, the DOSM, the F&B director, and the GM all look at the same picture at 9am. Trust in the numbers is built by everyone seeing the same numbers.

Second, change the agenda of the morning revenue meeting. Any pricing decision must cite at least three of the five signals. If someone quotes only pickup and last-year comp, the answer is what about the other three, every time, until it becomes habit. The discipline you enforce in the meeting is the discipline that ends up in the pricing.

Third, ask your RMS vendor one question in the next QBR: when will your recommendation see F&B pace, group displacement, and labour capacity inside the same query? Ask for the engineering roadmap version, with a date. If the answer is a shrug, that is the roadmap you needed to see.

None of this requires ripping and replacing the RMS. It requires refusing to keep pricing yesterday’s hotel on the assumption that the rest of the building has not moved since last night.