Your LLM bill is a time bomb: the tasks you should never send to a frontier model
Talk to founders about their AI bill and you hear the same shape of story. A SaaS founder laid it out cleanly in a r/startups thread:
That is the whole trap in one paragraph. And the reason it’s a time bomb — quiet now, loud later — is that the damage is baked in at the start, when the bill is too small to notice.
First, a quick definition, because the whole point turns on it. A frontier model is one of the biggest, most capable, most expensive general models — the GPT-4-class, Claude Opus, Gemini Ultra tier. It is priced for hard, open-ended thinking. Sending it a job a pocket calculator could do is like couriering a single letter across the country in a chartered jet. It works. You just pay jet prices, every single time.
The tasks that quietly detonate
Here’s the founder’s own list of what teams route through frontier models — worth reading slowly, because you are almost certainly doing several of these:
extracting fields, classifying support tickets, normalizing messy records, matching entities, converting text into JSON, scoring categories, summarizing highly templated notes, and deciding the next workflow step.
Look at what those have in common. Every one is deterministic and repeatable. The same input should give the same output. There’s no fresh judgment required on the ten-thousandth support ticket that wasn’t required on the first. This is exactly the kind of work computers were doing cheaply and reliably for fifty years before anyone said the word “prompt.”
And that’s the danger. These jobs feel like the perfect use of AI early on, because reaching for a model is faster than writing a parser or a classifier. The founder is honest about why it’s tempting: “Prompting an LLM is much faster than designing schemas, writing parsers, building classifiers, maintaining ETL jobs.” Shipping fast is the right call at the MVP stage.
The trouble is that this fast, cheap-feeling shortcut becomes the permanent architecture — and it’s the most expensive one you could have picked for work that never needed a model at all.
Why it detonates later, not now
Three things line up to hide the cost until it’s large:
-
MVP traffic makes the meter look harmless. As one commenter put it, “MVP traffic makes the model cost look harmless, then one power-user workflow starts doing 20 calls where you assumed 2.” At a hundred users a day, a frontier call per ticket is a rounding error. At a hundred thousand, it’s payroll.
-
The same chain runs millions of times. A deterministic task that shouldn’t cost anything past the first run is instead billed on every run, forever. The bill grows in lockstep with your success — the worse-timed cost curve there is.
-
The unit price is going up, not down. People keep waiting for model prices to fall to a sustainable level. On the frontier tier they haven’t. Over in an r/OpenAI discussion, one commenter noted top models still priced at “$30-50/1M tokens” with “enterprise customers in uproar about exploding inference costs.” Betting your margins on a future price cut is not a plan.
You just pay jet prices, every single time.
What to send instead
The fix is not “use less AI.” It’s matching each job to the cheapest thing that does it well. Think of it as a ladder — reach for the lowest rung the task allows:
-
Rung 1 — a plain function. If the task is fully deterministic (parse this format, apply this rule), the cheapest version is code. And you don’t even have to write it: have the model write the function once, then run that function for free forever. This is the single highest lever, and it gets its own writeup here.
-
Rung 2 — a small or local model. For fuzzy-but-narrow jobs like classification, a small model fine-tuned on your data is often as good and a fraction of the price. A founder in the thread: “For classification tasks we switched to a small fine-tuned model running locally and costs dropped ~90%.” The honest catch he also names: “The hard part was convincing the team to invest in that migration when everything was ‘working fine with GPT-4 right now.’” (A small model is not free — the cost moves to hardware and upkeep. We’ll size that trade in a separate piece.)
-
Rung 3 — a cheaper hosted model, routed. When you do want a hosted API but not the top tier, send the easy 80% of calls to a cheaper model and reserve the expensive one for the hard 20%. That’s the caching and routing lever.
-
Rung 4 — the frontier model, on purpose. Keep it for the work that genuinely needs fresh judgment every time: reasoning over a novel document, open-ended conversation, a task no rule captures. Here the price buys something the lower rungs can’t. This is where the model earns it.
The blunt version came from a sales veteran in the same thread who’s turned down companies over this: “if you don’t have a way to work with smaller open models, you don’t have a business.”
Measure per workflow, not per month
You can’t fix what you can’t see, and a single monthly AI figure hides everything. The sharpest advice in the thread was to change the unit you watch:
I’d track unit economics per workflow, not just total AI spend. Like “one generated report costs X” or “one support session costs Y.” Then you can decide what to cache, downgrade to a cheaper model, or turn into a paid feature before usage grows.
That reframe is the whole game. “Our AI bill is $9,000” tells you nothing you can act on. “One support session costs us $0.40 and 90% of it is a classification step” tells you exactly what to move down the ladder — and it tells you before the workflow scales, while the fix is still cheap.
The deeper problem: the meter has no floor
This is the same blind spot behind every cloud bill-shock story, just wearing an AI costume. The platform is built so your bill scales with usage and nothing enforces a sensible floor on what each unit of work should cost. Nobody sends a frontier model to normalize a phone number on purpose. It happens one reasonable shortcut at a time, and the bill only speaks up once the workflow is load-bearing and the numbers are large.
The way out isn’t a dramatic migration. It’s a habit: for every AI call in a hot path, ask whether the task needs judgment or just needs doing. Judgment earns the frontier price. Doing does not — and doing is where almost all the money leaks.
If your AI bill scales straight up with usage, a good chunk of it is probably deterministic work being rented by the call instead of run for pennies — and finding it is part of what I do. It’s just me for now, so I read and reply to every message myself, usually within a day. Send me your AI setup and I’ll flag which workflows are paying frontier prices for work a small model or a plain function should be doing — free, within a business day.