A “code red” at a supplier, and what it tells a customer

OpenAI released GPT-5.2 on 11 December 2025, three weeks after Gemini 3 and reportedly following an internal « code red » memo about competitive pressure from Google. It comes in three variants, including reasoning modes.

This blog argued on 25 November that the November cluster was a competitive reflex rather than a technological necessity. Two weeks later a reported internal memo made that argument for us more vividly than we could.

What a supplier under pressure means for you

Three things, and only one is bad.

Good: prices and terms improve. A provider defending market share is a provider who will negotiate, and the January renewal conversation from yesterday’s post is being held in exactly this weather.

Good: capability arrives faster. Three years of competition has produced the commodity market described in November, which is the best outcome available to a buyer.

Not good: release cadence under pressure tends to produce more changes, faster, with less warning. That is the version-stability question from 13 August, and a supplier in a hurry is precisely the supplier most likely to change something under you.

The practical reading

If you are negotiating anything in the first quarter, you are negotiating from a stronger position than you were in the summer. Ask for what you want, including a stability commitment and a per-tier usage report.

If you run scheduled processes, treat the next six months as a period of more frequent change rather than less, and pin what you can.

And a note on how to read reported internal memos

Carefully. Competitive urgency is a real phenomenon and also a convenient story for a company to have circulating.

Either way the observable facts are the same: four major releases in five weeks, and a market in which no supplier can afford to sit still. Those facts favour you, and they do not require you to do anything this month.