Every few weeks a smarter model ships, and the price of last month’s intelligence drops. If that keeps up, raw model capability stops being an advantage, because everyone can rent the same one. The edge moves to what stays scarce. Here’s my view of what that is, and how a team can get ready now.
September 2026 brought GPT-6 Astra, Claude Fable 5.1, Claude Opus 5.5 and Gemini 4 Argon, each claiming the top of some leaderboard. Opus 5.5 arrived cheaper than the model it replaced. Rumors about the next generation are already circulating, though none of it is confirmed.
Most teams respond by chasing each release: rewrite the prompts, rerun the demos, argue about which model is best this month. That’s a treadmill. The more useful question is what a much smarter model would still need from you, because that’s the work that won’t be thrown away next month.
I ran an experiment to see which prompting habits still help as models get stronger: What Smarter Models Make Obsolete. The prompt tricks faded; tools, verification and tests didn’t. This essay is the thought experiment that goes past what one test can show.
The ideaTreat intelligence as a commodity that gets cheaper every quarter. Invest in the things it can’t supply for itself: knowing exactly what you want, owning the ground truth, giving it access and tools, deciding what it may do, and paying only for as much intelligence as each job needs.
Think about how a team spends its AI effort today. Much of it goes into compensating for the model: writing long prompts, catching its mistakes, rephrasing until it behaves. As models improve, that compensation shrinks. What grows is everything around the model.
My estimates, not measurements. Shares of a team’s AI-related effort; toggle to compare.
A smarter model needs fewer instructions. It does not need fewer facts, fewer tools or less accountability.
Five things a model can’t generate for itself, however capable it becomes. Each one has a measured hint from the builds on this site.
The prompt doesn’t disappear; it changes job. Today’s prompts are full of technique: personas, rules, worked reasoning. Tomorrow’s look more like a good brief to a senior colleague: the goal, the constraints, the materials, the definition of done, and how the work will be checked.
Examples survive, but differently. In my test, two worked examples no longer improved accuracy, yet they cut the top model’s output by 44%, because it copied their format. Examples become a contract for the shape of the answer rather than a lesson in how to think.
Context matters more, not less. A smarter model can use far more of what you give it, so the work shifts from trimming context to curating it: the right documents, current and trustworthy, with the stale ones taken out.
Cheaper intelligence doesn’t make waste free. Smarter models tend to think longer when asked hard questions, and agents call models thousands of times a day. A team that routes well spends a fraction of what a team that sends everything to the top model spends, for the same results.
Three habits held up in my tests. Let code do exact work, because a program is short and right where reasoning is long and occasionally wrong. Use the lowest thinking level that holds accuracy, because the top settings mostly bought cost. And measure cost per right answer, not cost per call, because a cheap model that fails costs more than an expensive one that doesn’t.
The team that can test a new model on its own work in a day will get every future model’s gains first.
This is a forecast. Progress could slow, prices could rise, or new models could bring new quirks that need new techniques. My experiment used exact-answer problems, which favor tools; open-ended work like writing and strategy may keep rewarding careful prompting longer. And “intelligence is abundant” is true only for those with access: the most capable model this month, Gemini 4 Argon, is open only to vetted security teams.