# Why output tokens cost more than input tokens and what that means for feature design

There's a pricing detail most product teams don't look at closely enough.

Input tokens and output tokens are not the same price. Output tokens cost more. Sometimes 2-3x more depending on the model. The reason maps directly to the computational difference between prefill and decode.

Prefill is parallel. The model reads your entire input in one pass. Fast, efficient, the cost is real but bounded. Decode is sequential. The model generates one token at a time, each depending on the last, consuming compute at every step. This sequential process is why output tokens carry a higher price tag. You're paying for the model's time, one token at a time.

![](https://cdn.hashnode.com/uploads/covers/5fd4714295130967e09927bf/634011a9-43ba-401a-b9a1-7c237967a6f2.png align="center")

Most product teams know there's a cost to using AI. Very few have modelled what that cost actually looks like broken down by feature.

* * *

A feature that generates short, precise outputs on long inputs is using the cheap side of the pricing model. A feature that generates long outputs, summaries, drafts, explanations, step-by-step reasoning, is living on the expensive side.

At low usage, the difference is negligible and tolerable. At scale, it contribute to the difference between a feature that's profitable and one that isn't.

A mental model I work with: **output length is often a design choice**. For instance, a summarisation feature needs to produce a summary. However, a lot of AI features generate more output than the user actually needs. You need to ask the question: **how long does this response actually need to be?**

* * *

Three features. Three different output cost profiles.

A classification feature: is this support ticket urgent or not, generates almost no output. A label, maybe a confidence score. The entire cost is on the input side.

A chat assistant generates moderate output per turn. The length is bounded by the conversational context. A well-designed system prompt that discourages unnecessary verbosity, asking the model to be concise, directly reduces cost per interaction at scale.

A long-form writing assistant generates substantial output by design. This is the feature type where output cost dominates. Every word the model writes costs more than every word you fed it. The design question isn't how to make it cheaper, it's whether the output length is proportional to the value being created.

![](https://cdn.hashnode.com/uploads/covers/5fd4714295130967e09927bf/0e840943-57ea-46cf-bbbb-aeec134b1ae5.png align="center")

* * *

What this means for feature design.

**Output length is a product variable, not just an engineering one.** The number of tokens your feature generates per request is something you can influence through prompt design, through output constraints, through how you frame the task to the model.

![](https://cdn.hashnode.com/uploads/covers/5fd4714295130967e09927bf/ec47a08a-1abb-4f04-9420-75764df49da4.png align="center")

Streaming matters more for expensive features. A long-form feature that streams output gives users value immediately and lets them stop generation early if they have what they need. That early stop is a cost saving. Build the UI to enable it.

Model routing becomes strategic. For features that generate long outputs, a smaller, cheaper model that produces good enough quality is worth evaluating seriously. The cost difference between a frontier model and a mid-tier model compounds fast when output tokens are the primary cost driver.

The question to ask in feature planning: **what is the expected output length per request, and what does that cost at the scale we're targeting?**

* * *

The asymmetry between input and output pricing isn't a footnote in the documentation. It's a design constraint that belongs in feature spec, unit economics model, and conversation with the engineering and infra team.

If you're not thinking about output tokens as a variable you can influence, you're leaving cost on the table. And at scale, that cost finds you whether you planned for it or not.