IT that surprises your CFO is IT without a roadmap.

Chapter 01

The switch that fails in high season was always going to fail. The date was known. The budget wasn’t.

Every piece of hotel IT has a lifecycle: access points, switches, servers, door locks, TVs, licences. None of it fails as a surprise to the equipment, only to the budget. Lifecycle planning replaces the annual scramble with a rolling roadmap: what gets replaced when, what that costs, and how it aligns with occupancy, openings and compliance deadlines. The CFO gets one predictable line. The operation gets hardware that retires before it fails.

Picture the surprise version. A core switch dies on a Friday in July. The hotel is full. The replacement has to be found, quoted, shipped and installed under pressure, at whatever price the situation demands. The invoice lands in a quarter that had no room for it, and the CFO reads it as proof that IT is unmanageable. Nobody in that chain did anything wrong on the day itself. The failure happened years earlier, when the switch was installed without a retirement date.

Now picture the planned version of the same event. The switch sits in the inventory with an age, a support status and a replacement window, and enters the roadmap well before end of support. Procurement compares offers without a deadline. The swap happens on a quiet Tuesday in the low season, inside an agreed maintenance window. Same switch. Same cost category. An entirely different experience for the hotel, the guests and the budget.

The pattern repeats across every asset class. Door locks, terminals, servers, operating systems, licences: each one has a known life and a known end. A hotel group that writes those dates down and plans against them has removed the single largest source of IT budget shock. Not by spending more, but by deciding earlier. That is the whole premise of a hotel IT roadmap. The information already exists in the estate. Lifecycle planning simply moves it onto paper before it moves onto an invoice.

Chapter 02

Four practices, repeated yearly.

Lifecycle planning is not a document. It is a discipline with four moving parts, each simple on its own. The value comes from running all four together, every year, without exception. Skip the inventory and the roadmap rests on guesses. Skip the review and the roadmap drifts away from reality within a season.

A roadmap does not make IT cheaper. It makes IT decidable.

A living inventory of every asset, its age, support status and role: access points per floor, switches per cabinet, servers, terminals, licences and the contracts behind them. Most budget surprises are just inventory gaps with an invoice attached. You cannot plan the replacement of something you forgot you own. The inventory turns that unknown exposure into a list, and a list can be budgeted.

Every asset class gets a lifecycle and a replacement window. Access points age on one rhythm, servers on another, door locks on their own. End of support dates, like Windows versions or network hardware, land in the roadmap years ahead instead of as emergencies. The window matters more than the date: it gives procurement room to negotiate and the operation room to schedule.

Replacements scheduled around occupancy, renovations and openings, so one site visit carries multiple upgrades and no work lands in high season. A floor being renovated is a floor whose access points can be replaced at near zero disruption. A generic IT calendar does not know what a full house in July means. A hotel IT roadmap is built around it. How openings fit is covered in the opening playbook.

Lifecycle, maintenance and support consolidated into a predictable periodic amount. Finance plans years ahead, and IT stops competing for emergency budget. The conversation shifts from justifying invoices to choosing priorities, which is a better conversation for everyone at the table. For the CFO, this is also where capex and opex stop fighting each other. Planned replacement can be financed deliberately, spread or bundled as the balance sheet prefers, instead of arriving as forced capex in whichever quarter the hardware chose.

Chapter 03

What good looks like for a hotel group.

Not every roadmap deserves the name. A spreadsheet listing hardware and hopeful dates is a wish list. A roadmap earns the name when it can answer the CFO’s three questions without preparation: what will IT cost next year, why that amount, and what happens if we defer. Deferral is a legitimate decision, but only when its consequences are priced. A real roadmap shows what a postponed replacement does to risk and to next year’s hotel IT budget, so the board defers with open eyes or not at all.

The standard we hold roadmaps to is practical. It covers every property in the group, not just the flagship, because the oldest switch in the portfolio sets the risk level for the whole brand. It looks at least three years ahead, because that is the horizon on which hardware ages and financing decisions are made. And it is owned by one party who is accountable for keeping it true, because a roadmap nobody maintains is out of date the day after it is written.

The third test is the hardest: the roadmap has to survive contact with the business. A new opening, an acquisition or a rebrand should slot into it, not blow it up. When a group takes over a property, the roadmap absorbs the inherited assets, flags what is at risk and reprices the coming years. That is the difference between a plan and a planning capability.

Hold your current roadmap against these tests. If it fails one, you have a document. If it passes all three, your CFO already knows, because the budget meetings got shorter. The honest version of this exercise takes an hour with the current plan on the table. Where the answers require research, the roadmap has told you where it needs work.

Chapter 04

Four steps, then a yearly cycle.

Our IT Strategy & Project Services team builds and maintains lifecycle roadmaps for hotel groups: grounded in a real inventory, aligned with your commercial calendar and reviewed with you every year.

The order matters. Groups that start with a budget target and work backwards end up with a number nobody believes. Groups that start with the inventory end up with a number nobody argues with, because every line in it points at something real in a rack or on a wall. When a CFO challenges a line, the answer is an asset with an age and a support date, not an opinion.

Audit every asset, age, support status and dependency, on site rather than from paperwork. This is where inherited surprises surface: the unmanaged switch behind the bar, the server nobody dares to reboot. Documentation and reality drift apart in every hotel, and the gap between them is where budget surprises live. Walking the building closes it.

Plot replacement windows per asset class, three years out, aligned with renovations, openings and season. Every window has a cost estimate attached, so nothing on the roadmap arrives without a price. The estimates hold because the same team designs and delivers: the people planning the window are the people who will stand in the cabinet doing the work.

Translate the roadmap into one agreed periodic amount that covers lifecycle, maintenance and support. Finance gets a number it can plan on. The operation gets replacements it never has to fight for. And because the number traces back to the inventory, every euro in the hotel IT budget can be pointed at the asset it maintains or replaces.

Annually: roll the horizon forward, absorb what changed in the portfolio, retire what was completed and renegotiate where the market moved. The review takes an afternoon, not a quarter. It is also the moment the CFO sees the roadmap prove itself: last year’s plan next to last year’s actuals, variance explained line by line.

The first year does the heavy lifting. After that, the review is a routine, not a project. The inventory is built once and then maintained. The roadmap is drafted once and then rolled forward. The cost of planning falls every year, while the cost of not planning stays exactly where it was.

Groups sometimes ask whether the effort pays off for smaller portfolios. It pays off faster. A group of three hotels has no slack to absorb an unplanned server replacement in August. The smaller the operation, the more a surprise hurts, and the more one predictable number is worth.

Chapter 05

A short budget conversation is a sign of a healthy IT estate.

There is a simple test for whether lifecycle planning is working: listen to the annual IT budget meeting. In the surprise model, the meeting is long, defensive and backward looking. Someone explains last year’s overruns. Someone questions invoices. Nobody talks about next year until the recriminations are done.

In the roadmap model, the numbers were agreed long ago and have held. The meeting moves to real questions in minutes: should the group pull the WiFi upgrade forward ahead of a strong summer, should the next renovation carry the new door locks, is it time to raise the security baseline across all properties. Those are business decisions, informed by an IT roadmap, taken with time to spare.

When the roadmap works, the annual IT conversation stops being about surprises and starts being about choices: which improvements to pull forward, which standards to raise. That is IT as a strategic asset instead of a recurring incident. Read what unplanned failure costs in the true cost of hotel IT downtime, and which new technology deserves a place on the roadmap in which hotel tech deserves budget in 2027.