Lead Hospitality

Thirty Days Running a Hotel Without Opening the PMS

THE IDEA

For thirty days, I will run a hotel without opening the PMS. Every management question and decision will go through a conversation with HotelGEX in ChatGPT or Claude. Here are the challenge rules, what I will measure, what a typical morning will look like and where I expect it to fail.

I estimate that I have spent a considerable part of my professional life looking at a PMS. Not working in it, which is different, but looking: searching for a figure, checking an arrival, moving through screens to piece together something I needed to know before making a decision. On many mornings, the first hour of a hotel manager’s day is not spent managing. It is spent navigating.

That is why I have decided to do something that would have seemed eccentric a couple of years ago. For the next thirty days, I am going to manage a hotel without opening the PMS. Not the PMS, not the channel manager, nor the spreadsheets that we all end up building around them. Every management question and decision will go through a conversation with HotelGEX from ChatGPT or Claude, thanks to the connector that enables work with hotel data from those assistants.

This is not an attack on the PMS. The hotel will continue operating with its systems, the team will continue using them, and every reservation will still be recorded where it belongs. What changes is the way I manage. I want to test something I have been arguing in writing for some time: that a manager’s job is to make decisions, not to know where every piece of data is. If that is true, I should be able to manage for an entire month by asking rather than searching.

This article does not tell the outcome, because there is no outcome yet. It sets out the rules, what I will measure and what I expect to fail. I will publish what happens week by week, including what does not go well.

The rules of the challenge

An experiment without rules quickly turns into a sales demonstration, and that does not interest me. These are the five rules I have set myself:

  1. I do not open the PMS. Nor the channel manager or tracking spreadsheets. The team works as normal; the restriction is mine and affects only my management work.
  2. Every management question goes through conversation. Occupancy, arrivals, booking pace, Housekeeping, incidents, guests, pricing. If I need to know it, I ask.
  3. AI proposes and I decide. No change is implemented without my explicit confirmation. In pricing, for example, every proposal is reviewed before it is applied, has limits on the permitted variation and can be reversed. This is not about delegating management to a machine, but about changing the way I arrive at each decision.
  4. If I open the PMS, I log it and explain why. These emergency openings will probably be the experiment’s most valuable data point, because they will show exactly where conversation still falls short.
  5. I publish what works and what does not. A challenge that only reports successes teaches nobody anything.

What I will measure

The feeling that something is more convenient is not enough to change the way a hotel is managed. That is why I will keep a daily record of six indicators:

  • Time to the first decision of the day. How many minutes pass from when I start work until I make the first relevant decision. Today, much of that time is spent gathering information.
  • Emergency openings. How often I need to return to the traditional screen and for what reason.
  • Unanswered questions. Queries the system cannot answer, either because the data does not exist, is not available, or because the question requires context that only someone on the team has.
  • Answers I had to verify. How often I doubted a figure and how I verified it. Trust is not declared; it is built or lost with every answer.
  • Decisions made through conversation. What proportion of my daily decisions I could make without changing tools.
  • Reporting hours. The time spent preparing summaries for ownership, the team or management meetings.

What a typical morning will look like

The first request of the day will always be the same: a management briefing with occupancy, arrivals, departures, open incidents and the matters requiring my attention. This is exactly the function of HotelGEX’s Action Center and 360 briefing, except that instead of opening a dashboard, I will ask for it in a single sentence.

360° Hotel Intelligence

Stop managing isolated systems. Start managing the whole hotel.

HotelGEX connects guests, operations, Revenue, F&B, Groups & Events and Management into one intelligent hotel context — so every decision starts with a clearer picture.

See what your hotel could become
Discover HotelGEX →
✓ 30 days free · no commitment

