Key Takeaways

  • United poured hundreds of millions into ditching mainframes for cloud databases during the pandemic despite having zero calculable financial return on day one.
  • United is the only major airline globally that owns its reservation engine, while competitors outsource their core booking flow to Sabre and Apollo.
  • Replacing third-party seatback software from Panasonic allowed United to link in-flight displays directly with passenger apps and map data.
  • Texting travelers a real-time radar map during weather holds produced a 120-point swing in Net Promoter Score, jumping from negative 60 to positive 60.

The Trap of Calculating ROI on Architecture

Most legacy enterprise software stays broken because finance teams demand payback periods on plumbing. If you ask an accountant to calculate the return on retiring a 1980s mainframe, the math stalls. The mainframe runs. The bookings clear. The cost of a ground-up rebuild looks entirely irrational on a quarterly spreadsheet.

Scott Kirby bypassed that logic during the pandemic downturn. United committed hundreds of millions of dollars to strip out ancient databases and move core operations to the cloud.

“We started a several-hundred-million-dollar project to get not just on the cloud, but get everything off of mainframes, to build databases that are modern, that we can access the data just to really modernize our tech stack,” Kirby said. “There was no ROI. There was no payback, which is why companies don't do it.”

When you outsource your core architecture to legacy vendors, you inherit their product velocity. Kirby observed that competitors surrendered their autonomy years ago. “We have more in-house, I think, than any airline in the world,” Kirby noted. “We're the only airline in the world that owns our own reservation system. Everyone else has outsourced Sabre and Apollo.”

Taking Back the Screen from Panasonic

Outsourcing does not just hurt back-office throughput. It ruins the passenger experience at the seat. For years, airlines treated seatback entertainment hardware as a bundled vendor problem. You bought screens from hardware manufacturers like Panasonic, took whatever default moving map software they bundled, and lived with the lag.

Kirby noticed how bad the experience had become by watching passengers ignore their screens. “The seat-back entertainment screens. I didn't actually realize it until I started complaining about the maps. The maps are terrible,” Kirby said. “We're taking over the map software from Panasonic. They're taking over the whole software.”

Taking over seatback software turns a passive screen into an extension of the United mobile app. Instead of a slow map loop designed in 2008, United can push flight connections, personalized gate changes, and live operational updates straight to the headrest.

Information Beats Apologies During Delays

Kirby is blunt about where American carriers stand against international rivals: “The Asian and Middle East carriers do better than the US airlines on product for sure, and probably service too. I think we do a really good job, but they have different cultures for service, so they do better on that. But I think technology is the differentiator.”

Consider how an airline handles delays. For decades, the standard procedure was an automated text message announcing a delay, with zero context. Passengers assume the airline is incompetent or lying, and customer satisfaction plunges.

United tested sending passengers a live radar graphic showing storms blocking the route. The change in passenger reaction was immediate. “The people with a 1-hour delay, I think the numbers were negative 60 NPS on the normal way of sending it, plus 60 when we send a picture of the map,” Kirby said. “A 120-point difference. It wasn't just that they weren't mad. They were actually happy.”

Showing the work removed the suspicion. But sending live radar imagery to tens of thousands of delayed flyers requires data access that rigid legacy databases cannot handle.

What to Do With This

Audit your core customer touchpoints this week and find the vendor screen you gave up on because building it felt unglamorous. If a third-party vendor controls the UI where your customers experience frustration, pull that interface in-house. Replace generic apology emails with the actual internal telemetry explaining why the delay happened.