OpenAI shipped a new flagship model on July 9. If you run a mid-sized company, here is the correct amount of your week to spend reacting to that: none.
That's not cynicism about the model. It's what the launch itself says, read closely.
What actually shipped
GPT-5.6 went generally available across ChatGPT, Codex, and the API. It comes in three tiers, and OpenAI's own announcement lists the prices per million tokens: Sol at $5 in / $30 out, Terra at $2.50 / $15, Luna at $1 / $6.
Look at the flagship number for a second. $5 / $30 is exactly what GPT-5.5 cost. The new frontier model launched at the old frontier model's price. That is not what a decisive capability leap looks like when it's priced by the company that built it.
On performance, OpenAI points at the Artificial Analysis Intelligence Index, where Sol lands within a single point of Anthropic's Claude Fable 5 — 59 against 60 — while, in OpenAI's framing, "completing tasks in 61% less time at roughly half the estimated cost." (That's OpenAI's chosen benchmark and OpenAI's chosen comparison, so read the speed and cost claims as a vendor's best case. The part worth keeping is the gap: one point.)
One point. Between the two most expensive frontier models in the industry, from the two labs furthest ahead. That's the whole story, and everything below is a footnote to it.
The tell: OpenAI didn't switch its own default
Here's the detail that got almost no coverage, and it's the one that should decide how you feel about all of this.
GPT-5.6 did not become the default model in ChatGPT. GPT-5.5 Instant is still what everyday conversations run on. Sol powers the reasoning options on eligible paid plans — an option you select, not the thing you get.
Sit with that. The company that built the model, that has every commercial reason to put its newest and most impressive work in front of every user, looked at its own launch and decided the previous model was still the right default for most requests.
If OpenAI isn't in a hurry to move everyone onto GPT-5.6, the case for you rebuilding anything around it this quarter is thin.
What companies actually do with the "best" model
The buyers furthest along have already stopped shopping this way.
Forbes reported in July on why leaderboards no longer decide enterprise AI buying, and the numbers in it are more useful than any benchmark chart. Databricks ran a test on real million-line codebases — not puzzles, actual work. Claude Opus 4.8 completed 87% of tasks at $1.94 each. An open-weight model, GLM-5.2, came in statistically tied at $1.28.
Same outcome. A third less money. From a model most people reading this couldn't name.
That's not an isolated result, either. Per the same reporting, Chinese-origin models climbed from 4.5% to somewhere between 30% and 46% of enterprise token volume on OpenRouter. And Microsoft — which has spent more on a relationship with OpenAI than most companies are worth — now routes commodity tasks to its own in-house models and saves the frontier models for the genuinely hard reasoning.
Read that last one twice. Microsoft's answer to "which model should we use?" is "depends on the task, and mostly not the expensive one." They're not picking a winner. They're routing.
Commodity doesn't mean simple
This is where the "models are commoditizing" argument usually overreaches, so let's not.
Cheap and interchangeable does not mean easy. If anything it's the opposite: the more real options exist, the more someone has to own the decision of what runs where, and when, and what happens when it fails.
DeepSeek is the sharpest example. Its V4 release was reported in mid-July to introduce something genuinely new: time-of-day surge pricing, with rates roughly doubling during Beijing peak hours. (Reported, but we couldn't confirm it against DeepSeek's own documentation before publishing this — treat it as directional until you verify it yourself.) Even as a directional signal, think about what it implies. The cheapest frontier-class inference on the market may now cost different amounts depending on what time it is in another hemisphere.
Google, meanwhile, is a lesson in a different direction: Gemini 3.5 Pro is still in limited preview after missing multiple general-availability targets. Any plan built around a model that was promised but hasn't shipped is a plan built on someone else's roadmap.
So: the models converged, the prices fell, the options multiplied — and the job got harder, not easier. That job has a name. It's not model selection. It's deployment.
The question that actually matters
"Which AI is best?" is a question with a fresh answer every six weeks and no operational consequence. Here's what to ask instead:
- What work are we actually trying to move? Not "where can we use AI" — which process eats the most hours for the least judgment. The inbox. The phone after 5pm. The report someone rebuilds every Monday.
- Is it wired into our tools and our data? A model that can't see your CRM, your calendar, or your ticket history is a very articulate stranger. The integration is the product.
- What happens when it's wrong? Who reviews it, what does it escalate, where does a human step in. If there's no answer, you don't have a system — you have a demo.
- Can we swap the engine without rebuilding the car? This is the real one. Given how fast the frontier moves, any system that's welded to one vendor's model is a system you'll rebuild inside a year.
Notice none of those mention a model name. That's the point. The model is the easiest, cheapest, most replaceable component in the entire stack — and it's the only one anybody argues about.
We build on the frontier models, all of them, and we treat that choice as an implementation detail we own and can change. When something better ships, we move — you shouldn't have to know, or care, or re-sign anything. What you should notice is that the work keeps getting done.
Because the model was never the hard part. Getting it plumbed into the way your company actually runs — that's the hard part. That's the part that's worth paying for. And it doesn't have a version number.
Related reading: From ChatGPT Chaos to Integrated AI Systems — why a chat tab saves an individual 30 minutes but never changes how the company operates, and why a third of companies that cut jobs for AI are hiring them back.
Related solution: explore our AI automation solutions — voice, chat, workflow, and ticket triage, built and managed for the team you already have.