A simple analogy
Inference cost is like an electricity bill that charges per device per hour. The more your AI feature is used, the higher the bill. A popular feature with an inefficient prompt design can be a loss at scale.
What it looks like in practice
A startup prices a document review feature at $10/month per user, then discovers after launch that each user triggers 40,000 tokens per session. At current token rates, the feature costs $12 to deliver for every $10 charged.
When to use it
Model inference cost into every feature design discussion. Map typical input and output sizes, pick the smallest model that meets quality requirements, and size the running cost before pricing the product.
When to avoid it
Never design an AI feature without a cost model. The cost of that omission is usually discovered after launch, when changing the architecture is expensive and the pricing is already set.
What it signals about cost
An ongoing operating cost that scales with usage.