Beyond Budget Season: How Guest Intelligence Can Shape Hotel Technology Investment

Technology projects are competing with renovations, staffing, and other priorities for investment.

These financial disciplines remain essential. However, they provide an incomplete foundation for some of the most consequential decisions hotels need to make. Hotels now have far more evidence about how their businesses actually operate, from guest feedback and staff insights to operational and financial data. Bringing those signals together can make hotel budget planning more closely reflect the capabilities the business needs to build, improve, or protect.

Takeaways

Treat the annual budget as part of a multi-year business plan. 

Use guest and staff feedback diagnostically.

Connect experience, operations, technology, and financial impact. 

Use positive feedback when evaluating cuts. 

Define success before investing. 

Why technology challenges the traditional budget cycle

Technology makes the limitations of annual planning particularly visible. A PMS migration, network overhaul, data strategy, or guest experience platform rarely creates value within one department. Nor does technology capability develop neatly within a 12-month financial cycle.

A decision made today may depend on infrastructure installed several years earlier. It may also enable systems and processes that will not be introduced until later. Therefore, assessing technology primarily through individual annual budget lines can obscure the larger capability the hotel is trying to build.

To explore this issue further, Shiji Insights brought hospitality technology strategist Mark Fancourt into the discussion. We initially wanted his perspective on how guest feedback and operational evidence should influence technology investment. Mark challenged a more fundamental assumption: whether hotels should think of the exercise as “budgeting” in the first place.

Mistake number one in this conversation is referring to the process as ‘budgeting.’ Budgeting is a crude, outdated financial numbers exercise that is completely inadequate for how hospitality enterprises must run in 2026. The macro process is Business Planning, the strategic determination of where the business is going, how it will improve, and how capital is allocated to build long-term capability.

That distinction changes the starting point. Rather than asking what technology the hotel can afford during the next financial year, leaders first need to consider where the business is going and which capabilities will be required to get there.

For technology, that perspective is particularly important. Infrastructure, platforms, integrations, data capabilities, and guest-facing systems develop over several years. The annual budget still matters, but it becomes one funding cycle within a much longer business and technology roadmap.

Technology planning starts with the business, not the budget

Mark’s argument does not diminish the importance of financial planning. Hotels still need forecasts, spending controls and accountability for capital.

Instead, he argues that those numbers should emerge from a broader business plan.

In previous technology leadership roles, Mark saw technology plans developed alongside the organization’s brand, vision, mission, five-year strategy, business goals and annual objectives. Technology initiatives were connected to defined organizational outcomes. Those outcomes, in turn, linked back through business-unit and corporate plans.

Nothing was executed in isolation.

That is very different from departments compiling separate technology requests during an annual budget cycle.

A Front Office platform can affect reservations, payments, housekeeping, and the guest journey. An F&B system can touch loyalty, guest profiles, payments and financial reporting. Network infrastructure sits beneath almost everything.

When these investments are considered only through departmental budgets, each decision may make sense locally. Collectively, however, they can create duplication, integration problems and an increasingly fragmented technology estate.

Mark therefore argues for treating technology as an enterprise capability. The commercial structure, CAPEX, OPEX or SaaS, is secondary to a more important question: what capability does the organization gain from the investment?

The timeframe matters too.

Building technology capability is a multi-year roadmap exercise; it is not a 365-day matter.

This is particularly relevant when hotels are modernizing legacy environments. A network upgrade completed today might enable mobile operations tomorrow. Better integrations may later support more useful guest profiles. Improved data architecture can eventually make AI-driven analysis more practical.

The individual investments occur at different times. The capability develops across all of them.

That suggests a different starting question for annual planning: what part of the organization’s longer-term capability roadmap needs to be funded next?

Guest feedback can reveal where capability is breaking down

Once planning begins with business capability, management needs evidence showing where those capabilities are working and where they are not.

Guest feedback provides one important source.

Reviews, surveys and direct interactions can reveal recurring friction around Wi-Fi, reservations, check-in, housekeeping, F&B and service delivery. At sufficient scale, technology can turn thousands of individual comments into patterns around specific parts of the experience.

Yet there is an important limitation.

A guest can usually describe what went wrong. They cannot necessarily identify why.

A complaint about slow check-in, for example, tells management that the experience failed. It does not reveal whether the cause was staffing, training, payment processing, PMS performance, hardware, network connectivity, or process design.

That is why Mark places guest feedback at the beginning of a diagnostic process rather than at the end of an investment decision.

He also deliberately includes staff feedback.

Guests experience the outcome of a hotel’s operating model. Employees experience the systems and processes producing it. Looking at one without the other can leave management with only half the picture.

A guest may report that check-in took 15 minutes. A front-desk employee may report that payment processing repeatedly stalled. System data might then reveal intermittent network performance.

Together, those signals create a diagnostic trail.

