The scenario plays out the same way for a lot of AI startups. You ship something, it gets picked up somewhere, traffic spikes for a week, and then you open your LLM provider dashboard and feel sick. The usage is there. The invoice is real. And your runway just got meaningfully shorter.

This should not be possible. A good week of user engagement should never be a financial threat. But the pay-per-token pricing model that every major LLM provider uses makes it structurally likely for any product with variable user behaviour.

The maths of a bad spike

Suppose your product normally handles 50,000 requests per month at an average of 1,500 tokens per request on a model that costs around $6 per million tokens blended. Your normal monthly bill is around $450.

A viral week brings 200,000 new users. Even if they each only make a handful of requests, you have just added 400,000 to 600,000 extra requests in a few days. At the same token rate, that is an additional $3,600 to $5,400 before the week is out. If those users happen to be more exploratory than your usual audience, with longer sessions and more back-and-forth, the number goes higher.

Now imagine that same scenario at a more mature scale. 500,000 requests per month normally. A spike of 10x for two weeks. You are looking at an additional $45,000 on your invoice. For an early-stage startup with 18 months of runway, that is a serious problem.

The cruelest part of an LLM cost spike is the timing. You find out about it three to four weeks after it happens, when the invoice arrives. By then the spike is over, the traffic has normalised, and you are paying for a problem you can no longer see.

Why the usual fixes are not good enough

The first instinct is usually to add rate limiting. Cap requests per user per day. Throttle new users during a spike. Require account creation before allowing more than a few queries.

These measures work in the sense that they limit your exposure. They also turn your best growth moment into a frustrating first impression. A user who finds your product through a viral post and immediately hits a rate limit is unlikely to come back. You have spent the goodwill of the moment to save a few dollars in API costs.

Spending limits help, but LLM provider dashboards typically update with a lag. By the time you get an alert that you are approaching your budget, you may already be over it. And hard cutoffs mean your product stops working entirely for all users, not just the heavy ones.

The structural problem

The deeper issue is that pay-per-token pricing couples your cost structure directly to user engagement. Every user action has a direct cost. The more engaged your users are, the more you pay. In most software businesses, engagement is good. In an LLM-heavy product on variable pricing, engagement is a risk.

This is backwards. The goal of a product is to drive engagement. Building a cost structure that punishes engagement is a misalignment that compounds over time. As you grow, the variance in your bill grows with you. What was a $500 surprise at 1,000 users becomes a $50,000 surprise at 100,000 users.

What protection actually looks like

Real protection from cost spikes means breaking the coupling between user engagement and your infrastructure cost. That requires one of two things.

The first is building enough internal optimisation that your marginal cost per request is low enough to absorb spikes without material impact. Aggressive caching, tight prompt compression, and smart model routing can reduce your average cost per request by 50 to 70 percent. That does not eliminate variance, but it shrinks the damage from any given spike significantly.

The second is moving to a fixed-cost model at the infrastructure layer. If you pay the same amount for LLM access regardless of how many requests your users make in a given month, a viral week is just a great week. Your costs do not move. Your runway does not shrink. You can focus on converting the new users rather than managing the bill.

This is exactly the problem Griyo solves. We absorb the variance, handle the optimisation, and charge a single fixed monthly fee. Your best week is just your best week.