Every hotel tech company I have worked with has a slide somewhere that says onboarding takes two weeks. It usually does, the first time. What the slide leaves out is that many of the people you onboard in week one will not be there in month six. Front desk teams turn over constantly, and every new hire meets your software as if it had launched yesterday.

I call this the adoption tax. It is paid quietly, by the hotel and by you, and almost nobody puts a number on it.

I spent 14 years at eZee Technosys, now YCS, and a large part of that was in support and training. The pattern was the same across markets. The property that was happy at go-live was often the property that was unhappy nine months later, and when we looked, the people who had been trained were gone.

Why the front desk is different

Most B2B software is used by people who stay in their jobs long enough to become experts. A finance team learns an accounting system and keeps that knowledge for years. The front desk is not like that. It is often an entry-level role, it runs on shifts, it relies on seasonal and part-time staff, and it is a common stepping stone to other departments or other hotels.

That means the person using your PMS at 2am on a Saturday may have started on Tuesday. They were shown the basics by a colleague who was shown the basics by someone else. Whatever your trainer taught at go-live has been passed down like a photocopy of a photocopy.

What the adoption tax looks like in practice

It rarely shows up as a complaint about turnover. It shows up as other things.

Support tickets that repeat the same how-to questions, from the same property, months apart. Features the hotel paid for that nobody uses, because the person who knew about them left. Workarounds on paper or in spreadsheets that creep back in because a new hire did not trust the system. And eventually a general manager who says the software is hard to use, when what they mean is that nobody on the current shift was taught it properly.

From the vendor's side it looks like a usage decline with no obvious cause. From the hotel's side it looks like the product getting worse. Both readings are wrong, and the renewal conversation suffers for it. I have written before about why hotel tech companies lose customers around month three; turnover is one reason that pattern repeats later in the year.

Why nobody prices it in

Vendors do not price it in because their onboarding metrics stop at go-live. A property is marked as activated and the account moves to success or support. Nobody tracks whether the knowledge survives the next three hires.

Hotels do not price it in because the cost is spread across small moments: an extra ten minutes at check-in, a rate loaded wrongly, a night audit that needs a call to support. None of those feels like a software cost. Together they are.

And sales teams do not price it in because buyers do not ask. A general manager evaluating software asks how long implementation takes. They almost never ask what happens when half the desk has changed by next summer. That silence is where the tax hides.

Consider a mid-size city hotel

Consider a hypothetical 120-room city hotel that goes live on a new PMS in March with a front desk of eight people, all trained on site. By October, five of the eight have left. The three who remain train the five replacements between shifts. Group bookings, split folios and channel mapping, the things that took longest to teach, are the first to be lost.

By the time the contract comes up for renewal, the hotel has a long ticket history, a front office manager who believes the system is clumsy, and an owner asking whether the old one was better. Nothing about the product changed. The people did.

What vendors can do about it

The fix is not more training at go-live. It is designing for the fact that the go-live team will not last.

Train roles, not people. Build short, role-specific training that a new hire can complete in their first shift without a trainer. Night audit, check-in, group handling. Each one short enough to finish between arrivals.

Make the product teach. In-product prompts, checklists for rare tasks and sensible defaults do more than a manual nobody opens. The goal is that a new receptionist completes an unfamiliar task correctly the first time.

Watch for knowledge loss. Track new user logins at each property alongside feature usage. When a property adds several new users and usage of a key feature drops, that is the moment to step in, not at renewal. It is the same thinking behind designing onboarding for properties with no IT staff: assume the expertise is not there and build for that.

Offer refreshers by season. Hotels hire in waves before peak periods. A short refresher timed to those waves protects you in exactly the months when mistakes cost the most.

What it means for sales

There is a sales opportunity here too. Most competitors pitch implementation speed. Very few talk about what happens after the implementation team leaves. A vendor who can say, credibly, here is how a receptionist who joins in eight months will learn this in one shift, is answering a fear the buyer has but has not voiced.

It also sharpens who you talk to. The general manager feels the tax. The owner pays it. Showing either of them that you have thought about staff churn is a stronger argument than another feature.

Where to start

Pull your support tickets for the last twelve months and tag the ones that are how-to questions about features the property was already trained on. Then check how many came from users created after go-live. That single cut tells you how much of your support load and churn risk is really the adoption tax. It is one of the quieter places revenue leaks in a hotel tech company, and one of the easiest to measure once you look.

If you want to see where activation and retention sit against the rest of your funnel, run the 12-point leak audit on your own numbers. It takes about twenty minutes and shows you which leak to fix first.

Frequently Asked Questions