Brett Adcock’s compute bet: what Figure still has to prove

Brett Adcock’s latest argument is straightforward: better robots need more training data and more computing power. Figure’s September 3 agreement with Nscale puts a large infrastructure commitment behind that view. The company describes an initial $3.5 billion compute commitment and up to 100,000 GPUs, with initial deployment targeted for the second half of 2027. Those are future commitments and targets, not installed capacity today. Figure’s announcement

In the same announcement, Adcock connects Helix’s progress to more data and compute. That is the proposition to follow. The size of an agreement tells us something about the resources being sought; it does not measure the intelligence of the robots those resources may eventually train.

The earlier piece was access to the real world

A year earlier, Figure’s Brookfield partnership centered on collecting varied real-world training data and exploring deployment opportunities. Adcock described access to household environments as part of the path toward more general capabilities. September 2025 partnership

Read together, the announcements describe two inputs to the same strategy: varied experience for the model to learn from, and computing capacity to train on it. That is a coherent explanation of what Figure is trying to build. It is not yet a measurement of how efficiently one input turns into a useful new skill.

What the factory evidence can tell us

BMW provides a more concrete place to look. Its June account describes Figure 02 handling sheet-metal parts in production, followed by a planned Figure 03 logistics workflow. Those are defined tasks in a defined setting, which makes them more testable than a general promise about robots in homes. BMW’s account

But success at one task does not answer how much retraining another task needs. For the wider strategy, we would want to see a robot learn a new workflow with less task-specific preparation, retain earlier skills and recover when objects or surroundings change. The relevant improvement is what a customer can use, not simply how much data entered the training process.

The spending clock and the revenue clock

Infrastructure may need to be arranged well before commercial returns arrive. That creates an interval in which commitments become more visible than revenue. The investment case depends partly on what happens during that interval: development progress, customer acceptance and the cost of supplying and supporting the machines.

NVIDIA is explicitly named in the Nscale arrangement, so the connection is documented. That does not mean the entire announced compute commitment becomes NVIDIA revenue at once, nor that an announcement specifies when a supplier recognizes revenue. The underlying services, delivery schedules and contractual details matter.

Brookfield’s earlier involvement is also documented, but that is not a reason to treat every Brookfield-listed entity as an interchangeable proxy for Figure. A stock connection needs the particular entity, exposure and materiality established before it becomes useful to a reader.

What would make the next headline stronger?

A confirmed infrastructure delivery would answer an execution question. A customer reporting dependable operation would answer a deployment question. Evidence that each new task requires less setup would support Adcock’s broader learning argument. These developments could arrive at different times.

For now, the agreement sharpens Figure’s direction of travel. The next step is to follow the conversion from resources into capabilities—and from capabilities into work someone will pay for.