Where the Innovation Actually Comes From
If you’ve spent any time inside the hospitality industry, or adjacent to it watching from the technology side, you’ve probably developed a working theory about where innovation comes from. Outsiders, most people say. Founders who looked at the industry from a distance and saw problems that operators, buried in operations, couldn’t see clearly enough to solve. That theory is partially right. It’s also incomplete in ways that matter.
The actual pattern is more specific than “outsiders,” and more revealing.
The first source is the operator who left. Not the person who observed the industry from the outside — the person who worked inside it long enough to understand it deeply, then had to leave entirely before they could build anything. Matthijs Welle spent eight years at Hilton, moving from management trainee through front office manager to cluster director of sales for Eastern Europe and Russia. He understood, from the inside, what was wrong with the systems that ran hotel operations. He understood it the way someone understands a recurring headache — not as an abstraction, but as something felt daily, at seven in the morning, on a sold-out Saturday. What he couldn’t do, while running those operations, was build anything to fix it. So he left. He and Richard Valtr, who had grown up in his family’s hotel business and later built a boutique property in Prague, founded Mews. The company is now valued at over a billion dollars and serves properties in eighty-five countries.
Marco Benvenuti ran revenue management for roughly twenty-five thousand rooms at Wynn Las Vegas before leaving to co-found Duetto. He has said, with a candor that might surprise people who don’t know the industry: “Leave the hotel as fast as you can. There’s really no innovation going on there.” It sounds harsh. It isn’t, really. What he’s describing is not a judgment about the people — it’s a description of the structural conditions. The hotel is optimized, at great cost and over a long time, for one thing: running. That optimization leaves almost no room for building something new. The people who build leave not because the industry failed them, but because the industry’s economics demand a complete focus that leaves no oxygen for anything else.
The second source is the enterprise chain — and this is where the scale problem becomes visible in a different way. Marriott committed more than a billion dollars to technology in 2024. The company operates an innovation lab beneath its Bethesda headquarters, a ten-thousand-square-foot space with full-scale model hotel rooms where new ideas can be tested before they reach actual guests. Hilton’s Connected Room program has processed tens of millions of digital check-ins; at peak, a Hilton door was being unlocked via smartphone roughly every second and a half. These are not the technology budgets of an industry that doesn’t understand the value of innovation. They’re the technology budgets of companies large enough to fund it — which is a different thing entirely.
The independent operator who runs two hundred rooms has no equivalent. That operator’s technology allocation, after the percentage that goes to maintaining systems already in place, may not be large enough to pilot a new solution at meaningful scale, absorb the learning costs of implementation, or sustain the disruption of switching something that currently, however imperfectly, works. Enterprise chains aren’t faster because they’re smarter. They’re faster because they can afford to move.
The third source arrived uninvited. Online travel agencies didn’t enter the hospitality industry through a front door — there wasn’t one. They entered through distribution, captured the guest relationship, and then moved steadily inward. Expedia took a majority stake in ALICE, a back-of-house hotel operations platform, not because it was interested in housekeeping workflows, but because it understood that whoever controls the operational layer controls the guest layer. Booking.com built an entire suite of tools for independent hotels — website builders, booking engines, rate intelligence — then discontinued them when the strategy shifted. The suite’s closure stranded hundreds of operators mid-migration. That’s not a cautionary tale about bad actors; it’s an illustration of what happens when innovation in an industry is driven primarily by entities whose core interests are adjacent to, but not identical with, the operators they serve.
The fourth source is the rarest: the founder who happens to have domain knowledge, proximity to capital, and structural freedom at the same time. Look closely at the companies that have scaled meaningfully in hospitality technology and a pattern emerges. The successful operator-founders — Mews, Duetto, and others almost always required a technical co-founder to make the domain knowledge actionable. The purely technical founders, strong engineers who studied the domain, required deep and patient immersion before their products fit. The ones who built fastest were typically people who had lived inside the industry, then stepped outside it long enough to get access to capital and engineering talent, then built back in. They are not common. The conditions that produce them are not common either.
What the pattern reveals is not a shortage of insight. The people closest to hospitality’s problems understand them with a precision that no outside observer fully replicates.
The front desk manager who has watched the same integration fail in the same way for eleven years. The restaurant group’s operations director who has rebuilt the same inventory workflow from scratch at every new location. The events coordinator who has watched the same group booking process collapse under its own friction for the fifteenth consecutive year. The revenue manager who has been manually correcting for a system’s blind spots since the system was installed. That knowledge is real, and it is not being wasted through inattention or lack of ambition.
What’s missing is the conditions under which that knowledge becomes a foundation for building rather than a ceiling on it. The structural freedom to step back from operations long enough to design something new. The proximity to technical talent and capital that makes building possible rather than theoretical. The environment where an operator’s insight can meet a founder’s capacity to act on it before the founder has to learn the industry from scratch and the operator has to leave it entirely.
The industry has not built those conditions in any deliberate way. The conferences exist. The trade publications exist. The vendor expos exist. None of that is the same thing.
What would have to be different — and whether it can be built — is the question the next part of this series tries to answer.
Scott Hill is the Founder and Executive Director of The Proxenia Foundation and the founder of the Proxenia Accelerator programs in Central Florida.
