Pricing models

What is usage-based pricing?

Also known as: consumption pricing, metered pricing

Published September 10, 2026 · Reviewed by the Fidiora team

Definition

Usage-based pricing charges according to consumption rather than a fixed licence count. In support software the metered unit varies: conversations, messages, AI actions, or resolutions. The model tracks demand rather than headcount, which lowers cost in quiet periods and raises it during spikes.

Why it matters

Usage pricing has become the default for AI-heavy software because inference has a real marginal cost. For buyers, the trade is predictability for fairness. You stop paying for idle capacity, and you take on forecasting risk instead. Whether that trade is good depends entirely on whether the vendor offers a cap.

What to know

  • The metered unit matters more than the unit price. A cheap price on an easily inflated unit is not a discount.
  • Spikes are the whole risk. Incidents, launches, and seasonal peaks all multiply usage at once.
  • Caps, alerts, and commitment tiers are the tools that make a usage model safe to sign.
  • Usage pricing tends to be cheaper for lean teams with high volume and worse for large teams with low volume.
  • Finance teams generally accept usage pricing when there is a hard ceiling and a clear cost-per-outcome number.

How to calculate it

Monthly cost = billable units consumed x unit price, subject to any cap or commitment

An example

Example: two teams pay the same headline rate. One is metered on messages and one on resolutions. A single chatty customer conversation might be thirty billable messages and one billable resolution. Same price, thirty times the cost.

Common mistakes

  • Focusing on unit price and ignoring how the unit is defined
  • Going live without a spend cap or a usage alert
  • Forecasting on an average month with no spike allowance
  • Assuming usage pricing is always cheaper than a licence
Where Fidiora fits

Fidiora meters on genuine resolutions, which is the unit hardest to inflate, and pairs it with a monthly spend cap. When you approach the cap, Fidiora alerts you or routes everything to your team, so the bill has a ceiling you set.

See Pricing
FAQ

Questions

Is usage-based pricing risky?
It is risky without a cap and reasonably safe with one. The question to ask a vendor is not whether costs can spike but what mechanism stops them. A hard ceiling plus proactive alerts turns a variable bill into a bounded one.
Which usage unit is best for support?
Resolutions, because it is the unit closest to customer value and the hardest to inflate. Messages are the worst, because a verbose model or a chatty customer inflates the count without adding value.
How do I budget for usage-based support software?
Estimate your normal month, add your worst historical spike, set the cap between the two, and track cost per resolved issue monthly. That single ratio tells you whether the model is working.

Related terms

Per-resolution pricing Per-resolution pricing charges only when a customer issue is genuinely resolved. Abandoned chats, timeouts, and conversa... Per-conversation pricing Per-conversation pricing charges a fee for each customer conversation the tool handles, regardless of whether the issue ... Per-seat pricing Per-seat pricing charges a fixed recurring fee for each agent licence, regardless of how many tickets that agent handles... Cost per resolution Cost per resolution is the fully loaded cost of genuinely solving one customer issue, including agent salaries and benef...
Get Started

See Fidiora resolve a ticket in 60 seconds.

No credit card, no sales call required. Connect your docs and watch it work.

Start Free Book a 15-min Demo

No credit card · Live in under an hour