Product & Strategy

The Product Desk

The Signal

Grok 4.5 cuts tokens per task 4.2x, making your AI cost model wrong by 16x

Grok 4.5 finishes SWE-Bench Pro tasks in 15,954 output tokens vs Opus 4.8's 67,020 — at $2/$6 pricing, that compounds to ~16x cheaper per completed task. Every feature your team cut for unit economics needs rescoring this week, before competitors run the same math.

In Play

  1. The 16x Task-Cost Reset

    Grok 4.5 finishes SWE-Bench Pro tasks in 15,954 output tokens vs Opus 4.8's 67,020 — 4.2x fewer — at 4x lower pricing ($2/$6 vs $5/$25). GPT-5.6 Luna: $1/$6. Compounded: ~16x cheaper per completed task. Your 'too expensive per user' threshold just moved an order of magnitude.

    Ask Clarity
  2. Subsidized APIs Meet Rising Compute

    Today's $1-2/M pricing is a land-grab atop rebounding compute costs, with steep API hikes expected once share is captured — portability, not price, is the durable strategy. Details in the deep dive.

    Ask Clarity
  3. Benchmark Trust Collapse

    OpenAI audited the industry's primary coding benchmark and retracted its recommendation — and top scorers lose on cost-per-task anyway. Domain-specific eval suites are now the moat. Details in the deep dive.

    Ask Clarity
  4. Your Users' Interactions Are Training Rivals

    SpaceXAI trained Grok 4.5 on Cursor's full interaction corpus — trillions of tokens of real developer data — while Claude Code shipped undisclosed location telemetry that China's national vuln database classified as a backdoor. Contractual no-training guarantees now differentiate enterprise deals more than benchmark deltas.

    Ask Clarity
  5. On-Prem AI Goes Default

    Ollama: 8.9M monthly developers (2x since January), ~1M installs/week, 85% Fortune 500 penetration — with 14 employees. JPMorganChase deployed SambaNova SN40/SN50 for on-prem inference; Prime Intellect raised $130M at $1B to help enterprises train their own models. Cloud-only AI features forfeit regulated-industry revenue.

    Ask Clarity

Deep Dives

Your Cut List Is Now Your Roadmap — But Naive Routing Will Eat the Savings

The Cache Trap Nobody Priced In

Routing easy calls to cheap models backfires in production. Prompt caching gives ~90% discounts on previously-seen input, but caches are model-specific: route call #3 of a five-step agent task to a different model and you re-bill the full context at cold rates. Result: a cache-hot expensive model can cost less than a cache-cold cheap one. Optimize at the session level, not the call level.

The converging production pattern: a guardrail filter, a 1.5B-parameter router (Arch-Router, trained on human preference data), a cost/speed policy, and session pinning that locks the winning model to the whole task. Open-source Plano (Katanemo) cut costs 2x on the Hermes agent benchmark with zero agent code changes, via YAML config. At $50K/mo inference spend, that's $25K back without engineering cycles.


Where the Sources Converge

Three independent analyses agree: OpenAI's Sol/Terra/Luna tiering is an explicit routing blueprint — Terra delivers GPT-5.5-level performance at $2.50/$15, half the cost, and without routing you overpay 3-5x on ~80% of calls. A second analysis warns per-call routing raises costs via cache misses. Synthesis: routing is table stakes; only session-pinned routing captures the savings. And quality no longer trades off against efficiency — GPT-5.6 Sol scores 80.0 on the Coding Agent Index vs Claude Fable 5's 77.2, using under half the tokens at a third the cost.

Caveat: the window is symmetric — your competitors' cut lists just became viable too. Advantage goes to whoever re-runs unit economics and ships first.

A cache-hot expensive model can cost less than a cache-cold cheap one — optimize AI costs per session, not per call.

What to do

  1. Rescore every backlog feature previously cut for unit economics using cost-per-completed-task at Luna/Terra/Grok pricing by end of week

  2. Prototype session-pinned model routing this sprint — evaluate Plano against your current single-provider integration and instrument per-request cost visibility

The Subsidy Trap: Cheap Tokens Are Sitting on Expensive Silicon

