Procurement Tools
Compute Procurement Guide
Compare the cost of renting cloud compute, buying hardware, or optimizing equipment you already run. This guide includes a printable RFQ and acceptance form, examples of records to retain at handover, and a checklist for cross-border projects.
01 / BUYER’S GUIDE
Procurement options and costs
Compare total costs for the same workload over the same period. Set the required scale, expected utilization, and business targets, then include the relevant costs of deployment, operation, and exit.
| Option | Costs and considerations |
|---|---|
| Cloud compute rental | Compute, storage, networking, support, migration out, and any remaining charges at exit. |
| Hardware purchase | Equipment, shipping and taxes, data center costs, deployment, spares, and operations. |
| Optimization of existing hardware | Check whether tuning can address the bottleneck. Estimate testing and change costs, the maintenance window needed, and any capacity shortfall that may remain. |
The break-even point varies with workload and duration. Accounting treatment follows the contract and applicable accounting policy.
02 / BUYER’S GUIDE
Delivery and acceptance milestones
The table shows examples of acceptance records. Before ordering, agree in writing on what will be delivered, who does the work, who signs off, and what evidence to retain.
| Milestone | Cloud compute | Hardware | Hardware optimization |
|---|---|---|---|
| Console visibility / receipt / baseline | Match the order to the console records. Verify the tenant, region, configuration, and permissions. | Check the packing list, receipt record, condition photos, and verifiable serial numbers against the agreed BOM. | Keep traceable records of the baseline, environment versions, and sample workload. Note what was in scope and what was left untested. |
| Readiness | Check that the image, storage, and network are usable. Record the access handover and when billing starts. | Within the agreed scope, check rack installation, power-on, component detection, and alerts. Record any deviations at the site. | Approve the changes, maintenance window, rollback conditions, and owners. Record the approved version. |
| Technical acceptance | Run the agreed sample in the target environment. Record inputs, concurrency, the measurement window, and results. | Verify configuration and health against the contract, run the agreed sample, and record sampling and deviations. | For existing hardware, retest under baseline conditions and retain before-and-after measurements and change records. If a trial is agreed for a planned purchase, retain the measurements from the agreed test plan. List departures from test conditions and any unmet criteria. |
| Support / exit | Check data export, access revocation, resource release, and outstanding charges. Record who is responsible. | Confirm when the warranty starts, who handles claims, and what evidence is needed. Before returning anything for repair, confirm the return reference and who pays. | Hand over open issues, owners, and retest plans. Check warranty separately under the applicable contract and manufacturer terms. |
Record each check as pass, fail, pending retest, or not applicable. For failures, name the owner and record the remediation deadline and retest plan. Explain any items marked not applicable.
03 / BUYER’S GUIDE
Printable RFQ and acceptance form
Start with a project summary. The supplier marks each requirement as met, different, pending, or not applicable. Agree on the form version before ordering and record any approved changes.
| Item | Buyer input | Supplier response | Evidence | Sign-off and date |
|---|---|---|---|---|
| Project reference and version | ______ | ______ | ______ | ______ |
| Workload and quantity | ______ | ______ | ______ | ______ |
| Country, city, or cloud region and availability zone | ______ | ______ | ______ | ______ |
| Configuration or bill of materials (BOM) | ______ | ______ | ______ | ______ |
| Required, optional, and excluded items | ______ | ______ | ______ | ______ |
| Rental start or delivery timing requirements | ______ | ______ | ______ | ______ |
| Handover location and applicable trade terms | ______ | ______ | ______ | ______ |
| Acceptance sample, measurement method, and pass criteria | ______ | ______ | ______ | ______ |
| Measured results, deviations, and retest plan | ______ | ______ | ______ | ______ |
| After-sales contacts and responsibilities | ______ | ______ | ______ | ______ |
Use document or record references in the evidence column. Agree in writing on acceptance metrics, sampling, test duration, and retest deadlines.
04 / BUYER’S GUIDE
Cross-border project checklist
Base the checks on the parties actually involved, intended use, data flows, and shipping routes. Record the relevant jurisdictions, review date, version of the applicable rules or terms, owners, and open items.
| Area | Information to gather | Review responsibilities | Prerequisites |
|---|---|---|---|
| Cloud account and use | Proposed account holder, actual users, deployment location, and a summary of intended use. | Both sides confirm roles. The provider checks the region, account eligibility, and terms of use. | Identify the parties and actual use, and complete the provider’s eligibility check before confirming provisioning. |
| Data flows | Data categories, sources, storage locations, who has access, and backup and remote support locations. | The customer’s data owner and legal team check applicable obligations. The provider checks storage and access settings. | Complete the applicable checks before transferring data across borders or importing production data. |
| Hardware and delivery | Configuration summary, destination country, end user, and end use. Follow up with exact item details, the actual route, handover location, and applicable trade terms. | The exporter, supplier, and relevant specialists check item classification, restrictions, required permits, and import arrangements. Assign responsibility for freight, taxes, and handover. | Verify the items and end use and secure any required permits before shipping. Repeat the relevant checks for repair returns. |
| Contract and payment | Proposed contracting entity, payer, consignee, and their roles. List the proposed currency, taxes, and invoicing arrangements. | Commercial, finance, and legal teams on both sides review the terms, consulting the bank or customs broker as needed. | Before signing or ordering, confirm responsibilities, payment terms, taxes, invoicing, and customs clearance in writing. |
Review cross-border requirements again if the deployment location, equipment configuration, or parties change.
INQUIRIES
Project inquiries
Start with the deployment location, workload and target dates.