Our Take
Omio's move is discipline, not hype: the company is forcing architectural choices, not adding a chatbot to existing work.
Why it matters
Most companies retrofit AI into outdated processes and call it progress. Omio's requirement that teams redesign end-to-end signals a structural shift in how large-scale operations think about AI integration.
Do this week
CTO or VP Engineering: audit your top three product workflows this week and identify which ones still optimize for pre-AI bottlenecks so you can prioritize redesign, not plugin.
Omio embeds OpenAI across engineering to accelerate product velocity
Omio, a multimodal travel platform that coordinates operations with over 3,000 transportation providers across 47 countries, has integrated OpenAI models across its engineering operations to accelerate travel product development and launch booking interfaces.
The integration spans internal functions across the company. Critically, the company's approach rejects the superficial addition of technology to outdated processes. According to the company, CTO Tomas Vocetka requires all internal functions to completely redesign their workflows around AI models, rather than layering models onto existing systems.
Process redesign, not feature bolting
The distinction between Omio's approach and typical AI adoption is material. Most enterprise deployments treat AI as a tool that fits into existing workflows. A team that managed travel bookings one way before now uses a model to speed part of that work. The underlying process remains unchanged.
Omio's mandate is different: redesign the entire function around what the model can do. This shifts the burden from "how do we add AI to what we do" to "what should we do now that we have this capability." That distinction determines whether AI saves time within old constraints or eliminates constraints entirely.
For a company coordinating thousands of providers across dozens of countries, that delta compounds. Booking interfaces, operational handoffs, provider communication loops, and internal approval chains all become candidates for reimagining, not patching.
The redesign mandate is rare and difficult
Vocetka's requirement that "all internal functions" redesign around AI is operationally expensive. Teams resist. Legacy systems have dependencies. Customers have expectations built on old workflows. The short-term friction is real.
But the precedent matters: a CTO is publicly stating that bolt-on integration is not acceptable. That is a signal to other engineering leaders that half-measures should not pass as strategy. If Omio's velocity gains materialize and are attributed to this discipline, others will follow.
For now, the company's decision remains internal. No independent benchmarks confirm that this approach ships features faster than competitors. The claim rests on operational discipline, not yet on published outcomes. Teams that adopt similar redesign-first principles should measure and share results within 6 months so the field can separate discipline from theory.