IREN’s new compute contract puts the chip bill on the buyer’s clock

IREN has disclosed a five-year compute contract with an unusually large customer funding contribution: prepayments covering 90% of estimated GPU capital expenditure. The November 5 announcement puts estimated annual revenue at about $22 million per megawatt of IT load. The agreement was signed after September 30; the exact date was not disclosed. IREN results announcement

PCT first noted the signed contracts in yesterday’s inventory. Today’s question is what their structure means for a buyer and an operator. Our reading is that an advance this large makes the customer an important source of deployment funding. It can reduce the operator’s initial capital requirement, while making the buyer’s protection against late or inadequate delivery more consequential.

Establish the transaction before valuing it

The evidence supports a company-reported signed service agreement. It does not establish the customer’s identity, allocated megawatts, GPU configuration, location, total contract value or acceptance date. Those omissions prevent a useful comparison with an hourly GPU rental and a calculation of the contract’s aggregate value.

The release’s footnotes define prepayments as amounts contractually payable before service delivery. They do not reconcile the amount due under this particular agreement with cash received. PCT therefore records the payment commitment separately from verified collection. Results announcement, note 7

This is a useful example of why a deal record needs several fields. Signature, payment, equipment delivery and customer acceptance can occur on different dates. An operator can have a valuable contracted sale while still needing to collect funds, complete the installation and demonstrate the promised service. A single label such as “closed” would obscure those steps here.

Put the denominator back into the prepayment

IREN’s accompanying presentation offers a concrete illustration. Per IT-megawatt, its model assumes $40 million of GPU spending and $20 million of data-center spending. A 90% GPU prepayment contributes $36 million. Those are illustrative inputs, not the disclosed cost of the new contract; the company expressly says other inputs can differ from the signed deal. Presentation, pages 9 and 24

The arithmetic leaves $24 million of the modeled $60 million initial investment to fund. In that example, 90% of GPU capex covers 60% of combined GPU and building capex. This calculation excludes any costs outside the model. It is a practical correction to the temptation to treat the headline percentage as the customer funding almost the entire project.

For an operator comparing proposals, the useful spreadsheet should show both the equipment-only funding gap and the complete deployment funding gap. The first helps evaluate hardware financing. The second shows whether a project can reach operation without another capital raise. A generous chip advance can coexist with a substantial construction bill.

Earlier cash changes the relationship

IREN’s illustration amortizes the prepayment over the contract term and warns that actual results may be less favorable. It assumes timely construction and acceptance, and excludes delay credits, service credits and terminations. It is not a forecast for this customer. Presentation assumptions, page 24

The commercial interpretation is straightforward: receiving part of the consideration early can reduce the amount the supplier must finance before service starts. It does not create an extra pool of revenue that should automatically be added to the later contractual charges. A buyer comparing offers needs the complete payment schedule to determine how the advance is credited and whether it changes the all-in price.

The timing also changes the buyer’s exposure. Paying before use means cash is committed before the required output has been demonstrated. The value received in return might include delivery priority, a lower price or stronger remedies, but none of those concessions is established for this agreement. Their presence and enforceability would need to be checked in the contract.

A smaller headline advance could be commercially preferable if it follows verified milestones and gives the buyer better recovery rights. Conversely, a larger advance could make sense where the supplier, schedule and technical specification are dependable. The percentage alone cannot decide between them.

Delivery remains the operating test

IREN’s November 5 quarterly filing says revenue generally begins at customer acceptance, after construction, energization, hardware installation, integration and testing. It also reports that Horizon 1 was delivered to and accepted by Microsoft in August and remains in service. A Microsoft-requested network change affects other Horizon delivery scheduling. Those are separate deployments, not delivery evidence for the unnamed new contract. IREN Form 10-Q, customer delivery and operating factors

The contrast is useful. The Microsoft disclosure names both a customer and a completed acceptance milestone. The new agreement’s public description supplies financing and pricing terms but does not supply equivalent operational evidence. A diligent tracker should preserve that difference without treating the absence of disclosure as evidence of failure.

For a customer planning a training run or inference launch, the contractual acceptance test matters more than a ribbon-cutting date. The specification should cover the usable cluster: networking, storage, software configuration and workload performance as well as accelerator count. A building becoming available and a production job meeting its requirements are different operational milestones.

The buyer’s next negotiation

A procurement team considering a similarly funded deployment should start with three linked schedules. First, specify when each advance becomes due and which observable milestones support payment. Second, define the capacity and performance required for acceptance, including who runs the tests and how disputes are resolved. Third, show how advances reduce subsequent invoices and what happens to any unused balance on termination.

Then test a delay scenario. If hardware arrives but networking fails acceptance, who continues paying construction interest and operating expenses? Can the buyer recover its advance, obtain replacement capacity or defer later payments? These are diligence questions prompted by the structure, not claims about IREN’s undisclosed remedies.

PCT’s assessment is that the agreement provides a meaningful example of customers helping finance the capacity they want to consume. The next evidence worth watching is the disclosed deployment size, cash collection and acceptance milestone. Until those appear, the strongest supported conclusion is a signed contract with substantial advance-funding terms, rather than a measured return on a completed deployment.