The AI price war has started

This morning's window is a little shorter than usual, but the pricing signal is obvious: AI model vendors are cutting and tiering prices faster than product teams can treat them as static infrastructure. The market now looks less like a single leaderboard and more like a ladder of tiers, each priced for a different job. For PMs, that changes vendor choice, margin math, fallback planning, and launch timing.

The important part is not that one vendor got cheap. It is that the whole market now spans a much wider cost band, and the same product can land in very different economics depending on the tier you pick. CNBC framed the shift as a move from bigger models toward routing, cost, control, and compute, which is the right diagnosis for product teams even if the term sounds technical. 6

First, stop asking which model is best in the abstract. Ask which task deserves premium inference and which task can live on the cheap tier. A classification job, a short summary, or bulk enrichment can usually tolerate a lower-cost model. A planning step, a complex code task, or a user-facing answer with high downside still needs a stronger model.

Second, treat model cost as part of product margin, not procurement trivia. Meta is pricing like it wants adoption share, not just revenue per token. Anthropic still charges a wide premium for its top tier. 5 That means a feature that looks fine in demo traffic can become expensive fast once usage scales.

Third, spec fallback before launch. Every AI feature should declare a primary model, a fallback model, and the degradation mode if the preferred model is unavailable or too expensive. Meta’s API is still in public preview and limited to Meta’s own properties, which is a reminder that access and packaging can change under you. 2

Fourth, use caching wherever the prompt prefix stays stable. OpenAI now exposes explicit cache breakpoints and a 30-minute minimum cache life, which matters if your product reuses the same instructions, policy text, or context across many requests. 1

A simple rollout spec is enough to keep the team honest:

That is the practical shift. The team is no longer choosing a model once and moving on. It is managing a price ladder, a fallback plan, and a cost envelope at the same time.