# AI and the Build-versus-Buy Decision in Platform Engineering

DevFeed: [AI and the Build-versus-Buy Decision in Platform Engineering](<https://devfeed.tech/articles/just-because-we-can-build-it-should-we-19735.md>)

Original publisher: [Read original article](<https://medium.com/expedia-group-tech/just-because-we-can-build-it-should-we-a292fbdd22ce?source=rss----38998a53046f---4>)

Author: Rick Fast

Published: 2026-05-05T11:01:02Z

Content type: opinion

Language: en

Sources: [Expedia](<https://devfeed.tech/sources/expedia.md>)

Topics: [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Software as a service](<https://devfeed.tech/topics/saas.md>)

Tags: [agentic-coding](<https://devfeed.tech/tags/agentic-coding.md>), [ai](<https://devfeed.tech/tags/ai.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [engineering-leadership](<https://devfeed.tech/tags/engineering-leadership.md>), [platform](<https://devfeed.tech/tags/platform.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [saas](<https://devfeed.tech/tags/saas.md>), [scale](<https://devfeed.tech/tags/scale.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

## AI overview

This commentary examines how agentic coding tools and AI-native workflows have changed the economics of building software for platform engineering teams. It argues that lower initial build costs do not eliminate the ongoing costs of ownership, including maintenance, compliance, operational tooling, UX work, and long-tail requirements. The article supports selectively replacing low-value, undifferentiated SaaS products while maintaining discipline about build-versus-buy decisions.

## Source excerpt

Expedia Group Technology -- PlatformHow AI changed the build vs. buy equation, and why discipline matters more than everPhoto by Ali Kazal on Unsplash Agentic coding tools and AI-native workflows have changed what's possible for platform engineering teams. I lead Platform Engineering at Expedia Group™, one of the world's largest travel technology companies. We power brands like Expedia®, Hotels.com®, Vrbo®, Orbitz®, and Travelocity®. My organization builds the technology that all of these brands and their partners run on: APIs, data and AI services, developer tools, CI/CD infrastructure, and the shared capabilities that let thousands of engineers ship reliably at scale. For many greenfield problems, it now feels like we can build almost anything from scratch with a fraction of the effort it used to take. But that creates a harder question: just because we can build it, should we? The temptation is real When you lead a platform organization and your engineers suddenly have access to powerful agentic coding assistants, the possibilities open up fast. It's tempting to look at SaaS products your company is paying for and think, "We could build that in a weekend." And honestly? In many cases, you probably could stand something up quickly. The initial build cost has dropped through the floor. But building something and owning something are very different decisions. That's where the new calculus gets interesting. The hidden cost of owning software Vendors aren't just shipping features. They're maintaining the software, fixing bugs and edge cases you haven't thought about yet, and improving the UX across thousands of customers with different requirements. Mature platforms have decades of accumulated work behind them: production hardening, compliance, operational tooling, and long-tail requirements you'd only discover slowly through real-world use. You can't clone that maturity quickly, even if the initial build feels cheap thanks to AI. The build side of the equation has cha