What you need to know
Make the assumptions explicit, ask for evidence and test the handover. A buying decision is easier to defend when the trade-offs are written down.
Read the unit before the price
A seat, a token and a successful task measure different things. Ask what is included, what is metered and what happens at the limit. Compare a normal month and an unusually busy one.[1]
Build a full cost picture
Start with licences and usage. Add integration, human review, support and maintenance. Keep one-off build costs separate from recurring commitments so a low entry price does not hide a larger operating cost.[1]
Test the uncomfortable scenario
Model more users, longer agent runs and a team that needs to rebuild part of the application. Ask for a cap, an alert and a named owner of the bill.[1]
Take these questions to procurement
What triggers overage? Can the organisation set a hard budget? Do unused credits expire? Can the vendor change the metering unit during the contract?[1]
Your vendor checklist
- Record the metering unit and the maximum commitment.
- Test access, review and recovery with your own use case.
- Open the export in another environment.
- Get the transition obligations in writing.
- Agree a date to review the evidence again.
More field guides
Sources & assumptions
- App Build Index sample research model, 14 October 2026. Prices and scores illustrate the interface and are not verified vendor offers.
- European Commission · AI Act framework. Reviewed 14 October 2026. Apply the rules to your exact use case with qualified advice.