The implication is important for technology investment: feedback can tell management where to investigate, but it should not automatically tell management what to buy.

From guest experience to financial impact

Mark’s approach can be reduced to a simple sequence:

Guest and staff experience → Organizational process → Business capability → Underpinning technology → Financial impact

Each stage forces a different question.

What did the guest or employee experience?

Which operational process produced that experience?

Does the organization possess the capability to execute that process effectively?

Is technology enabling that capability or restricting it?

And finally, what is the business consequence?

Mark explains the connection this way:

Incoming feedback must be evaluated against the specific business process it is meant to support. Management must assess whether the underlying technology asset is adequately supporting or actively hindering that process, and then quantify the micro-level financial impact, such as lost revenue, diminished yield, or customer churn resulting directly from service failures.

That final step matters.

Hotels can collect enormous quantities of guest feedback without necessarily making better investment decisions. The value emerges when experience data is connected with operational and financial evidence.

Consider service response times.

Guest sentiment may reveal growing frustration with responsiveness. Operational data can establish how long requests actually take. Staff feedback can identify workflow bottlenecks. Management can then investigate consequences such as compensation, productivity, repeat behavior, or revenue.

The business case becomes more precise.

It is no longer: guests are complaining, therefore we need new software.

It becomes: a recurring experience problem has been identified; the affected process has been examined; a capability gap has been established; and its operational or financial consequences justify intervention.

Technology may be that intervention. It may not.

Sometimes the right investment is beneath the problem

This diagnostic discipline matters because hotels can easily misinterpret operational friction.

Imagine several issues appearing at once. Front Office reports unreliable applications. F&B experiences connectivity problems. Staff devices disconnect. Guests complain about Wi-Fi.

If each problem enters the planning process through its respective department, the hotel could end up considering several separate technology purchases.

Mark points to under-provisioned core network and hardware infrastructure as an example of what might actually sit beneath those symptoms.

Management frequently misdiagnoses operational friction as isolated departmental issues. Tracking systemic technical failures across the entire enterprise often exposes a deeper root cause: under-provisioned core network and hardware infrastructure. Correcting foundational infrastructure, rather than buying piecemeal software applications, delivers a macro- and micro-level turnaround in enterprise reliability, staff enablement, and customer experience.

This distinction matters because the most valuable technology investment may be almost invisible to the guest.

Few guests will praise network architecture in a review. Yet they experience its consequences when Wi-Fi works, payments process quickly, staff applications remain available, and connected services function as expected.

The same principle can apply elsewhere. Integration architecture, hardware, identity management, and data quality may all sit beneath more visible experience problems.

Adding another application can sometimes make those environments more complex without resolving the underlying constraint.

So the investment conversation should start with the capability gap, not the product catalog.

Rethinking what ROI means for hotel technology

This also complicates the traditional ROI discussion.

Every technology investment should be financially accountable. However, not every investment creates value through the same mechanism.

A revenue-management capability may reasonably be evaluated against revenue or yield. Automation may be measured through processing time and labor productivity. Guest-facing technology could be assessed against adoption, conversion, or service outcomes.

Foundational infrastructure is different.

A network exists partly so dozens of other business processes can function reliably. Calculating its value with the same formula used for a revenue-generating application can therefore produce an artificial comparison.

Mark argues that hotels should examine the capability created instead.

Most modern hotel tech represents foundational infrastructure required simply to execute hospitality. Instead of forcing arbitrary payback metrics onto essential tools, evaluate spend through the lens of business capability: does a tool enable or restrict organizational execution?

That does not mean abandoning ROI.

It means defining the return according to the problem being solved.

For infrastructure, management might examine uptime, failure rates, and the performance of dependent systems. Automation investments could instead be measured through labor hours or processing time. Meanwhile, guest-experience technology might require measures such as response times, conversion, satisfaction with a particular process or reduced service recovery.

The stronger investment case therefore connects strategy, capability, intervention and outcome.

It also avoids manufacturing an attractive ROI figure simply because a capital approval process demands one.

Guest intelligence can identify what not to cut

Another side of business planning receives less attention: deciding where not to reduce expenditure.

Guest feedback can be particularly useful here.

Management teams naturally focus on negative sentiment. Problems demand attention, while consistently positive experiences can easily disappear into an aggregate satisfaction score.

Yet positive feedback contains operational information too.

Suppose breakfast repeatedly emerges as one of a property’s strongest guest experience attributes. Finance identifies an opportunity to reduce food costs or staffing. On the P&L, the savings look attractive.

Guest intelligence introduces another question: what exactly is creating that positive sentiment, and what happens if the hotel changes it?

Mark sees positive feedback as empirical evidence that the product, service, processes, and supporting capabilities in an area are aligned well enough to create customer value.

That should change the conversation around cuts.

