An AI budget should separate fixed commitments from usage-linked variable charges and include a distinct line for dependencies that may not appear in the primary resource. The cited guidance identifies data volume, query count, and throughput as cost drivers, but it establishes neither their billing treatment nor any specific fixed fee. Cost behavior—not the name of a driver—must determine the correct budget line.
Fixed, Variable, or Both?
| Budget category | What belongs in it | What the cited guidance supports |
|---|---|---|
| Fixed | A documented baseline, commitment, or other charge that remains due regardless of short-term consumption. | No specific fixed charge is identified. |
| Variable | A charge that rises or falls with consumption, such as usage-billed data processing, query handling, or capacity. | Data volume, query count, and throughput are identified as cost drivers, but no billing units or rates are stated. |
| Dependencies | Supporting resource costs that require separate tracking. | Dependency costs may sit outside the primary resource and create hidden costs. |
Throughput is a workload driver, not itself a price. The guidance does not specify whether meeting a throughput requirement produces a fixed capacity charge, a variable processing charge, or both. Data volume can affect both indexing and processing, which may have different billing bases. The same cost driver may therefore need to be allocated according to how each underlying charge is billed.
How to check the classification
- Identify the billing basis. Record whether each charge remains due regardless of consumption, changes with a defined unit, or combines fixed and variable components.
- Attach workload evidence. Capture the amount of data indexed and processed, the query count, and the required throughput. The cited guidance names these drivers but provides no values, so actual workload records are needed.
- Trace supporting dependencies. Identify the resources required by the workload and where each related charge appears. An unmapped dependency should remain visibly unresolved rather than being assumed to be included in the primary resource.
- Reconcile contract and billing records. Confirm the applicable billing units, rates, commitments, and fixed or variable treatment before incorporating a charge into the budget.
What operators must still confirm
The cited guidance is not sufficient to establish a complete price list. Operators must still verify actual workload measurements, the full dependency inventory, contract terms, billing units, rates, and any baseline or commitment. Until that evidence is available, an estimated amount should remain explicitly unverified rather than being presented as a quoted cost or complete total.