← Back to concept explainers

Concept Fable

Usage-based pricing

Conclusion first:Usage-based pricing charges customers according to actual usage, with common billing units including number of requests, tokens, tasks, volume of data processed, storage, autocompletions, or tickets. The marginal cost of AI / Agent products usually varies with model calls, tool calls, and human escalation, so usage-based pricing can bring revenue closer to cost and value. But it requires reliable metering, clear plans, budget caps, overage rules, and customer predictability; otherwise customers worry about runaway bills and vendors struggle to manage gross margin.

Usage-Based Pricing · Business model / pricing

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

After the canal began charging by the number of gate openings, the landowner finally dared to plant another plot

Qingqu Village's water association used to charge an annual fee per household. Whether a household grew only two mu of vegetables or contracted half a rice paddy, they paid the same amount at year-end. When the village was small, everyone thought this was fair.

A few years later, greenhouses, orchards, and large rice paddies appeared in the village. Water usage diverged more and more. Small vegetable farmers found it too expensive, while large field owners feared that water would prevent canal expansion. The annual fee kept light users out and let heavy users take advantage.

Water fees would first be changed to charge by mu. It sounded reasonable, but problems soon appeared. Orchards had few mu but used water precisely; rice paddies had many mu but irrigated in concentrated bursts; some fields had small registered areas but secretly opened the gates for a long time at night.

The guild leader then limited each household to opening the gate at most three times. As a result, everyone rushed to open the gate in the same time slot, water pressure dropped, and those who truly needed to save their seedlings could not get a turn. The limit brought costs somewhat under control, but it also suppressed customer value along with it.

After a drought season, the water utility would discover that what it lacked was not harder restrictions, but bills that changed with actual water use. Light users should enter with a low threshold, heavy users should pay more for using more, and sudden excess usage should have a price signal.

They installed water gauges at every gate, recording gate-opening duration, flow, field plot, season and the overage portion. Bills changed from a flat annual fee to a base fee plus usage fee; large customers could prepurchase water volume, with overages billed separately.

The new method changed the behavior of both sides. Small vegetable farmers dared to try it, orchards were willing to pay for stable water pressure, and large field owners became more cautious during peak periods. The water association could also expand the channel based on real demand, rather than guessing who needed how much through arguments.

The key to usage-based pricing is not to sell every drop of water at a high price, but to let revenue, cost, and customer value grow together with usage. As long as metering is trustworthy and the cost curve is clear, it can move a product from fixed subscriptions toward charging that is closer to consumption and value. Later the water association also encountered new disputes. Some complained that peak-season unit prices were high, and some worried that bills were hard to understand. The chairman made the water gauge records public for each household to check, and wrote the tiers, caps, and prepurchase rules clearly in advance. Usage-based charging without transparent metering only becomes new distrust; when metering is trustworthy, customers are willing to entrust more fields to the canal. Later the water association reviewed peak costs monthly. If usage growth did not bring enough revenue, expanding the canal was out of the question; if prices were too rigid, light users would leave again.

Reveal

This story is about: usage-based pricing

Usage-based pricing charges customers according to actual usage, with common billing units including number of requests, tokens, tasks, volume of data processed, storage, autocompletions, or tickets. The marginal cost of AI / Agent products usually varies with model calls, tool calls, and human escalation, so usage-based pricing can bring revenue closer to cost and value. But it requires reliable metering, clear plans, budget caps, overage rules, and customer predictability; otherwise customers worry about runaway bills and vendors struggle to manage gross margin.

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • Annual fee per household: fixed subscription, unable to reflect usage differences among different customers
  • Charging by acreage: a coarse proxy metric that does not fully match actual consumption
  • Open the gate at most three times: using hard limits to control cost, yet suppressing value expansion
  • Water gauge: usage metering system
  • Base fee plus usage fee: a common usage-based pricing structure
  • Prepaid water volume and overage billed separately: commit, quota and overage
  • Dry-season peak: peak requests and cost fluctuations in AI services
  • Channel expansion decisions: using real usage data to guide capacity and pricing design

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

Consumption pricingtoken costmeteringbillingSaaS pricingoverage

Related distinctions

This concept is easily confused with adjacent concepts; it is recommended to continue to the comparison page.

京ICP备2026014272号