Most companies are somewhere on the AI adoption curve. But very few have actually mapped out where they are—or where they’re going.
The conversation around AI is loud, crowded, and often useless. People speak of tools, models, and features, but rarely of choices. 

To move past the hype, you need a framework that clarifies what kind of work you’re actually doing when you “do AI.”
You’re less interested in talking about models and features, and more interested in clarifying the tradeoffs organizations are making when they decide where—and how—to apply AI.

Here’s a simple one: two axes, four quadrants.

Build vs. Buy: Are you developing proprietary capabilities tied to your guest data and tech stack, or licensing someone else’s?
Are you developing proprietary capabilities, or licensing someone else’s?

Internal vs. External: Is the AI serving your internal teams (revenue, marketing, operations, front desk), or your guests and partners?Is the AI serving your team, or your customers?
When you plot these against each other, the abstract idea of “AI adoption” resolves into four distinct strategies for hospitality organizations.

Productivity (Buy + Internal)

This is the entry point.

You’ve rolled out ChatGPT, Claude, or Copilot licenses. The team is using AI to summarize revenue meetings, draft marketing emails and analyze guest feedback.

The goal is efficiency. This work matters. It lowers friction across departments, builds AI literacy at property and corporate levels, and helps individuals move faster. The gains may show up as cost savings, increased output, or faster iteration.

But productivity optimizes individual effort. It doesn’t, by itself, change what your hotel group or platform is capable of delivering to guests.

It’s also a commodity. Your competitors are doing the exact same thing.

Internal Tooling (Build + Internal)

This is where AI starts to act as a multiplier across the hospitality ecosystem.

Instead of generic tools, you’re building systems connected to guest data, property management systems, CRM, CDP, and operational workflows:: RAG pipelines over internal documentation, automations that understand business rules, or tools that encode institutional knowledge instead of letting it remain tribal.

The goal is capability.

When internal AI works, your guest and operational data compounds in value—not because it exists, but because your team can actually find it, trust it, and act on it. You aren’t just working faster; you’re working with full organizational context.

This is higher investment work, but the returns compound quietly and persistently across properties and portfolios.

Service (Buy + External)

This quadrant is the front line.

You’re deploying vendor-provided AI to interact with guests: booking assistants, chatbots, virtual concierges, AI-powered contact centers. You didn’t build the engine, but you’re responsible for the guest experience it delivers.

The goal is scale.

Service AI can provide 24/7 guest engagement across time zones without a 24/7 headcount. It can handle pre-arrival questions, upsell room upgrades, assist with on-property requests, and deflect repetitive inquiries from the front desk. But it comes with real responsibility. When the AI gets something wrong, it’s still your brand doing the talking. Alignment, guardrails, and escalation paths matter more here than most teams expect.

Product (Build + External)

This is where AI becomes strategic.
Some organizations approach this as “AI features,” but the more durable shift is enablement.

Building AI into your guest-facing products is one path; making your platform AI-ready for partners, owners, and third-party systems is another.
Clean APIs. Structured, unified guest data. Real-time event streams from PMS, CRS, POS, and ancillary systems that make sense to machines, not just humans.

The goal here is growth.

Not every AI feature is a moat. Most aren’t. The differentiation comes from making your platform a foundation intelligence can attach to—internally, externally, and at scale.

The Shift: From Efficiency to Leverage

Most hospitality organizations today are camped in the Productivity quadrant. That’s normal. It’s accessible, mostly safe, and a good place to build confidence.
But productivity is about efficiency.

The other three quadrants are about leverage.

Efficiency helps you do the same work better.
Leverage means you’re not just faster—you’re delivering more personalized stays, smarter pricing decisions, and more consistent service across every property.

As teams get comfortable and guest data becomes cleaner and more unified, the central question shifts from:“How can this help you write an email?”to“How can you make your entire hospitality organization—and every guest interaction—legible to AI?”

The Grid Shapes the Work

The grid doesn’t tell you where you should be. Every hotel group, brand, and tech platform needs a different mix. But it does make the implications of your choices visible.

If you’re moving toward Internal Tooling, the work is legibility: documentation, internal APIs, unified guest profiles, and systems designed so machines can reason across reservations, stays, preferences, and revenue data.

If you’re moving toward Service, the work is alignment: vendor evaluation, brand safety, data privacy, and operational guardrails that protect the guest experience.

If you’re moving toward Product, the work is differentiation: understanding what owners, operators, and guests need AI to do that only you can provide—and designing your platforms so intelligence can actually integrate across the hospitality stack.

The mistake isn’t starting in Productivity.

The mistake is stopping there—and mistaking operational efficiency for a long-term guest experience and revenue strategy.