Understand the economics of your AI products.
Connect AI and infrastructure costs to customers, workflows, and revenue. Make informed pricing decisions, understand margins, and plan for growth.
● The premise
Know what your AI costs to deliver. Decide how to price, build, and grow.
You cannot price what you cannot cost. Everything below is drawn from one dataset, so the three answers agree with each other.
What does our product cost to deliver?
Across workflows, features, and customers, with every layer metered rather than inferred from the model bill.
How do those costs relate to revenue?
Across accounts, usage patterns, and plans, joined to your own revenue events.
What should we change or invest in next?
Model comparisons, measured outcomes, and spending trends, each with the evidence behind it.
● Cost to deliver
Delivery cost is six layers. Your invoice shows one.
Tokens are the part you can already see, and they are less than half of it. ai-tally meters vector search, tool calls, embeddings, GPU hours, and egress from their own ingest paths, then attributes the total to the workflow that spent it.
| Workflow | Runs | Cost / run | 30-day cost | Share |
|---|---|---|---|---|
| Support copilot | 212,400 | $0.0710 | $15,080 | 43% |
| Doc search | 124,000 | $0.0800 | $9,920 | 28% |
| Report writer | 31 | $139.03 | $4,310 | 12% |
| Onboarding agent | 8,640 | $0.4086 | $3,530 | 10% |
| Internal jobs | 46,200 | $0.0563 | $2,600 | 7% |
| All workflows | 391,271 | $35,440 | 100% |
● Cost and revenue
Margins vary more inside your book than between your plans.
Direct spend lands on an account by hashed account id. Shared layers cannot be attributed that way, so they are allocated pro-rata on direct spend, and the rule is named on screen. You are told which half of each number was measured and which was derived.
| Account | Revenue | Direct | Allocated | Margin |
|---|---|---|---|---|
| Northwind Ltd | $5,400 | $4,132 | $1,988 | −13% |
| Brightline | $17,790 | $3,362 | $1,618 | 72% |
| Kestrel Health | $9,530 | $2,188 | $1,052 | 66% |
| Vantage Group | — | $1,627 | $783 | — |
| 138 other accounts | $124,600 | $12,621 | $6,069 | 85% |
| 142 accounts | $157,320 | $23,930 | $11,510 | 79% |
● Recoverable cost
Some of that delivery cost bought nothing.
The cheapest margin you can gain is the spend that returned nothing. Each detector names where the waste is, says whether its number is spend already incurred or a saving it estimated, and drills through to the runs behind it. Findings are hypotheses with evidence, and two of the five below refuse to put a number on themselves.
● Forecast
Where the month lands, and the day you cross budget.
Planning for growth needs a number before the month is over. A day-of-week-weighted median projection with an 80% confidence cone, held to a 14-day settled-history floor: a volatile number early in the month is worse than no number at all.
● Model choice
Are you on the right model? Decided on your traffic, not a leaderboard.
The last lever is what you build on. Replay is a separate opt-in feature: an admin turns it on for the whole organization, and only then is a sample of request content captured, replayed against candidate providers under a daily budget cap, and scored by a pairwise judge. Ordinary cost telemetry never carries prompts or answers. Win rates carry Wilson 95% intervals, so a tie reads as a tie. What replay stores.
● Setup
What you connect, and what each connection buys you.
A provider key alone gets you the first view. The three after it each need one more connection, and every page says which numbers are still missing until you make it.
- Send your calls Proxy, Python SDK or OpenTelemetry, whichever suits your stack. One call takes about five minutes and fills in cost by workflow, feature and model.
- Connect your cloud bill Compute, vector search and egress come from your cloud bill, through a reference to a role or a secret rather than a pasted key. Skip it and delivery cost is the model bill again.
- Tag calls with a customer Per-account cost needs a hashed customer id on the call. The Python SDK hashes it inside your app; with the proxy or OpenTelemetry you hash it yourself. Untagged calls still count toward totals, and toward no account.
- Upload what customers pay A CSV, one row per customer per month, keyed on the same ids. Until it lands, margin reads as a blank instead of a zero.
Model comparison is a separate decision. It replays a scrubbed sample of your requests against candidate models, an admin turns it on for the whole organization, and it sends that sample to providers you may not have used before. What is captured and how long it is kept is written out in the security docs.
Know your margins before you price.
Send one call and cost by workflow is there in about five minutes. Accounts, margins and forecasts follow the four connections above.
Already have an account? Sign in.