Hotel software does not have a feature shortage. It has a defaults shortage. Most PMS, channel manager, RMS and guest messaging products already do more than the average property will ever switch on. What decides whether a hotel gets value in its first month is what the product does before anyone touches a setting.

That is the stance of this post: the next feature you ship matters less than the defaults you ship with it. If you sell hotel software, the roadmap meeting should spend as much time on what is preselected, prefilled and switched on out of the box as it does on what is new.

The evidence that defaults decide behaviour

Defaults are one of the best studied ideas in behavioural science. A 2019 meta-analysis in Behavioural Public Policy, When and why defaults influence decisions, pooled 58 default studies covering 73,675 people and found a considerable effect (d = 0.68). Two findings matter for software vendors. Defaults were more effective in consumer domains, and they worked best when people read them as an endorsement of what the designer thinks they should do, or as the status quo they already own.

Both conditions describe a hotel team opening new software. A front office manager assumes the vendor preset the system the way good hotels run it. Whatever is on at go-live becomes how the property works, because nobody has time to revisit it.

Jakob Nielsen made the same point for interfaces in 2005. In The Power of Defaults he cites a Cornell study where 42% of users clicked the top search result. When researchers secretly swapped the top two results, the new top result still got 34% of clicks. His conclusion for product teams: users rarely use customisation features, so optimise the default experience, because that is what most users stick to.

Features you add mostly go unused

The other half of the argument is what happens to new features. Pendo's 2019 Feature Adoption Report found that 80 percent of features in the average software product are rarely or never used. Its later feature adoption benchmarks put the median at 6.4%: for every 100 features a team ships, only 6.4 drive 80% of click volume. Products in the top 10% reach 15.6%.

Hotel software is not exempt. A feature that needs a manager to find a settings page, understand an option and choose a value is a feature most properties will never meet. If it is off by default, for most customers it does not exist.

Why hotels feel this more than most buyers

Hotels change people constantly. The US Bureau of Labor Statistics reported a quits rate of 3.5 percent in accommodation and food services in August 2026, against 1.9 percent for all nonfarm jobs. That is a monthly rate. The person who configured your product at onboarding is often not the person using it six months later, and the new person inherits whatever was set, right or wrong.

That is why front desk turnover hurts software adoption so badly. Training does not survive staff churn. Defaults do. A sensible default keeps working through three general managers and a dozen front desk hires; a training session on an optional setting is gone when the trainee leaves.

Hotels also buy without IT teams. Many independents and small groups run with no one whose job is configuration, which our post on onboarding properties with no IT staff covers. For them, the default is the configuration.

What a better default looks like

A good default is not the vendor's preference or the first option in a list. Nielsen's advice was to pre-populate fields with the most common value when you can determine it in advance, and to avoid always picking the most expensive option, because that costs credibility. For hotel software that translates into a short set of questions you can ask of every setting.

Call this the default test: common case, safe failure, segment aware, survives turnover, reversible. A setting that passes all five rarely needs a help article. A setting that fails two or more will show up in support tickets and churn calls.

Some vendors already sell defaults

Group level configuration is the clearest public example. Mews describes Mews Multi-Property central services as a way to set up a service once and roll it out across all properties, saving time and reducing manual work. That is a default sold as a feature: the group decides once, and every property starts from the same sensible setup instead of a blank screen.

The same thinking applies to independents. A booking engine that ships with a tested cancellation policy, a payment flow already connected and rate plans named in plain language gets a small hotel live faster than one with twice the options. Our post on reducing time to first value shows why that first week decides so much of the renewal.

The objections, answered

"Every hotel is different"

True, and defaults do not stop anyone from changing a setting. They decide what happens when nobody does. Segment aware presets, by property type, size and market, handle most of the difference without asking every customer to start from zero.

"Prospects buy on feature lists"

Feature lists help win RFPs. They do not keep customers. When a hotel says software is easy to use, it usually means the product did the right thing without being told. That experience comes from defaults, and it is what reviewers and referees describe to the next buyer.

"Opinionated defaults create liability"

They create responsibility, which is different. The meta-analysis found defaults work partly because people read them as an endorsement. If you preset something, own the choice: explain it, show it and make it easy to change. A visible, reversible default is safer than a hidden one and safer than a blank field that leads to an error.

What to change on your roadmap

1. List the twenty settings every new property touches in onboarding, and record what most customers end up choosing.

2. Make the most common choice the default for each property segment, and mark it as recommended.

3. Turn protective settings on by default, such as overbooking protection, parity alerts and payment security, with a clear off switch.

4. Rewrite setting labels in hotel language, not engineering language.

5. Measure activation, not just feature releases, and use the methods in signs you have an activation problem.

6. Announce default changes in your release notes so existing customers know what changed and why.

None of this needs a big build. Most of it is product decisions your team has avoided because a new feature is easier to put on a slide than a better preselected value.

The commercial case

Defaults are a go-to-market lever, not just a design choice. They shorten onboarding, lift activation, cut support load and give your customer success team fewer fires to fight. They also make your demo honest: the product a prospect sees is the product they will run on day one, not a fully configured showroom. That matters at every stage of the hotel tech GTM system, from the first demo to the renewal call.

Want to know whether your product's setup is quietly costing you activation and renewals? Book a free GTM leak audit and we will show you where new properties stall between signature and first value.

Frequently Asked Questions