Skip to content
Salyro
Tool

AI project cost quote builder

Build the running-cost estimate a software house shows its client — features, low/expected/high volumes, reserve and margin — and print it or export it.

What it does

A client asking for an AI feature asks what it will cost to run. This tool builds that answer as a document you can hand over.

  • Features. List the AI features of the project. For each one, choose the model it calls and describe one call: input tokens (and how many of them are read from or written to the provider's cache), output tokens, and how many calls an active user makes a day. Add, duplicate and delete features; the form works fully from the keyboard.
  • Three volumes. Give the number of active users per day in a low, an expected and a high scenario. Every figure in the quote is shown for all three.
  • Your terms. Add a reserve (a buffer for usage you did not foresee) and your margin, as percentages. Choose the currency the client reads; for anything other than US dollars, you type the exchange rate.
  • The document. Beside the form is the quote as the client sees it: the monthly running cost and the total over the project period for each scenario, the provider cost of each feature, the assumptions it rests on, notes on models and prices, the price-list revision, and a disclaimer. Print it, or save it as a PDF from your browser's print dialog — only the document is printed. You can also download it as CSV or Markdown, or copy the Markdown.

Everything runs in your browser. Nothing you enter is sent anywhere, and the files are made on the page.

How it computes

  • One cost engine. Each feature, in each scenario, is one cost scenario — the same model the LLM cost calculator uses — and each call is priced by calculateCost, the function Salyro prices usage with, over Salyro's own price list. The quote adds nothing of its own to the price of a call: a month is the price of one call times the calls in it, exactly, and a total is the sum of those months.
  • A month is 30 days. Monthly calls are calls per user per day × active users per day × 30. The project total is the monthly figure × the number of months.
  • Reserve and margin are kept apart. The provider cost is what the providers charge. The reserve is your percentage of it; the margin is your percentage of the provider cost plus the reserve. Each is its own line in the document, and neither is ever folded into the provider cost.
  • Currency. Prices are in US dollars. Another currency is the dollar amount at the rate you typed, and the document says so beside the rate. There is no live exchange rate.
  • Exact arithmetic. Amounts are exact decimals throughout and rounded only for display; totals are added up before rounding, so a column can differ from the sum of its rounded lines by a cent.

What it does not know

  • A model with no price for part of a call is not priced, never $0. The feature is marked "Not priced" with the reason, and every total is marked partial: it adds up only the features that could be priced. The most common case is cache writes on a model whose price list states no cache-write rate.
  • Retiring models. A deprecated model whose retirement date falls within the project period is flagged, and so is a model the provider only commits to until a date inside it. Where a provider publishes no lifecycle, the document says the model's availability is unknown rather than calling it active.
  • Announced prices. When a provider has announced a price change that takes effect within the project period, the document says so. The quote uses the prices in force on the date shown throughout.
  • It does not estimate your token counts or your volumes — those are yours, and the document labels them as estimates. Your prototype's logs are the best source for them.
  • It prices tokens only: not per-request fees, image or audio pricing a provider bills separately, taxes, discounts, credits or committed-use agreements. It does not price development work, and it does not save quotes anywhere.

FAQ

Is the margin part of the provider cost?

No. The document shows the provider cost, the reserve and the margin on separate lines, and the total to the client under them. The provider cost is the same figure whatever reserve and margin you set.

Why is a feature "Not priced"?

The document gives the reason under the feature. Usually the call uses something the model's price list does not state a rate for — cache writes, for example — or the model is not in the catalogue. A missing price is shown as missing, because $0 would be a claim that the feature is free.

Can I share a quote?

Yes. The link holds the quote, compressed after the #, which your browser never sends to a server. The client and project names are marked sensitive: the share dialog warns while they are filled in and can leave them out.

How do I see what the project really costs once it runs?

Salyro records the cost of every request it routes, per gateway. With one gateway per feature or per client, the dashboard shows what each one actually costs — see attributing cost per feature.

Sources

The document names the price-list and catalogue revisions it was priced from, and each provider's pricing page with the date it was read. Model lifecycle comes from each provider's own model pages, and context windows from the Reference Data listed under the page.

Where the numbers come from

  • Model and pricing data is a snapshot of the catalogue Salyro itself uses, taken when this site was built.
  • Facts about models and providers that are not in that catalogue carry their own source and the date they were checked, and are shown as unknown where no reliable source exists.