A licensing deal can change the supplier you depend on

Newcomer reported on August 20 that Poolside had reached a $6 billion non-exclusive licensing deal with Nvidia, alongside a separate $1 billion investment. Its report attributes the terms to an investor letter. Those reported terms describe a licensing transaction; they do not establish that the arrangement is invisible to regulators.

There is a direct reason to reject that automatic conclusion. In 2024, the UK Competition and Markets Authority examined Microsoft’s hiring of Inflection staff and associated licensing arrangements. It found a relevant merger situation within its jurisdiction, then cleared the transaction on competition grounds. The CMA’s decision summary separates jurisdiction from the substantive outcome.

My procurement rule is broader than the transaction label: review a supplier when the people, rights or infrastructure behind its service materially change.

That review does not require predicting whether a particular regulator will intervene. It asks whether the organisation on the other side of the contract can still deliver what we bought.

The legal entity is only one dependency

A company can remain legally independent while changing its product priorities, staffing or access to essential technology. A buyer whose monitoring only watches for a formal change of control may miss those operational changes.

Conversely, a large licensing deal can fund a supplier’s continued development and strengthen its delivery position. The existence of a deal is not evidence of decline. The useful question is what changed in the capabilities the customer actually relies on.

For a hypothetical model supplier, I would identify the team maintaining the endpoint, the rights required to serve the model, the infrastructure supporting its capacity and the owner of promised updates. Then I would ask which of those commitments the transaction affects.

A non-exclusive licence can coexist with continued service. It does not itself explain the remaining company’s support capacity or roadmap. Those need their own answers, tied to the customer’s actual agreement.

Ask for a continuity account

In that hypothetical review, I would request a concise continuity account rather than a reassurance that nothing changes. It should name the service owner, current support arrangement, update responsibilities and any changed dependencies that could affect delivery.

I would compare that account with a few concrete obligations: the incident-response contact, the next required compatibility update and the capacity already committed to us. If the answers rely on people or resources now controlled elsewhere, the dependency should be explicit.

The exercise also tests the contract’s notification language. A clause covering only acquisition may not describe a material shift in staffing or licensed rights. Counsel can assess whether additional obligations are appropriate; engineering should supply the changes that would actually threaten continuity.

I would keep a proportionate fallback ready for the parts of the service that are difficult to replace. That could mean preserving an approved alternative model or rehearsing export of application-owned state. It need not mean abandoning a supplier because a headline changed.

The transaction’s economics are interesting. The buyer’s immediate responsibility is more ordinary: establish whether the service it depends on still has the same means to deliver.

Review the supplier’s surviving capabilities, even when the transaction leaves its company name intact.