Multi-Currency Team Budget Planner
Per-seat licences and per-token usage in one monthly budget, with the licence half converted at an exchange rate you supply.
$50.60 per seat per month. That is 1,150 EUR at 1.1000 USD/EUR, dated 2026-07-31.
- Seat licences (25 × 20.00 EUR)
- 500.00 EUR = $550.00
- Requests per month
- 21,000
- Input tokens per month
- 52.50M
- Output tokens per month
- 10.50M
- Usage cost
- $315.00
- Shared platform
- $400.00
- Total per month
- $1,265
- Per seat, per month
- $50.60
- Annual run rate
- $15,180
Two budgets, one sheet
Team AI spend has a fixed half and a variable half, and they fail in opposite directions. Seat licences are predictable and are wasted quietly — the seats nobody uses cost exactly as much as the seats somebody lives in. Usage is unpredictable and is wasted loudly: one automation left running against a long context can outspend the entire licence line in a week. A budget that models only one half will be wrong about the other.
The currency split matters more than it looks. Licences are commonly billed in your local currency while token usage is billed in dollars, which means half your budget moves when the exchange rate moves and half does not. Finance will want the total in one currency; the rate you use to produce it is a decision with a date attached, so this tool records the date next to the answer rather than pretending the conversion is a fact.
What to do with the per-seat number
Use it for comparison against the licence price, not for chargeback. If usage per seat is a fraction of the licence, the licence is the lever and the tokens are noise. If it is a multiple, per-seat pricing is the wrong shape for what your team does and the conversation to have is about caps and cheaper routes for the routine calls. Chargeback needs per-user measurement, which is a logging job, not an averaging one.