Write to us

AI Solutions · Service

What AI actually costs to run

Cost per token at production volume, and the exception queue nobody prices.

At a glance

Activity AI Solutions
Engagement Scoped mandate
Markets UAE · India · UK · US · Europe
Replies Two working days

What it is

“The model cost is usually the smallest line in the bill.”

A principal, Kaelo AI Solutions

AI business cases are routinely built on demonstration usage and fail at production volume. The model cost is usually the smallest line. What moves the number is the volume of retries, the length of the context you are sending every time, the exceptions that still need a person, and the engineering time to keep it all running. None of those appear in the vendor's pricing page.

What’s included

Four areas of scope
01

Cost per unit of work, not per token

Tokens are the billing unit; the meaningful figure is cost per document, per query or per resolved case — including the retries and the failures that consumed tokens without producing an answer.

02

Context length as the hidden multiplier

Sending a large context on every call is the most common reason a business case is wrong by an order of magnitude. Retrieval quality is a cost decision as much as an accuracy one.

03

The exception queue, priced

Whatever proportion the system cannot handle confidently still needs a person. That is a real, ongoing cost and it belongs in the case from the start.

04

Build against buy, argued honestly

Sometimes an off-the-shelf product is cheaper than the engineering time to maintain a bespoke one. We have no licence revenue riding on the answer.

How the work runs

STEP 01

Volume model

Real expected throughput, including peaks.

STEP 02

Unit cost build

Per unit of work, with retries and context accounted.

STEP 03

Exception rate estimate

From the evaluation, not from optimism.

STEP 04

Total cost of ownership

Including engineering maintenance and model change risk.

When to come to us

  1. 01 You are approving an AI business case built on a pilot's usage pattern.
  2. 02 A live system's costs have grown faster than its usage.
  3. 03 You are choosing between building and buying.

What we do not do

  • Publishing model pricing as though it were stable — it changes, and a page quoting it ages badly.
  • Estimating exception rates before an evaluation exists.

Common questions

Why not just quote current model prices?
Because they change frequently enough that any page quoting them is misleading within months. The structure of the cost — units of work, context length, retries, exceptions — is stable and is what actually decides the case.
Is a smaller model always cheaper?
Per token, yes. Per resolved case, often not: a weaker model that needs three attempts and produces more exceptions can cost more in total and considerably more in review time.
Begin

Send a brief. A principal reads it.

Written, considered replies within two working days.