In this article
A purchase estimate should reference dated quote versions; an old price without its scope is not evidence of the current complete system cost.
Track GPU vendor quote validity in a register containing the document version, date, equipment scope, currency, delivery terms and next review point. Link the working budget to a specific version so an updated price does not silently rewrite earlier assumptions.
For funding GPU purchase and operation, this makes the proposed need reviewable. Participants can see which costs are confirmed and what must be clarified before an order is considered.
Separate estimates and confirmed documents
A public catalogue reference, a written configuration quote and an approved order have different purposes. Preserve the source status without assigning legal meaning solely from its title. Commercial terms are addressed separately from this working-budget method.
FinOps planning and estimating relates projected cost to needs and assumptions. For hardware, retain why the configuration was chosen, what it includes and where each figure came from.
Keep a version comparison
| Field | Initial document | Updated document |
|---|---|---|
| Components | Exact parts and quantities | Changes shown separately |
| Price and currency | As quoted | New source and date |
| Delivery | Included or unresolved | Confirmed scope |
| Power and installation | Separate question | Work boundary stated |
| Validity | Document’s stated period | Next check date |
| Status | Working estimate | Approved next review step |
An empty delivery field is not zero cost. Show uncertainty explicitly rather than presenting the subtotal as a complete ready-to-run system budget.
Compare equivalent configurations
Suppliers may include different SSDs, system memory, networking and support. Align those requirements before comparing price. A different GPU part or chassis should appear as a configuration change, not an unexplained correction to the total.
Check placement, power and installation needs as well. Buying a card does not establish that a compatible operational host exists. Follow the relevant manufacturer’s requirements and the proposed site’s conditions.
Update the forecast with a reason
FinOps forecasting treats estimates as revisable when facts or assumptions change. Record whether a revision follows quote expiry, configuration change, clarified delivery or a delayed start. Preserve the previous budget.
For example, an updated quote might retain the GPU price while adding delivery and a different SSD. The higher total would not demonstrate that the accelerator itself became more expensive. Keep the comparison tied to what actually changed.
Continue with Build a Payment Calendar for a GPU Pilot and Report Unspent GPU Pilot Funding and Commitments.