SpendAssureAI spend management guides
For finance, IT and procurement teams who need to explain what the organisation spends on AI, what it will spend and what actually limits it. Each guide links to its primary sources.
Start here
Managing AI spend across providers
Build the inventory, give every cost an owner, separate budgets from the controls behind them and report what finance needs to decide.
Licences, forecasts and renewals
Start here if you answer for the AI budget. These guides follow the money: seats that are paid for but not used, a forecast that holds up against the approved budget, and contract renewals that need a decision before the notice date. Each one separates what the vendor documents from what your own contracts and invoices say.
The figures that matter usually live in three places: invoices, the usage reports in each product’s admin console, and the order forms. The guides show where to find each number, how to compare them and how to record a decision so that the result can be checked on a later invoice.
Unused AI licences: how to find paid seats nobody uses
Paid, assigned and active seats, product by product.
Read the guideHow to forecast AI spend against an approved budget
Seats, usage, commitments, currency and accuracy.
Read the guideAI contract renewals: what to check before the notice date
Notice dates, renewal terms and next-term cost.
Read the guide
API project and workspace controls
Start here when an application’s AI bill belongs to an API organisation, project or workspace. These guides distinguish an approved budget from an alert and an enforced provider setting. They also separate tracking usage from permission to change a limit. Choose the billed product before choosing an endpoint: a vendor’s enterprise seat product can have a completely different administration model.
The practical review begins with a resource identifier, workload owner and saved setting. Confirm which applications actually use that resource. When several teams share it, decide whether a shared control is acceptable or whether the application structure needs to change. The guides include review questions and clearly labelled examples; they are documentation reviews, not instructions tested on your account.
Enterprise member and workspace limits
Use these guides for employee access to ChatGPT Enterprise or Claude Enterprise. The questions are about members, defaults, exceptions and the workspace’s billing model. A setting inherited by every person in a group should not be presented as a pooled departmental budget. A limit increase should retain its owner, reason and review date.
Before comparing two products, confirm what the amount measures and which period applies. The same word can refer to a member allowance, a workspace overage control or a finance allocation. Keep those records separate. These articles explain the currently documented administrative scope and the recurring review process around it, with links to the provider’s own references.
Control evidence, approvals and tool selection
A useful finance review needs more than a total. It should show who authorised spending, what control supports that authority and where evidence is missing or stale. The control-class guide provides a vocabulary for that discussion. The policy template turns responsibilities into an editable record, while the tool guide helps distinguish reporting, request-level decisions and native provider administration.
Choose the smallest useful next step for your team. Build the inventory if ownership is unclear. Adapt the policy if increases arrive without a responsible approver. Compare tool categories if you know the operating problem but not where the control should run. None of these tasks requires adopting SpendAssure, and sample amounts should always be replaced with decisions appropriate to your organisation.
What actually stops AI spending? Four control classes
Classify the control and explain its limits.
Read the guideAI spending policy template with an owner for every limit
An editable record of owners and approvals.
Read the guideLLM cost management tools: where each approach can act
Select the right control and reporting approach.
Read the guide
Start with your own records
Editable templates. No sign-up required.
SpendAssure publishes this library with dated primary sources for provider claims. We distinguish reviewed documentation, illustrative examples and tested behaviour. Sources change, so check your own account before changing a setting. Read how we source our figures or send a correction.