When something is working particularly well, management first needs to understand why. The objective is not to make high-performing areas immune from scrutiny. It is to recognize that reducing their resources may carry an experience cost that the initial financial calculation misses.

This gives hotels two useful categories during planning.

Improvement priorities are areas where evidence indicates that a capability needs attention.

Protection priorities are areas where evidence indicates that an existing capability is creating value.

The second category helps expose potential false economies.

A cheaper amenity, reduced staffing level, or deferred system investment can improve one financial line while weakening an experience guests disproportionately value.

Guest intelligence cannot predict the commercial consequence with certainty. However, it can tell management that the proposed saving carries a risk worth investigating.

AI is a capability, not a budget category

No technology planning discussion for the year ahead can avoid AI.

However, the current enthusiasm creates another opportunity to start with the technology rather than the business requirement.

A hotel may decide it needs an AI strategy. A department identifies an AI product. Funding is requested. Only later does the organization establish what measurable business problem the technology is expected to solve.

Mark argues for reversing that sequence.

For him, AI is not a separate category of technology. It is an evolutionary layer of software capability that will increasingly become embedded within enterprise platforms or layered over legacy environments while those systems evolve.

Guest intelligence illustrates the point well.

Hotels already generate enormous volumes of unstructured information through reviews, surveys, guest messages, and service interactions. AI can accelerate the classification and synthesis of those signals. It can help management identify patterns that would be difficult to detect manually across thousands of interactions.

However, an inability to make sense of operational data is not necessarily a new AI problem.

It may expose an older technology capability gap.

As Mark puts it:

Struggling with massive volumes of unstructured, unanalyzed guest and operational data simply exposes a pre-existing technology capability gap. Running a modern hotel without data synthesis capabilities is an operational vulnerability that should have been solved long before AI.

This is a useful warning for planning teams.

AI can accelerate analysis, but it cannot indefinitely compensate for fragmented systems, poor data quality, or weak processes. Nor does it replace direct engagement with guests and staff.

The better planning question is therefore not “Where can we use AI?”

It is “What capability does the business need, and where can AI strengthen it?”

That keeps the investment tied to an operational outcome.

Measurement should begin before the investment

Perhaps the most important part of this approach comes after the technology has been approved.

Hotels can spend months developing a business case, selecting a vendor, and implementing a system. Once the project goes live, attention moves to the next priority.

That makes it difficult to establish whether the original problem was actually solved.

Guest and staff intelligence can close that loop, but only if management defines the relevant measures early enough.

If slow check-in helped justify an investment, the hotel needs a baseline for check-in before implementation. That might include queue time, transaction time, payment failures, guest sentiment about arrival, and staff feedback about the process.

The same measures can then be examined after implementation.

For service requests, the relevant indicators may include response time, fulfillment time, employee workflow, and guest perceptions of responsiveness.

For connectivity, hotels might compare network reliability with Wi-Fi-related guest sentiment and service complaints.

The metrics differ because the problems differ.

What does not change is the need for specificity.

Mark is particularly critical of using broad satisfaction ratings to evaluate targeted technology interventions.

Because every technology investment underpins specific business processes, the expected improvements in guest or staff experience must be clearly defined from the start. Shallow star ratings offer zero actionable insight. Post-implementation evaluation requires gathering granular feedback on micro-processes to verify whether supporting tech tools are performing as intended.

That gives the planning process a natural endpoint.

The hotel begins with evidence of a problem and identifies the process involved. From there, management diagnoses the capability gap and funds an appropriate intervention. Once implemented, the same process is measured again to determine whether performance has improved.

In other words:

Evidence → Diagnosis → Investment → Measurement → Learning

And then the cycle begins again.

From budget season to continuous business planning

There will still be a budget.

Hotels need revenue forecasts, cost assumptions, and capital controls. CFOs need accountability. Owners need to understand where money is going. Technology leaders need to demonstrate why an investment matters.

What changes is the thinking that precedes those numbers.

Technology capability develops across multiple years. Guest expectations evolve continuously. Employees encounter operational friction every day. Meanwhile, hotel systems generate evidence about what is happening and what it costs.

Bringing those signals together makes hotel budget planning considerably more useful.

A guest complaint is no longer simply something for the reputation team to answer. It can be the first signal of a process or capability problem.

A positive review is not merely a marketing asset. It can reveal an experience the business should be careful not to undermine.

A technology proposal is not justified because a department wants another tool. It should connect a strategic objective with a capability the organization needs.

And AI is not automatically another line on next year’s spreadsheet. It is one possible layer within a much broader technology and business architecture.

This returns us to Mark’s original challenge.

Perhaps “budget season” is too narrow a description for what hotel leaders should actually be doing.

The more valuable question is not simply: how much can we afford to spend next year?

It is what capabilities the business needs to build, what it needs to protect, and what the evidence tells us should come first.

Ready for 2027? Download the scorecard and validate your budget priorities here.