Pod-Ed: Inside Breeze Airways’ Technology, Distribution, and Growth Strategy

NEW YORK — In Season 10, Episode 6 of The Airways Podcast, hosts Rohan Anand and Vinay Bhaskara welcome Austin Speaker back to the program a decade after he joined its first recording. Speaker, Breeze Airways’ (MX) Manager of Interline and PSS Strategy, traces his path from Southwest Airlines (WN) through JSX and into Breeze while explaining how technology decisions reach far beyond an airline’s IT department.

The conversation becomes a case study in how a young carrier adapts after launch. Breeze began with a direct-booking, leisure-oriented proposition. Speaker describes an airline that has since added outside distribution, pursued business travelers where its schedule supports them, expanded across secondary and tertiary markets, and moved toward an all-Airbus A220 fleet. His comments reflect an employee’s operational perspective; Breeze remains privately held, and the episode does not provide an independent financial assessment.

1. Airline technology is strategy

Speaker and Anand begin with passenger service systems (PSS), the infrastructure behind reservations, inventory, check-in, ticketing, and connections with other sales channels. The subject can sound removed from route planning or passenger experience, but their argument is the opposite: legacy platforms and the interfaces built around them can determine what an airline is able to sell and operate.

Speaker saw that relationship at Southwest, where he worked during the carrier’s long reservation-system transition, and again at JSX, where he helped move the operator from Radixx to Navitaire New Skies. He notes that a migration is not merely a software replacement. An airline must carry years of business rules, operating practices, and customer expectations into the new environment, then live with the choices made during the transition.

The discussion also explains why airline systems rarely fit into a clean old-versus-new divide. Carriers may replace one function at a time while retaining legacy translation layers underneath. Distribution, operations, seating, ticketing, and departure control can move on different schedules. The visible passenger product may change quickly; the underlying architecture often does not.

2. Breeze moves beyond direct sales

Breeze was not built around corporate travel or broad third-party distribution, Speaker says. Its earliest assumption was that bookings would come through the airline’s website, mobile app, and contact center. Staff travel became the first exception because interline employee benefits required an outside platform and agreements with other carriers.

More exceptions followed. Breeze added online travel agencies, travel management companies, New Distribution Capability (NDC) connections, and global distribution systems (GDS). In the episode, Speaker estimates that indirect channels now account for between 10% and 15% of Breeze bookings. He presents that growth as incremental business rather than a replacement for lower-cost direct sales.

Breeze’s published distribution documentation distinguishes API-based sales, including NDC, from legacy GDS and interline channels. Speaker argues that modern retailing through NDC offers more flexibility, but many corporations, agencies, and government customers still depend on traditional GDS access. For Breeze, distribution strategy means meeting those customers where they book while trying to move partners toward newer connections over time.

3. Business traffic follows schedule utility

Distribution alone does not make an airline useful to corporate travelers. Many Breeze routes operate fewer than seven days a week, and the carrier continues to design much of its network around leisure and visiting-friends-and-relatives demand. Speaker says business traffic becomes viable as Breeze adds frequency and offers flights at times that suit a work trip.

That opportunity is market-specific. A leisure route to Cancún (CUN) does not need to carry a large corporate component, but Speaker points to Hartford (BDL)–Raleigh-Durham (RDU) as the kind of city pair that can serve both business and leisure demand. Breeze has developed its BreezeCorp products for those travelers without making corporate traffic the sole basis of its network decisions.

The distinction matters because airline sales channels and schedules have to reinforce each other. A carrier can appear in a corporate booking tool, but it will not win the booking if its frequency, timing, or route is impractical. Breeze’s gradual entry into managed travel therefore follows the growth of the network rather than preceding it.

4. The route map is built around selective competition

At the time of the conversation, Speaker says Breeze served 91 destinations across six countries and one territory, including airports in 35 U.S. states. Across a full year, he counts 350 nonstop city pairs, along with 89 direct city pairs that include an intermediate stop. He adds that some markets receive both nonstop and one-stop direct service on different days.

Those distinctions reveal how Breeze creates schedule breadth with a limited fleet. A market may receive two nonstop flights and two one-stop direct flights in a week, giving travelers four days of service without requiring daily nonstop capacity. The pattern is more complex than a conventional hub-and-spoke timetable, but it lets the airline connect many city pairs while adjusting capacity to demand.

Speaker describes the network as heavily weighted toward the eastern United States and toward secondary or tertiary markets. Summer flying becomes more east-west, while winter flying shifts strongly north-south. Some stations operate only seasonally. That flexibility is intentional: he argues that a young airline cannot maintain weak flying simply for the appearance of network permanence.

The same reasoning explains why Breeze is cautious about crowded airports and established battlegrounds. Speaker points to the Pacific Northwest as a region employees often ask about, but notes that its largest markets already have substantial service. For Breeze, an unserved or underserved route can offer a better use of aircraft than joining a fight built around incumbent scale.

5. Scale is a condition for durability

The episode’s central business argument is blunt: a jet airline needs economies of scale. Speaker says Breeze was never expected to remain in its launch-era form. Growth and adaptation were necessary to spread fixed costs, deepen the schedule, and give individual commercial functions enough volume to mature.

At the time of recording, Speaker counted 56 A220s in operation, plus two remaining Embraer E190s. He said the E190 schedule was due to end on Labor Day, a change that would leave Breeze with an all-A220 operating fleet if completed as planned. The newer fleet is not entirely uniform, however. Speaker says two secondhand A220s from EgyptAir retain cabin differences from Breeze’s other aircraft, including a different aft-galley and lavatory arrangement.

Speaker also put Breeze’s workforce at about 3,250 people. In his telling, that lean structure requires employees outside tightly defined operational roles to cover several responsibilities. As the airline grows, individual teams can specialize, but the broader lesson remains: fleet size, staffing, distribution, and schedule depth have to advance together.

Pod-Ed analysis: Breeze’s model depends on adaptation

The episode’s most revealing theme is how often Breeze has departed from its original assumptions without abandoning its core proposition. The airline remains predominantly direct but now uses intermediaries to reach customers it would otherwise miss. Its push into corporate travel is limited to markets where timing and frequency create a credible product, while its seasonal network favors opportunities outside the largest hubs.

That flexibility comes with tradeoffs. Less-than-daily service limits convenience. A distributed network is harder to explain and sell than a simple hub map. Third-party distribution adds cost and technical complexity. Rapid fleet and route growth also requires an organization capable of supporting more aircraft, more stations, and more commercial relationships without losing cost discipline.

Speaker’s account suggests that Breeze treats those tensions as design constraints. Its technology choices have to accommodate partnerships and real demand, while the network remains willing to move aircraft between seasons and markets. The A220 supplies the physical platform. Durability will depend on whether the commercial and operational organization can keep pace.

The Airways Podcast is hosted by aviation analysts Rohan Anand and Vinay Bhaskara and produced by Helwing Villamizar. The episode is available through the Airways Substack. The previous Pod-Ed examined SAS, easyJet, and American Airlines.