A month with Vidai¶
The question: "What does running AI spend actually look like, week to week?"
This is a month at Grachtwerk Agency Group, a European creative agency, as its Finance director, Amélie Laurent, lives it. Grachtwerk's client teams (Zuiderhoeve Dairy, Kessler Autohaus, Maison Ardelle, Fjordair and others) and its studio teams call models in Europe, billed in euros, and in the US, billed in dollars. Every screen below is from that organisation.
Day 1: the budgets are already there¶
Amélie set the budgets once; they reset at midnight on the first, in the organisation's time zone (Amsterdam).
- Zuiderhoeve monthly, €50, Notify only: the client's account director hears at 50%, 80% and 100%.
- Data & insights monthly (USD), $495, Stop calls at the limit: the data team's experiments can't run away.
- Media buying: cheaper model past the limit, $40: once reached, the media team's calls go to gpt-4.1-mini instead of stopping.

Week 1: where's it going?¶
Monday morning, the group CEO asks what AI cost last month by client. Amélie opens Money › Cost, chooses Last month, Break down by Team. One list in euros, one in dollars, each ranked, each against the month before. She sends the link: the address keeps the period and the breakdown, so the CEO sees the same page.
Week 2: a budget passes 80%¶
Needs attention on Home says Budget Data & insights monthly (USD) passed 80%. The bell shows it on every page. Amélie opens the budget: it's the RFP assistant, drafting a big pitch due Friday.
The team's admin, Priyanka, asks to lift the budget for the RFP assistant's key; the request waits on Approvals. Amélie approves it for 24 hours. The pitch goes out; the budget acts again the next day.
Week 3: the reroute¶
The media team hits its $40. Their calls don't fail: the route budget sends them to gpt-4.1-mini, and the budget's page says Sending its calls to gpt-4.1-mini now. Calls it decided opens Request logs with exactly those calls.
Week 3: a price correction¶
Mistral sends a corrected contract rate for mistral-small, backdated ten days, into last month. Amélie adds it as a manual price applying from that day. Vidai checks which calls since then would change and offers Recompute now Enterprise.
She starts with a Dry run: the open days would be updated, the locked days of last month corrected by adjustment, side by side, with each budget whose spend this period would move. She applies it. The days already invoiced don't move; the difference shows as Adjustments in this period, each linked to its calls and to the day it belongs to.
Week 4: would a cheaper model have done?¶
Before the next quarter's plan, Amélie runs What-if on the last 30 days of calls to claude-sonnet-4-6. The cheapest model that could have taken them is first in the list, with the percentage and the amount saved. She sends it to the platform team, who start an A/B experiment before switching anyone.
Month end: close and export¶
- Is this period final? says one held price change and a few unpriced calls. She prices the model from the Models without a price list.
- On Billing periods, she locks through the last day of the month, with the reason "October invoiced to clients; corrections from now on are adjustments".
- She exports Cost totals by group for October as CSV, downloads it when it's Ready, and sends the SHA-256 with the file. Client teams are billed list price plus the 15% handling fee set as a markup on Client accounts.

What she never did¶
Export a provider's usage by hand. Match a key to a project. Convert a currency. Ask IT for a report.