From there, the conversation will branch out according to the day:

  • Arrivals and guests. Who is arriving today, who is returning, what special requests there are and what we know about each guest thanks to their longitudinal profile in Customer 360.
  • Operations. Which rooms have a same-day departure and arrival, whether the Housekeeping team is on schedule and which incidents remain open, supported by the operations control tower and AI-powered Housekeeping planning.
  • Revenue. Booking pace for the coming weeks, weak dates and pricing scenarios, supported by Revenue Intelligence. When I decide to change a rate, I will see the proposal before confirming it.
  • Reports. At the end of the week, I will request a summary for ownership covering what happened, variances and pending decisions.

None of this is impossible with traditional tools. The difference lies in the journey: instead of opening five screens and reconstructing the context, the question goes straight to the data. I want to test whether that difference changes the quality of decisions or merely their convenience.

What I expect to fail

It would be dishonest to begin a challenge like this convinced that everything will go well. I have five suspicions I want to test:

  • The exceptions that live outside the systems. What is agreed over the phone, what is resolved in a corridor, or what only the person on duty knows. If it is not recorded anywhere, no conversation will be able to find it, and that will be a lesson about the hotel, not the technology.
  • Data that exists but is not accessible. There will be information the PMS holds that does not yet reach the conversation. It is the same phenomenon I described when discussing the innovation ceiling a PMS can impose, which is why I am so interested in HotelGEX’s integration architecture: the challenge will show which connections are genuinely needed.
  • My own habits. I suspect that some emergency openings will have nothing to do with technology, but rather with twenty years of reflexes. I will log those too.
  • Trust in the figure. Will I believe an occupancy figure I have not seen on screen? As I wrote a few weeks ago, hospitality AI must demonstrate how it knows what it knows. If an answer cannot explain its source, I will verify it and report it.
  • Limits of authority. There will be decisions that should not be made in a conversation, or at least not without further controls. The challenge will help refine, in practice, the authority matrix hospitality AI needs.

Why it is worth trying

For months, I have been writing that managing a hotel in 2027 will require redesigning management work and that the person who will ultimately take the place of many managers is already working with artificial intelligence. Writing it is easy. Testing it firsthand, with the hotel operating and no safety net, is something else.

I am also interested for a less obvious reason. A conversation is only as good as the context it can access. As I said recently, AI knows a great deal about hotels and almost nothing about your hotel. At its core, this challenge is a test of how much the system knows about one specific hotel and how much knowledge still lives only in people’s heads.

If, at the end of the month, the conclusion is that the manager needs to return to the PMS, I will say so. If the conclusion is that they can manage better without it, I will say that too. What I will not do is pretend the experiment went perfectly.

If you want to take the challenge with me

Any manager can try it on a small scale: one week, one single rule and a notebook to record every time they return to the usual screen. If you want to see how the conversation with a hotel’s data works, you can explore the live HotelGEX demo or request a demonstration using data from your own property.

And if you would rather wait for the results, the countdown starts now. In a week, I will publish the first challenge diary: what worked, what did not, and the first time I came close to opening the PMS.

KEEP EXPLORING

This article ends here. The archive does not.

Lead Hospitality brings together 1200 English articles published since 2018: years of experiences, decisions and lessons you can keep exploring.

CONTINUE FROM HERE

What would you like to explore next?

Choose a direction and keep reading around what you want to solve, learn or challenge.

Discover something interesting ↓Surprise me ↗
01MAKE MOREProfitability, revenue and decisions that reach the bottom line. 02LEAD BETTERTeams, culture, talent and the conversations that matter. 03SELL BETTERPositioning, marketing, distribution and customers. 04CREATE EXPERIENCESService, loyalty and details guests remember. 05UNDERSTAND WHAT'S NEXTInnovation, AI and new ways of thinking about Hospitality. ✦SURPRISE MEShow me something worth five minutes of my time.
✦ LEAD AI · MEMBERSHIP

Turn reading into actionable knowledge

Basic includes article recommendations. Premium unlocks questions, analysis, comparisons and applying the knowledge to your hotel.

See subscriptions →