Two Clocks Are Running Against Today's Prices

Clock one: OpenAI and Anthropic IPO'd in 2026 while still losing money every month. VC money subsidized land-grab pricing pre-IPO; post-IPO earnings pressure predicts API hikes within 2-4 quarters, premium tiers gating the best models, and quality degradation on cheap tiers. Clock two: Meta's and SpaceXAI's coding-model pricing is a deliberate land-grab, with 3-5x increases expected within 12 months once share is captured.

The silicon layer is moving the wrong way for the deflation narrative: H100 one-year contracts bottomed at $1.70/hr in October 2025 and rebounded 38% to $2.35/hr, with spot prices up 10% YTD. A 2026 roadmap built on trough compute pricing has stale margin math.


The Contradiction Is the Insight

Sources genuinely disagree on direction. The bear case on costs: memory stocks up 200-700% YTD, Micron margins above the 2018 peak that preceded a crash — a classic commodity supply squeeze — and SK Hynix's $26.5B IPO (largest foreign US listing ever, beating Alibaba's $25B) is pouring capital into supply. That scenario delivers 30-50% infrastructure cost declines in 12-18 months. SpaceX's disclosed infrastructure deal shows how sophisticated buyers read it: three-year tenor with 90-day cancellation rights — paying for optionality, not price.

Reconciliation: costs will be volatile in both directions — API stickers rise as subsidies end, infrastructure falls as supply normalizes. The only assumption surviving both scenarios: today's price is not tomorrow's. That makes model portability and short commitments the quarter's highest-leverage architectural decision — not picking the currently-cheapest vendor.

Build on subsidized prices today, but architect for the day the subsidy ends — the winners route to the optimal model at each price point and switch when the music stops.

What to do

  1. Model unit economics for every AI-powered feature at 3x and 5x current API pricing by end of quarter, flagging anything below 20% gross margin

  2. Negotiate enterprise API terms now while vendors compete for committed spend, but cap commitments at 12 months with exit clauses — mirror SpaceX's optionality play

The Benchmarks Lied — Your Eval Suite Is the New Moat

What the Retraction Actually Means

The industry's primary coding benchmark shipped with ~30% broken tasks; nobody noticed until OpenAI audited it and retracted its own recommendation. Every comparison, vendor claim, and PRD citation built on SWE-Bench Pro is now suspect. This isn't one bad benchmark — it's evidence the industry lacks trustworthy evaluation just as frontier labs hit near-monthly release cadences.

Databricks' Pareto analysis sharpens the point: plotting pass rates against mean cost-per-task on a multi-million-line codebase, the highest-scoring models are frequently dominated on the efficiency frontier — Sebastian Raschka's reasoning-setting curves show top configurations burning disproportionate budget without proportional quality gains. The Pi harness's 1.2-2.08x cost savings over native coding tools proves this optimization layer is real and measurable. When engineering says 'we need the top model,' ask: at what cost per task, and does a model 60% cheaper hit our quality bar?


The Reasoning Ceiling Changes Your Sequencing

Second signal: GPT-5.6 saturates traditional benchmarks but falls flat on ARC-AGI-3. Pattern-matching is saturated; novel reasoning has plateaued. Features deferred as 'needs smarter AI' may wait indefinitely — while everything achievable with current models is achievable now. Don't defer; ship and iterate.

The opportunity: in a monthly-release world with untrustworthy public evals, the best domain-specific eval pipeline compounds — faster model-selection decisions and confident switching when economics favor it, because you know exactly how each model performs on your actual user tasks. That converts the pricing chaos into leverage.

Public benchmarks just lost their license to decide your model selection — the team with the best private eval suite adapts fastest in a monthly-release world.

What to do

  1. Stand up a product-specific eval suite this quarter, adopt Pareto cost-per-task charts as the standard model-selection artifact, and strip public benchmark citations from PRDs

  2. Re-review backlog items deferred as 'needs smarter AI' this sprint and ship the ones that are pattern-matching tasks with current models

The bottom line

Rebuild model selection around cost-per-completed-task and private evals this week; make provider portability the acceptance criterion for every new AI feature — switching power is the only asset that survives the coming repricing.