← Back to Concept Contrast

Concept Contrast Fable

Token cost and usage-based pricing

Conclusion first:One calculates how much each call burns and how much each character costs; the other determines how to charge the customer for it. Treating cost as pricing makes it easy to run at a loss; treating pricing as cost makes it easy to miscalculate project margins. The two are not in the same boat.

One calculates how much each call burns and how much each character costs; the other determines how to charge the customer for it. Treating cost as pricing makes it easy to run at a loss; treating pricing as cost makes it easy to miscalculate project margins. The two are not in the same boat.

Fable

Material costs and quotation sheet

The translation house bought paper from the paper merchant by the character, but charged customers by the whole letter. The house manager oversaw two seemingly similar matters: one was how much capital each character and each sheet of paper consumed, and the other was how a job was ultimately priced to the customer. The new clerk found it troublesome and merged the two ledgers into one, thinking both were related to success or failure anyway.

At first no one objected. The new accountant mixed the two ledgers together, thinking that if paper was expensive, every letter should cost more; when the manager saw fewer pages, he even praised them for saving effort. But when peak season arrived, the old accounts suddenly could not be explained clearly: was it that the previous stall had not finished, or that the latter stall had not held the line? No one could answer.

They first added more seals and slogans and required everyone to write in more detail. As a result, the booklet grew thicker and disputes increased. When something went wrong, everyone could find a sentence to excuse themselves, but no one knew which end to save first.

The old steward called everyone into the courtyard and had them retrace the actual course of events. Whatever concerned the immediate action went into the first book; whatever concerned subsequent responsibility went into the second. The two books referenced each other, but were no longer mixed onto the same page.

Short urgent letters were very profitable, while long idle letters lost money; some customers were willing to pay more for punctuality, while others cared only about cheapness. After separating them, many old conclusions changed: some jobs looked busy but actually did not block trouble; some arrangements seemed unremarkable in ordinary times but preserved the whole in a disaster.

To prevent newcomers from mixing things up again, the old steward had them each handle a small case. Only when the two ledgers could each answer their own questions and also connect with each other at the boundary would the small case pass. If someone still wrote the two matters on one page, they had to return to the scene and look again at who acted first and who was ultimately responsible; when it was unclear, it was better to ask once more than let a muddled account stay overnight; because on the day something truly went wrong, one missing line of distinction would make an extra team work in vain.

The owner looked at them separately: the internal account counted paper, lamp oil and proofreading, while the external account priced by urgency, risk and outcome. Later, when newcomers entered the trade, the old steward had them remember only one line: cost tells you the floor, but price also depends on what the customer is buying.

Token cost

The direct cost calculated from the number of tokens consumed by input and output each time a language model is called. It is an expense item for the service provider and is linear—the more you use, the higher the cost. Token cost defines the floor price of a service.

Usage-based pricing

A pricing model that charges customers based on their actual usage, such as number of calls, volume of documents processed, or number of tokens used. It is a revenue item and can take many forms, such as tiered rates, monthly subscription plus overage charges, or pure usage-based pricing.

Story Mapping

  • Fixed monthly fee contracts meet linearly growing costs: a mismatch between pricing model and cost structure.
  • Cost and pricing are two lines that happen to intersect in the first month: using cost at a single point in time to infer pricing across the full cycle is dangerous.
  • Losing money because the contract didn't specify a usage cap: usage-based pricing isn't the only pricing option, but whichever you choose must cover the worst-case cost.
  • Add a real-time cost monitoring dashboard: record the token cost of each transaction and customer billing at the same time, reconciling cost and revenue one by one.
  • Material costs and menu prices: token cost is expenditure, pricing is revenue—calculate the two lines separately.

In the project

For every AI feature you ship, run three cost simulations: a token cost baseline at current usage, the cost change at triple usage, and the cost spike when customers concentrate on a high-consumption feature. Test these three numbers against your pricing model — can pricing cover the worst-case cost? If not, do you change pricing or add usage limits to the product? Keep at least a twenty percent buffer between cost and pricing, so that usage fluctuations and cost changes from model upgrades don't eat up your profit.

京ICP备2026014272号