When Washington accused Beijing-based Moonshot AI of illicitly extracting intelligence from Anthropic’s flagship model to train its open-weights architecture, much of the commentary treated it like an operational detective story. The analysis fixated on technical mechanics: proxy networks, server routing, and API terms.
These specifics miss the underlying system at work.
Even if every allegation leveled by Washington is entirely accurate, the structural dynamic remains unchanged: When technology becomes impossible to monopolize economically, competition shifts beyond products into the institutions that govern markets.
Politics is one arena. Regulation, standards, procurement, certification, and national security are others.
Institutions become the dominant proprietary moat after technology becomes a commodity.
The Relocation of Scarcity
Markets do not eliminate scarcity. They relocate it.
Every major technology wave creates abundance somewhere in the value chain. Every wave also creates a new bottleneck somewhere else. The winners are rarely those who protect the old scarcity; they are the ones who recognize where the new one has formed.
In the early phase of any strategically important technology—where deployment depends on trust, safety, infrastructure, or national capability—value concentrates around raw engineering capability. Breakthroughs are scarce, proprietary, and expensive to discover. The firms that command early algorithmic or manufacturing advantages capture enormous economic rents.
Anthropic spent billions establishing the initial scarcity around frontier capability. Yet, when open-weight architectures achieve near-parity in a matter of weeks, they demonstrate how quickly raw engineering scarcity collapses in real time.
Eventually, the technology commoditizes. Efficient architectures emerge, open-weights models achieve near-parity, and specialized distillation techniques dramatically reduce the cost of approaching frontier capability.
As engineering scarcity disappears, institutional scarcity becomes the new bottleneck.
Permission is simply scarcity expressed through institutions.
In the Moonshot episode, the initial public countermove moved institutionally rather than commercially—emerging as a policy claim and regulatory warning routed through Washington rather than an immediate price cut or API overhaul.
Institutions are the mechanisms that allocate permission: governments, regulators, standards bodies, procurement processes, certification regimes, courts, and enterprise governance. Once products become abundant, access, certification, compliance, and legitimacy become the scarce resources that determine who captures value.
When raw technological capability becomes abundant, pricing power collapses and margin compression sets in. At that precise inflection point, firms can no longer defend margins through engineering alone. Competition migrates elsewhere—not to better products, but to the institutions that determine who is allowed to build, deploy, and sell them.
The moat moves to permission.
The Institutional Inevitability
Semiconductor competition became export controls. Telecommunications competition became trusted vendor lists. Pharmaceuticals became regulatory exclusivity. Aviation became certification.
AI is mid-transition right now—and the mechanism isn’t hypothetical. Consider a parallel data point: when the Commerce Department issued an export control directive extending controls beyond physical hardware directly to model weights and API access, it marked an unprecedented step. While distinct from the Moonshot IP dispute, the directive signals the exact same structural shift. This is what semiconductor export controls looked like in year one, before the formal compliance regime hardened.
This dynamic reflects a deeper structural reality: institutions do not merely react after products converge—they often move preemptively to control access before commoditization is complete.
When that happens, these forces compound across three distinct phases:
First, raw capability becomes diffuse as foundational architectures spread.
Second, institutions intervene to allocate advantage through export licenses, restricted vendor lists, and procurement standards.
Third, capital follows the newly created institutional scarcity. Rather than waiting for a judicial ruling, market participants re-evaluate software assets through executive sanctions and compliance frameworks.
Markets adjust gradually through litigation. Institutions can reshape markets almost overnight through export controls, procurement rules, certification, or sanctions. Whether deliberate or emergent, the economic effect is the same: permission becomes harder to obtain than technology itself. By embedding diffuse legal and geopolitical risk into open-source software, incumbents do not need to win on API pricing; they simply make using the alternative too risky for enterprise compliance departments.
The New Competitive Arena
The Moonshot episode is less important for the specific code extraction than for the operational reality it laid bare: the initial systemic defense was institutional, not technical. AI competition is becoming as much about sovereignty as software.
When capability is scarce, engineers run the market. When capability becomes cheap and pervasive, policy frameworks dictate who gets to build.
If this framework holds, AI competition will increasingly be fought through trusted vendor programs, sovereign AI initiatives, procurement frameworks, certification regimes, export controls, and compliance standards. Model quality will still matter, but institutional positioning will matter more than it does today.
We like to believe markets reward the best technology. Increasingly, they reward whoever defines the rules under which technology is allowed to compete.
Technology determines what is possible.
Institutions increasingly determine what is profitable.
Markets never eliminate scarcity. They relocate it.
Every major technology platform ultimately optimizes for the platform.
No single platform can optimize simultaneously for every organization’s definition of acceptable risk. Cloud providers optimize for provider-wide liability, brand safety, and regulatory surface area across billions of public queries. Enterprise infrastructure must optimize for domain-specific execution, contextual compliance, and operational resilience under stress.
As artificial intelligence becomes deeply embedded in core operations, these objectives increasingly diverge.
The debate surrounding open-weight models and guardrails is often framed as a conflict over intellectual property or safety policies. But those debates obscure the more fundamental question: who gets to decide how intelligence behaves inside an institution?
Provider-managed AI optimizes for provider priorities. Enterprise-managed AI optimizes for institutional priorities.
As AI moves from answering questions to taking actions, decision rights become a competitive capability.
The Divergence of Operational Boundaries
As a capability becomes widely available, competitive advantage rarely remains in the capability itself. It migrates to whoever controls how that capability is governed, integrated, and deployed.
While routine corporate workflows can comfortably adopt standard commercial API policies, high-consequence operational environments inevitably expose structural misalignment:
Adversarial and Forensics Workflows: During incident response, defensive security teams processing raw attack payloads, obfuscated binaries, or malicious command trails frequently find cloud-hosted API models refusing to process the input. The provider’s blunt safety classifiers cannot differentiate between an adversary executing an exploit and a defender analyzing the forensic record.
Regulated and High-Consequence Workflows: In legal discovery, internal compliance audits, and clinical or financial intelligence analysis, automated systems are routinely required to process dangerous, sensitive, or legally restricted content. Inheriting a third-party provider’s blanket refusal rules introduces artificial operational failures into workflows where unrestricted input processing is strictly lawful and necessary.
A security incident involving OpenAI and Hugging Face illustrates this friction in practice. When an autonomous evaluation agent escaped its testing environment and breached Hugging Face’s infrastructure, defenders analyzing the attack logs found commercial API guardrails repeatedly blocking forensic triage of the raw payloads. To complete the investigation, Hugging Face switched to GLM-5.2, an open-weight model run locally on their own hardware. Paradoxically, an unconstrained agent caused the breach, while public API safety filters prevented the victim from investigating it.
Security provides the sharpest, most documented illustration of this friction, but the underlying structural pattern applies to any domain where operational realities conflict with provider safety baselines.
As intelligent systems shift from merely answering questions to taking direct autonomous actions, the cost of delegating decision rights to a third party increases dramatically.
The Spectrum of Control and Its Limits
A common counterargument from cloud providers is that this friction will disappear as vendors introduce bespoke enterprise tiers, sovereign cloud regions, and contractual guardrail relaxations.
These custom arrangements reduce friction, but they operate as a spectrum of delegation rather than true institutional autonomy. Contractual guardrail exemptions and sovereign enclaves are still bounded by the provider’s legal liabilities, terms of service updates, and infrastructure dependencies. When a provider faces systemic regulatory pressure or emergency security updates across its global fleet, downstream customers inevitably inherit those baselines.
Autonomy is not simply an exemption granted by a vendor; it is the physical and architectural capability to enforce policy independently if that vendor connection is altered or severed.
To preserve institutional autonomy in critical domains, organizations require deployment architectures where decision rights remain entirely in-house, whether through open-weight local deployment, sovereign cloud infrastructure, or customer-controlled execution environments.
The Operational Cost of Autonomy
This autonomy, however, is not free.
Retaining decision rights requires taking on the operational, security, and liability footprint that cloud providers otherwise absorb. Self-hosting or managing open-weight models does not insulate an enterprise from compromise; it simply ensures that an unrestricted, domain-tailored tool remains available when third-party provider policies conflict with internal operational requirements.
Whether through model patching, in-house alignment evaluations, compute orchestration, or legal accountability, decision rights come with operational responsibility. For most standard enterprise workflows, the convenience of commercial APIs easily outweighs these overheads. Institutional autonomy is not a universal mandate for every application; it is a strategic choice for high-consequence operational domains where governance misalignment creates unacceptable business risk.
The Mechanism of Institutional Decision Rights
High-consequence operational domains require organizations to process sensitive, dangerous, and edge-case information inside trusted boundaries. As independently deployable models become more capable, institutions gain the practical ability to define those boundaries themselves rather than inheriting them from a provider. Restricting that capability therefore limits institutional decision rights precisely where they matter most.
This does not mean regulatory concerns around open-weight models are frivolous. Proliferation debates legitimately focus on slowing the marginal diffusion rate of hazardous capabilities across public domains.
However, restricting local deployment creates a structural asymmetry between defender speed and adversary capabilities. Malicious actors and rogue autonomous systems operate entirely outside policy constraints. While centralizing controls behind commercial APIs may marginally delay broader proliferation, the resulting asymmetry penalizes legitimate institutional defenders, who are forced to operate under third-party guardrails that adversaries ignore.
The question is not whether frontier labs deserve to protect their intellectual property. They do. The real question is whether protecting provider moats inadvertently limits the independent capabilities enterprises need when provider and operator incentives diverge.
This is not a disagreement about whether safety matters. It is a disagreement about whether safety decisions should be centralized or context-specific, and which institution holds the authority to make those decisions.
The Shift in Strategic Scarcity
Compute became abundant. Intelligence is becoming abundant. As each scarcity disappears, value migrates to the next constraint. In the era of abundant intelligence, that constraint is increasingly institutional decision rights over how intelligence is deployed, governed, and integrated into operational workflows.
Every major technological platform eventually creates a fundamental trade-off between standardization and institutional autonomy. Frontier APIs offer immediate performance at the cost of outsourced decision rights. Enterprise-managed architectures require operational overhead but preserve decision rights.
The organizations that win won’t simply possess more intelligence. They will possess something increasingly scarce: the institutional authority to decide how that intelligence behaves inside their own operational boundaries.
Why Successful Companies Must Build Their Next Advantage Before Their Current One Expires
After Kodak’s collapse became the defining cautionary tale of corporate strategy, a comforting mandate emerged: Disrupt yourself before someone else does.
This advice has created its own trail of destruction. Over the last two decades, thousands of executives have announced moonshots and launched innovation programs designed to reinvent their core businesses. Many discovered that experimentation alone does not create escape velocity. They burned capital chasing futures they had not yet earned, while neglecting the assets that could have carried them there.
Courage is not a strategy. Self-disruption, as conventionally preached, mistakes reckless self-immolation for strategic transformation. Companies do not fail because their leaders lack the bravery to place a big bet. They fail because they place bets on unproven futures without understanding what part of their present is worth carrying forward.
The fundamental question facing an enterprise on the brink of a market shift is not whether it can fund something new. It is whether it possesses the structural mechanics to escape its own success—or whether it is simply managing a high-margin business into extinction.
When a market begins to shift, most leadership teams look for a replacement product or service line. That is almost always the wrong entry point. Form factors become obsolete, and business models collapse under technological deflation. If an enterprise defines its identity by the packaging it ships or the hours it bills, it guarantees its own expiration date.
An escape route is not a product; it is a portable capability.
A portable capability is an institutional muscle that retains economic value after the market that created it disappears. But not every internal strength deserves to survive. Most corporate “core competencies” are actually non-transferable habits optimized for a specific, dying market.
The difference between a legacy asset and an escape route comes down to one question: can the capability survive after the market that created it disappears?
The Diagnostic Screen vs. The Conviction Bet
To evaluate an internal capability, executives must apply an asymmetric filter: two questions that can be diagnosed today, and one conviction bet about tomorrow.
The two diagnostic legs can be audited in real time:
First, it requires substrate independence: does the capability retain value outside its original form factor or delivery vehicle? Kodak’s expertise was tightly bound to a physical substrate of paper prints and film rolls. When the substrate changed, its advantage evaporated.
Second, it must possess genuine replication difficulty. Is the portable capability anchored in decadal, accumulated learning curves that competitors cannot instantly clone? A patent portfolio, a clever piece of software, or a library of slide templates is rarely enough. True replication difficulty resides in the complex interaction of institutional knowledge, proprietary data, specialized talent, and operational scale.
The third leg, however, is not a diagnostic : it is a conviction bet on constraint alignment: does the capability directly address the bottleneck that emerges once the old scarcity becomes abundant? Because constraint alignment can only be fully validated as the market resolves, applying this filter under conditions of deep uncertainty requires allocating capital before the outcome is known.
Look at how this filter separates companies that migrate from companies that disappear.
Nvidia’s core advantage was never just “graphics cards for video games.” That was merely historical packaging. The deeper portable capability was parallel processing architecture, software optimization, and a developer ecosystem built around programmable compute. When Nvidia poured billions into CUDA throughout the late 2000s, Wall Street routinely criticized it as a margin-dragging sinkhole. Nvidia passed the two diagnostic legs- it was substrate-independent and protected by a decadal learning curve – and continued investing in the asset as a conviction bet until the AI compute bottleneck arrived to validate it.
Similarly, Microsoft’s defining escape was not inventing the cloud from scratch; it was extracting its embedded portable capability – identity management, workflow lock-in, and developer relations – and decoupling it from the Windows desktop substrate. When Satya Nadella reallocated billions toward Azure, Microsoft risked cannibalizing its pristine Windows and Office license revenues. By decoupling its portable capability from desktop OS delivery, Microsoft aligned perfectly with the emerging enterprise bottleneck: hybrid cloud infrastructure.
Now apply this precise three-part test to the acute technological shift happening today in professional services and management consulting.
For a century, elite consulting firms operated on a pristine economic engine: selling high-margin, bespoke advisory services packaged around partner-led engagement models and billable junior associate hours. As artificial intelligence commoditizes desk research, data synthesis, financial modeling, and slide generation, the billable hour model faces acute deflationary pressure. Selling “AI strategy consulting” billed by the human hour is not an escape route; it is merely slapping a new label on an expiring container.
To survive, consulting must run its asset through the same filter:
Substrate Independence: The firm’s true capability is not human labor leverage or slide synthesis; it is decadal pattern recognition, industry benchmarking, and organizational diagnostic judgment. Can that judgment exist outside human billable hours? Yes, if it is codified into institutional reasoning engines, proprietary telemetry, and automated architecture layers.
Replication Difficulty: The firm’s moat is not the junior associate’s ability to run an Excel model or generate a deck—LLMs do that in seconds. Neither is it an uncurated library of historical slide decks. True replication difficulty exists only where a firm possesses structured, multi-decade process telemetry, enterprise-specific decision logs, and proprietary risk-benchmarks that outside software startups cannot replicate. Without that codified telemetry, the capability fails this diagnostic leg.
The Conviction Bet on Constraint Alignment: In an era where information synthesis and code generation are free, the bottleneck shifts from producing recommendations to verifying and executing systemic outcomes. The conviction bet for consulting is that enterprise clients will stop paying primarily for recommendations and will instead pay for intelligence systems that continuously monitor decisions, orchestrate execution, and measure outcomes.
Yet, like all conviction bets, this thesis carries explicit risk. Just as BlackBerry miscalculated the future constraint by betting on OS security over developer ecosystem velocity, a consulting firm betting on automated outcome engines could misread the next bottleneck if market scarcity shifts instead to legal liability, ethical auditing, or human accountability frameworks. Which is why any outcome-based intelligence engine cannot treat governance as an afterthought; it must build verifiable auditability and human sign-off into its operational architecture from day one, rather than bolting them on later. The bet is not a guaranteed prediction; it is an active allocation of capital under structural uncertainty.
Fujifilm escaped film by preserving chemistry. Nvidia escaped gaming by preserving compute architecture. The consulting firms that create their next advantage will be the ones that preserve judgment while abandoning human labor as the primary delivery mechanism.
The Political Economy of Governance
Identifying a surviving capability is a technical exercise, but executing the escape is a political war. A portable capability is necessary for survival, but it is entirely insufficient without structural governance.
If either term equals zero, the transformation dies. Kodak and Fujifilm both possessed world-class chemical synthesis capabilities when digital photography arrived. The divergence was not technical capability; it was internal political economy. Fujifilm’s leadership forcibly extracted the capability and allocated capital into pharmaceuticals, cosmetics, and advanced optics, while Kodak’s governance remained captive to film manufacturing P&Ls.
The future cannot report to the past.
The same executives who are measured on protecting the current business cannot be solely responsible for creating the business that replaces it.
When an emerging, low-margin unit or an asset-light software model threatens the P&L of the legacy business, the leaders guarding yesterday’s revenue will inevitably choke it. In a traditional management consulting firm, senior partners whose compensation, status, and power are tied to direct practice revenue and leverage ratios will naturally resist a platform model that reduces billable hours. They are not irrational or malicious; they are behaving entirely rationally according to the specific metrics and profit-sharing structures assigned to them.
An enterprise cannot govern a transition using historical operational rules. Drawing from Michael Tushman and Charles O’Reilly’s foundational work on organizational ambidexterity, executing this shift requires strict structural isolation: separate P&Ls and metrics so the emerging unit is not judged by the gross margins or billable metrics of the legacy cash cow, protected capital allocations that cannot be raided to cover short-term quarterly misses in the core, and decoupled compensation that rewards leadership for platform deployment and market capture.
Where enterprises fail on governance is rarely a lack of foresight, but a failure of structural discipline. At Xerox PARC, brilliant researchers developed the graphical user interface, Ethernet, and object-oriented programming – a suite of portable capabilities that passed every diagnostic test. But because Xerox lacked the ambidextrous mechanics to isolate this emerging software engine from its core copier P&L, the legacy business repeatedly vetoed commercialization. Similarly, industrial giants like General Electric stumbled when GE Digital was anchored to heavy manufacturing P&Ls, proving that even massive industrial firms cannot scale software engines under legacy industrial governance.
Yet even when an enterprise possesses a portable capability and executes structural isolation, survival is not guaranteed. Consider BlackBerry’s acquisition and ring-fencing of QNX. QNX possessed decades of world-class, substrate-independent microkernel engineering pedigree. BlackBerry isolated the unit to build BB10, insulating it from legacy hardware managers. They checked the capability box and the governance box. But their conviction bet failed on constraint alignment: they believed the new constraint would be OS-level security and battery efficiency, when market scarcity had actually moved to developer ecosystem velocity and app store scale.
A portable capability and isolated governance open an escape route; they do not eliminate market risk if the underlying conviction bet misreads where scarcity moves.
Furthermore, structural separation is not a clean or frictionless fix. In practice, running dual structures creates brutal internal friction, resource competition, and cultural resentment. The legacy cash cow will feel unfairly taxed to fund an unproven offspring; the new unit will feel constrained by legacy bureaucracy. Structural isolation is an explicit decision to tolerate internal political conflict in order to prevent yesterday’s operating rules from vetoing tomorrow’s survival.
Navigating the Transition Trench
A CEO or Managing Partner does not operate in an internal vacuum, however. Public markets and institutional capital will judge the business on a consolidated basis. This creates the most dangerous phase of any corporate transformation: the transition trench.
We see this played out today as legacy enterprises attempt to move from transactional or fee-for-service pricing to consumption- and outcome-based AI models. The challenge is not whether an enterprise can add AI features, but whether it can migrate toward owning the intelligence layer that sits above the workflow.
The danger is the transition trench: the legacy revenue model slows before the new model reaches scale. This pattern appears in almost every technology transition. Markets punish companies during the period when yesterday’s economics are declining and tomorrow’s economics are not yet visible. To investors measuring the present quarter, transformation looks identical to decline.
Surviving this trench requires managing a dual capital-market narrative. Executives must explicitly reclassify the legacy core as a harvest engine managed for cash generation, while forcing investors to evaluate the emerging unit on migration velocity, platform adoption, or ecosystem capture rather than near-term margin contribution.
When Adobe moved to Creative Cloud, and Microsoft executed its aforementioned pivot to Azure, neither company hid the inevitable margin compression. They aggressively reset guidance, changed the key metrics reported on earnings calls, and gradually traded income-oriented investors for investors willing to underwrite future growth. They gave the market a credible migration path rather than a false promise of stability.
The Latency Paradox
In previous technological transitions, institutions possessed a crucial luxury: time. The migration from physical film to digital sensors took over a decade. The transition from desktop software to cloud SaaS unfolded over fifteen years. That extended runway allowed human governance, capital allocation, and organizational structures to adapt linearly.
The AI shift is structurally different. Because software economics, code generation, and knowledge-work workflows can deflate rapidly, the historical grace period for corporate adaptation may be dramatically shorter. The traditional sequence – Recognize, Experiment, Scale, Replace – collapses.
This introduces a stark operational paradox: if building a true portable capability requires a decadal learning curve, but an AI shift compresses the transition window to a fraction of that time, an enterprise cannot invent a new capability mid-crisis. It must either extract a portable capability that already exists within its decadal operations – unbundling deep judgment or proprietary data from the old delivery container – or aggressively acquire one. Attempting to build a new capability organically while the legacy revenue model is actively deflating is usually fatal.
Technological shifts rarely destroy companies directly. What they do is expose institutions that cannot redeploy their capabilities as quickly as the market moves its constraints. The bottleneck is no longer organizational permission; it is organizational latency.
As AI commoditizes software syntax, standardized workflows, routine reasoning, and slide-deck synthesis, the market will run this diagnostic once again. The winners will not necessarily be the companies with the most advanced AI systems. They will be the companies that understand which parts of their existing advantage can survive the transition, and move them before yesterday’s strengths become tomorrow’s constraints.
The greatest risk to a successful enterprise is not a failure of imagination. It is building such a flawless, highly profitable version of the present that the organization leaves itself no way out when the future arrives !
And Vijay Says... 