
Starbucks is building AI-powered replacements for enterprise software it currently buys from Microsoft and IBM, a move that challenges the decades-old logic that large companies should outsource software rather than build in-house. The news signals that AI-assisted development has made internal tool-building fast and feasible enough to compete with vendor platforms, reshaping how Fortune 500 companies approach technology spending and threatening application software vendors while benefiting infrastructure providers.
Summaries like this, in your inbox every morning.
Sign up free →What happened
Starbucks is building AI-assisted replacements for a Microsoft inventory-tracking system and an IBM maintenance platform, with some tools potentially rolling out by the end of next year. The company spends roughly $400 million(約640億円) annually on software and is reviewing every contract as part of a broader $2 billion(約3200億円) cost reduction effort under CEO Brian Niccol.
Why it matters
For decades, large enterprises stayed locked into vendor platforms because building software in-house was slow and expensive. AI-assisted development is changing that math—if engineers already customize a vendor's product heavily to fit their needs, they can now build a purpose-built tool in a fraction of the time. This signals a broader shift in Fortune 500 technology budgets toward build-versus-buy recalculation, potentially threatening application-layer vendors like ServiceNow and Salesforce while benefiting infrastructure providers like Microsoft Azure.
What to watch
The market reacted immediately—IBM fell about 3% in premarket trading, ServiceNow dropped 3.5%, and Salesforce slid 4%. Microsoft barely moved because it sells both the system being replaced and the Azure cloud infrastructure that will power the replacement. Watch whether other enterprises follow Starbucks' playbook on their most expensive, least-fitting legacy systems.
Starbucks' move reflects a fundamental shift in how large enterprises evaluate the cost-benefit of commercial software. For two decades, the story that propped up enterprise software valuations was simple: building is too hard, so companies buy. But that story breaks when AI lets in-house teams prototype and deploy faster than before. The coffee giant is not walking away from third-party vendors entirely—it still relies on Microsoft's cloud and AI infrastructure—but it is reclaiming ownership of the application layer where customization demands have always been highest and vendor fit worst.
Critically, the article notes that Starbucks learned this lesson the hard way. Earlier this year, it deployed an AI-powered inventory counting system that produced inaccurate counts and had to revert to manual tallies. That failure actually strengthens the credibility of the current move, because Starbucks is now approaching the problem differently: fix the underlying workflow first, then build the system around the corrected process, then let AI accelerate the work. This sequence—data consolidation, process redesign, then AI—stands in contrast to simply layering AI onto a broken process, which amplifies problems while core capability quietly erodes.
The ripple effects the body anticipates are significant. Vendors will reposition from application sellers to infrastructure and trust providers. A new services economy will form around process mapping, data consolidation, and system design for companies taking ownership back. And further out, once agents sit on consolidated systems with enough historical data, they may stop waiting for instructions and start auto-completing repetitive tasks—raising the question of who owns the data those agents run on. For Starbucks and others willing to do the unglamorous process work first, owning operations becomes possible again.
No comments yet. Be the first to share your thoughts!
Log in to join the discussion





Get curated AI news from 200+ sources delivered daily to your inbox. Free to use.
Get Started FreeFree · takes 30 seconds · unsubscribe anytime
1 minute a day. The AI essentials.
200+ sources · Email / LINE / Slack