Some companies are burning yearly AI budgets in months, and most can’t see it happening. Here’s the 3-step audit I run. Claude builds the cost sheet from your real receipts, prices every task, and you set caps with the exact clicks below.
In June, the Wall Street Journal reported a KPMG survey where only 26% of companies had full visibility into their AI costs, and KPMG’s global head of AI said some clients burned through annual budgets in months. (Implicator, citing the WSJ)
KPMG’s September AI Pulse of 2,131 leaders found that "only 12 percent consistently assess AI value against cost." (KPMG Global AI Pulse)
The reason is simple. AI billing moved from flat subscriptions to usage, like tokens and credits. Subscriptions behave. Usage doesn’t. This takes about an hour to set up, then a monthly prompt does the work.
Don’t type costs in from memory. You’ll forget the AI add-on buried in your CRM and the trial that started charging in March. Point Claude at where the money already shows up.
01
Connect Gmail
Most people start here. Claude searches your inbox for every receipt and renewal and builds the sheet from real amounts and dates.
02
Add your card statement
Drop in a CSV or PDF. Claude pulls the AI line items and catches anything that never sent a receipt. For API accounts, attach a screenshot of the billing page.
The two columns people skip are the ones that save you. Change catches a creeping cost at +$40, not +$400. Type matters because usage lines are the only ones that can explode.
On a paid plan, have it rerun itself. Describe the task and "the 1st of every month" in a chat, or click Scheduled in the sidebar, then New task. (Scheduled tasks)
A total spend number is useless on its own. You want the cost of the work. What does one blog post, one edited video or one agent run cost you? Without that, you can’t tell the $60 tool that replaces $900 of freelance editing from the $40 one that does nothing.
The 2-Month Rule
If a tool can’t show an output for two months straight, it’s a cancellation candidate. Subscriptions survive on forgetfulness, and the sheet takes that away.
Cap every usage-based account the day you add it. Here’s where.
01
Claude Console (API)
Go to Settings, then Workspaces, pick your workspace and click Spend limits. Under Monthly limit, click Change limit. Under Email notification, click + Add notification for an alert at, say, 80%. (Workspace limits) Then on the Billing page, click Manage auto-reload, then Turn off, so credits don’t quietly top themselves up. (Auto-reload)
02
Claude app usage credits
On Pro, Max or Ultra, go to Settings, then Usage. In the Usage credits section, click Adjust limit to set a monthly cap. This matters on Pro, where Fable runs on credits. (Usage credits)
03
OpenAI API
Open Project settings, then Limits. In Spend, click Edit spend limit, enter a monthly amount and turn on Enforce a hard limit. A spend alert alone only warns you and won’t stop traffic, and even a hard limit can run slightly over. (OpenAI spend limits)
04
The backstop
For any tool that won’t enforce a real cap, pay with a virtual card that has its own spend limit, like Privacy.com in the US or your bank’s virtual cards. If a tool has neither cap nor alert, your monthly audit from Step 1 is the alert.
One Hour, Then It Runs Itself
Build the sheet once, schedule the monthly prompt and set your caps. After that, the audit is a 10-minute read each month.