The Price Tag Is a Lie

Someone on r/artificial posted a complaint last week that read more like a confession. They were using an AI video tool, had a single three-second movement that looked wrong, and spent what sounds like an unreasonable amount of time trying to fix it. Regenerating. Adjusting prompts. Regenerating again. Downloading, previewing, scrapping. Two hours. Maybe more. For three seconds of footage that still wasn't right. The API call cost a few cents. The afternoon cost a person.

That gap is the whole story, and it's maddening that we keep pretending otherwise.

A thread on r/MachineLearning titled "Price is not cost" put it plainly enough to cut through. Published per-token pricing measures one variable in a system with a dozen cost drivers. What you pay OpenAI or Anthropic per million tokens is the invoice. What you actually spend to get a working output in production is the bill. These are different documents. Organizations that built ROI models on the invoice are now opening the bill.

The hidden line items are specific and they compound. Inference latency means your application sits and waits, and in any system with concurrency that wait multiplies. Retry logic — which you absolutely need, because outputs fail validation at rates that would embarrass any other software vendor — means you're calling the API multiple times for what counts as one successful result. Output validation takes compute and engineering time. Then there's the post-processing layer, the human-in-the-loop correction that nobody put in the budget because the whole pitch was that the loop wouldn't need humans. A cost comparison thread on r/OpenAI shows people doing the arithmetic on headline token prices, and the comments are full of practitioners pointing out that the arithmetic doesn't include any of this. The numbers look clean. The deployments don't.

In practice, the gap between published price and actual operational cost runs somewhere between three and ten times, anecdotally, depending on the use case. Video generation sits at the brutal end of that range. Text generation for internal tooling sits at the friendlier end. "Friendlier" still means the CFO who approved a budget based on the API pricing page is now being handed a number that doesn't match.

Someone builds a kit car because the kit price is accessible and the project sounds exciting. Then they discover that insurance on a non-standard vehicle is expensive and complicated, that registration requires inspections the car may not pass, that the garage space costs money year-round, and that every modification to fix one thing creates two new things to fix. The kit was never the cost. The kit was the entry fee. AI API pricing is the kit price. The production deployment is the garage, the insurance, the registration, and the Saturday afternoons you didn't account for — and unlike a kit car, you can't stop working on it when you get tired.

Token price is easy to publish, easy to compare, and easy to put in a press release. Total cost of deployment is messy, application-specific, and would require vendors to make claims they can't fully control. So the industry settled on the easy metric, and buyers settled for it too, because in the early stages of any technology adoption the enthusiasm outpaces the accounting.

The accounting is catching up now.

It is not flattering.

The question that actually haunts me isn't about retry rates or latency SLAs. It's simpler and harder: what human review step sits between the model output and the final deliverable, and what is that person's hourly cost? Because almost every AI deployment I've seen has one. It just isn't in the budget. The pitch was that the loop wouldn't need humans. The loop always needs humans. You find out how many, and how often, somewhere around month three, when the error patterns get specific enough to require judgment the model doesn't have. By then the ROI model is already in a board deck.

If you can answer that question with an actual number before you sign the contract, you're doing real cost accounting. Most teams can't. That's not an indictment — it's genuinely hard to know until you're in it. But it means the ROI model you're presenting is a guess, and the gap between the guess and the bill is where enterprise AI deployments go to stall.

The vendor prediction writes itself: whoever publishes a credible total-cost-of-deployment benchmark first wins the procurement cycles everyone else won't understand losing. But I've been waiting for that benchmark for two years and nobody has shipped it. OpenAI, Anthropic, Google — they all compete on the invoice because the invoice is the number they control. A real benchmark would require them to publish expected retry rates and post-processing overhead for common use cases, which means publishing evidence of failure modes they'd rather buyers discover on their own. The incentive to stay vague is enormous. So they stay vague.

CFOs don't need much justification to slow a rollout. The hidden cost revelation is exactly the kind of concrete, defensible reason to pause without looking anti-innovation. You're not against AI. You're against budget surprises. That's a reasonable position. It's also, increasingly, the position of people who went first and are now explaining to their boards why the numbers don't match.

The person on Reddit spent two hours on three seconds of footage and still didn't get it right. That's not a use case problem or a prompt engineering problem. That's the actual cost structure of the technology, showing up honestly for once. The invoice said cents. The afternoon said otherwise.