In a hotel, the review doesn't start at check-out. It starts with the room temperature at three in the morning, the check-in queue at six in the evening, the restaurant packed while the spa sits empty. The experience is operational long before it's emotional — and the operation leaves a trail in the space data.
Let's start with the obvious that nobody optimises: room readiness. A room that takes too long to be ready is a night you don't sell. Knowing in real time what emptied and what's already ready shortens the turnover and fills more beds — exactly the same logic as the hospital bed, in a different uniform.
Then the common areas. Without real occupancy, you size by eye: too much staff in the empty spa, a queue in the packed restaurant. With flow and dwell by zone, you schedule where the demand is and save where it isn't — and the guest stops waiting where they shouldn't.
And energy, which is top-3 of your costs but runs as if the hotel were always full. Setpoints that follow real occupancy cut the bill without anyone feeling it — because the comfort the guest values is exactly what you're controlling, not sacrificing.
This is where the two ledgers meet: the same sensor that cuts the kWh tells you if the room is too hot, if the lobby air is heavy, if the events room is stuffy. And that comes back — in reviews, and a review is future revenue. At chain scale, add the nightmare of multi-property reporting, which Sofia closes at quarter-end instead of leaving it by hand.
In a hotel, you're not managing a building. You're managing a promise of comfort, repeated room by room, day after day. The operation that keeps it without being noticed is the one that fills the house — and the one that fails it costs dearly, in the worst possible place: the opinion of whoever stayed.