Blog
For engineering leaders
You own a line item that grew 10x faster than anyone budgeted, and every vendor's advice is to spend less with them. Here is how to make the bill legible, then smaller, with the receipts your CFO will actually accept.
An engineering leader's LLM bill has three levers, in order of size: which model serves each class of traffic (up to 9x between tiers on our measured tasks), whether caching and batching are policy or accident (2.6x and 2x measured), and only then the per-token rates everyone negotiates over.
Why the bill is illegible
Rate cards quote per-million-token prices; your traffic arrives as requests. Translating between them requires token counts nobody tracks and per-model verbosity nobody expects: we metered the same prompt at $0.1158 on Claude Opus 5 and $0.0724 on Opus 4.8, identical rate cards, 60% apart. Your invoice aggregates thousands of these surprises into one unexplainable number.
The audit that takes an afternoon
Segment last month's traffic three ways: which model served it, whether the model tier matched the task difficulty, and how much context was resent uncached. In our measured data, the gaps are worth: up to 9x for tier-mismatched routine traffic (Fable 5 at $0.1462 vs Haiku at $0.0162, same working output), 2.6x for uncached agentic context (our published Claude Code session ledger), and 2x for batchable jobs running synchronously. Price your own mix in the cost calculator.
The part that is genuinely hard
Model-to-traffic assignment is not a one-time decision: the ladder repriced twice this month alone (Opus 5 launched, Sonnet 5's intro rate expires August 31). Owning that assignment by hand means re-running the analysis every launch, forever. Pareto makes it a per-request mechanism instead: a blended model that runs several LLMs on every request and synthesizes one answer, billed at cost, benchmarked against Opus 4.8 on seven public benchmarks at 1–45¢ on the dollar per task. The evidence standard is the point: same harness, both sides published, reproducible.
What to do this week
Run the Stack Finder against your actual workload profile (a few quick questions, no account), put $100 of credits against a sampled slice of real traffic, and compare the metered results to your current bill. That is a one-afternoon experiment with a number at the end, which is the only format budget conversations respect.
Questions we get from this seat
How do I explain the LLM bill to finance?
Translate to cost per completed task, not tokens: 'a support summarization costs $0.002, a code generation $0.07, and here is last month's volume of each.' Our measured task table gives you defensible reference points.
What is the fastest saving with no migration?
Batch what can wait (50% off both sides on both major providers) and make caching policy rather than accident (our measured session saved 2.6x). Both are configuration, not replatforming.
How do I evaluate Pareto without risking production?
Shadow a sample: identical prompts to your current model and Pareto, compare outputs and metered bills. $100 in credits covers thousands of comparison requests, and the methodology we use for our own claims is public.