AI in Hospitality, Part 3 of 15
In a first meeting, a managing director often says one of two things: «We need to do something with AI now too» or «We already have a chatbot, but somehow it isn't delivering.» Both statements share the same blind spot: nobody has looked beforehand at where the business actually stands.
What is an AI baseline assessment?
An AI baseline assessment is a structured stocktaking of a business's systems, data, team competencies and workflows, from which a prioritised list of measures emerges. It doesn't answer the question «Which tool should we buy?» but rather «What do we need in place before a tool can deliver anything at all?». The result is not a wish list, but a roadmap with three time horizons.
The process itself is unspectacular: conversations with teams from reception, housekeeping, reservations and administration, a look at the existing system landscape, a review of where data already comes together today and where it doesn't. This matches what current practical guides from the industry recommend: check the data infrastructure first before any investment, and only then start with a tightly scoped pilot project rather than tackling the complex application straight away (eHotelier: The hotel AI readiness audit).
Why the order determines success or frustration
The obvious mistake: choose a tool first, then see if it fits. This regularly leads to exactly the statement from the introduction — a chatbot that helps nobody because it accesses outdated room data, or a reservation assistant that doesn't know the PMS and the booking engine show different availabilities.
An analysis of AI readiness in hospitality names the most important step before any investment quite specifically: a review of data quality — how many years of clean data actually exist, in what format, in which systems (Tommaso Maria Ricci: AI for Hospitality – The Complete Industry Guide). This aligns with the first two articles in this series: data silos and missing system connections are not a side issue, but the foundation on which every later decision is built.
The three horizons as a thinking framework
A good baseline assessment doesn't end with a long list of possibilities, but with a prioritisation across three time periods.
Quick wins (0 to 4 weeks). Measures with no IT effort that can be implemented immediately: an assistant that pre-sorts standard requests from the email inbox, a knowledge repository for recurring guest questions, an automated workflow for internal checklists. No new system, no interface — just a different way of handling what is already there.
Medium term (1 to 3 months). This is where system integration comes into play: connecting the PMS, point-of-sale system and CRM from the last article, so that assistants can access a complete guest profile. This takes some lead time, but is achievable with most modern cloud systems.
Strategic (3 to 12 months). Independent automation: assistants that act on their own within defined approval limits — for example, sending a reservation confirmation automatically or suggesting a housekeeping reassignment, without every single action needing to be approved by a person. This is the most demanding horizon, because it requires both trust in the system and clear limits at the same time.
A practical example
A holiday resort with around 80 rooms had its systems and workflows reviewed and expected the result «new PMS, new CRM, high investment». The actual roadmap looked different: as a quick win, a knowledge repository was set up for the reservations team, because the most common questions were already being answered twice or three times over in emails. In the medium term, this was followed by connecting the booking engine and PMS, which had until then run independently of each other. Independent automation in room allocation was planned as the next step, but deliberately not yet tackled — the team was to gain experience with the simpler workflows first. This order, not tackling the biggest single project first, was the actual success factor.
Linking back to the data foundation
A baseline assessment is not an end in itself, but the place where everything already covered in this series comes together: the data silos from article 1, the system integration from article 2 and — in upcoming articles — the concrete applications in staffing, finance and guest contact. Without this stocktaking, every individual measure remains a matter of chance.
What's next in the series
The next article moves into internal organisation: AI in staff planning, from duty rosters to application pre-screening — and where the line runs between supporting and replacing HR responsibility.
Further reading
- The data graveyard most hotels are sitting on
- From data silo to shared foundation
- Hyper-personalisation 2.0: when the hotel website responds individually to every guest
Sources
- eHotelier (2026): The hotel AI readiness audit: a practical checklist for getting started
- Tommaso Maria Ricci (2026): AI for Hospitality: The Complete Industry Guide
Frequently asked questions
What does an AI baseline assessment cost, and how long does it take?
A structured analysis of systems, data, team and processes usually takes 2 to 3 weeks and ends with a prioritised roadmap across three time horizons.
Do you have to connect all systems first before you can start with AI?
No. Quick wins with no IT effort are usually implementable immediately. System integration and independent automation only follow in the medium-term and strategic steps of the roadmap.
What distinguishes a baseline assessment from classic IT consulting?
IT consulting usually focuses on systems and technology. An AI baseline assessment additionally takes into account team, competencies and workflows — because the most common cause of failed AI projects is not the technology, but acceptance within the team.
Tourismusconsult supports hotel businesses with the AI baseline assessment: a structured analysis of systems, data, team and processes that leads to a prioritised roadmap — with quick wins, medium-term and strategic measures.
