← Insights

Three Model Price Cuts in One Week: What to Do Now

GPT-6.1 Sol, Sonnet 5.5, and Gemini 4 all moved in the same week. If you're running AI in production, your cost baseline just changed.

What Actually Happened

In a single week, three frontier model releases hit with direct cost implications for anyone running AI workflows at scale. OpenAI's GPT-6.1 Sol launched at $2/$10 per million tokens — roughly one-fifth the price of GPT-6 Astra — while delivering a 7.7% error rate versus Astra's 11.4%. Anthropic's Sonnet 5.5 ships 30% faster at 30% lower cost than its predecessor, with no model swap required. Google's Gemini 4 Argon is in post-training with a year-end target. Meanwhile, OpenAI shelved GPT-6.1 Astra entirely over safety concerns.

This is not a story about which model is "best." It's a signal that the cost floor for production AI just dropped, and any workflow you priced six months ago is now overpriced.

The Operator's Problem With This

Most non-tech companies aren't running model benchmarks. They're running a specific workflow — a support triage chain, a sales content generator, a document processor — that was scoped, priced, and approved at a specific cost point. That cost point is now wrong, and nobody has a standing process to revisit it.

Sonnet 5.5 is the clearest example. If your team built on Claude Sonnet, you don't need to evaluate a new model. You need to pull your current monthly token spend, apply the 30% reduction, and figure out whether that unlocks volume you previously couldn't justify. Same capability. Lower ceiling. New use cases may now pencil out.

GPT-6.1 Sol is a different play: near-frontier performance at commodity pricing opens agentic and coding deployments that were previously cost-prohibitive. If you've been sitting on an automation pilot because the per-call economics didn't work, rerun the numbers.

The Actionable Takeaway

Do three things this week:

  1. Audit your current model spend by workflow. Know what you're paying per task, not just per month. Most teams have the invoice but not the unit economics.
  2. Map each workflow to the new pricing. For anything on Sonnet, the repricing is automatic if you upgrade — calculate the delta. For anything on GPT-4-class models, Sol is worth a head-to-head test on your actual prompts, not synthetic benchmarks.
  3. Create a model-review cadence. The frontier is moving on a quarterly cycle now. A one-time vendor selection is not a strategy. Build a lightweight review checkpoint — even a 60-minute quarterly check — into your AI operating rhythm.

The governance friction is real: OpenAI pulled a model over safety flags mid-cycle, which is a reminder that vendor stability is a legitimate planning input. But the cost opportunity is also real. Operators who act on it this quarter will have meaningfully lower per-unit AI costs than those who wait for the next annual review.