Hotel software is usually justified with "it will save time". That is true and it is unmeasurable, so nobody ever confirms it. These four numbers are measurable, and three of them convert directly into money.
Capture the baseline before go-live
This is the step that gets skipped, and without it every later claim is an assertion. Two weeks of observation is enough:
- Share of bookings arriving direct versus through platforms
- Total commission paid last month
- Minutes from guest arriving to guest holding a key, timed on a sample of about twenty check-ins
- How often rates differ between your site and the platforms, checked daily for a fortnight
Twenty minutes a day for two weeks. It is the difference between "the system is good" and a number you can put in front of an owner.
1. Direct booking share
The single most valuable metric, because a direct booking and a platform booking are worth different amounts for the same room night. Commission on a platform booking is a large fraction of margin.
A booking engine that shifts even a modest share of volume from platform to direct changes the economics. Track the percentage monthly, not the absolute count — total bookings move seasonally and the ratio does not.
Attribution caveat worth being honest about: some guests discover you on a platform and then book direct. That is still a win, but it means the platform is doing work you are not paying for. Do not expect direct share to rise indefinitely.
2. Commission avoided
Direct bookings multiplied by average room value multiplied by the commission rate you would otherwise have paid. This is the cleanest ROI figure in hospitality software and it is usually the one that justifies the whole spend.
Compare it against total software cost including the channel manager and implementation. For most properties with meaningful platform volume, the payback period is short enough to be persuasive on its own.
3. Time per check-in
Time the same sample after go-live. Expect it to get worse for the first fortnight while staff learn, then improve. If it has not improved after a month, something is configured wrong — usually rate plans requiring manual selection, or a document capture step that is slower than it needs to be.
Convert the saving into hours per month at peak occupancy. That is the number that tells you whether you need another front desk person next season.
4. Rate parity errors
Before a channel manager, rates drift between platforms because they are updated by hand and someone misses one. Every drift is either money left on the table or a parity complaint from a platform.
Count the errors before and after. This usually goes to near zero, and it is the easiest of the four to demonstrate.
What not to claim
Occupancy and average daily rate are affected by season, local events, pricing decisions and the economy far more than by software. A PMS that improves rate distribution may help, but attributing an occupancy rise to the system is not defensible and an owner will rightly challenge it.
Stick to what is attributable: commission, parity errors, and time. Those you can defend.
Review at ninety days
Not thirty — the first month is learning, not performance. At ninety days compare all four against baseline, and be willing to conclude that one of them has not moved. That finding is usually a configuration problem you can fix, and looking for it is what separates a system that gets better from one that plateaus.
About the author. Kislay Chandan has worked with schools since 2014. Rather than gathering requirements from the outside, he worked inside a school to see what actually goes wrong day to day, and built what he found into the software. He still works with Shemrock Glitters in Patna — most changes to the product start with something that came up there.
Gallery
