8 Questions Before Paying a Deposit for Compute That Isn’t Built

1. What capacity and rights are being reserved?

The first question is the purchased unit. A GPU count, a cluster reservation, a managed service and a completed workload are different promises. Record the hardware or capability, location, network, storage, software access, support and permitted workload that make the capacity useful. A future quantity without those conditions may be impossible to compare with an available alternative.

CoreWeave’s Form 10-Q for the quarter ended 30 June 2026 describes customer prepayments before service access. It reports a weighted-average prepayment of 15% to 25% of total contract value across active contracts at the stated 2023–2025 year ends. Those are dated company disclosures. They are not a standard quote, a term offered to every buyer, or proof that all prepaid capacity was unbuilt.

The procurement record should preserve that distinction. The article’s method applies when a buyer is asked to commit money before the agreed capacity is accepted. It does not infer a particular provider’s delivery condition from a corporate financing disclosure or a promotional rendering of a data centre.

2. What evidence counts as accepted delivery?

The second question is acceptance. Define the evidence that turns reserved capacity into delivered service: access credentials, available resources, a specified test, or another agreed condition. Decide who observes it and what happens when only part of the promised capacity is usable. A provider’s installation milestone and the customer’s acceptance milestone need not be the same event.

Write an acceptance record that a second operator can apply: promised resource, required condition, observation, evidence, decision and unresolved exception. A synthetic example might distinguish a reserved cluster from the subset actually accessible for the authorised workload. The record should show whether partial delivery starts billing, releases another payment or leaves the milestone unmet under the actual agreement.

Confirm who can accept the service and how a failed test is recorded. A procurement agent can gather evidence without being authorised to waive a missing condition. Preserve that distinction before the supplier’s readiness notice becomes an automatic purchasing-system approval.

3. Which milestone releases each payment?

The third question concerns the deposit itself. Is it a refundable reservation payment, an advance against future usage, an equipment contribution or another contractual amount? The label on an invoice does not answer what the buyer receives or when the supplier earns the payment.

Build a milestone table before reducing the offer to a unit price. Each row needs the amount, due date, triggering evidence, accepting party and consequence if the milestone fails. A later payment might depend on delivery, a test result or the passage of time. Those triggers create different cash exposures.

For a hypothetical 1,000,000 contract, a 20% deposit requires 200,000 now. Calling that amount 20% does not make its cash significance small. Compare it with the buyer’s available funding and other committed payments, using the same legal entity and currency.

A milestone schedule can reduce uncertainty without eliminating supplier risk. Evidence that a building exists does not establish that the buyer’s reserved resources will be available on time. Evidence that hardware has arrived does not establish the operating permissions, connectivity or support needed for the intended job. Tie each payment to the actual promise it is meant to secure.

4. What date starts the service and cash assumptions?

The fourth question is the contractual start date. Preserve the difference between an estimate, a target, a committed date and an acceptance-dependent date. An agent should not convert “expected” into “guaranteed” when moving a quotation into a purchasing system.

For the hypothetical 200,000 deposit, assume service is expected after 90 days and the scenario adds 30 days of delay. The deposit is committed for 120 days. At an assumed 12% annual simple funding rate, the deposit-only financing cost is approximately 7,890.41. This does not estimate a market borrowing rate or include the return the service might have generated.

Run the dates as scenarios rather than averaging them into one reassuring expected start. A short delay, a long delay and no usable delivery answer different funding and operating questions. Probability weights should appear only when there is evidence for them.

5. When can the buyer stop waiting?

The fifth question is the final decision point after delay. Record any long-stop date, cure period, notice requirement and termination mechanism. A right that can be exercised only after a specified notice is different from an automatic cancellation. The person responsible for the deadline needs access to the evidence and authority to act.

Delay can change the customer’s job as well as the cash calendar. A model-training window, contracted delivery or seasonal workload may expire before capacity arrives. Record the latest useful date separately from the supplier’s revised date. A remedy that preserves future access may have little value for work that can no longer be performed profitably.

The service decision and cash-recovery date are separate clocks. In the base illustration they coincide only by explicit assumption. A refund received 30 days after the 120-day decision would extend the modelled deposit holding period to 150 days. Enter that additional wait rather than treating acceptance, termination or a refund request as money returned.

6. What remedy does the actual agreement provide?

The sixth question is the remedy. Does the applicable agreement provide a cash refund, future service, substitution, a termination right or a limited credit? Preserve the exact trigger and covered amount. Do not infer a full refund from the word “prepayment.”

One publicly filed CoreWeave agreement includes specified termination, prepaid-fee refund and substitute-operator provisions. It also defines document precedence. Those negotiated clauses illustrate why the order form and agreement must be read together; they do not extend the same rights to every customer.

7. What supports practical recovery of the money?

The seventh question is practical recovery support. Identify the contracting entity, any guarantor, segregated arrangement, security or other documented protection, and the relevant jurisdiction. The existence and priority of a claim require analysis of the actual arrangement. A spreadsheet cannot establish that the buyer ranks ahead of another creditor.

Separate entitlement from receipt. A documented refund right can still require notice, agreement on the amount and time for payment. A supplier dispute or financial distress can affect collection. The cash model therefore shows the maximum amount committed before the assumed recovery, then a residual amount after it. It does not treat a contractual promise as cash already back in the bank.

When the source is incomplete, keep the field unresolved. A missing refund clause is not proof of no remedy under applicable law, and a marketing assurance is not proof of an enforceable priority. The buying decision needs the specific missing evidence, its owner and the deadline for resolving it before another payment is made.

8. Can the business fund replacement before recovery?

The eighth question is the fallback. If the original supplier misses the useful date, what capacity can complete the same job, under what rights, at what cost and when? An advertised alternative is not a funded replacement until the relevant availability and terms have been checked.

Assume the hypothetical buyer pays 40,000 for replacement service before recovering any of its 200,000 deposit. Peak cash committed becomes 240,000. A later 150,000 cash recovery leaves 90,000 of those combined outflows unrecovered at that point. These amounts do not represent total project profit or loss: the original service may still have delivered value, and the replacement purchase may produce revenue.

The DN Compute-Prepayment Worksheet isolates the quantities needed for this decision. It calculates the deposit, the peak cash committed before recovery, both the no-recovery outflow and the conditional residual after a scenario recovery and the simple funding cost of the deposit holding period. It leaves the replacement service’s performance unmeasured.

Change deposit size, delay, replacement spending and recovery independently. A low deposit with no feasible substitute may be operationally worse than a larger deposit with a well-supported fallback. Conversely, a generous paper refund can be insufficient if the business cannot finance replacement while waiting. The tool is a way to expose these tradeoffs, not turn them into a vendor ranking.

The next procurement action is a decision-ready record: the promised capacity, payment milestones, acceptance test, final useful date, remedy and funded fallback. If one of those remains unknown, name the unresolved assumption before authorising the next commitment. The useful commercial comparison is the cost and cash needed to obtain the required service under the delay scenarios the buyer can bear.

Frequently asked questions

Primary sources

1. CoreWeave Form 10-Q: quarter ended June 30, 2026. Dated take-or-pay/start-date/prepayment disclosures, not a standard customer offer. Reviewed 2026-11-11.
2. CoreWeave filed agreement: Exhibit10.24. One negotiated agreement with specific termination/refund/substitute-operator clauses. Reviewed 2026-11-11.

Related DN research

• The Neocloud Collateral Trade
• The Claim-to-Capacity Gap
• Akash vs io.net vs Render: Finished Compute Cost