How to Structure Payment Milestones for Reserved B300 GPU Capacity

A procurement team can negotiate a credible delivery commitment, approve the purchase order, and still create the wrong incentive with one sentence in the payment schedule.

The problem usually appears near the end of the contract: a large payment becomes due when equipment ships, arrives at the facility, or is marked delivered.

Those events matter operationally. They do not mean the buyer has usable GPU capacity.

For reserved Supermicro HGX B300 deployments, the payment schedule should distinguish between reserving supply, advancing the deployment, accepting usable capacity, and clearing the final commercial holdback.

Start with the payment event, not the invoice date

A payment milestone needs an objective trigger.

"50% due before delivery" is weak because delivery can mean several different things. A vendor may interpret it as shipment from an integrator. Procurement may mean installed and ready for workloads.

Instead, contracts should describe what has to become true before each invoice is earned.

A useful commercial sequence is:

Reservation payment: money becomes payable once the supplier has created the contractual reservation and completed whatever allocation evidence the agreement requires.

Progress payment: money becomes payable when an agreed deployment milestone has actually occurred.

Acceptance-linked payment: the largest remaining economic exposure becomes payable when the contracted GPU capacity reaches the defined acceptance event.

Holdback: a remaining portion stays unpaid until the agreed post-acceptance obligations are cleared.

This structure does something simple: each payment purchases a different reduction in procurement risk.

Buyers looking for reserved GPU capacity from Pacific should apply the same principle regardless of the precise commercial schedule negotiated.

A deposit should purchase reservation rights

A deposit should not merely prove that the buyer is serious.

It should correspond to something the supplier is committing in return.

For reserved B300 capacity, procurement should be able to point to the contract and answer: What did our deposit secure?

That might include a defined capacity reservation, allocation against an agreed architecture, contractual treatment if the reservation cannot be fulfilled, and a clear boundary around when the next payment becomes due.

The important point is commercial symmetry. The buyer advances capital because the supplier has taken a corresponding obligation.

A deposit that becomes broadly non-refundable before the supplier has made a meaningful reservation commitment transfers too much execution risk to procurement.

Progress payments should mark real reductions in execution risk

There can be legitimate reasons for payments before final acceptance. Hardware, integration, logistics, installation, and facility preparation create real costs.

The mistake is treating every operational event as economically equivalent.

A ship notice proves that something moved. It does not prove that the buyer's contracted Supermicro HGX B300 capacity is usable.

Procurement should therefore choose progress-payment triggers that represent a genuine reduction in the risk that usable capacity will not materialise.

The contract might distinguish between reservation, equipment allocation, deployment progress, installation and final acceptance without making any one intermediate event equivalent to completion.

This is also where procurement and finance should agree on a simple principle: the closer the supplier gets to delivering usable capacity, the more of the contract value it can reasonably earn.

That alignment matters when procuring through Pacific Intelligent Technologies, Inc. or when comparing any supplier offering reserved GPU infrastructure.

Keep meaningful money behind acceptance

The supplier should still have a meaningful financial reason to finish the deployment after hardware arrives.

That means procurement should avoid payment schedules where almost all consideration has already been transferred before the acceptance event.

The exact acceptance criteria belong elsewhere in the commercial package. The payment schedule does not need to recreate the technical test plan.

It only needs to state clearly that a defined payment becomes due after acceptance, rather than after shipment, physical delivery, installation notice, or another proxy.

This separation is important.

Technical teams determine whether the capacity meets the agreed acceptance standard. The commercial schedule determines what happens to the money once that determination is made.

If your team is structuring a reserved B300 procurement and wants to compare the commercial sequence with available capacity, book 30 minutes with Harper.

Use holdback for the last mile

Acceptance and final commercial closure do not always need to happen simultaneously.

A holdback gives procurement leverage for the narrow period between initial acceptance and complete contractual closeout.

It should have a defined purpose and a defined release condition. Otherwise it becomes an arbitrary retention amount that creates disputes rather than reducing risk.

For example, the agreement can make the holdback releasable once specifically identified post-acceptance obligations have been completed or an agreed resolution period has expired without unresolved issues.

The holdback should not become an excuse for procurement to indefinitely retain payment after the supplier has performed.

Its function is narrower: preserve enough economic alignment to close the final gap between "accepted" and "fully complete."

Match the payment schedule to the capacity plan

Reserved capacity is sometimes part of a broader deployment sequence.

A buyer may need bridge capacity while its longer-term GPU capacity comes online. In that situation, procurement should keep the commercial treatment of the bridge and the reserved deployment distinct.

Do not allow temporary capacity, equipment shipment, or another intermediate event to accidentally trigger payment as though the final contracted environment had been accepted.

Each commercial obligation should have its own trigger.

The underlying rule is straightforward: money should move when procurement receives the corresponding piece of contracted value.

FAQ

Should a reserved B300 contract require a deposit?

It can. The more important question is what the deposit purchases. Procurement should connect the deposit to defined reservation obligations rather than treating it as an unconditional payment for future performance. Teams sourcing capacity can review Pacific's reserved GPU capacity offering when structuring that commercial discussion.

Should payment become due when the B300 systems ship?

Shipment can justify an agreed progress payment if both parties choose that structure, but it should not automatically be treated as final delivery. A shipped Supermicro HGX B300 system is different from accepted usable capacity.

What is the difference between acceptance payment and holdback?

Acceptance payment recognises that the main contracted capacity has reached the agreed acceptance event. Holdback preserves a smaller amount of commercial leverage until specified remaining obligations are closed.

Keeping those concepts separate makes the payment schedule easier to administer.

What if procurement needs GPU capacity before the reserved environment is accepted?

Structure the temporary service separately. Pacific's bridge capacity is designed around the period before longer-term capacity becomes available. The bridge should have its own commercial terms rather than changing what counts as payment-worthy delivery for the reserved deployment.

For reserved B300 procurement, the core principle is simple: deposits should purchase reservation commitments, progress payments should correspond to genuine reductions in execution risk, substantial payment should remain behind accepted usable capacity, and holdback should cover a clearly bounded final-closeout period. That keeps the supplier funded as performance advances without forcing procurement to treat a ship notice as the economic equivalent of working GPU capacity.