Leaders Should Stop Buying AI Like Software
AI is not software. It is a strategic dependency, and most boards are procuring it as if it were just another SaaS license.
Avihu Marom · · 5 MIN READ
Leaders Should Stop Buying AI Like Software
Every board I brief right now is obsessed with AI procurement.
They treat it exactly like another SaaS license. They buy the seats, deploy the tool, train the team, and assume they have secured a competitive advantage for the next decade.
This is a critical misread of the operational map.
AI is not software. It is a strategic dependency.
When you buy software, you outsource a static process. When you buy AI, you are outsourcing part of your operational logic. You are renting cognition from a third party.
If you treat artificial intelligence like a standard vendor contract, you are building a massive single point of failure directly into the brain of your organization.
Look at the shockwaves hitting right now. Most of the media is tracking consumer downloads, stock fluctuations, and corporate drama. They are missing the operational reality.
The narrative is focused on which language model is smarter.
The real war is about control, sovereignty, and supply-chain fragility.
Three signals are flashing red
First, Anthropic walked away from the Pentagon fight over terms.
The significance is not only political. It is operational.
A commercial AI company effectively told the U.S. national-security system that access to its cognitive infrastructure would remain conditional. The message was simple: the vendor still decides where the line is.
Think about what that means for any corporate leader.
If a vendor can deny or limit access in one of the most strategically sensitive environments in the world, then you are not buying a stable capability. You are entering a conditional relationship with an actor whose incentives are not the same as yours.
They do not optimize for your earnings, your response time, or your continuity of operations. They optimize for their own policy, exposure, and alignment choices.
That means your “AI stack” may be far less yours than you think.
Second, the compute layer remains a choke point.
Your AI vendor is not a standalone capability. It sits on top of a deeper chain of dependencies: cloud infrastructure, model providers, hardware suppliers, and geopolitical constraints you do not see from the dashboard.
The point is not just that the ecosystem is concentrated. The point is that most enterprises are consuming intelligence capability through several opaque layers of infrastructure they do not control.
When the next shock hits, whether it is an export-control change, a supply-chain squeeze, or a geopolitical disruption around chips, your vendor will prioritize its own survival and its largest clients.
You will not receive sovereignty. You will receive latency.
Third, the cloud illusion is weaker than most executives realize.
Anthropic’s claim that Chinese firms used roughly 24,000 fraudulent accounts and more than 16 million interactions to extract value from Claude should be read as more than a competitive dispute.
It is a warning.
If frontier-model logic can be harvested at industrial scale through standard interfaces, then the comforting assumption that enterprise use happens inside a clean and sealed boundary becomes much harder to defend.
That matters because most companies are now piping sensitive internal reasoning, workflows, and proprietary context into systems they do not own.
In a world where outputs can be harvested at scale, what leaves your perimeter does not always stay under your control.
The real mistake is architectural
When I brief executives on this reality, the instinctive response is usually legal.
They point to enterprise contracts, service-level agreements, privacy terms, and procurement safeguards. They assume that if the paperwork is strong enough, the capability is secure enough.
It is not.
A legal contract may help with recourse after failure. It does not preserve operational tempo during failure.
If a vendor throttles access, changes terms, suffers a geopolitical shock, or becomes strategically constrained at the wrong moment, the contract will not give you back time. It will not restore continuity. It will not protect your internal decision cycle while the disruption is happening.
That is why this should not be framed as a standard procurement issue.
It is an architecture issue.
If the core analytical engine of your organization depends on a monolithic external vendor, then your intelligence function is operating on borrowed ground.
The future belongs to sovereign AI
The era of the monolithic AI vendor as the sole provider of enterprise intelligence is over.
The more resilient direction is clear: smaller, focused, locally controlled models deployed within your own perimeter, tuned to your own workflows, and governed by your own update cycle.
That does not mean every company should build a frontier lab.
It does mean leaders should start thinking in terms of sovereign capability rather than convenience.
Military intelligence understood this posture long ago. You build the secure room first. You establish the air gap. Then you bring the tools inside.
Business leaders need to absorb the same lesson.
The strategy is no longer about asking which vendor has the smartest chatbot.
It is about deciding which parts of your cognitive infrastructure must remain yours.
What leaders should do now
Start with four questions.
1. Who controls the absolute choke point of our analytical systems?
2. How fast can we replace this model under stress without halting daily operations?
3. What proprietary data leaves our perimeter every time our teams use these tools?
4. What exact market or geopolitical event would force us to bring this capability in-house immediately?
If you do not have clear answers to those four questions, you do not have an AI strategy.
You have a blind spot.